Replies: 10 comments 5 replies
-
That should be relative easy to add. Something like: davinci_fcpmxl.otio (Soda_Pictures.0001.exr) or: davinci_fcpmxl.otio (Soda_Clip.mov)
That, however, it is tricky. I'll need to dig into the source code to try to figure it out if it is even possible, as the check would impact playback performance possibly dramatically. |
Beta Was this translation helpful? Give feedback.
-
|
FWIW, I would fully expect a clip version change to invalidate the cache. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure if you prefer to to have a separate thread for each distinct idea, or whether you'd prefer them to be group into 'related thoughts' threads. I'll continue here... It would be super handy to be able to quickly set the in and out marks to a single shot's boundaries. eg: you are playing back a sequence cam010, cam020, cam030, cam040 etc... and you wanna take a closer look at cam020... you pause the playhead on cam020, hit a hotkey, and the in an out marks set to the boundaries of cam020 in the timeline. Hit the hotkey again, and the in and out marks clear. |
Beta Was this translation helpful? Give feedback.
-
|
Yes. Actually, if instead of posting here in ideas, you report them as Issues (tagging them as a Feature), that would be great. That way I can keep track of it, disscuss them and close the Issue once the feature is added. |
Beta Was this translation helpful? Give feedback.
-
|
Your three suggestions have been added to mrv2 v1.3.1 beta. You can give them a go at: |
Beta Was this translation helpful? Give feedback.
-
|
Heya Gonzalo, Thanks for implementing these. I'll be sure to log further RFE's as issues (tagging them as a feature). To round out this topic though, I do get an instacrash whenever I try any of the image->version menus. |
Beta Was this translation helpful? Give feedback.
-
Can you try the latest on sourceforge to see if you still get crashes. Also, in case you do, let me know what platform. |
Beta Was this translation helpful? Give feedback.
-
|
It's still crashing on windows11 on build: I'm unable to test on linux yet, as I i'm still tweaking the xml translator, and don't have a file with viable paths. i'll test on linux as soon as I can. |
Beta Was this translation helpful? Give feedback.
-
|
Please try this version that has Debug information. When it crashes, it should save a $HOME/.filmaura/crash.log. .exe: |
Beta Was this translation helpful? Give feedback.
-
|
Also, give me the .otio file it is crashing with. |
Beta Was this translation helpful? Give feedback.
-
|
Heya Gonzalo, I've tested versioning up and down using build: Unfortunately, I don't see a log file being created in $HOME/.filmaura mrv2.keys.prefs I'm attaching a single track otio file that i'm using to test with. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry. My bad. The crash goes to %TMP%. On Windows, this is usually: C:\Users<USER>\AppData\Local\Temp. |
Beta Was this translation helpful? Give feedback.
-
|
see mrv2.crash.log attached: |
Beta Was this translation helpful? Give feedback.
-
|
This one should not crash. .exe: Note that if you are using mrv2 to create an .otio playlist, you can also do it command-line (and it will create an EDL*.otio file in $TMP).
|
Beta Was this translation helpful? Give feedback.
-
|
It's working! Thank you for sorting this out! It's great to know about being able to use the CLI flag to write otio files. Very handy! I'm currently creating otio files via an in-progress fcpxml translator... |
Beta Was this translation helpful? Give feedback.
-
I've noticed that when you playback an otio timeline, the HUD displays the refrence to the OTIO file, instead of each individual clip currently being played.
I think it would be super handy for the hud to reflect the info based on the location of the playhead instead:
ps: it would also be super cool if you could see the 'image' menu there as well, for each clip the timeline to be able to compare the 'current' version to previous versions.
Beta Was this translation helpful? Give feedback.
All reactions