Reviving this thread. Recently moved from Mac to Windows and VE Pro causes this problem nearly every day. I've tried every single thing on this page and nothing fixes it. Doesn't matter whether I start Cubase 10.5 or VE Pro first -- VE Pro kills the eLicenser.

Any other ideas...? It's killing my workflow when it happens (I need to reboot in order for it work again).

Originally Posted by: Seventh Sam

Also, there's a little obscure pair of settings that might be the culprit of Bus 2 and beyond are not working.  Do the following:

- Open the Ensemble Pro Server FX window in REAPER.  Make sure you are using the VST3i version of the Ensemble Pro Plugin.  As far as I'm aware, Ports/Buses beyond #1 won't work in REAPER unless it's VST3 (this might have been fixed in REAPER 6).

- Click on the button in the top right part of the window that says something like "2/64" out.  It will open a window with a grid.

- On that new window, click the small button that says I/O, again in the top right.  You'll get a drop down menu.

- In that menu, you need to change a few settings.  They are:

• Midi Input -> Map REAPER MIDI Buses to VST3 MIDI Buses
• Midi Output -> Map VST3 MIDI Buses to REAPER MIDI Buses

Make sure both those are checked.  Once they are, Buses 2 and up will interact correctly with Ensemble Pro, allowing you to have 256 separate instruments in a single Ensemble Pro instance.  Yay!

THAT was it - I had forgotten about that. Thank you again good sir.

One question: I'm able to get this to work perfectly for the first port in VE Pro (which is Strings in my template), but I can't get any MIDI going to the second port (Brass in my template). I tried MIDI bus 2 and bus 1, with no luck. Is there something I might be missing? 

N/P

How do I delete a post here...?

Originally Posted by: Seventh Sam

When this happens to me, the two main culprits are:

1) I forgot to turn on "Input Monitoring" in the track itself (not the one with the Ensemble Pro Server plugin, but the track that's actually inputing MIDI and receiving audio back).  Depending on the theme you're using, you can find this in the TCP (Track Control Panel) or Mixer.

2) The Expression or Volume CC (11 and 7, respectively) are accidentally turned down for that particular instance of VI or Synchron Player.  I can't tell you how many times I've tweaked CC envelopes, forgot I had done so, and then freaked out thinking the audio wasn't working when the reality is that Expression was just set at 0 the whole time!

Does one of those two fix your problem?

- Sam

Yes, expression and volume CC are always ghosts in the closet, hahaha.

Thanks for the help!

It was total rookie routing error, it turns out...years on Cubase and getting used to Reaper. :-)

Thank you so much for this, Sam.

I'm new to Reaper after many years on Cubase and can't figure one thing out with your routing: Everything looks good but I can't figure out why I'm not hearing audio from any of the MIDI tracks. I'm seeing audio (colored red) on them, just not hearing it. I'm sure it's a stupid mistake but I just can't figure it out.

Hello, I'm on the latest VEP on Mac, High Sierra, Nuendo 8.2.1, 32g RAM.

VEP is not saving changed parameters in my Kontakt patches in it, so that when I re-open sessions later I have to go in and re-do all of the patch changes I made by loading presets I made for this reason. This is untenable, of course, with big projects so I want to find out why it's happening. I'm on Kontakt V 5.8.1 - the most recent version of 5, though it's been happening in the previous version as well (I only started using VEP when the previous version of Kontakt was out).

Here's what I tried, which didn't fix it: Trashing the preferences. Completely un-installing and re-installing VEP.

Thanks for any help.