GoogleNetworkSpeechSynthesis VS native-messaging-espeak-ng

If you want you can use Google's TTS service without Web Speech API with a proxy, see GoogleNetworkSpeechSynthesis. I made a feature request for Google to release the source code as FOSS Re: Issue 263510047: Release TTS and STT source code and Google voices as FOSS so we don't have to make external requests just to use Web Speech API.

I requested to Google to Release TTS and STT source code and Google voices as FOSS which you can request over the network here GoogleNetworkSpeechSynthesis. Those are the voices Google Chrome uses for Web Speech API. Feel free to chime on the feature request in in support of Google releasing the source code of its network-based cloud service (that google uses for Web Speech API implementation) TTS and SST code as FOSS.

Technically you can use Google API key shipped in the browser see guest271314/ GoogleNetworkSpeechSynthesis . No need to sign up for a Google account to use this. I don't think Google's TTS is related to "AI".

This is how you can make the request yourself GoogleNetworkSpeechSynthesis.

If anybody want to build a TTS "module" or "component" that accepts and processes SSML input, and that the user can control - to an appreciable degree - on the front-end you can play around with this https://github.com/guest271314/GoogleNetworkSpeechSynthesis. (Makes an external request). Have fun!

It is possible to use Google Network Speech Synthesis service "free of charge", see GoogleNetworkSpeechSynthesis. On Chrome if you use Google voices with SpeechSynthesisUtterance() and window.speechSynthesis.speak() you are doing that anyway.

I implemented SSML parsing in JavaScript by hand for Web Speech API per SSML specification https://github.com/guest271314/SSMLParser, where the Web Speech API nor Firefox nor Chrome or Chromium browsers (Google does implement SSML parsing as a service https://github.com/guest271314/GoogleNetworkSpeechSynthesis) have implemented SSML parsing.

FYI when Google voices are used on Chrome or Chromium-based browsers the browser also makes a remote request, see https://github.com/guest271314/GoogleNetworkSpeechSynthesis.

How is processing SSML an attack vector? Google provides that capability as a service - with embedded limitations on character input that are not specified. This can and should be implemented in the browser - without making an external request; native-messaging-espeak-ng, GoogleNetworkSpeechSynthesis.

I'm just trying to use coqui-ai/TTS so I can stream speech synthesis output to the browser as I do with eSpeak NG https://github.com/guest271314/native-messaging-espeak-ng. I think the issue has been brought up before on GitHub. I have not read a solution. I am ready to try again if you can suggest a minimal build process.

You can use a Native Messaging host to run local code controlled from the browser. See native-messaging-deno for a general purpose and extensible solution and deno-server where Deno's serveTls is dynamically started to run a local application, stream stdout from the application to the browser, then stop the local server.

A single page Deno server can be found here https://github.com/guest271314/native-messaging-espeak-ng/blob/deno-server/local_server.js. I have used this source code // https://github.com/chcunningham/atomics-post-message/blob/main/server.js, renamed to server.msj modified to use Ecmascript Modules instead of CommonJS, e.g.,

I've already achieved the requirement multiple ways, already; from using Native Messaging https://github.com/guest271314/native-messaging-espeak-ng, to using GNU Core Utilities tail, to Deno.watchFs() https://github.com/guest271314/fs, et al., see captureSystemAudio. The one approach I have not yet achieved is compiling to Emscripten - with SSML support.

Create a self-signed certificate. If you are on Chromium or Chrome launch with --ignore-certificate-errors-spki-list=.... Read this https://github.com/GoogleChrome/samples/blob/gh-pages/webtransport/webtransport_server.py#L42-L72. This is how I use HTTPS for Deno and Node local servers and WebTransport https://github.com/guest271314/native-messaging-espeak-ng/tree/deno-server.

I use the source code for Deno's serveTls https://github.com/guest271314/native-messaging-espeak-ng/blob/deno-server/local_server.js and wrote a Web server module for QuickJS https://github.com/guest271314/webserver-c/tree/quickjs-webserver.

This https://github.com/guest271314/native-messaging-espeak-ng/tree/deno-server is what I do using Deno

I created https://github.com/guest271314/native-messaging-espeak-ng which provides a means to send text or SSML to the eSpeak NG speech synthesis engine and parse the generated WAV in the browser. That bypasses waiting around another N years for Google to prioritize Web Speech API, which I see no evidence of Google doing - except for its cloud service.

I merely read the article to see how the author was implementing "Text-to-Speech"; how they implemented "Text-to-Speech"; e.g., native-messaging-espeak-ng to overcome or avoid the multiple issues and limitations with using the specified Web Speech API in the browser.