Flame Machine Learning Timewarp, now on Linux and Mac

well, to your point, I didn’t make a Flame TW to compare to. I don’t think it’ll be usable, not at 25% speed.

1 Like

Here is Flame’s TW at 12.5% speed. Slightly less artifacty but still wonky

4 Likes

Did you try reversing the clip before sending it to the ML tool? I wonder if that might give you a better result for the back half of the shot.

4 Likes

No, but that’s a good idea. I’ll give it a try

1 Like

Here’s the TWML8 applied on the previously reversed clip and the result is actually worse. Very weird, but it was a good test to do

Wacky! Thanks for trying it out.

1 Like

I wonder what would happen if you first did a 1/2 speed. And then take the result clip and do another 1/2 speed to get to 1/4 speed. And then take that result and do another 1/2 speed to get to 1/8th speed. Probably will still get some nasty artifacts, but it might be better than jumping straight to 1/8th speed.

1 Like

My guess is that the result will be exactly the same. I might just try it though, just out of curiosity

1 Like

Curious is anyone else is running into the same issue as I am today. Installed 2.0 of this yesterday, figured out it did not like being pointed to our server so I rendered locally. Getting some really promising test results and decided to call it a night. Rebooted at the end of the night as I always do. Came back this morning to try out some truck footage this might be perfect for and now it refuses to run. The dialogue box pops up, set it for 1/2, click the CPU button and point it to a local folder. When I hit the make it go button the window that shows it’s exporting the source runs, then the shell opens and then closes immediately without running anything. Tried going back to the clips I ran yesterday and I’m getting the same error. Wanted to see if this was happening to anyone else, or if you’ve run into it and have figured out what was happening that was making things angry. I’ve attached a screen grab of the shell if it helps. I greeked out project and file names just in case.

1 Like

It should be the same it is exactly the way it works to achieve 1/4 etc

1 Like

I found that it refused to output to a file path that had a space in it, so it’s picky about that sort of thing

2 Likes

What if you just copy the command before it says python3 and instead of the rest put, say, sleep 10 so the ending looks like OP_NUM_THREADS=1; sleep 10 and paste it in terminal and run? If everything is cool it should give the console for 10 sec and then go. And if you could please check that /home/flame01/flameTimewarpML/bundle/locks folder exists

2 Likes

Ok, i’ll double check that.

Just made a new folder and checked to make sure that I had no spaces and it’s still puking.

1 Like

looking into this now

Thanks!

1 Like

No spaces and no special characters?

1 Like

I have underscores, are those not legal either? (Tough Habit to Break plays softly in the background)

1 Like

Underscores and dashes are totally legit, no ampersands or punctuation

2 Likes

Underscores are all I have. Just checked to make sure there were no spaces before or after one of them and it’s still unhappy. Also shorted the file name to “Test” to be extra sure.

1 Like