Hey Erik,

 everything with MIDI and controllers inside Studio One is working (instruments respond, MIDI Learn works, etc), but I can't control anything via "MIDI Controllers" in the VEP Server.

But the only way I can get anything in the Server to be controlled is setting up an Automation Parameter and controlling that Parameter in Studio One. Controlling things in this way doesn't require MIDI CC to get across to the server, which makes me strongly suspect that the MIDI CC data is still not getting transmitted by the plugin for some reason, further evidenced by no Plugins in the server responding to any of the CC channels that are already assigned normally, and Omnisphere's and SWAM's MIDI Learn functions will also not work in the same way as the Sever's MIDI Learn; moving a knob/fader won't set anything when pressing "L" or "learn." 

Would love to know why this is happening.

After looking into it, I've discovered that I'm able to set an Automation Parameter and then MIDI Learn to assign that parameter in Studio One to a hardware control, which is great! This gets me most of the way there; assigning these parameters in this way will let me control most of my instruments in the Server.

However this will not work for plugins like Omnisphere. When loaded into VE Pro Server, Omnisphere won't respond to any attempt to have it MIDI-learn a control (under SYSTEM/MODULATION, cueing a parameter to be "waiting for MIDI," but it doesn't respond to any controller movements).
I think this is more evidence for the MIDI CC not making across to the the Server, since that's basically the same problem trying to use the Server's MIDI Learn function for MIDI Controllers.

That seems like a useful view from the cog icon, clicking it indeed shows that the MIDI CCs from my controllers ARE getting to the VEP plugin just fine, but they don't seem to be making it across to Server, only note data seems to be getting to the Server, given I can still trigger my instruments in the Server fine too.

Attached a screenshot of what my VE Pro plugin GUI looks like with the cog engaged (not sure why controller is on the left side while yours is on the right though)

If there was an equivalent MIDI monitor of some kind inside the VEP Server, that might help indicate if the problem is that CC isn't getting received or something being up with the Server's Learn function. But the Server picks up the MIDI CCs when connected to Pro Tools, but not when connected to Studio One, so that makes me think the CC messages just aren't making it over to the Server.

The crazy thing is I'm pretty confident I did manage to attach a CC control to a parameter in the Server at least once, but I've been unable to do it lately.

I appreciate the input!

HNY

I've been trying to get Vienna Ensemble Pro to be fully functional in Studio One 6.0.2. I'm nearly there, the only thing I still can't figure out is why am I not able to get MIDI CC across to my server?
I want to use VEP's MIDI learn function to control parameters with my hardware controllers, but I can't get the Server to acknowledge any CC at all in this setup.

It seems to be something to do with Studio One because I can get MIDI learn in the Server to work just fine with all of my controllers while using the .aax plugin in Pro Tools and all my MIDI controllers are able to control parameters on Plugins inside Studio One just fine.

Is there something I'm missing with the Studio One setup? Or is Studio One simply not able to transfer MIDI CC, only MIDI notes?
If it's not possible to directly control parameters with my controllers in S1, is there any sort of workaround? 

Software/Hardware specs:
-Studio One 6.0.2, running in Rosetta for VST3 plugin use (no way to access the MIDI ports otherwise, the AU3 plugin also can't be loaded in Studio One)
-VEP Server 7.1.1406 (64-bit)
-Sequencer computer: M1 Macbook on MacOS Big Sur
-Server computer: 2018 Mac Mini (intel) on MacOS Catalina

Glad it's being worked on!

I just figured out that this is the reason why most of my VST3 plugins weren't showing up in Studio One.

Bumping this thread bc it helped me figure out why my server would only sometimes connect to my laptop.
Thanks for the post!

Thank you, Paul.

I have not yet had a response from UA, I've submitted a support ticket with them. My request number is #592531. 

It's almost certainly the M1/ Big Sur compatibility issue. I had the same issue with LUNA freeze on start-up before. I figured out that Waves plugins were crashing Luna due to some older versions of those plugin being "semi-compatible" with Big Sur. They would work on other DAWs, not with LUNA. Strange and confusing, to say the least.

I'm looking for a workaround to prevent Vienna Ensemble Pro from crashing UA's LUNA on start up on my M1 Macbook (running Big Sur).

From what I can tell, VEP is not compatible with LUNA. I'm ok with that, it's what you get for working with new software, but my issue is that VEP prevents LUNA from opening, whether the VEP-related .component files are in the Library folder or not. Call me greedy, but I want to be able to use both VEP (but on different DAWs) and LUNA on the same machine!

UA's workaround for this issue is to remove the offending plugins' .component files from the folder (HD/Library/Audio/Plug-Ins/Components) as stated here. However, this does not work for the VEP plugins, I am only able to open LUNA when VEP is completely uninstalled using the uninstaller app. 

What could be causing LUNA to hang up if it's not the Components files? My current guess is that it has to do with LUNA's incompatibility with software using eLicenser copy protection, based on this UA article from last year, but so far I'm at a loss.   

I'd appreciate any input on the matter!