-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AY-979_Collect OTIO subset resources - get_media_range_with_retimes returns negative range values #895
Comments
I think these are reversed @robin-ynput So an image sequence 1001-1050 with five frame handles included means that without handles the range is 1006-1045.
This is what you may often see in AYON codebase - we have a frame start (which excludes handles) and the Meaning: # convert to available frame range with handles
a_frame_start_h = media_in + handle_start
a_frame_end_h = media_out - handle_end |
@BigRoy thanks for your comment but I'm not sure this is the fix actually. Initial example I gave on the ticket is stolen from Jakub logs but I run another example with TIF sequence from Resolve and got a different issue:
So this time it looks like the retimed range was OK and handles were properly adjusted to not go over the bound, But the detected frame-range in the @jakubjezek001 out of curiosity could you tell us what the status of this, is that WIP ? Was this ever bullet-proofed in prod ? |
From my tests, I've noticed that the issue lies with the "source in" frame value. It shouldn't match the "media in" value, as this is causing a significant offset. In this instance, the "source in" should be set to
It seems that there is no issue with the method rather with the incoming data. If you dont mind I will close the issue. |
@jakubjezek001 actually I found at least one culprit.
My sequence is Do we consider this to be a Resolve issue that needs to be work-arounded in the collector plugin ? |
Is there an existing issue for this?
Current Behavior:
There seems to be something wrong when computing the retimed values from an image sequence.
Issue was originally flagged by @jakubjezek001 on ynput/ayon-resolve#15
Expected Behavior:
Currently retiming
returns this representation:
I think it should rather be:
Version
1.0.0
What platform you are running on?
Windows
Steps To Reproduce:
Are there any labels you wish to add?
Relevant log output:
No response
Additional context:
No response
AY-979
The text was updated successfully, but these errors were encountered: