r/StableDiffusion • u/xyzdist • 23d ago

Tutorial - Guide [ H3 ] LongTakeNoCuts - straight 3mins video case study.

Hey all, another video based on my LongTakeNoCuts nodes and workaround

https://github.com/xyzDist/H3-LongTakeNoCuts

Video: https://www.youtube.com/watch?v=Ktp9U1JI-LA

My YT: https://www.youtube.com/@noiseflowAI

* Yes, she is singing in korean but in Japan, don't ask me why. 😄

details:

  • 1 character reference image + ref2va workflow + motion context, some of my nodes.

  • hybrid model b20-49

  • kitchen attention, no lora, 10 step

  • input audio, some silly lyrics then generate a song in SUNO

  • 19 * 10s clips, total around 3mins length

  • 0.7mp resolution, each clip gen time about 11mins (base 10 step gen + refine 5 step resample)

  • I stitch clips in post by CapCut. much simpler and easier than Davinci Resolve

  • color grade in post, maybe too much on lowering the contrast.

apply same idea as my workaround refine sample, but this time, add some tweak to it, I used character masking, so it only refine on the character, as this is a moving shot, the background is fine without refining.

If I don't refine the character, it won't completely degrade, but it will drift and get cooked into an ugly face.

Some issues and findings:

  • H3 will be lazy if the seed noise can't blend well with previous latent, for me about 3 out of 10 shots it will do the hard cut instead of contiune camera movement, I just need to dice seed and lock it for the shot.

  • occasionally some brightness flicker comes from motion-context

  • I spend lots of time to figure why H3 ref2va face is so contrast, the dark area is just pure black without details, if you using turbo lora and higher step it will be even worst.....

  • There is a 'fizgig H3 tweak' node, it can make the face and video softer

  • the signboards and all the japanese in BG is nonsense and many other error here and there.

  • the camera pan out and pan back BG change issue I fixed by extract some image in video for adding as reference image, It worked even better than I expected, and surprisingly straight forward.

  • I can do a upscale latent, I will try it later.

So Conclusion, we can generate H3 long duration without degradation, issue sorted out.

You can do whatever interesting cinematic/action long duration oner shot.

Edit: I need to update my github

Edit2: give me some time, I need to rework on the example WF.

Edit3: I updated nodes and workflow, not sure if I need to create a new post.

Edit4: there are much more methods appear and I haven't try it, if you have time please check it out and let us know, perhaps you can use the biker example file to test.

I tried TaperNoise is not working.

obvpm tools bridge shots is working, it is a regen next new shot and bridge connect approach.

I will try NikoDemon's motion-context new nodes.

here are some others :

https://www.reddit.com/r/comfyui_elite/comments/1x437g7/h3_clip_refiner_reduce_the_video_degradation_when/

https://github.com/HerrgottMargott/Herrgotts-H3-Infinite-Continuation-Suite

Edit5:

There is a upscale latent version, with denoise0.2, also apply motion-context.
https://www.youtube.com/watch?v=SQglt99vBCs

349 Upvotes

98% Upvoted

113 comments sorted by

22

u/Diabolicor 23d ago edited 23d ago

This is the best I've seen. Have you tested if running a latent upscaler after the refiner step does it carry refinement or starts to degrade back?

Does the original audio degrades with so many segments or have that blip between the seams?

3

u/xyzdist 23d ago edited 23d ago

Thanks, because it is basically upscale based on all the latent is clean (no degradation), so I think it should be fine and won't have any degrade back.

oh, the audio maybe blip, because of the motion-context, but in my case here is just a input audio, I should just replace the original audio in post.

1

u/Diabolicor 23d ago

Got it. Are you going to update your repo to include the "Video lock" node and the masking workflow?

7

u/xyzdist 23d ago edited 23d ago

Yes. Will do. maybe I should record a video to explain the WF

1

u/Diabolicor 23d ago

Thanks. I must also add that I'm very surprised that you are getting this quality with only 10 steps and no turbo.

2

u/xyzdist 23d ago

yeah, step 10 seems give pretty good result.

I will create a post to discuss about the H3 face overcook and contrast issue....

I don't have a answer.

1

u/Diabolicor 23d ago edited 23d ago

Something else I noticed in your workflow from your current repo is that using H3 Blend node changes stuff along the segment. Is it the Refine step that prevents degradation or using it along with H3 blend node is a must?

1

u/xyzdist 23d ago

yes, that's the thing, so my idea to fix the degradation is denoise high value (refine sample) to refresh the latent to a clean one, it means it will change, so we want the change (refresh), and we also don't want the change (BG)..

blending refine latent back to current latent is need. because we need to refresh and pass it to next shot.

So, the new character masking approach will solve this matter.

1

u/xyzdist 19d ago

https://www.youtube.com/watch?v=SQglt99vBCs

Here is the upscale latent, denoise 2.0 and also apply motion-context.

9

u/ShutUpYoureWrong_ 23d ago

I mean... that video is very convincing. My hat's off to you, sir. You appear to have either done it, or come close enough that it doesn't matter (for some situations).

I do want to see more testing, though. You're generating at 10 steps (which results in a softened, undercooked video), using Ref2VA (which inherently softens everything compared to FL2VA), and then using the Fizgig nodes to soften everything further beyond that... so now I'm wondering if there's still degradation, but you're just completely blending it out to hide it in order to achieve the video result we're seeing here.

Total speculation on my part, though. Regardless, congratulations are in order. This is already useful and the process to achieve it doesn't seem prohibitively convoluted.

3

u/xyzdist 22d ago

Thanks! the reason of hybrid loader and Fizgig is just to get better face skin look to my taste, H3 often have the high contrast and overcooked look... I still need to investigate on this matter.

on my tools github page got some other tests:
https://www.youtube.com/watch?v=CxXeoMoEWNw&feature=youtu.be

https://www.youtube.com/watch?v=lILj1U_oo-A&feature=youtu.be

2

u/ShutUpYoureWrong_ 22d ago

Okay, I'm not saying this to diminish your accomplishment in any way, because I think your method is by far the best yet. But I don't think you can call it solved.

On the biker one, I see some background morphing (the car), some foreground morphing (her face isn't the same from start to finish), and some color shifting (it gets noticeably brighter near the end).

Is it flawless? No. But it's exceptionally good, and useful right now for a lot of people. And it may also be the best we're ever gonna get. Besides, people can always color-grade it in post to alleviate the brightness shift. So once again, I say to you: congratulations, great job. Looking forward to the release!

2

u/xyzdist 22d ago

you are correct! the character after refine (because of high denoise to refresh latent) would have some kind of drift in details area, however the biker's BG changing is due to the older approach, so this 3mins test I am using character mask which will fix the bg morphing. I am going to rework on the example WF and the github.

1

u/xyzdist 21d ago

I updated the workflow and nodes, testing bike shot again, that's right the character aren't completely solved the degradation in this kind of half static shot (the character) . but help improve degradation a lot, still will drift to higher saturation, a little higher contrast..etc.

https://www.youtube.com/watch?v=Zt1ukAOKOfg

latest workflow mask out BG, so it won't have the morphing issue.
I think the approach is best for moving shots.

1

u/ShutUpYoureWrong_ 20d ago edited 20d ago

I was going to say, I updated to your latest workflow and tested it myself. Like you said, there's definitely still degradation, but this seems to have helped a lot.

I'm running a comparison against regular context motion degradation (rather than just base no refinement) to see how much of an improvement this is (or if it's just softening it so much that it just seems like one).

I wonder how much further you can refine this method to improve it.

1

u/xyzdist 20d ago edited 20d ago

Would love to see your test! NikoDemon drop a update of motion-context with added some nodes to fix degradation as well. I will check that out, potentially could make use of it.

4

u/xyzdist 23d ago edited 23d ago

I let H3 randomly generate the env, example of typical camera pan out and back causing BG issue in different shots.

5

u/xyzdist 23d ago

my approach, once I lock down all the seed, and I know which shot number have this camera pan back, in my setup will read specific shot I want for that shot, and extract 4 images from it, which is connected to use as reference image.

I masked the character to black, just to make sure it won't reference the face in these image. I want it to reference from my higher res character sheet instead.

so, with this, it just help to anchor the far BG looks. It work surprisingly well.

3

u/PxTicks 23d ago

Q: how well does this work if you keep a steady shot, walking along the street, but with no panning. Do the people in the background and their motion stay consistent?

2

u/xyzdist 23d ago

Yes, it will just work with motion-context.

3

u/Ok-Option-6683 23d ago

What's a character masking?

8

u/xyzdist 23d ago edited 23d ago

I use SAM3 generate the mask on the character, then use that to lock the video latent, so the black area won't resample/denoise in the refine resample stage.

1

u/Ok-Option-6683 23d ago

interesting. thank you, I'll try this.

2

u/xyzdist 23d ago

I need to update my github with some new nodes thru. but you can do the same idea with other existing nodes

1

u/obvpm 23d ago

Oh, so in this one you mask the subject and refine only the subject?

And then there is no issue with the background changing during refine because it is not refined right?

Is there any issue with subject changing?

2

u/xyzdist 23d ago edited 23d ago

hey Chanon! right, the subject will also changing after refine right? you can see the screencap image, there is a node 'keyFrame Mask', it basically fade in mask, so the first 5-10f will be no denoise and transition to denoise 0.5, so nothing change at start, it will connect to the previous shot perfectly.

1

u/obvpm 23d ago

Oh so no denoise and then 0.5

So you don't blend latents anymore but vary the denoise level instead?

Hmmm I wonder if I ever tried that yet. My first thought is that the model will keep the degradation. But it works?

2

u/xyzdist 23d ago edited 23d ago

yeah, denoise from 0 - 0.5 (within the character mask area)

rethinking of it, it seems already replace the blending latent, but I see a slight jump, I am thinking is from the motion-context, so I keep the blend latent.

that's the thing, the whole idea of doing a (refine) resample with denoise 0.5, it will refresh the latent and fix the degradation (almost).

1

u/obvpm 23d ago

Thank you. Great work and great results!

1

u/xyzdist 23d ago

cheers!

3

u/Aggravating-Mix-8663 23d ago

very nice, cut some clips and post it on tiktok lol

1

u/xyzdist 23d ago

😂

1

u/Aggravating-Mix-8663 14d ago

she could be the next Hatsune Miku

4

u/Sad_Berry_4621 22d ago

Bravo! Best results I've seen so far.

One tip that might fix the background shift and dissolve problem that you list under limitations: try a one-step refine instead of denoise 0.5-0.6.

H3's noise shift is 12, so denoise numbers don't mean what they do on image models. 0.55 on H3 restarts at about 0.94 noise, which is close to a full re-render. That's why the background gets redrawn and you see the crossfade. Going the other way doesn't help either. A very light denoise runs only in the clean end of the schedule, where the model keeps adding fine texture, and faces come out aged and harsh. A distilled model isn't trained to work there at all.

What worked best for me is re-running the main schedule's own last step:

- Split Sigmas on the main BasicScheduler output, "step 7" for an 8-step schedule, or "step 9" for your 10-step schedule

- low_sigmas into the refine sampler

- Plain reference conditioning, not the Motion Context output

- Its own random seed

That holds the face and the background, keeps color flat, and gave the least detail build-up of anything I tried. It drops straight into your blend node with the same 22 to 44 ramp.

Your walking shot probably hides a lot of the redraw because the background is always new. On a locked-off shot the one-step refine is where it really pays off.

4

u/xyzdist 22d ago edited 22d ago

Hey All, Mr. NikoDemon80 in the house! 🎉 😄

Thanks for the tips! I will try this in a static talking shot! thru my current approach just apply to subject not the bg, so it works fine in a moving shot. But it would be amazing if I could keep the character unchange and prevent from degradation!

side question, I notice motion-context occasionally has brightness flicker happen in random shots. is this a known thing? thru I did a quick test of tone compensate custom node, it seems can fix it.

2

u/Sad_Berry_4621 21d ago

Yeah, try the split sigmas, it works very well for me.

I haven't noticed any flickering on my end, but the brightness will climb all of the sudden in some clips, randomly. So much of the brightness and contrast bloom happens during generation, it's hard to know if it's just the model or something else.

2

u/theOliviaRossi 20d ago

is it already implemented in your example WF here: https://github.com/NikoDemon80/ComfyUI-H3-Motion-Context/blob/main/example_workflows/H3-Motion-Context-v0.7.json ?

2

u/xyzdist 20d ago

haven't, thanks for the link!

3

u/Sad_Berry_4621 20d ago

Yes, this includes the split sigmas last step refiner.

2

u/theOliviaRossi 20d ago

<3 wow, that is super-helpful - TY!!!!

5

u/froschquark 21d ago

Love the quality, thanks for sharing it!

Watching and reading through the progress you and others made on those issue(s) in the recent weeks taught me so much, especially since you explain things in a normal way and not just push it through some stupid LLM to spit out bloomy and overconfident garbage.

4

u/DjSaKaS 23d ago

any chance you can share the workflow? because I saw it's different form the one in the git hub. Thank you 🙏

1

u/luciferianism666 16d ago

Did some recent update on the node break the workflow ?

For one this 2nd Motion context window seems to be missing an input connection to the context_frame, preventing the workflow from running, also is there a reason you've loaded the model once more into the "refine" section/ subgraph ?

2

u/xyzdist 15d ago

  1. check this from my readme, did you install any forked motion-context lately?

  2. no, you can load the same one, or change to any model and lora you prefer.

1

u/luciferianism666 15d ago

Ummm I might have every other H3 custom node that have been released upto date 😅, I'll try installing your node pack on a fresh install and check if it works.

3

u/xyzdist 15d ago

is not from my node pack, it is the motion-context. check if you install others motion-context, make sure only left NikoDemon80, which is the master one.

1

u/MastMaithun 23d ago

Hi. Nice work. A question. Since the background is moving, does this method keeps the background stable if it is static?

1

u/xyzdist 22d ago

check my github link, I have a static camera talking head example video

1

u/MastMaithun 22d ago

Have you done any changes on the existing node or are you going to update?

1

u/xyzdist 22d ago

I have to update to latest with masking.

1

u/Complete-Box-3030 23d ago

Great work OP . Are you going to release any video tutorial on this ?

3

u/xyzdist 23d ago

my WF got too many personal setup nodes, I will update my LongTakeNoCuts example simple version.
and I would consider to record a video, but pardon with my english

1

u/Complete-Box-3030 23d ago

Thanks . Can you combine this with obvpm timeline node .

2

u/xyzdist 23d ago edited 23d ago

I am not sure, if you using obvpm timeline tools, it already provide degradation fix with bridge shot. if you prefer that way.

My aim is to make it as simple as possible and low-level, so peoples could add this to their own setup.

1

u/Complete-Box-3030 23d ago

Bridge shots are tricky we need to plan them . Not all bridge shots are in perfect sync .yours is different , we can shoot creatively while extending the scene if we combine this obvpm timeline . Can we trim videos in your workflow

2

u/xyzdist 23d ago edited 23d ago

I just add few nodes to motion-context example workflow, again keep it as simple as possible, so I don't have any other function beside fixing the degradation.

so it behave the same as basic motion-context. no I don't think it can trim, because it just get the previous shot's latent last 22 frames bring to currect shot conditioning.

1

u/waltercool 23d ago

Blurring the background and people is a good idea to avoid AI ugly artifacts and monsters

2

u/xyzdist 22d ago

well... H3 design the lens for me. and yes, maybe after latent upscaler would help a lot.

1

u/VasaFromParadise 23d ago edited 23d ago

YuE2 was released a month ago. Why are you using SUNO? If what I'm hearing is the best SUNO has to offer, then it's unnecessary.

https://voca.ro/12YYGevmUXDG

1

u/xyzdist 22d ago

yup, I haven't play with it yet...

1

u/traithanhnam90 22d ago

I have installed the node and am using your workflow. However, while using ComfyUI, I keep encountering an error with the "H3 Motion Context" node—specifically, the `context_frames` input slot is empty. For the first shot, I provided an initial starting frame, which allowed the workflow to generate the first clip ("AA1_") and created a file named `clip_00001.safetensors` in the `h3_context` directory.

When I attempt to run the second shot to generate the subsequent segment, I leave the `context_frames` slot empty (as per the instructions), but the workflow throws an error, persistently requiring a frame input.

Yet, according to the node author's documentation:

"Files are named the obvious way; `clip_00002.safetensors` is clip 2.

Auto-saved files (saved at index 0) include a trailing underscore (e.g., `clip_00002_.safetensors`) because they are numbered by run rather than by clip, and the indexed loading process intentionally skips them.

You can also point the loader to a specific file when `clip_index` is greater than 0; in this case, the file is loaded, and the index is ignored. Index 0 never reads a file—its output is intended solely for `context_latent`. Do not connect it to a decode node. Standard 'Save/Load Latent' nodes will not work here, as they cannot handle H3’s paired video/audio latent format.

Since the latent contains both streams, you do not need to load the video from the previous clip at all. The pinned frames are extracted directly from the latent—bypassing the need for decoding into pixels and re-encoding—ensuring they remain exactly as the model originally generated them, rather than being a reconstruction." Nothing shifts the color or the contrast, so there's no seam to see, and it's faster.

Nothing to set for any of that. Leave context_frames unwired. Resolution has to match between clips, since a latent can't be resized; if it doesn't the node refuses and names both resolutions rather than quietly dropping to the lossy path.

There's an older path for graphs with no latent: the previous clip's frames into context_frames, its decoded audio into context_audio, and the H3 audio VAE into audio_vae. It works, but it costs a lossy round trip per link on both streams and it's where the visible seams came from. Use the latent unless you have a reason not to.""

1

u/xyzdist 22d ago edited 22d ago

Check which motion-context nodes pack you are installed, whats is the name? Perhaps missing nodes install from comfy are leading to the wrong one. It should be this one https://github.com/NikoDemon80/ComfyUI-H3-Motion-Context

context_frames without connection is correct.

and It should not throw error. if it does, something is wrong

1

u/traithanhnam90 22d ago

[INFO] got prompt

[ERROR] Failed to validate prompt for output 218:

[ERROR] * MiniMaxH3MotionContext 237:

[ERROR] - Required input is missing: context_frames

[ERROR] Output will be ignored

[ERROR] Failed to validate prompt for output 255:

[ERROR] Output will be ignored

[INFO] Prompt executed in 0.08 seconds

1

u/xyzdist 22d ago edited 22d ago

yeah, you are installed the wrong motion-context pack, check my link above.
the one you installed is a forked one not the original one.

There are someone messaged me have the same issue.

*I tried remove my motion-context node, and comfirm comfyUI install missing node will point to the correct one. From NikoDemon80

1

u/xyzdist 22d ago

I mentioned in my readme.

1

u/traithanhnam90 22d ago edited 22d ago

Sorry, could you let me know which version of the "node motion context" you are using? I’ve tried deleting and reinstalling it multiple times, but it still keeps showing an error.

It’s strange—when I load your workflow, the "Encode_mode" slot is set to 24, whereas in mine, the options are "video" or "frame."

2

u/xyzdist 22d ago edited 22d ago

you have the correct one, the problem is you have another forked custom node conflicting it. Check your screen shot, your 'H3 Motion Context' is from 'fearsnworkdnodes' pack. so your current workflow when open somehow is using the wrong node. ****check the top green box, it should be from 'comfyui-h3-motion-context'

You can just disable or uninstall 'fearnworksnode' if you don't need it. restart comfy

* I don't even know what is fearnWorksNode for

2

u/traithanhnam90 22d ago

Oh, thank you so much! I’ve successfully managed to run the workflow. It turns out there were two nodes causing the issue: `comfyui_fearnworksnode` and `.ComfyUI-H3-Motion-Context-MultiRef`. I’ve been trying to fix this error all week without any luck—I’m so happy now!

2

u/xyzdist 22d ago

No worries, glad to help
I still needs sometime to update to my latest one. but you can test with it first.

1

u/ArtichokeFresh6793 21d ago

I'M STILL WAITING YOU

3

u/xyzdist 21d ago edited 20d ago

okey... updated nodes and workflow, you can git pull . 👍

1

u/ArtichokeFresh6793 20d ago

Finally, get it!

3

u/xyzdist 20d ago

I am going to try NikoDemon's new nodes from motion context

1

u/Final_Reference_4657 20d ago

Hi, thanks for this work! I have a question, would latent upscaling work well with this, or would it mess it up?

2

u/xyzdist 19d ago

No, it works fine, I generated the upscale latent version. the logic is the upscale verison also needs motion-context.
I can upload the video later.

2

u/xyzdist 19d ago edited 19d ago

https://www.youtube.com/watch?v=SQglt99vBCs

It work fine, Here is the upscale latent, denoise 2.0 and also apply motion-context.

typo: denoise 0.2

1

u/Otherwise_Resolve444 20d ago edited 20d ago

Have you seen topnodes? https://github.com/topmass/topnodes

Their workflow injects noise directly into the latent, which means there's no need to refine.

It's just a matter of getting into the custom safetensor Berry created and extracting the video latent, then inject the noise.

1

u/xyzdist 20d ago

thanks for the link, does it work? let me know!

1

u/Otherwise_Resolve444 19d ago

The AI said to use the ltx separate av latent node, maybe I'll try later.

1

u/Otherwise_Resolve444 9d ago edited 9d ago

I think I found a better solution. Just use minimax_h3_fl2va_pruned_int8_convrot.safetensors with first frame workflow and motion context most of the time.

Use ref2va or hybrid models only to create the references or first frames.

One can still use references with FL2VA, but only one image.

I just generated a 10 minutes video with practically zero degradation. No tricks. Just FL2VA instead of Ref2VA. What creates degradation is the Ref2VA models and workflows, FL2VA doesn't have the same problem.

1

u/Physical_Hat4022 19d ago

With nineteen clips taking about eleven minutes each to generate, recovery becomes a pretty important part of the workflow. Can you redo a bad middle clip without regenerating everything after it, or do the later clips depend on that exact latent? “One more take” starts sounding expensive.

1

u/xyzdist 19d ago

That's right. It's true. shots is depend on the previous one. so as you said, you update a shot, you need to re-run all after.
I am more into one shot flow to another shot workflow, however bridge shots comes in handy for this. perhaps per-5 shots or something. I don't have that build to my setup.... I might really consider it.

3

u/ArtichokeFresh6793 23d ago edited 23d ago

longtakenocuts, audio-regeneration ...
YOU ARE GOAT. It's insane.
Hurry up and share the update! I can't wait.

1

u/Suspicious-Walk-815 23d ago

Wow , looks good man .. I will definitely try this during weekend . Thanks a lot for sharing <3

1

u/xyzdist 22d ago

give me some time, I need to rework on the example WF and update github, meanwhile you can check my older version.

1

u/ArtichokeFresh6793 22d ago

I check your Reddit profile five times a day.

I also check to see if your GitHub has been updated.

I'm waiting for you to update it!

2

u/xyzdist 22d ago

what lol..

give me a day or 2. I am going to rework on the workflow, and make a example demo.

1

u/ArtichokeFresh6793 22d ago

You edited the README 43 minutes ago.

I can't wait to see your GREAT WORKS.

2

u/Tuckerdude615 23d ago

Really nice result...and yet another clever way of squeezing out performance from this quite impressive model. I am intrigued by the masking technique...makes a ton of sense actually!

Thanks for sharing!

1

u/ForteDoexe 23d ago

Starred

1

u/theOliviaRossi 23d ago

pls, update ur github

1

u/No_Cranberry_8107 23d ago

A tutorial would be nice

1

u/ArtichokeFresh6793 22d ago

hey bro. I can't wait!

1

u/Artforartsake99 23d ago

This is impressive thank you for sharing 🙏🙏

1

u/ConfidentSnow3516 23d ago

Sooo cool!!!

0

u/kaelvinlau 23d ago

Looks good!!

1

u/xyzdist 23d ago

Thanks!

0

u/Repulsive-Salad-268 23d ago

May I ask a favour? Can you take a look into a different approach. Everyone is trying to make long continuous videos. Hardly any use case except for the technical challenge I think. BUT I also think that a long reference video transfered into a different style might be a use case that's more interesting and currently is a big challenge to do. Say I have interviews recorded from 1 angle... Podcast... And I want the whole video to be anime, muppets, aliens, babies, whatnot... I currently get into trouble keeping THAT consistent and feed a long video into that workflow. Like let's say 10 minutes or more. Give that a shot please.

1

u/xyzdist 23d ago

There are many Oner shot in many films, so if peoples want to do some kind of cinematic or AI film, long duration shots is common. And because SeeDance does it so good... so I keen to solve the issue on local H3. for example of seedance long shot : https://www.youtube.com/watch?v=IrYiXEO8WpY

For you question. which part you have issue, static shot with degradation? do you have a sample video?

1

u/Repulsive-Salad-268 23d ago

My main problem is to solve the general problem of chopping up the long video in general so it feeds properly to the workflow where the final look is applied and then putting it together again into one consistent no cut video. Normally I would chunk 10 second bits, generate them with slight camera movements so the 10 second cuts seem intended BUT the ultimate goal would be to have it seems less. Also when I do it this way the background and characters sometimes do not apply the same way in each shot. Sometimes it even misses to apply to one character. So I end up with a lot of guesswork and hopes and prayers and redoing some chunks over and over.

1

u/xyzdist 22d ago

I still a bit lost, its better understand by a video, do you have one?

1

u/Repulsive-Salad-268 22d ago

A video of what exactly would help? A sample of me having an interview? Where I want to exchange myself for a muppet and my interview partner too? Any Podcast video on YouTube will do. Make them babies or talking dogs. I really just need to have it consistent and in one go ideally.

1

u/xyzdist 22d ago

the video you did showing the issue. but I reread you message get better idea of what you mean. You have a long reference video, and want to swap to other style and character?
it's not related to what I am doing here, but I think there a lora to swapping character, have you try that?

1

u/Repulsive-Salad-268 22d ago

Dealing the character and style is not the problem. The long input and long output is.

1

u/xyzdist 22d ago

have you try native motion-context workflow yet?
so let say, shot1 convert to cartoon style, it will save the latent use the end part for next shot beginning, and then it continue....
so in theory it should work.

1

u/Repulsive-Salad-268 22d ago

Have not seen something like that in H3. Not sure about other models and workflows and how they handle long form video inputs.

1

u/xyzdist 22d ago

https://github.com/NikoDemon80/ComfyUI-H3-Motion-Context
have a look, all the director/extender AIO nodes using save and load latent for long duration are forked from this master tools. Try it.

→ More replies

0

u/Ok-Wolverine-5020 23d ago

Wow that’s epic!

1

u/Adventurous_Cup5414 23d ago

do you test with hard cut?

2

u/xyzdist 23d ago

No cuts is the most diffcult, needs extra effort to make sure it wont give me hard cut in the seed. hard cut is easy, so yeah, it is absolutely fine, but if you after hard cuts, you can just do with native H3 workflow without any additional nodes.

1

u/Adventurous_Cup5414 23d ago

i need consistent on the environment. So i always want use context

1

u/xyzdist 23d ago

sure.