VERSION 3 NOTES
First off, this has a custom node I made for predicting flow to help smooth transitions iteration to iteration. Place the whole folder (included in workflow download) in your custom nodes.
Version 3 is an experiment at this point. Could use some more testing and tweaking, but it has some cool features so wanted to share.
Predictive Flow - this is probably the coolest one and is working the best right now. Basically at the end of an iteration, it predicts the beginning of what the next iteration should start like. This gets converted to a latent to get blended in with your subsequent iteration. Should reduce jitters from iteration to iteration
Noise adaptation - if your iterations start losing quality and get noisier, it should dynamically switch to adding more steps and adjusting sampler parameters
Face ID - Not working yet since I'm running into wan compatibility issues, but it's intended to prevent face warping. I'm working on this still.
So from version 2, I added a new T2V feature for it. With this, you can change the workflow to start from a T2V prompt creation instead of an I2V workflow for the first iteration. Then subsequent iterations will go off I2V so you can continue your T2V prompt for however many loops you want.
Heads up that FLF on T2V still references the uploaded image. I'm wanting a future version to reference the first image of the T2V created vod, but I haven't got the conditional logic set up yet.
Notes on credits:
I got the base of it from https://civarchive.com/models/1829052?modelVersionId=2070152
I got most of the florence stuff from https://civarchive.com/models/1687498/wan-2221-i2v-2-workflows-merge-fusionx-lora-2-sampler-florence-caption-last-frame-color-match?modelVersionId=2061133
The stuff around FLF was mainly me messing around so I added that myself and also made some adjustments from the previous two workflows mentioned to what I liked more.
What does it do?
It's basically a for-loop gguf wan2.2 workflow. You can set up however many iterations to go through. There is an option for the last iteration you have to go to a FLF workflow which should help continuity a bit.
Features:
For-loop based I2V gguf workflow
T2V first iteration to I2V gguf workflow
Auto captioning per iteration + customizable after text per iteration
Auto sizing images (to avoid mat errors)
Last For-loop iteration goes to FLF (optional selection)
Upscale + Interpolate
Individual Loras per high and low lora per iteration (power lora so easier selection)
Using ClownsharKSampler
To be added at some point... maybe (once I study up on these more)
VACE integration (wanting to look into Phantom too)
Spline Integration
So far I've been finding good results with linear/euler + beta57, but always looking for better options.
Description
Some clean up from the last, used get/set nodes to stop long stretching node connections
FAQ
Comments (12)
Great job! I've impressive how a small idea could grows to something bigger
Thanks for making the base workflow! 🙏
We should write a custom node that will have scenario and action per iteration, also ollama qwen is much better then florence.
Hmm, I'll have to check ollama. I remember using it in a workflow awhile back, but I haven't really dug into it much. Thanks for the tip. Maybe I'll put it in a future version if I can get around to studying up on it more.
I like your V2 WF, it is nicely organized! I use similar WF, similar complexity like yours but with kijai nodes. Anyway, I'm glad your's statment about unorganised and mess WF's is gone, as your WF are far from it.
If you're looking into VACE and Phantom maybe check out the model and workflow below. Having some great results with it personally.
https://civitai.com/models/1849007/wan-21-vace-phantom-merge?modelVersionId=2092479
Sweet I’ll check it out. I’ve been working on incorporating some VACE options into the workflow next.
This worked great thanks a lot! The workflow looks intimidating but just fill the models, add screenshot, select how many parts, add description and you should be good to go.
Awesome, glad it’s working well for you! The main thing that I’ve ran into errors in the past on workflows has been getting useable heights/widths. The auto resizer should help hopefully with that.
I'm using T2V to start and set a width and height of 480x832. I also set the I2V height to 832px. However when the I2V part of the workflow triggers it sets it's height to 480. Should I set I2V to 480 to fix this?
Ah, I'll check it out. It's possibly the auto resizer doing something funky on it.
Should be fixed in 2.1! root cause: In my conditioning logic, I had the w/h setter get mixed up in one of the conditioning nodes, so it was taking whatever was smaller. When I was testing it, I was using squares to make sure it wasn't taking an I2V path so I didn't catch it.
Thanks for the bug report.