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 it publishes with error whith was mentioned here (#5) but in integrates anyway BUT 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

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
2. thim it to 10 frames, create publisheble shot with 10 frames handles
3. get an error
4. see that it has been published anyway
5. 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:

resolve 19

and i have the same thing happening in hiero but without integration error, just one frame shorter than in ayon database
(ynput/ayon-hiero#2)

[BigRoy]

I gave this a quick go.

---

My project at 25 FPS:

1. Loaded a H264 clip of six frames.
2. Created publishable clip instance, published.
3. The loader showed:

So it shows 6 frames long in the database and also loads fine with the original length. Seems ok?
Are you sure you Resolve project and timeline are also set to 25 FPS?
Could you maybe provide a brief demo file that failed for you?

[timsergeeff]

This happens with prores files

https://cloud.blankpig.com/s/yL9iJBc4PazFJYK
Try it

[timsergeeff]

this problem is ffmpeg purely, mp4 works fine, prores looses 1 frame at the endm, mxf from arri not rendering at all

prepublish conversion to exr aces cg solves issue and makes sence aas further work will be rendered in exr anyway

[jakubjezek001]

Here is reaction on Hiero issue ynput/ayon-hiero#2 (comment) - this also applies to this issue.