{"id":3956,"date":"2021-12-08T10:56:18","date_gmt":"2021-12-08T09:56:18","guid":{"rendered":"https:\/\/www.pschatzmann.ch\/home\/?p=3956"},"modified":"2024-02-29T03:55:29","modified_gmt":"2024-02-29T02:55:29","slug":"using-the-ai-thinker-audio-kit-buttons","status":"publish","type":"post","link":"https:\/\/www.pschatzmann.ch\/home\/2021\/12\/08\/using-the-ai-thinker-audio-kit-buttons\/","title":{"rendered":"Using the AI Thinker Audio Kit Buttons"},"content":{"rendered":"

As you might know from my last posts<\/a> I am currently extending my Arduino Audio Tools<\/a> library to support the AI Thinker Audio Kit<\/a> which is based on the ES8388 audio chip.
\n.<\/p>\n

Originally I was of the opinion that the program logic for reading of the GPIO pins<\/strong> and the processing of the related actions should belong into a specific Arduino sketch<\/strong> and should not be part of an Audio Framework.<\/p>\n

The Audio Kit<\/strong> made me revise this because I think that an Arduino Sketch should be as concise as possible<\/strong>. Therefore I have created the AudioActions class that has been integrated into the AudioKit.<\/p>\n

\"Audio<\/p>\n

Since the Audio Kit does not have any display<\/strong>, I think to use TTS<\/strong> is a good choice to feed back information to the user.<\/p>\n

Here is the example:<\/p>\n

Arduino Sketch<\/h3>\n
#include \"flite_arduino.h\"\n#include \"AudioTools.h\"\n#include \"AudioDevices\/ESP32AudioKit\/AudioKit.h\"\n\nusing namespace audio_tools;\n\nAudioKitStream kit;\nFlite flite(kit);\n\nvoid button1(){\n  flite.say(\"Button One\");  \n}\nvoid button2(){\n  flite.say(\"Button Two\");  \n}\nvoid button3(){\n  flite.say(\"Button Three\");  \n}\nvoid button4(){\n  flite.say(\"Button Four\");  \n}\n\n\/\/ Arduino setup\nvoid setup(){\n  Serial.begin(115200);\n\n  auto cfg = kit.defaultConfig();\n  cfg.bits_per_sample = 16;\n  cfg.channels = 1;\n  cfg.sample_rate = 8000;\n  kit.begin(cfg);\n\n  \/\/ Assign pins to methods\n  kit.addAction(PIN_KEY1, button1);\n  kit.addAction(PIN_KEY2, button2);\n  kit.addAction(PIN_KEY3, button3);\n  kit.addAction(PIN_KEY4, button4);\n\n  \/\/ example with actions using lambda expression\n  auto down = []() { flite.say(\"Volume down\"); kit.volumeDown(); };\n  kit.addAction(PIN_KEY5, down);\n  auto up = []() { flite.say(\"Volume up\"); kit.volumeUp();  };\n  kit.addAction(PIN_KEY6, up);\n\n  \/\/ we are ready to process actions now\n  flite.say(\"The application has started. Please push a button to select the function\");\n\n}\n\n\/\/ Arduino Loop\nvoid loop() {\n  kit.processActions();\n}\n<\/code><\/pre>\n
You just need to define you handler methods<\/strong> (button1, button2…) and assign them to the GPIO pins<\/strong>. The PIN_KEY5 and PIN_KEY6 have been predefined in the AudioKitStream to handle the volume. But you can overwrite this with your own methods – as demonstrated in the sketch.<\/p>\n
I think it could not be easier then this!<\/p>\n
Source Code<\/h3>\n
The source code for this example<\/a> can also be found on Github. Please note that this example was working at the time of publishing. If you want to try it out please use this (potentially updated) example.<\/p>\n
Dependencies<\/h3>\n
You need to install the following libraries:<\/p>\n