More consolidations on Hiero OTIO exporter

[rdelillo]

Changelog Description

help resolve #29

• We were loosing some accuracy on OTIO export for source range start_time, this was causing rounding issues with longest frame range.

Additional review information

Testing notes:

1. Create a clip in Hiero with a long frame range (e.g. start_frame > 900,000 at 24.0 fps)
2. Drag and drop on a 23.976 sequence while preserving clip duration
3. Trim clip to specific frame input output
4. Export sequence to OTIO and ensure source range of the clip match input frame when rescaled back to 24.0 fps

[jakubjezek001]

looking good, lets merge

[jakubjezek001]

@robin-ynput shouldn't we similar change also in Resolve?

[rdelillo]

@robin-ynput shouldn't we similar change also in Resolve?

Actually we do not, I triple checked this morning, it really dependsof the DCC "source_in" value returned by the API:

• Flame and Hiero makes it based on the input media fps, hence the fix to keep it as accurate as possible during the conform.
• Resolve returns it based on the input track fps, so already correct