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.
First thing I’d suggest is trying the latest version (1.0.3) and seeing if the behaviour changes. (You can set the sample rate in 1.0.3)
If it’s still not working, I’d check the chain step by step:
- Confirm the LTC signal is definitely present on the exact device and channel you’ve selected (sounds like you’ve already done this with Timecode Monitor, which is great)
- Double-check that VB Cable is set to a sensible sample rate (e.g. 44.1kHz or 48kHz) in Windows sound settings
- Make sure no other application is exclusively locking the device
- Try a different input device if possible, just to rule out VB Cable
- Try a different time code source (like Timecode Generator)
And double check everything I mentioned in this post!
You’re absolutely right that with a setup like this there are a lot of possible failure points, so it’s just a case of narrowing it down one stage at a time.
Let me know what you find
All the best
Seb