-
Notifications
You must be signed in to change notification settings - Fork 154
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
Error for each supported audio file type #11
Comments
The FLAC file you uploaded is in WAV format. Try converting it to FLAC using ffmpeg.
|
That being said, the default FLAC encoding of ffmpeg, after converting the WAV file you provided, is 16 bits-per-sample with 1 channel. At the present, the beep/flac library is not capable of decoding that. However the fix is easy. I may look into it.
Cheers, |
There we go. With PR #12, the code you submitted works for FLAC files (after having converted the original WAV file to a FLAC file, as outlined below).
Cheers, |
A side note, the test files you linked to are identical. Are these the same files you used on your system?
|
A quick hexdump of the WAV sample you uploaded reveals that it contains metadata not yet supported by the beep/wav decoding library. Specifically the unannotated hex-dump in the middle is not yet supported. @faiface, do you know of a WAV spec where this is specified? I checked wiki and the some of its refs, but could not find the definition of some of these chunks, e.g. Edit: ok, I did a quick check. Missed that wiki does indeed mention the
|
I have tried running functional audio files for a .flac, .mp3 and .wav but receive different errors for each one. My code is pretty much the same for the 3 different tests:
Expected:
Audio plays normally.
WAV Result:
wav: missing data chunk marker
MP3 Result:
mp3: mp3: only layer3 (want 1; got 3) is supported
Flac Result:
flac: flac.parseStreamInfo: invalid FLAC signature; expected "fLaC", got "RIFF"
Here are the files for your own use:
Flac file
MP3 file
WAV file
All the files are generated by the IBM Watson text-to-speech API and run fine on my machine. All error messages occur within the AUDIO STREAMER ERROR block. Is this a bug? Thanks!
The text was updated successfully, but these errors were encountered: