Hi there,
Its been a while crocodile, we are back on track.
So I have made for myself this Device that joins together many of the devices I have developed in order to control Ableton Live , so It was working nicely , and I wanted to achieve another functionality. Why not create an additional instance of virtual-launchpad ? As It will help me with the drums programing.
So I first I cloned the tab of the whole device and renamed it virtual-launchpad2 renaming all the midi targets of the widgets to midi:virtual-launchpad2 .
This was not working , checking in the debugging window I saw that the device was still outputing to virtual-launchpad the original despite using the buttons for virtual-launchpad2
So I decided to change this for virtual-launchpadb and it worked!! . The only problem now , it seems that the devices are messing their coloring .
Meaning when I use either of the tabs virtual-launchpad or virtual-launchpadb to navigate through the set , the buttons will light up in both of them at the same time even when the devices are been recognised as different and they still output to a different midi port
I guess that has to be with the fact that the way this widgets receive the colour is by their property
ColorWidget: JS{{
var velocityReceived = OSC{/note};
var colors = @{colors-array}
return colors[velocityReceived] || "#E0E0E0";
}}
An thisone will probably not difference in between the MIDI port that is been used.
Please take a look to the project see if you have any ideas on how to solve this.
Thank you
lagrantesta.json (936.2 KB)