Fix OTIO export for Flame

[robin-ynput]

Changelog Description

Fixes custom AYON OTIO export for Flame.

• embedded timecode not detected properly for image sequence and movies
• image sequence source_range was relative to the available_range

##Additional info
Tested on Flame 2024.2.2.

Testing notes:

I have created a sequence in Flame under Reel 5 that creates a 25fps timeline with a mix of:

• regular movie
• movie with embedded timecode
• regular image sequence
• image sequence with embedded timecode

Here is the code to validate the results:

import ayon_flame.api as ayfapi
from ayon_flame.otio import flame_export

print("toto: ", ayfapi.CTX.selection)

seq = ayfapi.get_current_sequence(ayfapi.CTX.selection)
#with ayfapi.maintained_segment_selection(seq):
otio_timeline = flame_export.create_otio_timeline(seq)

print(otio_timeline)
v1 = otio_timeline.video_tracks()[0]
v2 = otio_timeline.video_tracks()[1]

tc_clip = v1.find_clips()[0]
notc_clip = v1.find_clips()[1]
tc_img_clip = v2.find_clips()[0]
notc_img_clip = v2.find_clips()[1]


# QT embedded timecode
tc_clip.available_range()  # TimeRange(RationalTime(86400, 24), RationalTime(100, 24))
tc_clip.source_range  # TimeRange(RationalTime(90000, 25), RationalTime(100, 25))

# QT no embedded timecode
notc_clip.available_range()  # TimeRange(RationalTime(0, 25), RationalTime(101, 25))
notc_clip.source_range  # TimeRange(RationalTime(0, 25), RationalTime(101, 25))

# Img srquene (embedded timecode)
tc_img_clip.available_range()  #TimeRange(RationalTime(87399, 24), RationalTime(101, 24))
tc_img_clip.source_range  #TimeRange(RationalTime(91040.6, 25), RationalTime(101, 25))

# Img sequence (no embedded timecode)
notc_img_clip.available_range()  # TimeRange(RationalTime(1000, 25), RationalTime(101, 25))
notc_img_clip.source_range  # TimeRange(RationalTime(1000, 25), RationalTime(101, 25))

[jakubjezek001]

It looks good.

Just to make sure, this will work as expected even if the timecode on the image sequence offsets the first image frame number. I see that on line 292, we are getting the timecode frame number from mediainfo, but it seems like we are not using it in the otio reference object. However, I might be wrong.

[robin-ynput]

It looks good.

Just to make sure, this will work as expected even if the timecode on the image sequence offsets the first image frame number. I see that on line 292, we are getting the timecode frame number from mediainfo, but it seems like we are not using it in the otio reference object. However, I might be wrong.

I believe this is correct. I made an attempt with an EXR sequence (1000-1101) and a "01:00:00:00" embedded timecode.
Resulting ranges looks correct to me:

• available_range (24fps) = TimeRange(RationalTime(87399, 24), RationalTime(101, 24))
• source_range (25fps) = TimeRange(RationalTime(91040.6, 25), RationalTime(101, 25))

Does this answer your concern ?