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?
We are working on this issue. Thank you for your patience.
@Hyungjae : in comparison with version version 5.14.e, the version 5.14.f brings fixes for MTC, especially when working with a Rosendahl MIF4. Does the other modes work correctly (24, 25, 30 fps) ?
@KMB : there is no change about LTC between version 5.14.e and 5.14.f, but only about MTC. Are you talking about LTC or MTC ?
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?
Hello @Hyungjae & @KMB,
We are working on this issue. Thank you for your patience.
@Hyungjae : in comparison with version version 5.14.e, the version 5.14.f brings fixes for MTC, especially when working with a Rosendahl MIF4. Does the other modes work correctly (24, 25, 30 fps) ?
@KMB : there is no change about LTC between version 5.14.e and 5.14.f, but only about MTC. Are you talking about LTC or MTC ?
Best. Philippe
When mif4 receives the LTC input and connects to the milumin, the device recognizes it as MTC.
NDF of all frames is fine.
There seems to be a problem with DF.
Hello @Hyungjae and @KMB,
We just release Millumin version 5.14.g that should solve your problem.
Can you tell us if you still have any issue ?
Have a nice day,
Nicolas