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

Add support for the Edge TTS voices #391

Open
stemplock opened this issue Apr 16, 2024 · 3 comments
Open

Add support for the Edge TTS voices #391

stemplock opened this issue Apr 16, 2024 · 3 comments

Comments

@stemplock
Copy link

Add support for the tts service.
https://github.com/rany2/edge-tts
Please, if possible.

@jkyndir
Copy link

jkyndir commented Jun 11, 2024

I had the exact same request. Microsoft Edge appears to have some amazing Voices

@ken107
Copy link
Owner

ken107 commented Jun 11, 2024

I think this is probably possible

@ken107 ken107 changed the title Add support for the tts service. Add support for the Edge TTS voices Jun 26, 2024
@ken107
Copy link
Owner

ken107 commented Aug 24, 2024

It may or may not be possible, proof of concept needed.

The linked repo is a standalone Python program that calls Azure Speech Services and masquerades as the Speech component/extension in Microsoft Edge browser, by sending these headers when setting up the WebSocket connection:

{
  "Origin": "chrome-extension:https://jdiccldimpdaibmpdkjnbmckianbfold",
  "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36 Edg/91.0.864.41"
}

I'm guessing Azure will reject the request if the headers aren't set correctly. But I'm not sure it's possible to set these headers in our Manifest V3 extension. Specifically:

  1. Does the declarativeNetRequest API allow modifying these two privileged headers (Origin and User-Agent), and
  2. Does the modification apply to the WebSocket setup requests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants