Does anybody know how to set the MIDI Control to ‘Generic 6 knobs’ by default (and also to change it in all existing instances at once)?
While trying to use the Keylab mkII LED control scriptlet from TripleB, I still noticed sysex data was being sent to my Keylab control, even after having removed the scriptlets alltogether.
The Global MIDI Monitor did also not show any activity, so after a lot of head scratching found out I could use the MIDI Monitor tool to sniff whether there was still data being sent. And, lo and behold, there indeed still was sysex data being transmitted.
After again scratching my head and some trial and error, I figured out that each Arturia plugin seems to automatically detect the presence of the Keylab mkII control, sets the MIDI Control to the Keylab and then starts sending a lot of sysex data, which then conflicts with the data sent by the scriptlet. The sysex data is also not very useful, since I want to link the knobs and buttons with plugin parameters through widgets, of course…
When setting the MIDI Control to ‘Generic 6 knobs’, the sysex data is not transmitted anymore… So, that is the setting I would like to have in all my plugin instances. By default, when creating a new instance, and if possible also in all existing instances at once, as I fear I now have to go through a lot plugins in a lot of racks to make sure they are set OK.
Any Arturia expert users here that can help me out?
It seems to me some of the plugins automatically switch back to the Keylab setting for the MIDI Controller when they detect the device.
Yesterday I had configured each and every plugin to the ‘Generic 6 knobs’ setting, and today they are all automatically reset to ‘Keylab mkII’. Aaaaarghh…
If anyone knows how to disable this behaviour, please let me know.
Also, all this communication with sysex data happens directly between the plugin and the controller, bypassing the GP Midi implementation! So, even when disabling the Keylab MIDI output in GP, the plugins keep on sending this data. There seems to be no way to stop this from within GP.
I think the developers see this as an advantage to directly control the plugins with the Keylab by directly mapping everything automatically. But sometimes one doesn’t want this behaviour, like in my case, where more than 30 plugins start sending their mapping when being loaded, overruling all my own data (sometimes, depending on who’s last). And this is especially annoying in combination with Predictive Loading, since this then also happens while playing…
@tripleB : Have you also experienced this and what is your solution?
Hi, currently not on my rig, and it may take until Sunday before making some tests
Are you running your Keylab in USER mode?
I have seen this behaviour in the past only, when running in ANALOG mode, where it makes sense.
So, I typically run my rig in USER, but I also have some rackspaces to tweak the Arturia plugins, therefore I have to change to ANALOG mode, after selecting these rackspaces.
Also, my USER config sends everything on MIDI channel 2+3 (for some historical reason with a different board…).
Could you provide some more information like USER config, used MIDI channels, wiring in GP (screenshots)?
I am indeed running the Keylab in USER mode, but I will doublecheck if somehow ANALOG is activated without me being aware of it.
I currently don’t use the ANALOG mode at all, as I only tweak the plugins using widgets, if at all (I tend to prefer my sounds to be set-and-forget while playing).
I send data on MIDI channel 1, except for the pads, which send on channel 10.
I am not at my machine right now, but I can tell the issue occurs with various wiring scenarios. Most surprisingly, even when the plugins are not wired to an input or output at all! They seem to communicate their Sysex data directly to the Keylab MIDI interface when detected, bypassing the GP MIDI routing entirely. The only way I can stop the communication is by setting the MIDI Controller in the MIDI tab to a ‘Generic’ setting, but this is somehow automatically changed to ‘Keylab mkII’ again when the plugin is loaded again (e.g. at startup, or when using Predictive Loading).
I’ll try to upload a screenshot later when I am at machine again…
I use my KL MKII same as you. Always in User mode and I have pretty much everything as set and forget, apart from a couple of real time widgets I use on a couple of songs.
I have found that on one or two occasions Analog Lab has switched my kL over to Arturia mode. Its only happened with this one VST, and was quite annoying. Pretty sure you can block all the Sysex stuff in the Midi in block though.
Sorry for the late response, I have been traveling for work…
So, I made a video to show the issue.
As you can see the issue is not that the plugin receives Sysex data, but rather sends it to the Keylab and sets the MIDI Device automatically when it detects the presence of the Keylab, even when set to USER mode! This is especially obvious when using predictive loading, but also happens when loading the Gig-file.
It cannot be blocked by GP, as there is no MIDI Out block connected and the data is not even visible in the Global MIDI Monitor in GP. I had to use an external tool that can sniff outgoing data to detect this…
I actually begin to think this is a bug (undocumented feature?) introduced in the latest release of Arturia, so I also sent this to their support. Let’s hope they have an idea what’s going on…
SO, be aware, these settings may seriously change your work!
Are you on Mac or Windows ? I bet they are directly opening the MIDI port themselves or have some other mechanism that the plugin uses to communicate directly. Arturia needs to provide a way to simply turn that off, if there isn’t such a mechanism already
I am on a Mac, and I agree, they seem to open their own port.
I have not yet found a way to turn this off, though.
Hopefully, Arturia provides a solution soon…
It’s probably as you say , the only thing I can tell you if you want to give it a try.
If you haven’t you should put an alias in the Rig Manager
Insert in Gig Script
var Arturia : MidiInDevice
ArturiaMidiEx : MidiInDevice
// Redirect Sysex message if any..
On SysexEvent (sysex : SysexMessage) from Arturia
end
// Called automatically after script is loaded
Initialization
End
You should not see Sysex messages transiting in the Global Midi Monitor either.
The Sysex change mode keyboard message should not be showing in the midi monitor either, and the keyboard does not update the menu LCD with preset information.
If you have MidiOut blocks in your rackspace even if they are not connected remove them
I assume that you do not have any scripts that process Sysex messages.
You only need to include this
