-
Notifications
You must be signed in to change notification settings - Fork 244
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
Excellent with MP3s but problematic with WAVE files #128
Comments
I'd be happy to investigate. Can you share an example WAV file with me? My contact email is in the commit history. |
Thanks!! (ps I also emailed you....) |
I also have this "bug" with 60min length .wav file (pcm / 16 bits / stereo / 48kHz). All is saturated in the json export (all values are -127,+128 in 8 bits, or -32767,+32768 in 16 bits). |
Can you provide an example audio file for me to look at? |
here is the WAV file (680Mb) : command executed :
and excerpt of the json generated file :
I set the zoom value at 172800 thinking there will be 1000 measurements (48000 * 3600 / 1000) ...
OS MacOS 12.5.1 (Monterey). audiowaveform installed with homebrew |
Thanks, I've downloaded the file, I'll take a look. |
It's the same if I view in Audacity, the waveform is saturated. You see more detail with a lower zoom level, but if you need a fixed 1000 pixel width image, with this audio it'll just look like a solid block. So audiowaveform is working as designed. I wonder what ffmpeg is doing? @Gigamick Did we figure out what was happening in your case? I don't remember the details, I apologise if I didn't reply... |
Thanks for your reply. The command i use with ffmpeg is the following :
|
When I use this on my application for MP3's it's all amazing. However I have some users uploading .WAV files and their waveform renders look like this:
Which is very wrong. Any ideas?
The text was updated successfully, but these errors were encountered: