We have upgraded our setup to Daslight 5 recently. I use an akai APC 40 mkII and I saw that in Daslight 5 it is possible to midi-map these buttons (see image below)
I mapped those buttons to these buttons on my akai (see image below) accordingly: MIDI input from the akai to turn of off when pressed and output to the akai to activate the button's led for feedback when the option is turned on. So when the button is lit in Daslight, I want the button on the akai to light up.
So what I expect from this is that each time I change the value of a fader on my akai, the button on top of that fader should light up (see image above). This works just fine when I only setup it for 4 buttons and 4 faders, but when I map it for 5 or more buttons, it starts to fail. What happens is that changing a fader's value do not activate the corresponding led immediately, it takes many changes of the fader until it finally lights on, and sometimes it does not light up at all. I've been troubleshooting (by reading the MIDI data sent from Daslight to the akai using a virtual cable) this issue and I can bring this information to the table:
- Daslight sends MIDI information to the akai when it receives midi, which is normal, but it sends the info for all leds each time a fader moved. So each time the akai sends new control information from a fader, Daslight updates ALL feedback leds wich is less normal... Isn't it more logical to update a led only if the associated button state changed?
- The previous point shouldn't be in theory a problem, but it appears that in this ocean of MIDI messages sent to the akai, some MIDI messages are skipped. In the following test, I only changed the second fader value, so in theory the led in channel 1 should turn on (velocity=1), the lines below correspond to the MIDI messages sent to akai from Daslight :
As you can see, only changing the second fader's value makes Daslight send midi messages to all the buttons (randomly?), but the worst of all is that it misses the second led (no messages directed to channel 1) and therefore the light on the akai does not turn on
Code: Select all
note_on channel=5 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=5 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=6 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=5 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=5 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=5 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=3 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=5 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=5 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=5 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=5 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=5 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=5 note=48 velocity=0 time=0 note_on channel=6 note=48 velocity=0 time=0 note_on channel=7 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=5 note=48 velocity=0 time=0 note_on channel=6 note=48 velocity=0 time=0 note_on channel=7 note=48 velocity=0 time=0 note_on channel=0 note=48 velocity=0 time=0 note_on channel=2 note=48 velocity=0 time=0 note_on channel=3 note=48 velocity=0 time=0 note_on channel=4 note=48 velocity=0 time=0 note_on channel=5 note=48 velocity=0 time=0 note_on channel=6 note=48 velocity=0 time=0 note_on channel=7 note=48 velocity=0 time=0
Regards,
Remy