The versions are the same for plug-ins and standalones :
VEP 4.1.8783
VI 4.1.8777
VIP 1.1.8778
Tried to delete preference files from both Library and Home Library (VSL software and my Alesis MasterControl), reinstall, nothing changed [:(]
UPDATE :
I've made some deeper researches :
- When pluging another MIDI keyboard (my LPK25) and activating it in software preference, everything works fine on the LPK25.
- My Alesis MasterControl is a control surface with one pair of IN/OUT MIDI ports. In the drivers, the control surface MIDI ports (sending messages to control software) used to be called "Control Port", and the physical MIDI ports (where my keyboard is plugged) called "MIDI Ports".
In the latest releases of drivers from Alesis (since OS 10.6 compatible ones if I remember well), both control surface and MIDI ports are now called "Alesis MasterControl MIDI Ports" in the drivers and then appear so in all software. In VSL, I can't activate one of these ports only without having the other being activated too (because of the same name?), whereas I can in other software like PLAY or Kontakt.
When I touch buttons on my control surface, VSL software get the message since I can see the keys playing on the screen, but it doesn't work if I use my keyboard keys (so the "secondary" MIDI port). Is it because they both have the same name that VSL software is confused? Because all other software I use correctly respond to my control surface buttons, and my keyboards keys.
So is it an Alesis driver issue (though occuring only in VSL), or a VSL software bug about handling MIDI ports?
If anyone at support staff could get an eye on this issue, thank you so much!