Hey @FAster77,
To get to the bottom of it, could you share two things?
- A screenshot of your MIDI mappings (the full list).
- The actual contents of the script you’re running.
I’m looking forward to your reply!
Hey @agustinvolpe ,
so first, here is my canvas:
the small black boxes underneath the gold inputs have a color toggle message, and they change color from black to red whenever a setShared is set to true or false. each small box has it’s own setShared.
the scrips look like this, all recieving from the pandamidi device:
and every script looks like this:
// channel 1
if(midi.type === "note-on" && midi.channel === 1) {
setShared("ch1", true);
await sleep(30)
setShared("ch1", false);
}
each with it’s own shared. the second one looks like this:
// channel 2
if(midi.type === "note-on" && midi.channel === 2) {
setShared("ch2", true);
await sleep(30)
setShared("ch2", false);
}
and so on.
As it stands now, it would not make a difference if I had them all in one script or in seperate scripts, because every midi event from the pandamidi, which are all controllers (keys1, keys2, drumpad, kick, snare, bar-trigger, launchpad) on the same device, but on different midi channels.
If I could set a script to only listen to channel 1 but “any note” (feature request), then the scripts would not get retriggered everytime, as each script only responds to said channel.
right now, every script restarts at every midi event, every time.
please ask some more if you need further explanations of the setup.
thanks for your time and patience!
Hey @FAster77,
Following up on your “any note” request: AbleSet 3.2.0 beta 2 added an option to map a command to any MIDI note, similar to the “Any Value” trigger for CCs, PCs and Notes.
You can download the latest beta here: AbleSet 3.2.0 beta 10. Since it’s a beta, I’d recommend testing it with your setup before using it live.
Would that work for your use case?