Timecode problems on v 1.0.3

[seb (Seb Lee-Delisle)]

Hi Mike,

Thanks for the detailed report - that’s really helpful.

A couple of thoughts here:

• 96kHz could definitely be a factor. There have been some edge cases with sample rates outside 44.1 / 48kHz, so it would be really useful if you could try dropping everything to 48kHz and see if the behaviour stabilises.
• The “keeps running after LTC stops” part is interesting - that can sometimes happen if Liberation is effectively “seeing” noise or residual signal and interpreting it as valid LTC. That could be:
  • feedback / routing loop (e.g. BlackHole being fed back into itself somewhere)
  • or just unstable decoding at that sample rate
• The fact that 1.0.0 works fine is a really useful data point - there have been quite a few changes in the audio/timecode handling since then, so it’s possible there’s a regression here.

If you can:

• Try 1.0.3 Build 5
• try 48kHz end-to-end (Ableton + BlackHole + Liberation)
• double-check there’s no routing loop in Audio MIDI Setup / Live
• Use Timecode Monitor with the same input as Liberation and see if it works.

That should help narrow it down quite a bit.

Also check all the advice in these posts :

LTC Signal not recognized in Liberation

Hi Vasav, welcome! A red indicator there can mean one of two things: either the audio device failed to open, or it opened successfully but there’s no incoming signal. I’ve improved that feedback in the next build as it’s a bit ambiguous in the current versions. I can see you’re on 0.9.6 - in that version Liberation connects using the device’s “preferred” sample rate, which I’ve since discovered can sometimes be set to unhelpful values. So it’s possible the sample rate is part of the issue. Fi…

LTC Stuttering?

Hi Nils, The first thing I’d suggest is isolating whether the issue is with the incoming timecode itself, or how Liberation is handling it. A good way to do that is to use something like Timecode Monitor and Timecode Generator TimeCode Monitor - Watch timecode while it comes in! TimeCode Generator - Timecode Generator! Try this: Feed your LTC (via Loopback) into Timecode Monitor Check whether it runs smoothly and increments cleanly, without jumps or jitter If Timecode Monitor also stutte…

Either way, I’ll take a look at tightening this up on my side before the next build, as there may still be some edge cases in the LTC audio handling.

All the best,

Seb