Yes, I’ll have to check if the restriction check (that worked fine in FW2) still works in FW3.
Hej @joris.roling and @martin,
FYI: I just tested the new Moss Bitwig Preset and the communication there also changes colors and names of my other presets… So it seems to be a FW3 thing? Also checked, if communication in my presets over the not used MIDI Device 2 helps next to the Bitwig presets communication over MIDI 1 and CTRL. It doesn’t.
Are you saying that elements in other presets are somehow overwritten? I cannot reproduce that.
Can you please give some more details what you are doing and what is changed?
EDIT: Oh, I see what you mean. It updates when something changes in Bitwig. Will fix it!
The DrivenByMoss fix is online. See here: DrivenByMoss for Bitwig and Reaper - #11 by martin
That was the problem - thanks @moss!
Greetings. I’m trying to figure out if what I want to do is possible as I’ve never fully understood Bitwig’s approach to mapping. And I’m trying to figure out if Electra One would work for me.
Let’s say I’m running an instance of a 3rd party VST synth in Bitwig and want it mapped to my Electra One in an order that I determine. Let’s say Repro-5 which is on one level quite simple, but has dozens of parameters. I want access to almost all the parameters on my Electra One, but ordered in a logical way that I decide.
Do I have to create a whole bunch of screens of 8 macros and then map them to the Electra One?
Or am I better off creating a preset for Electra One that maps to the instrument and then somehow saving it with the VST file in Bitwig so that any time I open it, it’s able to be addressed? I would then also have a separate preset on the Electra One and switch between that and other presets address to other instruments in the same set?
In Live, I know it’s all per-project, so I do all the mappings I want for a project and “save as” which is way easier on the mapping end. But of course that means I always have to have a default project that contains all the mappings I want at any time.
If you use DrivenbyMoss, there are dynamic device screens so once you create remote controls the bitwig preset will be able to see them automatically. The preset is dynamic so a bunch of things get handled this way.
If you watch the video this should be pretty clear.
Note that this is all very specific to the preset and bitwig plugin. If you make your own traditional Electra preset you would have a lot of manual mapping to do.
As dstengle already wrote, you have both options. Using the 8 remote control parameters (called “macros” in Ableton) is the easier way to setup than having to implement an Electra One template.
Creating a Electra One template has the advantage that you can see more parameters at once and create a nicer layout (e.g. with Envelopes).
With remote controls you do not need to map them to the Electra One, this is done automatically. Furthermore, you can choose to create remote control pages which are global to all projects or on a per project basis (or combine both and/or put them in a template).
I did a tutorial video about the topic some time ago: Using Bitwig Remote Control Pages, Macros and Poly Aftertouch - YouTube
Thank you @moss . One question–can you have multiple pages of 8 remote controls per device in your script, or only 8 controls per device? I know Bitwig allows multiple pages.
I’ll take a look at the video. Edit: I watched the video and I see that multiple pages show up so I just select them. Thanks for your great work on the Electra One!