-->
GhostReader 2.4 macOS. GhostReader is an easy to use, fully customizable Text to Speech app that allows you to listen to written text on your Mac. Read selected texts from other applications, import texts in almost every format and listen to them on the go. GhostReader 2.4 macOS. GhostReader is an easy to use, fully customizable Text to Speech app that allows you to listen to written text on your Mac. Read selected texts from other applications, import texts in almost every format and listen to them on the go. February 25, 2021 GhostReader Plus is an easy to use, fully customizable Text to Speech app that allows you to listen to written text on your Mac. Read selected texts from other applications, import texts in almost every format and listen to them on the go. It’s text-to-speech software for Mac OS X that features high quality, multilingual voices. It’s priced starting at $39.95. GhostReader converts text to speech which you can use to listen to.
The Speech service allows you to convert text into synthesized speech and get a list of supported voices for a region using a set of REST APIs. Each available endpoint is associated with a region. A subscription key for the endpoint/region you plan to use is required.
The text-to-speech REST API supports neural and standard text-to-speech voices, each of which supports a specific language and dialect, identified by locale.
- For a complete list of voices, see language support.
- For information about regional availability, see regions.
Important
Costs vary for standard, custom, and neural voices. For more information, see Pricing.
Before using this API, understand:
- The text-to-speech REST API requires an Authorization header. This means that you need to complete a token exchange to access the service. For more information, see Authentication.
Tip
See this article for Azure Government and Azure China endpoints. Tipard blu ray converter for mac 9 2 18.
Authentication
Each request requires an authorization header. This table illustrates which headers are supported for each service:
Supported authorization headers | Speech-to-text | Text-to-speech |
---|---|---|
Ocp-Apim-Subscription-Key | Yes | Yes |
Authorization: Bearer | Yes | Yes |
When using the
Ocp-Apim-Subscription-Key
header, you're only required to provide your subscription key. For example:When using the
Authorization: Bearer
header, you're required to make a request to the issueToken
endpoint. In this request, you exchange your subscription key for an access token that's valid for 10 minutes. In the next few sections you'll learn how to get a token, and use a token.How to get an access token
To get an access token, you'll need to make a request to the
issueToken
endpoint using the Ocp-Apim-Subscription-Key
and your subscription key.The
issueToken
endpoint has this format:Replace
<REGION_IDENTIFIER>
with the identifier matching the region of your subscription from this table:Geography | Region | Region identifier |
---|---|---|
Americas | Central US | centralus |
Americas | East US | eastus |
Americas | East US 2 | eastus2 |
Americas | North Central US | northcentralus |
Americas | South Central US | southcentralus |
Americas | West Central US | westcentralus |
Americas | West US | westus |
Americas | West US 2 | westus2 |
Americas | Canada Central | canadacentral |
Americas | Brazil South | brazilsouth |
Asia Pacific | East Asia | eastasia |
Asia Pacific | Southeast Asia | southeastasia |
Asia Pacific | Australia East | australiaeast |
Asia Pacific | Central India | centralindia |
Asia Pacific | Japan East | japaneast |
Asia Pacific | Japan West | japanwest |
Asia Pacific | Korea Central | koreacentral |
Europe | North Europe | northeurope |
Europe | West Europe | westeurope |
Europe | France Central | francecentral |
Europe | UK South | uksouth |
Use these samples to create your access token request.
HTTP sample
This example is a simple HTTP request to get a token. Replace
YOUR_SUBSCRIPTION_KEY
with your Speech Service subscription key. If your subscription isn't in the West US region, replace the Host
header with your region's host name.The body of the response contains the access token in JSON Web Token (JWT) format.
PowerShell sample
This example is a simple PowerShell script to get an access token. Replace
YOUR_SUBSCRIPTION_KEY
with your Speech Service subscription key. Make sure to use the correct endpoint for the region that matches your subscription. This example is currently set to West US.cURL sample
cURL is a command-line tool available in Linux (and in the Windows Subsystem for Linux). This cURL command illustrates how to get an access token. Replace
YOUR_SUBSCRIPTION_KEY
with your Speech Service subscription key. Make sure to use the correct endpoint for the region that matches your subscription. This example is currently set to West US.C# sample
This C# class illustrates how to get an access token. Pass your Speech Service subscription key when you instantiate the class. If your subscription isn't in the West US region, change the value of
FetchTokenUri
Peel cracked download free. to match the region for your subscription.Python sample
How to use an access token
The access token should be sent to the service as the
Authorization: Bearer <TOKEN>
header. Each access token is valid for 10 minutes. You can get a new token at any time, however, to minimize network traffic and latency, we recommend using the same token for nine minutes.Here's a sample HTTP request to the Speech-to-text REST API for short audio:
Get a list of voices
The
voices/list
endpoint allows you to get a full list of voices for a specific region/endpoint.Regions and endpoints
Region | Endpoint |
---|---|
Australia East | https://australiaeast.tts.speech.microsoft.com/cognitiveservices/voices/list |
Brazil South | https://brazilsouth.tts.speech.microsoft.com/cognitiveservices/voices/list |
Canada Central | https://canadacentral.tts.speech.microsoft.com/cognitiveservices/voices/list |
Central US | https://centralus.tts.speech.microsoft.com/cognitiveservices/voices/list |
East Asia | https://eastasia.tts.speech.microsoft.com/cognitiveservices/voices/list |
East US | https://eastus.tts.speech.microsoft.com/cognitiveservices/voices/list |
East US 2 | https://eastus2.tts.speech.microsoft.com/cognitiveservices/voices/list |
France Central | https://francecentral.tts.speech.microsoft.com/cognitiveservices/voices/list |
India Central | https://centralindia.tts.speech.microsoft.com/cognitiveservices/voices/list |
Japan East | https://japaneast.tts.speech.microsoft.com/cognitiveservices/voices/list |
Korea Central | https://koreacentral.tts.speech.microsoft.com/cognitiveservices/voices/list |
North Central US | https://northcentralus.tts.speech.microsoft.com/cognitiveservices/voices/list |
North Europe | https://northeurope.tts.speech.microsoft.com/cognitiveservices/voices/list |
South Africa North | https://southafricanorth.tts.speech.microsoft.com/cognitiveservices/voices/list |
South Central US | https://southcentralus.tts.speech.microsoft.com/cognitiveservices/voices/list |
Southeast Asia | https://southeastasia.tts.speech.microsoft.com/cognitiveservices/voices/list |
UK South | https://uksouth.tts.speech.microsoft.com/cognitiveservices/voices/list |
West Central US | https://westcentralus.tts.speech.microsoft.com/cognitiveservices/voices/list |
West Europe | https://westeurope.tts.speech.microsoft.com/cognitiveservices/voices/list |
West US | https://westus.tts.speech.microsoft.com/cognitiveservices/voices/list |
West US 2 | https://westus2.tts.speech.microsoft.com/cognitiveservices/voices/list |
Tip
Voices in preview are only available in these 3 regions: East US, West Europe and Southeast Asia.
Request headers
This table lists required and optional headers for text-to-speech requests.
Header | Description | Required / Optional |
---|---|---|
Ocp-Apim-Subscription-Key | Your Speech service subscription key. | Either this header or Authorization is required. |
Authorization | An authorization token preceded by the word Bearer . For more information, see Authentication. | Either this header or Ocp-Apim-Subscription-Key is required. |
Request body
A body isn't required for
GET
requests to this endpoint.Sample request
This request only requires an authorization header.
Sample response
This response has been truncated to illustrate the structure of a response.
HTTP status codes
The HTTP status code for each response indicates success or common errors.
HTTP status code | Description | Possible reason |
---|---|---|
200 | OK | The request was successful. |
400 | Bad Request | A required parameter is missing, empty, or null. Or, the value passed to either a required or optional parameter is invalid. A common issue is a header that is too long. |
401 | Unauthorized | The request is not authorized. Check to make sure your subscription key or token is valid and in the correct region. |
429 | Too Many Requests | You have exceeded the quota or rate of requests allowed for your subscription. |
502 | Bad Gateway | Network or server-side issue. May also indicate invalid headers. |
Convert text-to-speech
The
v1
endpoint allows you to convert text-to-speech using Speech Synthesis Markup Language (SSML).Regions and endpoints
These regions are supported for text-to-speech using the REST API. Make sure that you select the endpoint that matches your subscription region.
Standard and neural voices
Use this table to determine availability of standard and neural voices by region/endpoint:
Region | Endpoint | Neural Voices | Standard Voices |
---|---|---|---|
Australia East | https://australiaeast.tts.speech.microsoft.com/cognitiveservices/v1 | Yes | Yes |
Brazil South | https://brazilsouth.tts.speech.microsoft.com/cognitiveservices/v1 | No | Yes |
Canada Central | https://canadacentral.tts.speech.microsoft.com/cognitiveservices/v1 | Yes | Yes |
Central US | https://centralus.tts.speech.microsoft.com/cognitiveservices/v1 | No | Yes |
East Asia | https://eastasia.tts.speech.microsoft.com/cognitiveservices/v1 | No | Yes |
East US | https://eastus.tts.speech.microsoft.com/cognitiveservices/v1 | Yes | Yes |
East US 2 | https://eastus2.tts.speech.microsoft.com/cognitiveservices/v1 | No | Yes |
France Central | https://francecentral.tts.speech.microsoft.com/cognitiveservices/v1 | No | Yes |
India Central | https://centralindia.tts.speech.microsoft.com/cognitiveservices/v1 | Yes | Yes |
Japan East | https://japaneast.tts.speech.microsoft.com/cognitiveservices/v1 | No | Yes |
Japan West | https://japanwest.tts.speech.microsoft.com/cognitiveservices/v1 | No | Yes |
Korea Central | https://koreacentral.tts.speech.microsoft.com/cognitiveservices/v1 | No | Yes |
North Central US | https://northcentralus.tts.speech.microsoft.com/cognitiveservices/v1 | No | Yes |
North Europe | https://northeurope.tts.speech.microsoft.com/cognitiveservices/v1 | No | Yes |
South Central US | https://southcentralus.tts.speech.microsoft.com/cognitiveservices/v1 | Yes | Yes |
Southeast Asia | https://southeastasia.tts.speech.microsoft.com/cognitiveservices/v1 | Yes | Yes |
UK South | https://uksouth.tts.speech.microsoft.com/cognitiveservices/v1 | Yes | Yes |
West Europe | https://westeurope.tts.speech.microsoft.com/cognitiveservices/v1 | Yes | Yes |
West US | https://westus.tts.speech.microsoft.com/cognitiveservices/v1 | No | Yes |
West US 2 | https://westus2.tts.speech.microsoft.com/cognitiveservices/v1 | Yes | Yes |
Tip
Voices in preview are only available in these 3 regions: East US, West Europe and Southeast Asia.
Custom voices
If you've created a custom voice font, use the endpoint that you've created. You can also use the endpoints listed below, replacing the
{deploymentId}
Easy audio mixer 2 5 0 – audio editor tool. with the deployment ID for your voice model.Region | Endpoint |
---|---|
Australia East | https://australiaeast.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
Brazil South | https://brazilsouth.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
Canada Central | https://canadacentral.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
Central US | https://centralus.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
East Asia | https://eastasia.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
East US | https://eastus.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
East US 2 | https://eastus2.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
France Central | https://francecentral.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
India Central | https://centralindia.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
Japan East | https://japaneast.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
Japan West | https://japanwest.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
Korea Central | https://koreacentral.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
North Central US | https://northcentralus.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
North Europe | https://northeurope.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
South Central US | https://southcentralus.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
Southeast Asia | https://southeastasia.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
UK South | https://uksouth.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
West Europe | https://westeurope.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
West US | https://westus.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
West US 2 | https://westus2.voice.speech.microsoft.com/cognitiveservices/v1?deploymentId={deploymentId} |
Custom Neural Voice
The following table details regional support for Custom Neural Voice features.
Feature | Supported regions |
---|---|
Voice model hosting | East US, West US 2, South Central US, Southeast Asia, UK South, West Europe, Australia East |
Realtime Characters | East US, West US 2, South Central US, Southeast Asia, UK South, West Europe, Australia East |
Long Audio Characters | East US, West Europe, UK South, Southeast Asia, India Central |
Custom Neural Training | East US, UK South |
Long audio API
The Long audio API is available in multiple regions with unique endpoints.
Region | Endpoint |
---|---|
East US | https://eastus.customvoice.api.speech.microsoft.com |
India Central | https://centralindia.customvoice.api.speech.microsoft.com |
Southeast Asia | https://southeastasia.customvoice.api.speech.microsoft.com |
UK South | https://uksouth.customvoice.api.speech.microsoft.com |
West Europe | https://westeurope.customvoice.api.speech.microsoft.com |
Request headers
This table lists required and optional headers for text-to-speech requests.
Header | Description | Required / Optional |
---|---|---|
Authorization | An authorization token preceded by the word Bearer . For more information, see Authentication. | Required |
Content-Type | Specifies the content type for the provided text. Accepted value: application/ssml+xml . | Required |
X-Microsoft-OutputFormat | Specifies the audio output format. For a complete list of accepted values, see audio outputs. | Required |
User-Agent | The application name. The value provided must be less than 255 characters. | Required |
Ghostreader 2 3 – Easy To Use Text To Speech
Audio outputs
This is a list of supported audio formats that are sent in each request as the
X-Microsoft-OutputFormat
header. Each incorporates a bitrate and encoding type. The Speech service supports 24 kHz, 16 kHz, and 8 kHz audio outputs.Note
If your selected voice and output format have different bit rates, the audio is resampled as necessary.ogg-24khz-16bit-mono-opus can be decoded with opus codec
Request body
The body of each
POST
request is sent as Speech Synthesis Markup Language (SSML). SSML allows you to choose the voice and language of the synthesized speech returned by the text-to-speech service. For a complete list of supported voices, see language support.Note
If using a custom voice, the body of a request can be sent as plain text (ASCII or UTF-8).
Sample request
This HTTP request uses SSML to specify the voice and language. If the body length is long, and the resulting audio exceeds 10 minutes - it is truncated to 10 minutes. In other words, the audio length cannot exceed 10 minutes.
Ghostreader 2 3 – Easy To Use Text To Speech On Google Docs
HTTP status codes
The HTTP status code for each response indicates success or common errors.
HTTP status code | Description | Possible reason |
---|---|---|
200 | OK | The request was successful; the response body is an audio file. |
400 | Bad Request | A required parameter is missing, empty, or null. Or, the value passed to either a required or optional parameter is invalid. A common issue is a header that is too long. |
401 | Unauthorized | The request is not authorized. Check to make sure your subscription key or token is valid and in the correct region. |
415 | Unsupported Media Type | It's possible that the wrong Content-Type was provided. Content-Type should be set to application/ssml+xml . |
429 | Too Many Requests | You have exceeded the quota or rate of requests allowed for your subscription. |
502 | Bad Gateway | Network or server-side issue. May also indicate invalid headers. |
If the HTTP status is
200 OK
, the body of the response contains an audio file in the requested format. This file can be played as it's transferred, saved to a buffer, or saved to a file.