Skip to content

Latest commit

 

History

History
73 lines (60 loc) · 2.54 KB

GET_YOUR_KEYS.md

File metadata and controls

73 lines (60 loc) · 2.54 KB

Get your Keys

This documentation helps you to find the right keys for Azure Cognitive Services in order to use GLUE.

Text to Speech (TTS)

Before setting the keys, you should get the audio driver ffmpeg.

ffmpeg

In this section, we describe how to set up ffmpeg in case you do TTS.

Windows

  • Download the latest version of ffmpeg.
  • Extract the archive locally and copy the file bin/ffpmeg.exe to a location of your choice, e.g. to the assets folder of GLUE.
  • Add the location to the system environment variables "PATH" setting.
  • Finally, copy the path and insert it in your config.ini as below.
[driver]
path=C:/glue/assets/ffmpeg.exe

Ubuntu / Linux

  • Open your command line.
  • Make sure you have enough access rights to execute a sudo command or use the command line as root (not recommended).
  • Install ffmpeg using the apt-get package manager.
apt-get install ffmpeg

Keys

  • Go to the Azure portal, open the Cognitive Service resource you want to use.
  • Be aware that not every voice is available in every Azure region.

Microsoft Speech Service portal

[tts]
key=
region=
resource_name=
language=
font=

Speech to Text (STT)

  • Go to the Microsoft Speech Service portal, open your respective case and follow the breadcrumbs as illustrated below.
  • Copy the values from the highlighted fields.
  • In case you are not using a custom endpoint, it is sufficient to copy the subscription key as well as the region from your Azure Cogntitive Service resource in the Azure portal.

Speech Resources

The final file should look as below:

[stt]
key=
endpoint=
region=

LUIS

Open the file and set the respective keys for the [luis]-section. You can ignore the other parts. For this purpose, go to your LUIS app by accessing the portal. Click on your app and click MANAGE. In the Settings-section, copy the App ID and insert it in the file. Afterwards, go to Azure Resources below, make sure you are in the tab Prediction Resources and copy + paste the following keys and names.

LUIS Resources

For slot, either insert staging or production, depending which deployment slot you are using with your LUIS model. Region can remain blank.

The final section should look as below (fictional keys):

[luis]
key=
app_id=
endpoint=
region=
slot=
treshold=0