-
Notifications
You must be signed in to change notification settings - Fork 69
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
problems with different mimetypes in different browsers (v4) #28
Comments
I've added a part in the readme that discuss these type of issues exactly. for now, the best way to deal with this issue is to convert each file to your required format also, I will check again if there is a mime type that is supported by all |
@tchvu3 What about audio/mpeg (mp3)? It looks like it's supported in all major browsers, if I'm understanding these docs correctly, but it's not included as a possible web mime type. update: never mind -- if you run |
As we are using this plugin in production, we have now implemented a solution where we transform all audio files via ffmpeg to mp3 then save them as base64 strings and then all of our supported platforms can play them. I think @nkalupahana suggestion is the correct approach, if a viable implementation can be found for it. |
Seems related: #34 :) |
@DevRichter once we get the base64 data how are you saving it as a file. I tried to save base64 data with FileSystem API but it seems once its saved with following code, I am not able to transform the file format with ffmpeg. Here's the code:
ffmpeg just errors out. Most probably because the file is not saved in a format that ffmpeg can process any suggestions would be appreciated. |
@shyamal890 sorry for the super late answer. for anyone thats still wondering, we are using @ffmpeg/ffmpeg and then just
|
Hey,
i have a problem with the different encoding of the files. As far as i can tell the mime-types are different for each scenario: audio/webm (recorded with chrome, also different depending on which browser you record with.) for browser and audio/aac (with different sigantures) from android or apple devices.
We record the voice messages in different devices or different browsers and need to support as many platforms as possible, we upload them via aws s3 as the pure base64 string, then download them as these strings, create an instance of an Audio HTML object and play them. (current state)
The problem is that these files have for example different durations then the real duration or do not get played at all (only in safari an issue). The encoding of voice messages recorded by the android devices seem to work in every browser (we tested) for some reason.
Do you know of a way to record the voice messages with an encoding in e.g. Chrome that will work in Safari? Is there a way to convert this encoding, or record with a more broad possibilty to choose the encoding we want?
The text was updated successfully, but these errors were encountered: