You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the test suite OTIO, there are several trim-to-fill time warp effects which are not represented correctly. Those effects were added using Avid Media Composer's "Trim to FIll" from the Effect Palette window. They show up in the OTIO as TimeEffects but they should be LinearTimeWarp effects with a time_scalar value. I believe this is a bug in the AAF to OTIO conversion adapter, which is missing support for keyframes in the position graph. If so, I'll make a bug report there and link it here.
Linear time warps trim-to-fill
Trim-to-fill 99 frames into 100 (BUG: TimeEffect should be LinearTimeWarp)
Trim-to-fill 90 frames into 100 (BUG: TimeEffect should be LinearTimeWarp)
Trim-to-fill 50 frames into 100 (BUG: TimeEffect should be LinearTimeWarp)
Trim-to-fill 33 frames into 100 (BUG: TimeEffect should be LinearTimeWarp)
Trim-to-fill 5 frames into 100 (BUG: TimeEffect should be LinearTimeWarp)
Trim-to-fill 100 frames into 99 (BUG: TimeEffect should be LinearTimeWarp)
Trim-to-fill 100 frames into 50 (BUG: TimeEffect should be LinearTimeWarp)
Trim-to-fill 100 frames into 33 (BUG: TimeEffect should be LinearTimeWarp)
Trim-to-fill 100 frames into 10 (BUG: TimeEffect should be LinearTimeWarp)
Trim-to-fill 100 frames into 9 (BUG: TimeEffect should be LinearTimeWarp)
The text was updated successfully, but these errors were encountered:
jminor
changed the title
Trim-to-fill time warp effects are not handled
Trim-to-fill time warp effects appear as the wrong type
Dec 10, 2024
In the test suite OTIO, there are several trim-to-fill time warp effects which are not represented correctly. Those effects were added using Avid Media Composer's "Trim to FIll" from the Effect Palette window. They show up in the OTIO as TimeEffects but they should be LinearTimeWarp effects with a time_scalar value. I believe this is a bug in the AAF to OTIO conversion adapter, which is missing support for keyframes in the position graph. If so, I'll make a bug report there and link it here.
The text was updated successfully, but these errors were encountered: