-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This file cannot get the time code. #72
Comments
That looks like a super noisy signal which also is very quiet (-47.64dBFS). I managed to decode it after adding 40dB gain and a 2nd order Low Pass filter at 5kHz (with Q=0.9) and then feeding the result into the decoder. It contains timecode from 19:48:48:00 to 19:49:17:22 How did you record that sound? |
This should be generated by the hardware timer, but I can't confirm the model now. I will try it according to your method. |
Could it be that you directly connected BNC from a hardware generator to a soundcard's low impedance input? There definitely are issues, both signal level and impedance, and perhaps also a missing termination. It is far from a clean signal. |
It is no longer possible to trace how the file was generated, but I can parse it using other tools. |
How exactly is it realized? Can you teach me? After using ffmpeg to process such audio, can it be obtained accurately? |
The issue already happened when recording the signal. You need to fix the hardware. Get a proper cable [1], and then set the input level so that the AD receives perhaps -10dBFS peak. As for the current file, you can try with ffmpeg or sox or whatever you favorite tool is to add significant gain and low pass filter the signal. This is outside of the scope of the decoder library and not usually required for a properly recorded LTC signal. |
Yes, the hardware problem should be solved. But the old files must be obtained somehow. I tried sox but couldn't get the correct timecode.
Is it the wrong way I use it? |
output_right_channel.wav.zip
The text was updated successfully, but these errors were encountered: