Voice recognition and hotkeys.
I experimented with using voice recognition to trigger different things. In the video below you can see me opening Ableton with the phrase "music time" and causing effects to turn on and off using the word "octopus". Windows speech recognition picks up any sound coming through the audio device you set for it with even percussive sounds being picked up as sibilants and triggering unwanted actions. There is an example of this the last time I trigger octopus in the video.
I also used hotkeys in the video both on it's own (I press m on the keyboard to trigger slice to midi (an action that isn't accessible via Lives API)) and combined with WSR to create a more complex macro that turns effects on and off. In this video it works fairly smoothly but, as I'll explain further on, high cpu usage can cause these macros to be unreliable.
Simple speech macro that opens a specific path when it receives the specified word or phrase
WSR macro using Unicode that triggers key presses. I mistakenly used this one in the video alongside a hotkey macro that triggered more key presses. Although it was interesting to see that it worked (having two macros pressing different keys simultaneously) I hadn't assigned any extra key commands within Ableton so it resulted in unexpected behaviour.
A WSR macro that I didn't use in the video. It simply triggers the space bar which in turn starts playback. I also made another macro that used the word stop to trigger the space bar.
At first, every time I restarted my computer I was required to create a new digital signature when I created a macro. This resulted in a file full of useless digital signatures. I solved this by setting the security level to low.
The Hotkey script that triggers an audio track to be sliced to midi. I had to experiment a lot to get the timings as fast as possible, particularly after the dialogue box opens. I originally used a different piece of HotKey software but after trying this discovered it wouldn't press keys after the dialogue box had opened.
HotKey script that is triggered by pressing b. This is the macro triggered with "octopus". Again I experimented with timings to create different effects. Simpler HotKeys triggering events in Max that in turn trigger other events would allow the events triggered to be tempo synced.
The idea was to create a looper that could provide a creative workflow by combining differently effected versions of the same loop. I wanted to record into poke~ send the audio to the buffer~ and then play it back with three different groove~ objects.
In this snapshot we see incoming audio being sent to poke~ to be recorded and to abs~ to get the amplitude data. Once the audio goes over the peak it will trigger a bang, onebang only allows one bang through until it receives a bang in its right input. This bang is sent to count~ which triggers poke~ to start recording. Recording is stopped by pressing space bar. In this version count~ is also receiving the length that should be recorded- dspstate gives us the sample rate to seconds and we times it by four to get for seconds.
This section allows me to clear the buffer~
This section contains the playback devices. I send each one to a different filter and can change the playback speed and direction of each filtered groove~. Ideally I will add a button that allows me to start all the groove~s from the same point again.