Hi, iam new to the Electra One.
I want to use the E1 for controlling plugins and hardware synths.
I tried to use the Pigments-preset with the VST-plugin in Bitwig. But i need to remap all parameters under the DAW. Without re-mapping no parameters change values in the plugin. Is that the normal way to use the presets or is there another solution for this?
The Bitwig-Extension DrivenByMoss works fine. But its to control the DAW itself, not the vst-intruments.
I recognized that the filter controls work with the E1 but no of the other parameters in the preset. Maybe the Pigments preset in the library is an older one and for the previous Pigments version. If no idea.
When I checked it out last month with the E1, I was able to control any clap/vst effect and instrument I tried (u-he, FabFilter) if there was a remote control page available.
Guess: maybe Pigments is missing remote control pages? If I were to implement Bitwig’s control system, I’d probably make use of VST3 Units to automatically generate those pages. So maybe Pigments doesn’t support VST3 Units?
Ahhh, you mean the performances controls:
I use it in combination with my Ableton Push 1 + Bitwig and the DrivenByMoss Extension. In my case its for playing live and performing.
In order to program new sounds it only want to control the plugin, no DAW or so. The community offers some presets for Pigments and other Arturia plugins - but they dont work without remapping. I think the E1 sends some kind of CC or NRPN-messages. But the plugins dont react on it.
When i try hardware f.e. the Digitone and the E1 it works fine - without any changes. Whats wrong on the VST-plugin-side?
The official name of this Bitwig feature is Remote Control. It is not limited to performance only. VST plugin manufacturers have to provide these Remote Control pages via the plugin interface API. Sadly, a lot don’t do it at all or only expose a small part of the plugin’s internal parameters.
I’m starting lose track of this thread. If you’re focused on Bitwig, the recommended way is DrivenByMoss. Btw., if a plugin doesn’t provide remote control maps, you can always create them by yourself, either per instance or per plugin. Those will also be accessible via DrivenByMoss.
You can do this independently of your DAW by setting up E1 presets that follow the MIDI specification of the plugin you use or by changing the plugin’s MIDI assignments to whatever preset you use on your E1 (if the plugin supports changing its MIDI assignments, not super common, u-he Plugins are very flexible in this regard).