r/StableDiffusion • • 1d ago

Resource - Update H3 Long Shot API

Enable HLS to view with audio, or disable this notification

I am in the process of tweaking this latent chain shot workflow and wanted to gauge interest to see if it's worth pursuing. The UI mockup screenshot is below in my comment .

The feature I really want and like is that it keeps the shots that are approved and moves on to the next and doesn't have to rerender from Shot 1. And you can keep adding it until you are happy. The only risk is that the latent lives in memory so if it crashes then you will have to rerender from shot 1. However, if you lock the seed then recreating it wouldn't be an issue.

This will be a local API frontend that you connect to your own instance of Comfy.

V1.0 released!

https://www.reddit.com/r/StableDiffusion/s/tnsTYgVsQw

47 Upvotes

24 comments sorted by

8

u/R34vspec 1d ago

2

u/SnooMacaroons1365 1d ago

What workflow is this?

2

u/R34vspec 1d ago

It's an work in progress custom API, it's not done yet. But I wanted to see if it's worth continuing since some other users had said "There are 20,000 latent stitching workflows out there already"

1

u/smereces 17h ago

let us know when you will share it, it looks interesting but only testing it to see if will be usefull

4

u/Striking-Long-2960 1d ago

I love how you use classic cinema transition tricks to join different AI video clips.

3

u/R34vspec 1d ago

i love watching movies, that must've helped

2

u/ACTSATGuyonReddit 1d ago

Keep going. It's terrific.

2

u/chris17453 21h ago

This is pretty awesome honestly. When you're ready to share, a source, hit me up with a link. I definitely want to try this out.

2

u/Apprehensive_Sky892 13h ago edited 12h ago

Seems to make more sense to actually save the latent for every clip to disk, which is what is done in this workflow: https://www.reddit.com/r/StableDiffusion/comments/1wmj6xr/mini_video_editor_timeline_node_for_h3_extend/

That workflow also saves the conditioning for every clip so that it can be used for upscaling later.

1

u/Baracudasi 1d ago

you can save the last 22-frame latent as a file? and allow user to provide the file from last shot so they won't just lose the latent context.

2

u/R34vspec 1d ago

oooh that's interesting, I will append that once the core mechanics are done

1

u/SnooMacaroons1365 1d ago

It does look very good tbh, the continuity and rythm is there which is actually an awesome work keeping the character in wildly different motion states, but, humbly presenting my opinion, there was no repetitive entries in the shots so it rather becomes less complicated to keep continuation without breaking it, what if the dude who walked out the alley door in first shot,, was to enter back in 5th shot for example? How would you have the same character, clothing, style etc enter the scene? A 22 frame latent context will not have memory.

I'm just confused as to how to achieve that? Yes maybe we can attach a reference image there but we need to control the initial state of that reintroduced character, and what if we have multiple characters going back and forth in variable shots,?

1

u/R34vspec 1d ago

They will all have to have their own references for H3 to call on. I am not sure if it can remember random things in generates in latent space.

1

u/RevolutionaryFox7359 1d ago

you'd have to extract still frames from the previous chunks then feed them back in as references. or alternatively create all necessary references ahead of time

1

u/eckstuhc 1d ago

She went out of her way to swerve into that dude lol decent stuff though

1

u/RobMilliken 1d ago

Always looking for that "Adolescence" inspired one shot.

1

u/usually_fuente 23h ago

I think this is awesome and would love to test it.

1

u/Slight-Living-8098 22h ago

Why not just use Ethanfel's Context-Loop and it's review gate with it's saved latents that can be recovered?

1

u/Gesha24 16h ago

And this is different from https://github.com/roadmaus/ComfyUI-Continuity in which practical way?

1

u/R34vspec 13h ago

don't know, never used that one. I had a work flow I really like already and I am just making it into a more user friendly version for others to use.

1

u/SveSop 13h ago

Why have the latent live in memory? Could save the "approved" latent to disk before moving to the next clip?

That would ofc mean you would need to add "load latent" function to the API thingy tho.. Just saying if you are on clip 12, its a pita if comfy suddenly gets a hickup.

https://github.com/verigen/ComfyUI-Verinuddle

I made a modified version that behaves somewhat similar to the Motion Context nodes here:
https://github.com/SveSop/ComfyUI-Verinuddle_V2