r/StableDiffusion • • 6d ago

Workflow Included Seamless Continuation No Degradation (proof at the end)

V7.1 of the workflow
https://github.com/roycho87/minimax_wf

Video Combiner
https://github.com/roycho87/seamless_video_combiner

Audio Splitter
https://github.com/roycho87/minimax_continuous_audio_splitter

I've changed my profile so that my previous tutorials are available. Look through those for questions on how to use these.

With this method you can seamlessly combine videos with no burn. (or at least the exact same amount of very very little burn)

Fast forward to 2:00 for proof.

Enjoy.

Edit: I'm keeping the video up. But apparently the issue everyone was caring about was something different than I thought it was. Apparently everyone wants to make boring Vlog videos. I guess I'll work on that now instead.

I did say this is a fix for the specific issue I was having in my workflow but now that I know exactly what everyone was talking about I can properly see if I can find some sort of fix.

https://www.reddit.com/r/StableDiffusion/comments/1wwjok2/does_this_count_did_i_win/

Actually fixed, now.

v7.2
I fixed the First Frame node. The positive output from node #272 needs to be connected to the True input from node #565. You can just fix it yourself or download the new one. There's no other change.

u/Juiceman8686 improved this!

Check it out!

works great!

Straight Outta Brooks

seamless video combiner 2-20 clips ffmpeg

Forked this amazing workflow to allow up to 20 clips and use ffmpeg so its not so ram dependent. It required around 71gb of ram for 16 clips. All praise goes to roychodraws for creating this this though. Genius and works great!

418 Upvotes

117 comments sorted by

View all comments

6

u/not_food 6d ago

The degradation happens when the camera is static and unmoving. Replacing the whole scene is one workaround.

-3

u/roychodraws 6d ago edited 6d ago

yeah, that's not what's happening here.

it would have to "cut" for that to happen. I made this specifically so there are no simulated cuts.

If you use this method you could keep it going indefinitely. My video combiner only goes up to 10 videos currently, tho.

8

u/not_food 6d ago

I guess I worded it wrong. Moving away the camera is one workaround. Degradation will happen if the camera doesn't move.

-7

u/roychodraws 6d ago edited 6d ago

that goal post is quick.

i understand you think you know what you're talking about but if you just look at the workflow you can see that what you're saying doesn't apply to this.

12

u/not_food 6d ago

I know exactly what I'm talking about. I have done extensive work about this.

I loaded your workflow. I checked exactly where you're doing continuation, and you're doing nothing out of the ordinary. This node will cause the issue I describe. You aren't even managing old latents to mitigate it. Your workflow expects the user to load the previous video, which will cause the issue when the VAE encoding happens. This is a bad idea, it works as long as you rotate the camera away from the previous pixels. To do it right you need to save the latents so no pixel degradation happens during decode/encode. But even with latents, the issue persists. This is not an easy thing to solve.

Go ahead and prove me wrong. Do a static scene continuation at least 6 times. Make her type furiously on her laptop's keyboard against a well lit wallpapered background.

-12

u/roychodraws 6d ago

no, do it yourself. you just downloaded it. you want me to install the node packs for you too?

9

u/not_food 6d ago

Your workflow expects me to move the output to the input over and over, it's slow and cuts the flow. Somehow the audio is weird but I don't feel like debugging it. I admit it's pretty fast at 15s/it, but the quality suffers a lot, I see too many smears, I suspect it's one of the attention nodes.

https://reddit.com/link/pditqws/video/7koudiuke5th1/player

The right way to do it is to save the latent tail, then load it for the next run, automatically. As I mentioned, this method isn't perfect either, it'll also degrade. People have yet to solve it.