-
Notifications
You must be signed in to change notification settings - Fork 55
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
How does LIBLTC support 16bit/24bit data encoding and decoding? #67
Comments
wav can contain multiple chunks, meta-data, and different encodings (signed, unsigned). |
Thanks a lot, I've now been able to get and use PCM metadata correctly. But the sample format is 8bit unsigned mono, which cannot meet my needs. I want to change the sample format to 24bit mono, so what should I do? |
If it is signed 24 bit, divide each sample value by 256 and then use |
It may be that I didn't express clearly, I only use encoding, not decoding. The current encoded data is implemented based on 8bit unsigned data. If it is encoded based on signed 24bit data, how should it be handled? By the way, I did not understand the meaning of enc_lo and enc_hi in the structure LTCEncoder? What role do enc_lo and enc_hi play in the entire encoding process? |
For output you can likewise scale each sample:
LTC is a square wave. lo/hi are the signal levels for the waveform, you can change the default via Hope that helps. |
First of all, I am very grateful for providing an LTC encoding and decoding method. After my test, LIBLTC can only: encode and decode 8bit data, and does not support 16bit/24bit encoding and decoding. My steps are as follows:
2000-00-00 +0000 02:03:04:05 | -23 2002
2000-00-00 +0000 02:03:04:06 | 2003 4004
2000-00-00 +0000 02:03:04:07 | 4005 6006
2000-00-00 +0000 02:03:04:08 | 6007 8008
2000-00-00 +0000 02:03:04:09 | 8009 10010
2000-00-00 +0000 02:03:04:10 | 10011 12009
2000-00-00 +0000 02:03:04:11 | 12010 14011
2000-00-00 +0000 02:03:04:12 | 14012 16013
2000-00-00 +0000 02:03:04:13 | 16014 18015
2000-00-00 +0000 02:03:04:14 | 18016 20017
I have two questions
The text was updated successfully, but these errors were encountered: