composingkeys
Member
Did you make sure ASIO Guard was disabled for VE PRO?
VEPro 7 now available!
- Thread starter Ben
- Start date
Dewdman42
Senior Member
I had it turned off globally, I did not yet do it per plugin. I will try that. Any other tips anyone has to kick cubase mac into better CPU behavior? I'm honestly regretting my purchase of Cubase based on this performance its simply awful compared to LogicPro...and DP's performance is somewhere halfway in between.
OP
OP
Ben
VSL
Thats a new feature added just in the last version. There should be a hint in the changelog.
DANIELE
I love to make music but I also love to make music
I have perfomance problems again, Reaper randomly start to stutter, then it goes well again, then stutter again, I don't know why...
This happens in an empty template while I'm building one using VEP. Is there anyone that experience the same problem?
How many threads per instance should I set?
This happens in an empty template while I'm building one using VEP. Is there anyone that experience the same problem?
How many threads per instance should I set?
Guy Rowland
Senior Member
AFAIK it's not yet in the manual. It's on the midi controller Automation Window, drag an event to a blank slot with the modifier(s), and a new event is created.
DANIELE
I love to make music but I also love to make music
I tried it and it doesn't work. When I press alt+drag it opens the menu, the same as I simply click on it.
Guy Rowland
Senior Member
If you're on the latest build, I'm not sure I can help you further, sorry - out of ideas. Modifiers and dragging is all I do - I'd head over to the VSL forum / support.
Guy Rowland
Senior Member
As described above (except it works for me!) - create blank events, and populate the first as normal. Then Alt-drag for copy, Alt-Shift-Drag for increment CC, Alt-Cmd-drag (in Windows Alt-Cntrl-drag) for increment channel). Massive time-saver.
jneebz
Senior Member
Any chance any of the power VE Pro users (@Guy Rowland, @Mihkel Zilmer, etc.) plan on a video describing a Cubase-VE Pro 7 template procedure? I'd actually pay for that...
Guy Rowland
Senior Member
£1.50 and its all yours.
I'll do one for 7 to add to the ones I did for 6, but it makes sense to wait until Wake On Midi is part of the deal. As it is right now, I'm using all the same techniques as for 6, except the really tedious manual adding of every parameter is massively sped up by the alt-dragging thing.
Here's the detailed one for 6:
jneebz
Senior Member
Makes perfect sense. Thank you Guy...very generous as always! PM me your PayPal email address!
Very excited that it's officially out now! Now to upgrade my version 6 template and have it all work well in Nuendo. 
I'm by no means one of the VEPro power users you mentioned, but I do plan to make an entire video series on how to build a VEPro 7 setup with Cubase/Nuendo (I use Nuendo). I have a rather large template with dedicated servers in a machine room over 10Gb networking
. So once I migrate everything over, I'll begin a YouTube video series from scratch.
There's one gentleman over on YouTube with a 3 part series on how to build the template, including expression maps integration. That was with version 6 although. I forgot his name, but thanks to him, I've been able to build my own version of my template
I'm by no means one of the VEPro power users you mentioned, but I do plan to make an entire video series on how to build a VEPro 7 setup with Cubase/Nuendo (I use Nuendo). I have a rather large template with dedicated servers in a machine room over 10Gb networking
. So once I migrate everything over, I'll begin a YouTube video series from scratch.There's one gentleman over on YouTube with a 3 part series on how to build the template, including expression maps integration. That was with version 6 although. I forgot his name, but thanks to him, I've been able to build my own version of my template
Shad0wLandsUK
Contemplating Composing...
I installed Windows 10 on my MacPro for this very reason :/
I just could not accept that Steinberg had willingly sold me a half-performing product because it is on macOS
I am still not sure why this is the case, but I want what I paid for. Not half of the monies worth...
Dewdman42
Senior Member
That is sad news. And lame. Well, if Apple blows it on the next macPro, then I may end up switching to Windows, and then I'd probably use Cubase, but that is probably years away, hopefully never because I don't want to leave OSX. I will go back to my regularly schedule LogicPro and DP challenges. I guess Cubase might work for some stuff so I'll mess with it now and then, but man...it is literally double the CPU use of Logic playing back 100 tracks through VEP. Where Logic is humming along at 20-50% to play it, Cubase is peaking the 90's. Too close for comfort. I haven't even tried any synth plugins in it yet.
composingkeys
Member
As a Cubase user on PC, I've found that the less instances in VE PRO, the better. Can't confirm but this may help you on a Mac running Cubase. With Logic, it tends to be the reverse where you want many instances with less instruments in each one.
Dewdman42
Senior Member
true except I have multiport templates working great on Logic so I can do one instance there too....and CPU is getting half the use compared to Cubase.
The main reason for single instance, in my view, is that in VEP you have to configure the number of threads per instance. So if you are going to use 4 instances on a 12 core system, you really would only want maybe 4 threads per instance or something like that. Then if you have an instance that isn't doing much, you have under-utilization of cores. So I see real benefits to single instance also, but as it turns out I am happily doing that with LogicPro already using my multiport templates. So Cubase doesn't score enough of a point there to make up for their outrageously poor cpu performance.
I will say at least, even though the CPU is peaking out 95% and in the red...Its not necessarily getting drop outs while it does that. But I don't know what happens when I try to push some synths or other plugins heavy in processing.
The main reason for single instance, in my view, is that in VEP you have to configure the number of threads per instance. So if you are going to use 4 instances on a 12 core system, you really would only want maybe 4 threads per instance or something like that. Then if you have an instance that isn't doing much, you have under-utilization of cores. So I see real benefits to single instance also, but as it turns out I am happily doing that with LogicPro already using my multiport templates. So Cubase doesn't score enough of a point there to make up for their outrageously poor cpu performance.
I will say at least, even though the CPU is peaking out 95% and in the red...Its not necessarily getting drop outs while it does that. But I don't know what happens when I try to push some synths or other plugins heavy in processing.
