Sorry if it wasn’t too clear, I meant the whole switching from frame 1001 to timecode and getting those stupid long clips.
I have no doubt that your system works a treat. Looking forward to seeing someday soon.
Sorry if it wasn’t too clear, I meant the whole switching from frame 1001 to timecode and getting those stupid long clips.
I have no doubt that your system works a treat. Looking forward to seeing someday soon.
@kyleobley - no apologies necessary at all, brother.
Thank you for offering a solution.
The metadata theft and transfer looks like it might help to maintain alignment of rendered files within the openclip container, and sometimes that can be useful.
Obviously, it’s ugly, but nuke is ugly…
hey @kyleobley
align to zero is def a great option if flame is your final destination, but if you need to publish to color or move the shots along to some other destination requiring source timecode it’s a deal breaker. as far as i can tell that align to zero function effectively wipes your source tc. found that one out the hard way recently.
Ah, I didn’t know that. That’s pretty crappy.
Less of an issue with a write node since it’s coded there no?
I am watching from a distance because Im am so busy, but let me know if you need any help with Nuke related stuff. Looking forward to see this in action in a future demo video.
Thanks for the demo @philm, it’s just fucking amazing! looking forward to adopting it.
@marios - thank you kindly brother!
I’m glad that you liked it.
(The cheque is in the mail!)
@john-geehreng - Thank you for doing a proper run through brother.
I appreciate you.
With copy metadata node and write node, toggle allow all metadata. The nuke defaults to rgb and only some metadata. That should in theory get all tape and timecode data on your render.
@johnt - thanks John - I’ll try that in the morning or better yet, we’ll have you demonstrate that when we do the LOGIK-PROJEKT Logik Live session!
I appreciate you brother.
@finnjaeger - Thank you brother.
That was a great session - we clearly have some common ambition.
We can now add Oxnard → Hamburg → Oxnard open clip workflow - tick!
I appreciate you.
dude what you did here is nothing short of amazing, its like putting a checkmark behind every odd flame feature available and then some.
love it.
@finnjaeger - Thankyou for your help and support brother.
I appreciate you.
Thank you, Phil! I’ve been fortunate enough to have had a few demos and something blows my mind every time. The way you’ve thought about every aspect of the workflow and the way you’ve automated and simplified very complex (as well as tedious) things is just awesome!
@john-geehreng - Thanks so much for the kind words brother.
It was fun running through the toolset with you.
I think we are going to build some great stuff together.
I appreciate you.
@MikeV - Thank you so much for taking the time to cast your gaze over this toolset, brother, and thank you sincerely for your extensive and committed contribution to the flame community.
You are a legend.
I appreciate you.
I pubbed out a rec709-in-dwaa show in jobs/x01 btw…. All looks like it’s working except for some color issues but I suspect they are user-error on color management setup. Shots 10 and 30 ran through batches and all is well.
@cnoellert - I saw your activities and Thank you so much for going on safari - you are an intrepid soul brother.
I appreciate you.
Not only is @philm the president, but Im a member too!