-
Notifications
You must be signed in to change notification settings - Fork 130
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
audio file format #31
Comments
Hi. As far as I can tell, the MediaRecorder API currently doesn't support the |
oh okay, thanks, so probably the also i was wondering, can the bytes in the recorded file be changed to |
That being said, currently this library defaults to For a quick conversion, I'd suggest |
yes thanks, ffmpeg worked ! added it on the server side though, and just realised I could have done it on client side instead. anyways I was able to convert webm to wav |
Hey I got the same issue and need to convert to wav file in client side so I can send a wav file to a server. |
ffmpeg -i <input_webm> -c:a pcm_f32le .<output>.wav |
@liadbelad not sure if this would work, https://www.npmjs.com/package/ffmpeg |
@liadbelad for client-side, there's https://github.com/Kagami/ffmpeg.js/ and https://github.com/ffmpegwasm/ffmpeg.wasm |
Ffmpeg is an overkill..try this https://github.com/ai/audio-recorder-polyfill it has wav encoder and mp3 encoder works in iOS world as well |
Note, Chrome does support Using Web Audio API a |
Does this still not work? |
This is what I used the last time I needed to convert floats to WAV https://github.com/guest271314/webcodecs/blob/main/WavAudioEncoder.js, usage
|
|
In case it helps anyone in the future, I posted my solution using ffmpeg here #101 (comment) |
This should be written in the document 😀 I was thought |
This worked for me on Google Chrome |
Hi,
I am trying to record audio in the browser
and fetching the file from it
Now i saved this file in disk, and used
file audio.wav
and it shows up as as WebM file
what i need is a wav file ! and it is giving me a WebM file
The text was updated successfully, but these errors were encountered: