Hi!
Is there a simple-ish way to get source_timecode or input/timecode from exr to the mov or mp4 review files?
By using -timecode {timecode} in the ffmpeg arguments section, it always sets the timecode to start at frame 1001, meaning the starting timecode is 00:00:41:17 for every single review.
Appreciate the help!
For information: The only mentioning of timecode is here in docs below Output arguments in extract review output defintiontions.
https://help.ayon.app/en/help/articles/3005275-core-addon-settings#qwwr6a1dab2
I believe @BigRoy can provide further info.
Hi,
If your transcodeing source has timecode (for example mov file from Nuke Extract Review Intermediate), the timecode will be present in output without any need for timecode argument.
In OP3, there was a way to store arbitrary medatada to file formats that support it , for example this output argument allowed to add reelid to Movs:
-metadata reel_name={asset}_v{version:0>3}
I didn’t test this in Ayon…
This should set it to the start frame of your the instance. So you’re likely publishing from frame 1001.
As stated on discord:
That
{timecode}metadata uses the frame start and FPS of the instance to compute the value - that’s done here.
Thank you for answers everyone 
Somehow, Nuke Extract Review Intermediate files didn’t have the timecode information before, but they do now after I’ve reset the settings. These are the ones with the delivery_ prefix. The files with the oiio_ prefix are reviews that get created after the Extract OIIO Transcode step, they don’t have the original timecode, it gets set to frame 1001 like you said @BigRoy
This works for now, since currently this is all production is asking for.
But maybe in the future they will need more, so an idea I had was to have an option to burn the metadata to a temp file with ffprobe and be able to access it with ffmpeg in the Extract Review step and maybe be able to use that data in the Extract Burnin step, but that’s for another topic I believe.
Thanks again everyone!
