I compared a mac flame that works correctly and a mac flame that does not work.
The name, clip and path are the same.
Shot name is A. The path is Desktop(Users).
Here are the logs for a correctly working mac ↓
initializing Timewarp ML...
Trained model loaded: /Users/work01/Documents/flameTimewarpML/bundle/trained_models/default/v2.4.model
---
Free RAM: 92.5 Gb available
Image size: 1920 x 1080
Peak memory usage estimation: 4.1 Gb per CPU thread
Using 18 CPU worker threads (of 20 available)
rendering 9 frames to /Users/work01/Desktop/ML/A_TWML4_2021JUN05_0148_B97/
56%|███████████████████████▎ | 5/9 [00:13<00:10, 2.73s/frame]
Hi Masaki, sorry for letting this things with spaces to stay for a bit too long, it is a technical debt I need to fix and I really hope it will be fixed in one of the next of upcoming releases. It looks like there’s somehow a space before 605_0156_CED, so it looks like ‘space + 605_0156_CED’. Could you please double check if it is not in the name of the clip you’re trying to export form Flame. If you stuck just let me know and I can try to teamviewer to your machine and have a look
Hi @talosh, wondering if you can shed any light on this error. only happens on 3 out of 5 clips with varying timewarps. Using the beta flame TW effect. v2.4
Received 1 clip to process, press Ctrl+C to cancel
Initializing TimewarpML from Flame setup…
“invalid literal for int() with base 10: ‘10.999999’ in <class ‘ValueError’>”
[‘Traceback (most recent call last):\n’,
’ File ’
'"/opt/Autodesk/flame_2021.0.2/flameTimewarpML/bundle/inference_flame_tw.py", ’
‘line 520, in \n’
’ frame_value_map = bake_flame_tw_setup(args.setup, args.record_in, ’
‘args.record_out)\n’,
’ File ’
'"/opt/Autodesk/flame_2021.0.2/flameTimewarpML/bundle/inference_flame_tw.py", ’
‘line 327, in bake_flame_tw_setup\n’
" tw_timing[int(index)] = {‘frame’: int(frame), ‘value’: float(value)}\n",
“ValueError: invalid literal for int() with base 10: ‘10.999999’\n”]
Traceback (most recent call last):
File “/opt/Autodesk/flame_2021.0.2/flameTimewarpML/bundle/inference_flame_tw.py”, line 520, in
frame_value_map = bake_flame_tw_setup(args.setup, args.record_in, args.record_out)
File “/opt/Autodesk/flame_2021.0.2/flameTimewarpML/bundle/inference_flame_tw.py”, line 327, in bake_flame_tw_setup
tw_timing[int(index)] = {‘frame’: int(frame), ‘value’: float(value)}
ValueError: invalid literal for int() with base 10: ‘10.999999’
Press Enter to continue…
Not sure if this is caused by index or frame (you could find out by printing both variables), but I guess they are strings containing float values. I‘ve seen this in timewarps where the keyframe is between the actual frames.
If you convert them to float before converting to integer, it should fix the issue:
Glad it worked!
I had this issue when importing XMLs or AAFs (don’t remember). I would guess it can happen inside Flame, too, if you stretch the track in the animation editor.
Hi Claus, the part that reads and understands timewarp curves is actually using quite ancient ruby code made by Juliik I believe more than ten years ago and amazing that with a couple of patches it really works well. Though that limitation is still there that keyframes has to be integer frame values. I’ve ported some of that to python already and it is a bit of a technical debt to get it done fully. In the meantime the workaround is to rebuild keyframes in flame.
If you know anyone around who would fancy to help with coding it lel him or her pm me!
Hey Andriy, I only did a quick read of the code (there is really a lot of stuff going on for the calculation! :D), but if I’m not mistaken, the error happens right after reading the flame timewarp setup and before the actual parsing of that data is done. As mentioned above I think fixing the str to int conversion should get rid of the problem:
I saw this error recently me thinks. Avid aaf. Every frame was a key frame. My solve was to reset them and rebuild them with only a couple key frames and let flame interpolate.
Hey @talosh ! I’m digging into this lovely looking tool on the recommendation of @randy as he said it’s amazing. I pulled the latest from GitHub (I’m on a Mac), went through the install without error, but when I try and run it I get this error:
Traceback (most recent call last):
File “/Users/westley/Documents/flameTimewarpML/bundle/inference_sequence.py”, line 3, in
import cv2
ModuleNotFoundError: No module named ‘cv2’
logout
Saving session…
…copying shared history…
…saving history…truncating history files…
…completed.
[Process completed]
It seems it’s not seeing the OpenCV library (my best guess). Any idea as to how I can remedy this issue? I was going to install the OpenCV library using brew but thought I’d ask you before going that route.
Did you use the installer or did you install manually?
I had the same problem when I installed manually:
The conda env was active, but the pip command that I used to install the requirements.txt still referred to the system pip and not the one from conda (run which pip to see what is called). Therefore the libs weren’t installed correctly. After I used the conda pip opencv and the others were installed as expected.
I still don’t know why it referred to the system pip…
Hi Westley,
The easiest way is to get the installer from releases page on github and let it do the job. It should build an isolated anvironment with dependencies needed (you should probably remove the github pull you’ve copied before).
Let me know if it works for you.
It’s been a notion recently on github that having a separate environment for just pne plugin is a bit of an overkill. I atill think the simplicity of getting it up and running should win, but as we’re all moving towards 2022 with python3 being default it might be good to have an option for easier approach.
Currently all deps are embedded into the installer so no internet access or root pw needed, all happens in userspace.
P.S. Iv3 models has been released by the upstream algorythm devs but unfortunately whilst better by pure numbers they suffer visually vs v2 branch. This development lead to the split in the upstream branch. Now its “scientific” vs “practical” and we’re much followiing the latter one though it’s in embryo stage.
P.P.S
I’ve been using interpolation between two stills 90% of the time recently. If its the case for you as well - we’d need a better interface for the thing, I really suffer myself doing complex shots with current approach.
Looks like it should be done in batch and probably old-school furnace repair style should come first, any thoughts?