{"id":2835,"date":"2021-06-24T12:31:23","date_gmt":"2021-06-24T12:31:23","guid":{"rendered":"https:\/\/wordpress-634681-2064240.cloudwaysapps.com\/?p=2835"},"modified":"2021-06-24T12:57:41","modified_gmt":"2021-06-24T12:57:41","slug":"azure-percept-audio-custom-keywords-and-commands","status":"publish","type":"post","link":"https:\/\/www.petecodes.co.uk\/azure-percept-audio-custom-keywords-and-commands\/","title":{"rendered":"Azure Percept Audio – Custom Keywords and Commands"},"content":{"rendered":"\n

In the previous post<\/a> we got started with the Azure Percept Audio System on a Module <\/a>(SoM).<\/p>\n\n\n\n

We deployed a Sample Hospitality application and saw how we could issue commands to the Percept, the Percept would respond, and the Sample Application would simulate the effects of the commands on screen.<\/p>\n\n\n\n

\"Azure<\/a>
Azure Percept Audio – Hospitality Sample Application<\/figcaption><\/figure><\/div>\n\n\n\n

In this post we’ll take the sample further by training our own Custom keyword and creating a Custom Command.<\/p>\n\n\n\n

Custom Keywords<\/h2>\n\n\n\n

For the Azure Percept Audio, a Keyword is the word that the Percept “listens” for in order to begin listening for commands. Sometimes referred to as a “Wake-Word”, this word defaults to “Computer” in the Hospitality Sample.<\/p>\n\n\n\n

We have access to some pre-trained keywords deployed along with the sample, allowing us to choose from;<\/p>\n\n\n\n