Skip to content
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

Integrated WebUI does not support Firefox #103

Open
0pac1ty opened this issue Jan 30, 2025 · 5 comments
Open

Integrated WebUI does not support Firefox #103

0pac1ty opened this issue Jan 30, 2025 · 5 comments
Labels
bug Something isn't working in-progress

Comments

@0pac1ty
Copy link

0pac1ty commented Jan 30, 2025

Describe the bug
The MIME Type used for audio generation is not supported by Firefox (v134.0.2).
Works fine with Chromium based Browsers.

Screenshots or console output
Error generating speech: MediaSource.addSourceBuffer: Type not supported in MediaSource

Branch / Deployment used
Tested with the kokoro-fastapi-gpu v0.1.4 docker image

@remsky
Copy link
Owner

remsky commented Jan 30, 2025

I think Firefox just doesn't support the mpeg/mp3 format for mediasource as far as I'm aware

Do you get the same issue if selecting WAV?

@0pac1ty
Copy link
Author

0pac1ty commented Jan 30, 2025

Do you get the same issue if selecting WAV?

Yes. The error appears with either of the three options: MP3, WAV and PCM.

@remsky
Copy link
Owner

remsky commented Jan 31, 2025

Will check it out

@remsky remsky added the bug Something isn't working label Jan 31, 2025
@signalstop
Copy link

signalstop commented Feb 1, 2025

Hello! : )

I can't generate in Firefox using mp3 , wav or PCM. In Chrome and Edge I can generate but the play button is blocked and I can only download the audio file.

"Error generating speech: MediaSource.addSourceBuffer: Type not supported in MediaSource"

@xektop
Copy link

xektop commented Feb 1, 2025

I have tried to change the address from 0.0.0.0:8080 to localhost:8080 which allowed me to use my headset in Firefox.
From what I read this is served via HTTPS and you have to self sign a certificate and whatnot... I found that localhost is easier for my use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working in-progress
Projects
None yet
Development

No branches or pull requests

4 participants