I’m having a strange issue. I have a 4x8 group of pads that light up in the startup animation and were working a few days ago, but now only a few respond to midi. I have this script to test them using the sendmidi utility from: https://github.com/gbevin/SendMIDI
#!/bin/bash
for i in {0..31}
do
sendmidi dev "PHENOTYPE MIDI 1" ch 2 on $i 127
done
I configured all these to respond to Channel 2, Notes 0 - 31. Yet only Notes 1, 5, 9, 13, 17, 21, 25 work. Up until a few minutes ago, 29 worked also. And after pushing the default config and reloading my config, note 29 works again! The configurations are identical except for the note number. The pads do work with the default configuration.
Not working pad:
Working pad:
The only difference is the note number. I’ve tried changing the note number and channel of the not working lights but nothing seems to work. Restoring the default configuration, it does work with the default config. It was working fine a few days ago and I haven’t changed anything with this part of the configuration. I’m not sure why they are not responding anymore. In the default configuration, they do light up (though other pads set to the same messages do too as that’s how it’s configured). The script to test the default config is:
#!/bin/bash
for i in {64..95}
do
sendmidi dev "PHENOTYPE MIDI 1" ch 2 on $i 127
done
Default config:
default.ytx (404.7 KB)
Custom config:
phenotype.ytx (403.8 KB)
I’m thinking this is possibly an issue with the configuration loading or being sent to the controller since that note 29 stopped working and started working after I loaded the default config followed by loading my custom config. Not really sure what is happening or how to get these pads responding to midi again.