Locking LTC after silent
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
- Is this a known issue or limitation in Millumin 4?
- Is there a recommended workaround besides keeping LTC running continuously?
- 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
Hello @YP_Yj,
We are not aware of such an issue in Millumin V4 or V5.
A few questions to better understand the situation :
Thank you for your answers. Philippe
Hello,
Thank you for your reply. Here are the answers to your questions with more details:
Additional context:
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.
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