Archetype Plini X - MIDI mapping issue on the latest version ( v1.0.0 - X )

Hi everyone,

I hope it’s appropriate to discuss this technical issue here. I’ve already been in contact with support via email, and they are currently looking into it. However, I wanted to bring it up in this forum as well, as it might be something others are struggling with too, and perhaps the discussion under this topic could provide additional insights and potential solutions that might benefit everyone facing a similar problem.

Here’s what’s happening:

I’ve been using Archetype Nolly and Archetype Rabea for live performances for a while now, and I have have never had any issues. My setup includes using a Bluetooth MIDI controller (I’m using the M-Vave Chocolate wireless MIDI controller, which I guess is kind of a budget version of the Hotone Ampero Control, but it does the job), which allows me to switch presets using the footswitches A, B, C and D. This setup has been flawless with both Nolly and Rabea plugins (even simultaneously), where I map CC messages (like CC #00, CC #01, etc.) to different presets. A specific feature of this particular controller is the ability to use combined footswitch presses (A+B for “E” and C+D for “F”) to navigate preset pages.

However, with the recent addition of Archetype Plini X, I’m facing a significative issue with the MIDI mapping, as it isn’t responding like on the other plugins. When I press any of the A, B, C, or D switches, there’s no response from Plini X – it’s as if the plugin isn’t receiving the messages. The weirdest thing is that when I use the combined presses for page navigation. For instance, pressing C+D, which should send “F” for page navigation on the controller triggers the response for CC #03, normally sent by D alone. Similarly, pressing A+B, meant to send “E”, results in the plugin reacting to CC #02, typically sent by C alone. I couldn’t figure out how to solve this for the life of me, so the workaround was to map CC#02 and CC#03 to “CC Preset Dec/Inc” so at least I could jump from a preset to the next (or previous) using the combined footswitches.

I have tried running both standalone and on my DAW, on a single instance and also along the other Archetypes. In all cases, Nolly and Rabea plugins work as expected, while Plini X behaves unusually, as mentioned above.

I’ve detailed this to Neural DSP Support and am awaiting their guidance, but I’m curious if anyone here has experienced similar issues with MIDI mapping in Archetype Plini X or other newer plugins. My best guess is that this is particular of the “X’ update (for future compatibility with QC). Any insights or suggestions from this community would be incredibly valuable.

Thank you for your time and help!