Timecode problems on v 1.0.3

[meb31 (Mike)]

When I try to use LTC with v.1.0.3 build 4 it does not recognise it most of the time. Sometimes it picks something up but it is the wrong value and keeps on running by itself after the LTC has stopped.

I am using Live to Black Hole at 96k and set the correct channel and sampling rate on the Liberation window and on the timeline settings. When I revert back to v 1.0.0 it all works fine again, I did notice there is no sampling rate selection on v 1.0.0 but it still works fine.

[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

[meb31 (Mike)]

Hi Seb,

Thanks for the reply. Here are my findings:

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.

1.0.3 b5 - no difference, still not recognising LTC

48k same problem not working on 1.0.3b5 but both 48k and 96k fine on 1.0.0

Seems OK to me but I will include some screen grabs so you can check over settings.

Downloaded TC monitor and connected it to BlackHole o/p16 (same as Liberation) and it reads it fine both at 48k and 96k.

[seb (Seb Lee-Delisle)]

OK thanks good to know. Out of interest what is your LTC source? Is it an audio file? Can you share it with me?

I would stick with 1.0.0 for now while I try to fix this for the next build.

Thank you!

Seb

[meb31 (Mike)]

Sure, I tried but the WAV files are 43Mb and 83Mb at 48k and 96k and the limit for uploading here is 30Mb. How else can I get these to you?

I generated LTC WAV file using ‘LTC WAV Generator’ @ 24-bit BTW.

Am I the only one experiencing this problem?

Thanks

[seb (Seb Lee-Delisle)]

Can you send it to support@liberationlaser.com - thanks!

It’s definitely working here on my Mac with Timecode Generator going through BlackHole at 44.1 and 48k, so it is a bit of a mystery! But let me check with your audio file to just rule that out.

All the best

Seb

[meb31 (Mike)]

Thanks. Files have been emailed.

[Robert_Koren]

Some time ago i have issues regarding time code and soundswitch played from virtualdj…. all looks normal but lights was not working. I had to recode all not working mp3 files, then all starts to work normally .

Robert