LTX-2 - V2V (extend any video) Can it be changed?
So it works great but its loading in the entire video (heavy) then decoding the entire video (even heavier) so you can only do it like once unless you have a super computer?
cant it take in the last 100 frames and audio, then vaedecode then merge to the previous video (something like this?)
Yes i'll try a more "Wan like" approach where just using last frame(s) as motion frames and generate from that.
The main challenge is audio, to make it consistent to the new video. Probably might work with some last audio frames, as ref audio.
Will try that, to make a workflow you can extend over and over, for an "infinite" video length.
But will be a separate workflow
But the current workflow is not that, its a "Re-Take" feature, that inpaints into the existing video (loaded as a whole), so you can inpaint start middle or end (and pad end). Its something LTX-2 has on their site even. So this might be something a few are looking for. Either to change a part of a video, or change end (and extend end).
But as you say, one drawback is length. Maximum input video is 21 seconds. And additionally a drawback is that it will use a lot of resources (ram)
Or thinking of it, maybe just chunking the loaded input video to be shorter input (with the "inpaint retake workflow") and then merge the videos at end....
Will try make one that is less resource hungry ;-)
yeah i only been chucking in 100 frames or so then i'll probably use like capcut to redo the entire video as the end video is just frames i put in + new rather then the whole 15+15 seconds ect, unless im just not looking at a setting somewhere
Yes, should work fine. Will try make a workflow like that, that doesnt use whole video.
If using the "inpaint/retake" node, it says in the LTX-2 site that the minimum is 73 frames, so 100 frames should be plenty
From LTX documentation => "minimum 73 (around 3 seconds in 24fps), maximum 505 (around 21 seconds in 24fps)"
if its not an inconvenience could you please reduce the get/set node usage for easier readability? unet, clip, vae is fine but other things are hard to keep track of due to the get/set nodes.
if its not an inconvenience could you please reduce the get/set node usage for easier readability? unet, clip, vae is fine but other things are hard to keep track of due to the get/set nodes.
Did that to not be too much stuff on screen or too much spaghetti ;-)
but yes, i could always reduce it a bit
if its not an inconvenience could you please reduce the get/set node usage for easier readability? unet, clip, vae is fine but other things are hard to keep track of due to the get/set nodes.
Did that to not be too much stuff on screen or too much spaghetti ;-)
but yes, i could always reduce it a bit
I totally agree with you, its not that big of an issue it was just a little hard to keep track of wheres what coming from and looking through the whole workflow for that tiny set node xD, i like to kindof tidy things up with reroutes, easier to backtrack. But nonetheless absolutely love your workflows.