SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
SDL TTS (Text to Speech) is a plugin which allows you to listen to the audio of a segment (source or target) or to the entire file. We use the Micosoft Azure Text to Speech solution which is available through their Cognitive Services to generate the audio file.
This a is paid service provided by Microsoft, currently the first 5 million characters /month are free. To use it you'll have to create an Azure account and generate the API key in order to use it in the TTS plugin.
More details about the service billing can be found here.
After you create an Azure account, please login into the Azure Portal and search for "Cognitive services"; then from Marketplace select "Cognitive Services":
A new page will appear where you need to enter details for your Subscription, Location and Resource group (if you don't already have a resource group you'll have to create one).
The location of the service is very important, please choose a location near you because this will affect the speed of the TTS plugin.
After the service was created successfully in the Azure Portal select the Service by clicking on its name -> Quick Start
The API key will be used for the TTS plugin.
SDL TTS can be opened in the following ways:
By default the TTS plugin is minimized. A bar will appear at the top of the screen. When you hover on the bar the action options will be expanded:
When you hover over the bar it will display like this:
In the Files View select the files you want to use SDL TTS with, activate "Tell Me" and type TTS into the entry field. Finally select "Open TTS" from the search results.
The selected files will be opened in the Studio Editor and the SDL TTS plugin will be available at the top of the screen. The next step is to configure the settings by clicking on the Settings icon.
The Account options is where you will add the API key generated in the Azure portal. You also need to choose the Account region you selected when you created the account. The Selected Account region in the SDL TTS plugin must match the region from Azure Portal.
"Playback all segments" is unchecked by default. If you want to generate an audio file for the whole document (source or target segments) then check this option. Note that this could take a litle while for large files.
The audio file is saved locally in the following folder structure: Project Name -> Language Pair -> FileName.wav file at:
C:\Users\[username]\AppData\Roaming\SDL Community\SDL TTS\Playback audio local path
"Source/Target playback" allows you to select whether you wish to listen to the text for the source or target segments.
"Available devices" allows you to select a footpedal from the list of supported devices.The first device available in the list will be selected by default. Note that the SDL TTS plugin only supports footpedals using the USB HID driver supplied by VEC. An example would be the Infinity USB Foot Pedal (IN-USB-2).
Playback speed can be changed any time using "Speed" button. By default is set to 1. If you hover on the button a tooltip will appear with the selected speed.
To change the speed click on "Speed" button and from dropdown select the speed:
Select the segment you wish to listen to in the Editor and press "Play" . A loading window will appear on screen and the Play button will be disabled. After the audio file is received from Microsoft the loading message will disappear and the audio will start automatically. Typically this is quite fast, but for long sentences you might have a lag for a few seconds.
After the audio starts you can Pause the playback at any time. When the playback is paused the "Play" button will be enabled and you will be able to resume the playback from the position you paused it. Alternatively you can use "Replay" and this will restart the audio from the begining.
If you click on "Stop" the audio will not be available anymore. If you want to hear the segment again you'll have to click on "Play". This means we'll make another request to the Microsoft service and you'll be charged with the number of characters used.
If you want to listen another segment just navigate to it in the Editor and click "Play".
Right pedal - move to the next segment. If you hold the pedal down you will navigate through the segments automatically until you release the pedal.
Left pedal - move to the previous segment. If you hold the pedal down you will navigate through the segments automatically until you release the pedal.
Middle pedal - Play/ Pause the sound. To hear the audio playback press and hold the middle pedal. To pause the audio simply release the footpedal.
There are no default shortcuts, so these must be set by each user in order to become available in the plugin. When you set a key combination please make sure is not already used in Studio as there may not be an warning. If the shortcut fails to work the most likely reason is duplicate shortcuts.
An additional piece of functionality provided by the shortcuts is to :
At this point Microsoft Text to Speech Service supports 45 languages. TTS language mapping view allows the user to select another language variant for the active project in the Editor.
When a file is open in the Editor if there are any unsupported languages in the project this window will appear.
The Language table will be autopopulated with the unsupported languages detected in the active project. The Supported Languages dropdown list is populated with the Supported variants provided by Microsoft Cognitive services.
Save language mapping option
By default this option is unchecked, if you check this option the next time you open the project in the Editor, the Languages Mapping view will not be displayed any more and the languages selected previously will be used by the TTS.
If the "save language mappings" option is checked when you select a different variant you won't see the mappings View again until you remove the mappings for the active project. This option is availabe in the "Settings" view:
After you click on the Remove option a confirmation message will appear. After the form is closed by clicking on the "OK" button, the language mappings view will automatically appear.
If all the languages for the active project are supported by Microsoft this option will be disabled:
Language Mapping option in Files View
This option will not be visible when you open the "Settings" page from Files Controller unless one file from the selected project is open in the editor. Then you can edit the language mappings for all unsupported languages and the changes will also be reflected in the Editor View.
The plugin has a logging system which logs the errors in a text file. These can be found at the following location: