Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/CharlieEtienne/t2s
Google TextToSpeech 2 mp3
https://github.com/CharlieEtienne/t2s
google-text-to-speech ssml ssml-editor texttospeech
Last synced: 3 months ago
JSON representation
Google TextToSpeech 2 mp3
- Host: GitHub
- URL: https://github.com/CharlieEtienne/t2s
- Owner: CharlieEtienne
- License: mit
- Created: 2021-06-07T20:35:41.000Z (about 3 years ago)
- Default Branch: master
- Last Pushed: 2024-02-11T09:26:13.000Z (5 months ago)
- Last Synced: 2024-02-11T10:25:39.214Z (5 months ago)
- Topics: google-text-to-speech, ssml, ssml-editor, texttospeech
- Language: JavaScript
- Homepage:
- Size: 453 KB
- Stars: 15
- Watchers: 3
- Forks: 4
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Lists
- awesome-stars - CharlieEtienne/t2s - Google TextToSpeech 2 mp3 (JavaScript)
README
# Google TextToSpeech 2 mp3
![2021-08-06_17h12_54](https://user-images.githubusercontent.com/9772943/128532513-0c71f4a1-cf5a-409d-a8e7-f5b3d98a4c35.png)
Download mp3 from Google Text to Speech API
This app provides a simple way to convert Google Text to Speech audio to a mp3 file you can download.
## Features
- SSML editor (prosody, emphasis, break, spell-out)
- Syntaxic highlight
- Code editor/visual editor
- Dark mode
- RSS feed of cloud.google.com Text to Speech releases## Installation
1. Copy files from this repository into your project
2. Run `composer install`
3. Follow [these steps](https://cloud.google.com/text-to-speech/docs/quickstart-client-libraries) to configure and activate your api and credentials
4. Copy the content of your credentials file into `PROJECT_NAME.credentials.json` (replace `PROJECT_NAME` with your actual project complicated and secret name)
5. Copy `.env.example` to `.env` and set `GOOGLE_APPLICATION_CREDENTIALS` to the `PROJECT_NAME.credentials.json` actual filename
## Warning
> Please be aware that with this code your credentials may be exposed. If you plan to make this public, you should protect them by renaming, moving the json file and block public access (for example with htaccess methods) to .env file and credentials json file.
## Contributors
- [PabloGuyez](https://github.com/PabloGuyez)
- [CharlieEtienne](https://github.com/CharlieEtienne)## Contribution
Feel free to open issues or PRs!