{"id":2796,"date":"2021-06-22T23:18:01","date_gmt":"2021-06-22T23:18:01","guid":{"rendered":"https:\/\/wordpress-634681-2064240.cloudwaysapps.com\/?p=2796"},"modified":"2021-06-25T11:14:11","modified_gmt":"2021-06-25T11:14:11","slug":"azure-percept-audio-first-steps","status":"publish","type":"post","link":"https:\/\/www.petecodes.co.uk\/azure-percept-audio-first-steps\/","title":{"rendered":"Azure Percept Audio – First Steps"},"content":{"rendered":"\n

In the first post in this series<\/a> we took a first look at the Azure Percept and it’s primary components.<\/p>\n\n\n\n

In this post we’ll take a look at the Azure Percept Audio Module, which allows for the recognition of Custom Keywords and Commands.<\/p>\n\n\n\n

Azure Percept Audio<\/h2>\n\n\n\n
\"Azure<\/a>
Azure Percept Audio<\/figcaption><\/figure><\/div>\n\n\n\n

The Azure Percept Audio is a System on a Module (SoM), which is designed as the Audio Interface for Audio Processing at the edge for the Azure Percept.<\/p>\n\n\n\n

Along with the Carrier Board, Azure Percept Studio, Microsoft LUIS and Speech, the system can recognise keywords and commands to control devices using voice at the edge. This works both online and offline with the aid of the Carrier Board.<\/p>\n\n\n\n

Azure Percept Audio Specifications<\/h2>\n\n\n\n

The basic specs for the Azure Percept Audio SoM are;<\/p>\n\n\n\n