Timecode mismatch when using no-handles

Hi! We are generating one DNxHD review that includes handles and one h264 review that needs to have the handles stripped. DNxHD has the correct timecode, while h264 has the timecode minus number of handles.
For example: DNxHD timecode - 16:13:09:00; h264 timecode 16:13:08:21 (number of handles 3).

Is there a way we can add the number of handles to the no-handles timecode?
I’m adding the no-handles flag here:
ayon+settings://core/publish/ExtractReview/profiles/0/outputs

Could you elaborate on the no-handles flag?

As far as I know, handles are excluded from your published product via disabling Use task handles option.

There’s a tag in review you can use no-handles
Then that review doesn’t have the handles included, but the timecode is then incorrect.

I have this tag in the h264 review, but not the one that make the DNxHD, because a client wants the full range with handles of the DNxHD, but not the handles in the h264.

oh yes, found it in tags.

So, I’ve found places in code where an action is taken based on no-handles:

and they don’t mention timecode and also don’t touch the instance metadata so I wonder if the timecode computation still follows the instance metadata without considering the no-handles tag.

Unfortunately, I’m not sure about where to look in the code to fix it. but I can see this function frames_to_timecode.

I hope this helps. and PRs are more than welcomed.

Also, feel free to create an issue on AYON Core. However, I don’t think it’ll be picked up soon as it won’t be a sponsored issue.

Thanks!

I’ll give it a look, but no guarantee I’ll actually be able to do anything about it since I’m not a programmer :sweat_smile:
Will try tho.

1 Like