Thank you !!!!!!
It seems to work.
-
Do you mind sharing what buffer size and soundcard you are using? I have not be able to get my latency down to a rate I'm comfortable using. I run a 2012 maxed out Mac Pro as my sample computer and a 6 core 2013 mac pro as the sequencer with an UAD Apollo quad as my interface. I am away from my 2nd computer for the week but I have had zero luck getting Reaper to play nicely with VEPro. Are you all cutting off the anticipate FX feature?
Thanks for sharing your settings!!
-
Do you mind sharing what buffer size and soundcard you are using? I have not be able to get my latency down to a rate I'm comfortable using. I run a 2012 maxed out Mac Pro as my sample computer and a 6 core 2013 mac pro as the sequencer with an UAD Apollo quad as my interface. I am away from my 2nd computer for the week but I have had zero luck getting Reaper to play nicely with VEPro. Are you all cutting off the anticipate FX feature?
Thanks for sharing your settings!!
Sure!
Presonus AudioBox USB interface w/ current drivers. Buffer size is set to 128, and then a setting of "2" in the VEPro plugin. I do not have Anticipative FX turned off. VEPro 7 settings are at factory default. I'm on Windows 10, optimized for audio, quad-core 4.5ghz (OC'ed), 64gb ddr3 ram, single machine.
Hope that helps. Let me know if there's any more info you need.
- Sam
-
You are getting much better performance than I am. I will have to take a dayto try and trouble shoot what is making my system choke at any buffer less than 1024. Are you able to run large sessions (full orchestra) at 128?
If it's all VI pro instruments (40-60 instances all in mirpro), then it will occasionally click here and there every 5 min or so (I think that's my entry level interface). Once I add kontakt, third party verbs, cfx, synths etc. there are clicks every min or so and I'll up it to 256. It's worth noting that I only use this buffer setting for live playing in parts. Once it's all settled and time for fine tuning, I crank it up to 2048. I'm finding I live play less and less since integrating Reaticulate into my workflow, which is lovely - feels more like composing and less like DJing. I also use the "render take fx" function to get individual midi items into temporary WAV "takes" if a certain section is clicking too much.
-
I embarrassing realized that I was trying to run my VEPro through my wifi connection rather than the ethernet cable between my two computers. Now that I fixed that I am getting much better results (duh).
The feedback routing is working well for me, except sometimes the first channel stops sending midi to VEPro if I have an effects send on the channel. Does this happen to anyone else?
-
I embarrassing realized that I was trying to run my VEPro through my wifi connection rather than the ethernet cable between my two computers. Now that I fixed that I am getting much better results (duh).
The feedback routing is working well for me, except sometimes the first channel stops sending midi to VEPro if I have an effects send on the channel. Does this happen to anyone else?
Another user found a bug with feedback routing. If you have any of the feedback routing enabled tracks sending to anything else, the first (but only the first) track will not send MIDI if it's *above* the VEPro track in the track control panel. If this is the case with you, try moving any tracks with VEPro instances to the very top of your project's track list and it should fix the problem.
- Sam
-
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.
-
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.
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
-
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. 😊
-
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. 😊
Most welcome 😊 Let me know if there's anything else you need.
Also, I tend to be a bit of a broken record on this, but check this out:
This articulation management system (for REAPER) - if you like its workflow - will save you HOURS of time diddling with keyswitches.
- Sam
EDIT:
This post I made might be of use to you as well:
-
-
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?
Make sure the following settings match, as pictured:
Essentially:
When using MIDI Bus/Port #1, the following settings should be made:
In REAPER's Send configuration window:
MIDI: [All] and [Channel #]
In Ensemble Pro:
Port: 1 Channel: [Channel #]
Once you want to expand beyond 16 instances and use Bus/Port #2 and beyond, REAPER's syntax gets a little confusing. I'll use examples:
Let's say you want the track to receive MIDI data on Bus #2, Channel 12.
- Set REAPER's Send configuration for that track to:
MIDI [All] -> [Bus 2, 2/12]
- Then, set Ensemble Pro's settings to:
Port: 2 Channel: 12
Hopefully that clears it up and fixes your problem!
- 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!
-
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.
-
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.
No worries. I guess the trade off for REAPER's flexibility is the interface is a little...unintuitive 😊
I recommend saving those settings into a track template so you never have to deal with it again.
- Sam
-
Thank you for your original post Sam.
I was close to pulling my hair out over this.
Many thanks! 👍👍👍
You're welcome! Glad to have helped.
-
Hey - Just a thank you for the tip about using the VST3i version of the plugin as well as NOT using the Event Plugin. I was using both the 'wrong' vst version as well as the event plugin and not getting anywhere fast. I also agree that routing inside Reaper is very much 'non-intuitive' at first... :-D