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
As reported in #68, there's a bug where the source timecode is being calculated incorrectly - i.e. frame 4 will be correct, but frame 5 will be the same value as frame 5.
Frame 4 (0.16sec) is correctly displayed as 17:32:11:01 / 1578276 frames / 63131.04 seconds. Frame 5 (0.2sec) is incorrectly displayed with the same value.
As reported in #68, there's a bug where the source timecode is being calculated incorrectly - i.e. frame 4 will be correct, but frame 5 will be the same value as frame 5.
Here's an example FCPXML:
Frame 4 (0.16sec) is correctly displayed as 17:32:11:01 / 1578276 frames / 63131.04 seconds.
Frame 5 (0.2sec) is incorrectly displayed with the same value.
Looking at the JSON cache:
Something is going wrong in the
asset-clip
source calculations.The text was updated successfully, but these errors were encountered: