You know what sucks about generating short videos? That's right, everything. They're unwatchable. VACE is kind of awesome. It's great for bridging the gaps. Pingponging can only get you so far. Not that anyone even bothers to use it, when appropriate.Choose a start frame. Choose an end frame. Hit the button.You can use images for the frames or you can flip the switch and grab the start/end frames of existing videos. There's a Florence auto prompting group that will let you generate a prompt from either of the endpoints, or an interpolated midpoint. The latter will be blurry mess if the images differ by too much but is useful if they're close. You can add prompting about motion and speed in a separate box that is concatenated with the Florence output if you choose to use it, as it obviously won't supply you with that. If you prompt manually, it can all go in the regular box.There are upscaling, interpolation, and face restoration groups.I've written detailed notes for each group explaining how to use it.If a section is important, there is a note somewhere nearby. I promise.Unless you want to mix video and image inputs, you shouldn't have to yank any node connections. The only adjustments you really should have to make, as far as the intended output is concerned, is the weight of the LoRa (model/CLIP weights can be tuned independently) and the VACE strength. Pretty nice, compared to the usual nightmare of permutation purgatory. Oh btw this is insanely fast. Sage Attention helps, (you may want to disable that if you're scared of it) but it's still crazy fast without it as well. Takes me maybe 6 minutes for a nice 61 frame transition @ 704x1280, which comes out really nice with a 14B 480p model. You can halve that and upscale it, but it's not nearly as good. 720 model quality doesn't seem to be worth the extra time. Yet.Still a lot to implement on the automation side but any more boolean switches and it will be too confusing for other people to use it so I'll post it like this. I would like to try an auto 3-6 frame cross dissolve, that will help the color issues that still occur, though not as bad now. And of course there is chaining, which I've seen in other WFs, but they all suck horribly and I never got anywhere with them. We shall see.This workflow is based on the basic Intro to VACE that can be found in comfyui templates.The major models are linked, you can figure out the rest.*Original posted WF had an error in the reActor group that could cause premature halting. I corrected this. I also added a slider to the frame selector so you don't have to do any mental mathematizing. It's set to increment appropriately for this use case. The second image set is always n-2, this is still done automatically underneath.

VACE FLF2V for Looping, Morphing and Whatnot

Base is WAN VACE.  Make it a choice and I'll choose it.  The resource options are awful as well.  Nothing is showing up, even when I get rid of the base selection.  Sorry.

Files with SHA256: 422fab35f7e4b2a8bab0eb099b7582b03aea8f2bb6d8f52a36e54aae5411b3ed