›

Locking LTC after silent

YP_YjYP_Yj
edited January 12 in MAIN

Hello Millumin team,

I would like to report an issue I’m consistently experiencing with Audio LTC input in Millumin 4, and I would like to confirm whether this is a known limitation or bug.

System

  • macOS (Apple Silicon)
  • Millumin 4
  • Audio interfaces tested:
    • Focusrite Scarlett 2i2
    • MOTU M4
  • Timecode type: Audio LTC
  • Input level is healthy (around -12 to -6 dB)
  • Phantom power OFF, mono OFF

Issue description

When LTC is sent continuously, Millumin locks correctly at first.

However, if there is a period of silence (no LTC) for several minutes and then LTC starts again:

  • Millumin does not re-lock to the LTC
  • The LTC signal is clearly present at the audio interface
  • If I manually change the input channel in Millumin and then switch back,
  • → the LTC immediately locks again

This happens consistently, and I can reproduce it every time.

Important note

I tested this with two different audio interfaces (Scarlett 2i2 and MOTU M4), and the behavior is exactly the same.

Because of this, it does not appear to be an audio interface–specific issue, but rather related to how Millumin 4 handles Audio LTC re-locking after silence.

My understanding

It seems that when the Audio LTC stream goes completely silent for some time, Millumin 4 releases or idles the CoreAudio input stream, and when LTC resumes, Millumin does not automatically rescan or reopen the input unless the channel is manually changed.

Questions

  1. Is this a known issue or limitation in Millumin 4?
  2. Is there a recommended workaround besides keeping LTC running continuously?
  3. Has this behavior been improved or changed in Millumin 5?

Any clarification would be greatly appreciated, as this affects live show reliability.

Thank you for your support.

Comments

  • MilluminMillumin

    Hello @YP_Yj,

    We are not aware of such an issue in Millumin V4 or V5.

    A few questions to better understand the situation :

    • When the LTC is stopped (silent) then restarted, was the audio interface stopped as well ? Or is it stricly silence (no change on the audio interface) ?
    • When the LTC is stopped (silent), is the small vu-meter at zero in the device-panel (CMD+K) ? And when it is restarted, is this vu-meter showing that audio is coming in ?
    • If the problem persists, could you please send us a TeamViewer session (or equivalent) ?


    Thank you for your answers. Philippe

  • YP_YjYP_Yj

    Hello,

    Thank you for your reply. Here are the answers to your questions with more details:

    1. When the LTC is stopped (silent) and then restarted, the audio interface remains powered on and connected the entire time. There is no restart or reconnection of the audio interface itself. During the issue, there is simply no LTC signal coming in (silence).
    2. When the LTC is stopped, in the Device Panel (CMD + K), the green audio level meter next to the audio interface is still visible and reacting, which suggests that the audio input is detected at the system level.
    3. However, Millumin does not lock to the LTC and shows “Waiting for timecode”. Even after the LTC signal is restarted, Millumin sometimes does not re-detect it unless I change the input channel and switch it back.

    Additional context:

    • MacBook Pro with M3 Max chip
    • macOS Sonoma
    • Millumin V4
    • Audio interface stays stable and visible in macOS at all times

    I wanted to ask whether this behavior could be related specifically to Millumin V4, and if upgrading to Millumin V5 is known to improve LTC re-detection or stability in this kind of scenario (especially when LTC drops to silence and resumes).

    Please let me know if you need any additional information from my side.

  • MilluminMillumin

    Hello @YP_Yj,

    Sorry, I could not reproduce your problem. Could you please send us a TeamViewer session (or equivalent) via email ?

    I do not think Millumin V5 would make a difference as there is not change when receiving LTC in comparision with Millumin V4.

    Best. Philippe

  • HWANK1MHWANK1M
    edited February 6

    I had similar issues with scarlett 2i2 3rd.

    It worked fine when I use intel mac, it kept losing the signal when I use that interface with apple silicon macs

    After I switched interface to behringer umc204hd, It never lost LTC signal.

    Also steinberg ur22c and zoom ams24 were stable, too.

    Maybe it's about interface itself or driver issues with apple silicon I guess.

    I tested on millumin v3 and v4 with Intel macbook pro 2017, 2019 / Macbook pro m1max, m2max ,m3max / mac studio m1ultra.

  • HyungjaeHyungjae

    I had a similar situation when using LTC in the past.

    When using LTC with Millumin4, M1 MAX MBP and Scarlett 2i2, LTC was not recognized in the middle of the performance.

    In this case, it was a symptom of changing the channel or replacing the interface with another one and then selecting it again.

    Now I'm using Millumin5, Rosendahl mif4, and I haven't had any major problems yet.

Sign In or Register to comment.