I have recently bought the Mariana VST, which I am running on Ableton 12 in Windows 10. I had hoped to map many/most of the controls to MIDI controllers, but I have run into some baffling problems. Some examples of this are to be found in the LFO controls on the CNTRL 2 page. For instance, I can successfully map LFO3 Wave Shape to a control, but not the equivalent for LFO1 or LFO2. Likewise, none of the Sync or KB Reset buttons for the LFOs can be mapped.
These mappings all work fine for the CNTRL 1 page. Indeed, I have been able to map everything I need for the SYNTH 1, CNTRL 1 and Output pages, the problems seem only to be associated with SYNTH 2 and CNTRL 2.
Has anyone else encountered this? I am running Mariana 1.2.0 and Ableton Live Standard 12.1.10.
Okay, two things. Firstly, I got a reply from Moog shortly after I re-reported this via their new ticket system. And secondly, I could not reproduce the problem on a new PC after clean-installing everything with Windows 11. So whatever the problem was, it was no doubt down to something pathological outside of the Moog plugin.
Incidentally, for MIDI mapping it is definitely an advantage to run the plugin in Ableton and use Ableton’s MIDI mapping, rather than using the standalone program or using the Mariana internal MIDI mapping in the plugin. I am mapping 128 controls across two devices, for which I am using mappings on three separate channels. Neither of these things (multi-channel or multi-device) is possible using Mariana’s own MIDI mapping. Nor, I think, is the MIDI out that will allow the Behringer hardware (LEDs and motorised sliders) to follow the plugin settings.
BTW, Mariana needs more than 128 controls for a complete mapping, but 128 is an Ableton limit. Time will tell if my experiments with mapping all those controls will actually prove to be useful!