Could be permissions issue, difficult to say. You can remove ~/flameTimewarpML folder and restart Flame app - it should unpack it again. If it doesn’t help dm me and we can do some step by step checks
2 Likes
Sure! I’m just doing the sleep 10 business you suggested now that I have the engineer free. I’be been known to break things 
so I try to CYA with them in attendance. Then i’ll do the ~/flameTimewarpML removal.
1 Like
YAY! “remove ~/flameTimewarpML folder and restart Flame” did the trick! I’m going to pop in and out of a few different projects and see if it’s working everywhere. Thank you and Zorrofx for all of the help!
3 Likes
I just installed this on Mac, very exciting!
But, how do I call it in Flame, where is it?
1 Like
If you right click on a clip in your Library you should see it at the very bottom of the dialogue box as Timewarp ML.
2 Likes
Killer! Thanks, Cory 
2 Likes
I was wondering if it was possible to have MLTW slow down a clip AND an associated matte at the same time. I tried sending both a matte container and a multi-channel clip, and (unsurprisingly) both came back with no alpha. Would it be possible in a future version to have MLTW use the same slow down data from the RGB, and automatically apply it to the clip’s alpha? That would be very useful for retiming clips that have already been keyed or rotoscoped.
2 Likes
Good point Paul, that’d be definitely useful, I thought about warping one image driven by another for future versions but it’ll be nice to preserve original channel set as well.
Thanks for the hard work. I tested it recently. The result is quite acceptable. Anyway, much, much better than flame’s motion warp. I tried with extreme settings. With more time I’ll try with more common speed settings. I can’t upload tests because of confidentiality agreement (it’s from my current project).
I only have one suggestion/question: Is it possible change the installation path or edit the path of the folder installed into user’ folder? I’m running out of space in my system HD and it gave me some problem.
Possible or not, big thanks again.
Thanks so much for this!
I’ve had both great results with this, vis-a-vis flame’s in-built motion vector time warp. In my brief tests, flames tw did better in situations when there were very large differences between frames. It’s as though the ML version has a narrower “search radius” for finding a matching pattern (although I don’t think that’s how it works in ML). The ML solution did better on “inpainting” the missing areas that are occluded, so the “tearing” artifact on the edges was present but significantly better with the ML.
Time warps are a tough nut to crack, and it’s clearly content dependent. So, I’m grateful to have another tool to throw at a tough problem! “What a time to be alive!” Thaaaaank you!
2 Likes
Hi guys, here is a new version with some new modules in:
- Fluid Morph transitions
- Timewarp from Flame TW Effect (thanks to the code from @julik that reads Flame’s animation channels)
- Duplicate frames interpolation / removal
7 Likes
Dude…Andriy…YOU’RE AMAZING!!! Can’t wait to give it a try!
2 Likes
There’s new Reduce Flow Res button that may improve overal motion detection, worth to try with it and without to see what works best. I see I keep it rathet on most of the time and then if there are not enough details trying to turn it off
Hi Kily, that’s absolutely possible and it is a very good point too, I’m going to add it to the next update
1 Like
That’s what “Reduse flow Size” button should possibly helps with. The thing is that the model is trained by the guys behind the algo and they use so called Vimeo90 dataset wich is basically lots of frames from Vimeo videos resized to 480x260 or smth. They randomly scale that up 2x, 4x, and 6x times during training but I’ve found that flow net does not detect bigger motion on HD+ res. So the workaround they’ve use at the moment to process higher resoultions without retraining is to scale down oflow and it seem to help it to detect motion beter with the trade for some finer moving details
Hey @talosh … I’m trying to get the TW to work but I keep getting an integer error. I put a TW effect on the clip I want to export and set some keyframes. Am I missing something?
Hi Andy, could you please try the same with baked keyframes and send error msg along with the original (non-baked) timewarp setup? There’s a man in a middle at the moment with old Julik’s code old code in Ruby and this new pipeline has not been tested broadly
That did it! Thanks, Andriy. I’ll send the error and setup shortly.
Make sure to send the error message - setup sem to run flawlessly at this end. My testbed is one mac and two linux flames I have access to so it is pretty limited to check everything out there
1 Like
Ok…strange. Now it’s working. Sorry for the false alarm. If it returns I’ll let you know.
1 Like