Investigate potential audio mismatch with new OTIO frame range computation

[robin-ynput]

Is there an existing issue for this?

• I have searched the existing issues and added correct labels.

Description

Current Behavior

From a discussion with @jakubjezek001 we might have some issue with the audio extraction:

We might have broken the audio otio workfow too with the rework of source vs available otio frame range. Or it seems to me that the puzzle I am trying to solve is pointing towards that direction..
It is creating audioMain representation as file, but it is empty or at least very small and very suspicious file.

Json log file: publish-report-241120-14-53.json

More information from Jakub:

The FPS used for the calculation of seconds in the script is 23.976024627685547.

To convert the third command from the previous reply into frameStart and frameEnd, we need to use the FPS value to calculate the frame numbers.

The third command is:
"C:\Users\jakub\AppData\Local\Ynput\AYON\addons\ayon_third_party_1.0.0\ayon_third_party\downloads\ffmpeg\bin\ffmpeg.exe" -ss 7207.199804110342 -t 2.1688332743850567 -i "C:\Users\jakub\AppData\Local\Temp\pyblish_tmp_audio_ehg3gm6t.wav" "C:\Users\jakub\AppData\Local\Temp\pyblish_tmp__shots_sq01_P01sq01sh010_1jrmvmjh.wav"

Calculate frameStart:
frameStart = 7207.199804110342 * 23.976024627685547
frameStart ≈ 172778

Calculate frameEnd:
frameEnd = (7207.199804110342 + 2.1688332743850567) * 23.976024627685547
frameEnd ≈ 172830

So, the frameStart is approximately 172778 and the frameEnd is approximately 172830.

Expected Behavior

A concise description of what you expected to happen.

Steps To Reproduce:

No response

Additional context:

What platform were you running when you found the bug?

Windows

Relevant log output: