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

Notification

Icon
Error

Forum Jump  
VEPro 7 and Cubase 10
Last post Fri, Aug 30 2019 by civilization 3, 9 replies.
Options
Go to last post
Posted on Tue, Jul 09 2019 21:09
by Danicar
Joined on Wed, May 22 2019, Posts 6

Hello!

I'm new to the community and I'm new to VEPro.

I have a BIG problem: when I play - in Cubase - an instrument loaded into a VEPro istance I hear very often pops, clicks and other sort of noise. These are in the recording too so you can imagine when I do the mixdown...

The problem happens both with istances loaded in the main computer and in the slave machine. I have 7/8 istances with max 16 virtual instruments each, in the main computer and in the slave machine as well. Main PC and the secondary one are both pretty powerful machines (in fact the  %CPU usage in both server projects is low). Audio card buffer is set to 128.

I tried to change something in VEPro preferences (like multiprocessing) but it seems that nothing has changed and almost all instruments loaded in VEPro Server project remain unplayable cause I can play few notes sounding good and then suddendly I have a "click - pop - crack". :-(

Any suggestion?

Thanks,

Daniel

Posted on Mon, Jul 15 2019 01:15
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1630

128 is pretty low; first you want to see if more latency (latency is compensated relatively well by VE Pro) helps.

You also have more buffering on the VE Pro side, in the VEP window from the VST rack.

Are you returning a large number of outputs to Cubase? 

MacBook Pro 15,1: 2.9 GHz 6-core i9
32GB 2400MHz DDR4
OSX 10.14.5
VE Pro 7
Posted on Thu, Aug 22 2019 10:27
by Danicar
Joined on Wed, May 22 2019, Posts 6

Hello!

Thanks for your reply and sorry for being late but I was busy with other stuff.

Yeah, I'm gonna try with more latency and see what happens. Actually I am returning a quite large number of outputs to Cubase. I see there are many different ideas on how to create a large template with VEP: I've not found yet the one suits best for my setup; but I am working on it ;-)

Dan

Posted on Thu, Aug 22 2019 16:55
by Dewdman42
Joined on Tue, Feb 27 2018, Posts 377

which version of Cubase?  Mac or PC?

5,1 MacPro 12core X 3.46ghz, 128gb ram, RX580 video, OSX Mojave, VSL (almost everything), LogicPro, Cubase10, StudioOne, DP9, Reaper, Dorico, Finale, MuseScore, Notion6, EW Hollywood Orch, Kirk Hunter, GPO, much more..
Posted on Thu, Aug 22 2019 19:27
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1630

Originally Posted by: Danicar Go to Quoted Post
Actually I am returning a quite large number of outputs to Cubase. I see there are many different ideas on how to create a large template with VEP: I've not found yet the one suits best for my setup; but I am working on it ;-)

Dan

Well, the big reason to use more than one output is stems, simultaneously. A large no. of outputs is a drag on your system and you'll find that with less your performance improves. It's not unusual to want to keep mixing in Cubase, but with the automation capabilities of VEP, you literally don't have to, or not much. So as a balancing act you may want to examine the need for all that realistically. I return 2 or 3 stereo outs, and when I want stems I create these more individually (I do create a separate reverb return and weigh that after-the-fact). I could get rid of all but the master out from VEP in most cases but I have this habit of separating piched from non-pitched; sometimes I send a return channel to another instance of VEP as an FX rack (this is something I tend to render because of the resources eaten).

MacBook Pro 15,1: 2.9 GHz 6-core i9
32GB 2400MHz DDR4
OSX 10.14.5
VE Pro 7
Posted on Mon, Aug 26 2019 16:04
by Danicar
Joined on Wed, May 22 2019, Posts 6

Cubase 10.. PC...

Win 10 and Apollo x8p...

I'm sure I'm missing something in the "ideal" setup (since I'm new to VEP). In each istance I've uploaded many Kontakt plug-ins: all on MIDI port 1 and MIDI channel 1, 2, 3...up to 16, then the output 1/2, 3/4, etc. so in Cubase I have rack instruments and I can have more control on each instrument. But I don't know if it's the best way to operate...

Posted on Mon, Aug 26 2019 16:29
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1630

Well, again returning every output channel to Cubase is very expensive and there is no way around it, so it'd be hard to call that ideal. Except for inserts/sends to Cubase-proprietary plugins there is nothing you can't do in VE Pro's mixer. I was where you are when I started, with one of the more robust machines of the time and learned to mix this way, it was far too much overhead. And, I don't consider mixing in Cubase ideal since I embraced automation.


Also note you have up to 48 midi ports available, so you don't need to be running out of channels at 16 and creating new instances behind that. 1:1 channel output replication seems like the thing to do but you're cutting yourself off at the knees.

MacBook Pro 15,1: 2.9 GHz 6-core i9
32GB 2400MHz DDR4
OSX 10.14.5
VE Pro 7
Posted on Mon, Aug 26 2019 16:38
by Danicar
Joined on Wed, May 22 2019, Posts 6

Hello,

thanks for the pro reply!

Honestly I have no clue how VEP automation works, I really need to study it. As I replied to the other guy here in the forum my VEP-Cubase set up is probably not the best one.

Anyway, the good point is that I can always improve!

Here's another thing: why when I turn up the monitor knob on my Apollo (x8p) I hear so much noise from the speakers? (fffffffffffffwwwwwwwwwwwooooooooooosssssffffff, just for giving you an idea, LOL). The same happens when I have max volume on the headphones. Shouldn't the signal be clear? 

 

Originally Posted by: civilization 3 Go to Quoted Post

Originally Posted by: Danicar Go to Quoted Post
Actually I am returning a quite large number of outputs to Cubase. I see there are many different ideas on how to create a large template with VEP: I've not found yet the one suits best for my setup; but I am working on it ;-)

Dan

Well, the big reason to use more than one output is stems, simultaneously. A large no. of outputs is a drag on your system and you'll find that with less your performance improves. It's not unusual to want to keep mixing in Cubase, but with the automation capabilities of VEP, you literally don't have to, or not much. So as a balancing act you may want to examine the need for all that realistically. I return 2 or 3 stereo outs, and when I want stems I create these more individually (I do create a separate reverb return and weigh that after-the-fact). I could get rid of all but the master out from VEP in most cases but I have this habit of separating piched from non-pitched; sometimes I send a return channel to another instance of VEP as an FX rack (this is something I tend to render because of the resources eaten).

Posted on Fri, Aug 30 2019 20:01
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1630

VE Pro automation vs Cubase automation boils down to everything in one VEP instance is in one place, in Cubase's dropdown menu from that single instrument channel, vs needing to look at several or many of them.

Your basic channel level and sends to an FX channel from the perspective of audio channels in Cubase is probably no great hassle for you but 1) this is simple enough in VE Pro and 2) once you're doing very involved mixing more ideas will tend to occur to you having it all visually consolidated in this way.

If you *do* need to print a bunch of ste
ms in a hurry, there's nothing to say about that. But I would say if this is the case, just print them when it's time. You're going to have trouble dealing in the meantime; and I get a sense that your mixing is not all that involved, as mine wasn't, if automation as a way o' life hasn't really occurred to you. So you can control the channel levels and sends just as easily really, in considering the VEP mixer as at least a submix for now and let go of all that input which is bringing your system to its knees.


Particularly now that what VEP exposes to Cubase is what its plugins expose to it verbati
m. It used to be a long string with a lot of redundant reporting and only "Parameter n" as a clue.

MacBook Pro 15,1: 2.9 GHz 6-core i9
32GB 2400MHz DDR4
OSX 10.14.5
VE Pro 7
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.