Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
Options
Go to last post
2 Pages<12
Posted on Mon, Jul 08 2019 23:00
by Seventh Sam
Joined on Sat, Dec 29 2018, Posts 116
Originally Posted by: crd Go to Quoted Post
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.
Posted on Fri, Jul 19 2019 06:16
by crd
Joined on Wed, Dec 05 2018, Posts 4

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?

Posted on Sat, Jul 20 2019 15:57
by Seventh Sam
Joined on Sat, Dec 29 2018, Posts 116

Originally Posted by: crd Go to Quoted Post

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

Posted on Sun, Jul 21 2019 08:40
by crd
Joined on Wed, Dec 05 2018, Posts 4

Moving it to the top solved it. Thank you! I am loving the workflow I'm developing with Reaper.

2 Pages<12
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.