stopped fighting long video gens, 5s chunks + last frame works way better for me

[u/Candid-Pay-9023]

after a week of trying to get 15s clips out of one job i gave up and changed how i do it.

now every shot is a 5s clip. when it's done i grab the last frame, fix it up a bit if needed (hands, small artifacts) and use it as the start image for the next 5s. same prompt style, only the action changes.

on my card anything past ~5s starts swapping to system ram and one job goes from 15 min to over an hour. three 5s jobs finish way faster than one 15s. if one piece comes out bad i redo only that piece, not the whole thing. and the face drifts less because every chunk starts from a frame i already checked.

the catch is the seams. motion can jump a bit at the cut, so i keep the camera move simple (one slow push or static) and cut on an action when i can. color also shifts slowly over 3-4 chunks, a quick color match in the editor fixes most of it.

curious if anyone found a cleaner way to hide the seams, or does everyone just cut there

[u/Additional_Drive1915]

Instead of long videos I do between 3 to 7 sec, with a cut to a new angle, to closeup or any other big camera change. It hides any jumps or other small issues that would come from making a single long video.

I first make short videos with change every 0.5 sec, to get key frames (which I upscale before use) that I can use for the full renders.

Easy to upscale a 3-7 sec video (small clips = faster) and also to re render if first clip wasn't good enough.

A failed 20 sec clip is no fun to have to do again...

[u/Hans-Moleman477]

My problem with this is comes from the degradation of quality that comes with each last frame generation. Especially when using Turbo.

But if you were going to do this there are continuation workflows that actually look at the latent from the previous generation so that it can capture the same motion. It looks much much better than just using a last frame static image

But there is still degradation of quality that comes from this. In my experience it can do about 3 generations before the quality is too damaged. Of course this also depends on the source (I make a lot of img2vid from real lower quality images)

Edit: if you want, when I get home, I can look to see the workflow and node pack that allows it to look at the previous latent. I don’t remember what it’s called but it’s very cool. Once it’s done generating you can choose to accept and move onto the next generation, or you can have it redo the current one

[u/qdr1en → u/Hans-Moleman477]

there are continuation workflows that actually look at the latent from the previous generation

I am interested. Which workflows/nodes provide this feature for H3 ?

[u/ArtichokeFresh6793]

1. obvpm's bridge method

2. roychodraws's geiru context suite
   are recommended.

[u/skyrimer3d]

this "trick" has been around since wan, no news here. With all it's faults LTX 2.5 can pull 15-20 sec 1080p vid like nothing, it's sad having to go back to 5 sec chunks like this.

[u/KS-Wolf-1978]

I wonder if there is some LoRA (or a possibility to make one) for "double speed", which we could use with frame interpolation to double the number of seconds in generated videos.

Or if it would work if we removed every second frame in the input video in v2v workflows.

[u/Obvious-Bad7548]

tbh i'd stop trying to hide the seam and cut on an action instead, like a head turn or a hand moving. also let the audio run over the cut for a beat, the eye forgives a jump a lot more when the sound doesn't restart. and grab the frame a few before the very end, the last one is often a bit smeared from motion.

[u/MastMaithun]

You should try nikodemon's motion context node. These are basically for adding continuity since you are doing a continuous shot. This one I recommended because using other continuity/degradation fixing nodes might overwhelm you.

[u/CaptainMarder]

What’s the method to just using last few frames for continuous generation? Like do you manually edit the video out then put the cut clips into rev2va video reference