I also observed this issue, and to explain in more detail: when receiving LTC at 29.97 drop-frame in version 5.14.f, the device settings window displays it as 30, while the preview shows it as 29. This behavior is typically seen with standard 29.97 drop-frame timecode.
However, over time, a discrepancy begins to appear between the original timecode and the received timecode.
For comparison, I ran versions 5.14.e and 5.14.f simultaneously on the same Mac Pro and configured both to receive the same LTC signal. Version 5.14.e operated normally, while 5.14.f showed the issue.
Additionally, when testing with 30 non-drop-frame, both versions worked correctly.
Could you please confirm whether this issue is related to the OS, or if it is a bug specific to version 5.14.f?
Comments
Hi!!!
I also observed this issue, and to explain in more detail: when receiving LTC at 29.97 drop-frame in version 5.14.f, the device settings window displays it as 30, while the preview shows it as 29. This behavior is typically seen with standard 29.97 drop-frame timecode.
However, over time, a discrepancy begins to appear between the original timecode and the received timecode.
For comparison, I ran versions 5.14.e and 5.14.f simultaneously on the same Mac Pro and configured both to receive the same LTC signal. Version 5.14.e operated normally, while 5.14.f showed the issue.
Additionally, when testing with 30 non-drop-frame, both versions worked correctly.
Could you please confirm whether this issue is related to the OS, or if it is a bug specific to version 5.14.f?