happy to hear that :)

If you use animatediff or svd or something like this and you want to make interpolation it can be hard on the vram because it gets done in one step. with this workflow you can interpolate between frames step by step. so you dont need large vram.

yes, this should be possible. you have to devide the batch. I can tell you the nodes later.

Not planed at the moment. But I keep it in mind.

thats strange. check all the settings. this should be possible.

Thanks! :) I tried the workflow again, and for me it works and goes through all of my frames. Be sure that the max_value of the base incrementor node is bigger then your amount of frames. The double loading of the images is not the best solution, you are right. Maybe I come up with a different solution for this.

​@@neuron_ai Hi Neuron. I re-tried a few more times with other setting and with other datasets: and it seems to work now! I have no idea why it didn't work on my initial testing. But I wanted to let you know your workflow is working well. I'm currently stress-testing it on a huge batch, to see if it would run out of memory eventually. (which in theory it should not)(I will keep you informed!) Is there a way we can load parts of a batch / specific images only, in order to speed up the process? So let's say I have 100k images, the workflow will load ALL 100k images, which takes likes a few minutes, and seems unnecessary process time. Looking forward to hear from you. Many thanks!

@@ARTificialDreams Hey, I am glad it works for you now. Its a tricky workflow, and I had some strange things happening when buidling it. Might be some buggy nodes. You can divide your images in parts by simply adjustinge the seed of the incrementer node to the starting frame -1 and the second one to the starting frame and set the max value to starting frame + amount of frames you want to process. that way you can render everything in parts.

@@neuron_ai Hi Neuron. I tried out a small batch, and went well. I tried a small batch with multiplier 10 and also went well. Alright, the big test: I retried and let it run loading a folder of 190k images, having the first frame starting at 15000. multiplier at 10... ...the animation would go well as intended until frame 120. But then the exported frame 120 is a random frame from my folder. It seems like that the 'Load Image Batch'-node 001 has have some issues loading the right image. Node 'Load Image Batch 002' seems to still be correct loading the next one. I can make a video and upload it, if you want to see the results. Anyway, maybe you know what the issue might be. I suspect that the node itself might have issues handling bigger numbers. Or maybe we can flush the memory inbetween? Alternative I was thinking about, we might get the same results with loading a folder into animate-diff? So far I believe that has limitations as it couldn't handle SDXL in the past, but maybe now it's possible and open opportunities to explore new workflow to solve the issue? Let me know what you think! And would be awesome if you have a solution. Many thanks!!!

@@ARTificialDreams i know theres a ksampler with restarts perhaps a way of "restarting" at current frame before it gets to 120? Thanks for your testing also!