Recording docker won't render full timelapse?

Support and Advice General Questions
, , ,
1

Hello! So last night I spent around eight hours on a painting, and I had the recording docker running the entire time. I know it worked, because I have each individual frame saved in the folder, but Krita will not export it properly. The export window opens, and all my settings are exactly the same as they were the last time I (successfuly) exported a timelapse, and it loads to 100% and gives me the option to watch the timelapse, but the timelapse video itself cuts off around midway through. It won’t render all the frames.

I’ve already looked through the folder, and there aren’t any missing pictures or number jumps - everything is numbered in order with no gaps. A few details that might be contributing:

  • the painting ended up being well over 10k frames. Is there a size limit for recordings? In the export window it says it will render all 10162 frames, but the video only renders to frame 9980.
  • I changed the canvas size midway through, and I’ve seen a few other posts talking about how that causes issues. But the main issue I’m seeing people talk about is that it stretches the final render a bit, and that’s happening too but I don’t mind it. But could that be causing the unfinished render as well?
  • Krita crashed midway through the painting, but I had just saved, so I didn’t lose any progress (thank god LMAO). I turned the recorder back on when I reopened Krita, and it worked normally for the rest of the painting. I would just think this is the reason the render won’t work, except the timelapse renders WELL past that point, at least 3,000 extra frames past it.

On top of this, I can’t transfer the timelapse video to my phone. I prefer editing reels in the Instagram app so I usually transfer my speedpaints to my phone to do so, but it doesn’t work. It plays on my computer - it just cuts off too early - but my phone won’t play it at all.

Like I said, I’ve used the recorder a few times and I’ve never had this issue. I haven’t changed any settings. Is there any way to get the entire timelapse to render? Or should I just mark this one a lost cause and move on? What can I do to prevent this in the future? Thanks in advance :smile:

2

If nothing works but all the frames exists you can load them into an application like kdenlive as Image sequence and render the clip from there. Your artwork doesn’t become a speedpaintig when it wasn’t painted as such in the first place, though.

2 Likes
3

A lot of people seem to make that mistake and I’m sure they’ll keep on making it.
Maybe you need to make a topic called ‘Timelapse vs Speedpaint’ so you can simply link to it each time this happens :slight_smile:

1 Like
4

Hehe, maybe even make it a wiki page. But in this case it was meant more as a joke because they used the term time lapse correctly through the whole post except for that one time. I’m pretty sure they know the difference pretty well.

5

Hello @vincentfrankenstein2 and welcome to the forum :slight_smile:

Here goes with the questions:

Which version of krita are you using and where did you get it from?

Which version of Windows are you using?

Which version of ffmpeg are you using and where did you get it from (if it’s not the internal krita version)?

Was there any kind of error or status message that was ‘not normal’?

What is the initial and then changed size of the canvas?

Have you ever made a timelapse recording video of about 10,000 frames before with no problems?

Have you ever made a recording of greater than 9980 frames before?

Does the endpoint of the video correspond to where you changed the canvas size?

Apparently not but do have a closer look and confirm that.

That is krita saying it will tell ffmpeg to render all the frames in the document recording folder.

That is ffmpeg not doing them all for some reason.

It sounds like you can transfer it but not play it.
That may be an indication that the rendered video has some kind of problem but I don’t know about that area at all.

I’m heading for that conclusion.
Somebody with more knowledge and experience of ffmpeg may be able to see what has been happening here and give further advice.

It depends what caused this problem.
Thinks: Changing canvas size, maybe too many frames.
It’s not something I get involved with or have experience of really.

The suggestion to use an external application by @Takiro is a good one and Kdenlive (and other video creation/editing applications) can do that easily with a very large number of frames.

1 Like
6

iiiiii actually wasn’t aware there was a difference til you pointed it out! The more you know I guess haha. But yeah, I meant timelapse throughout. I’m looking into kdenlive right now, and I think that’s gonna be my solution for now. Thank you!

7
  • I’m using 5.2.0, and I got it from the krita website. It’s the same version I’ve done my previous timelapses on.
  • Windows 10.
  • I downloaded ffmpeg from the ffmpeg website, and I believe I’m running 6.1.
  • No, no error messages at all. The only thing that was different from the last few timelapses I’ve done was that the export took way longer, but my last timelapse was barely over 1k frames, and this is over 10k, so a longer export time seems logical.
  • The canvas was originally 2400 x 2400, I cropped it to 1800 x 2400, and no the endpoint didn’t correspond to when I cropped the canvas.
  • I’ve never made a timelapse this large before, so I’m thinking it is probably just the size.

I don’t know enough about ffmpeg to troubleshoot it if it is a problem with that, so for this painting I’m just gonna use kdenlive and play around with krita’s timelapse feature a bit more to figure out the limits.

2 Likes
8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.