framerange missmatch

[timsergeeff]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior:

When i crate publisheble clip and publish it will go with wrong frame range: one frame less than nedeed so further publishing for example from nuke isnt working because of a out of frame range error. I mean that AYON reads frame range corectely, but publishes one frame shorter version

Expected Behavior:

Correct frame range

Version

1.0.0

What platform you are running on?

Windows

Steps To Reproduce:

1. take any video file (my test was mov apple prores 25fps)
   2)put it inside timeline
   3)trin it to 10 frames
2. create publisheble shot with 10 frames handles
3. publish a shot('s)
   6)see published shot is 29 frames long but in AYON datadasae it is 30

Are there any labels you wish to add?

• I have added the relevant labels to the bug report.

Relevant log output:

No response

Additional context:

Hiero 15

Resolve has the same error (ynput/ayon-resolve#8)

[timsergeeff]

i just discovered that problem is only with prores files and i think in ffmpeg trimming proccess because with mp4 h264 source in works fine

[jakubjezek001]

Hi @timsergeeff, thank you for reporting this issue. We are currently redesigning the Hiero editorial publishing, and as part of this process, we reviewed the OTIO frame range calculations. Here are some updates in ayon-core that may fix the issue. Please update your server to the latest version of ayon-core and test the workflow again.

Fixes by @robin-ynput:

• Issue 895
• Issue 912

Additionally, there is an open PR for migrating Hiero into the current publisher: #14.

If you have a chance to test it and provide feedback, that would be fantastic! 💯