[ISSUES] VST performance related

[Split]

Just switch OFF "real time export"

What he said ^

[arise]

New eLicenser drivers available today
http://www.elicenser.net/en/latest_downloads.html

[Dan Korneff]

yes

[marcus82]

got a lot of spiking of the cpu meter

lot of audio drop outs also whit just loading a sound presets of instruments that came with cubase 7

got a mac osx 10.8.2 i7 cpu 2.8 ghz 12 gb memory got the buffer at 256

test : when a start with a project i clean the memory quit all app ,wifi

please help or just need a fix with an update

[gmmccurdy]

Mine is doing it too. Disabling the "ASIO-Guard" seems to help it but it hasn't totally resolved it for me. In fact I'm trying to find a copy of 6.5 because I have a live performance this Week and I don't know what I"m going to do. Very frustrating.

[vanhaze2000]

Here also massive cpu spikes, when just loaded a couple of Steinberg's VSTi's.

I am on Cubase 7.01, osx 10.8.2 , core i7 with 8 cores , 32 gig ram.
ASIO Guard turned off.
Sorry to say but from what i gather on this forum more people are suffering from this issue and imho there is seriously something wrong with cpu usage in cubase 7.

[Rumdrum]

I am experiencing the same on some of my projects and I think there is something wrong with the CPU usage as well. However until it is solved and a fix is released, I freeze my VST instuments or sum the MIDI to audio (you can always keep the MIDI track and make a note of the MIDI settings even if you quit the VSTi). It also seems like some VSTi are more likely to cause the problem, so most projects run smoothely. A modern DAW should not have these problems however. Just for test I have manually converted the "problem" projects to Logic 9 projects. Same VSTi same plugs same files etc etc.. No problems what so ever there.

[gmmccurdy]

I rolled back to 6.5 last night and so far today's work has been smooth. Hopefully they will get it fixed soon. I've wondered if the spikes happen when it's accessing the dongle. I keep trying to watch the light on the dongle to see if it blinks when the spike happens.

[NorthWood MediaWorks]

Here too, and in simple projects, but its not consistent, some of my test projects work well, others which worked well the other day, are now pooched.... I still have previous versions installed, so no issues for working, but I do feel like I am on the bleeding edge with C7.

[vanhaze2000]

I also went back on mac to Cubase 6.5.
Sorry to say but i stay of C7 until the poor performance is fixed.

[jpgtr]

Thanks for the warning guys. Hopefully the devs @ Steinberg are on the case.

[ruffindajungle]

Valuable info right here! I hope you guys let us know ie.guys who hasnt made the jump yet if it stills occurs after the update which is right around the corner. And Q7 supposed to be better on osx performance this time arghhh.....

[Racer67]

I'm on a home built PC, Win7Pro, 2.8 quad core i7, 16gig RAM, Ti based firewire card, MAudio Profire and I have had similar issues with C7 and ASIO guard on. I can achieve very close to C6.5 performance (which is excellent) with ASIO guard off. I expect software with new features to be more damanding on my system. However, in C7.01 ASIO Guard seems to create problems when loading mutiple Vst instruments. I add couple of Kontact instuments and ASIO meter is climbing toward 75 or 80% with lots of wild fluctuations. When ASIO Guard is off with same intruments/project only read about 15 or 20% usage and stable. I hope that the updates in February will resolve the problem and I don't think it is just the Mac based people who are having these issues.

[Tp3]

I don't know if it's conclusive but...

As of the latest RME HDSP(e)+eLicenser drivers [v3.32/v6.5.4.1115 respectively] - Cubase 7.01 has restored it's 6.5.4 performance (bar the 2 or 3% difference - which is to be expected as Cubase is marginally "hungrier") - at least on my system (9550/8GB Ram/RME 9632).

I got those numbers yesterday and I hope they will sustain...

JFYI

[machete143]

Hello,
I have a Intel Core i7-2700k CPU with 8GB DDR3-1066 (or was it even faster? Don't remember) Ram and a M-Audio FastTrack Ultra 8R Interface (USB-2.0) and an SSD via SATA (yes, cubase is installed on the SATA, no the temp dir is not on the sata). I use Cubase 7 with the latest M-Audio Driver.

I have the problem, that my system load looks fine (see attachement) but I still got very high ASIO load when working on bigger projects.

Since I do not exactly know, how ASIO works and if ASIO uses the interface to process, I can only guess, that the problem is the underlying USB 2.0 which seems to me the only bottleneck possible.
I know that there are ways to freeze channels and stuff, but I really don't like that and I bought this system specifically for production.

Based on that assumption I think about getting a FW, PCI, PCI-E or USB 3.0 interface. Do you think that this will solve my problem? Or is the ASIO load based on something like the FSB (although 64bit should be pretty fast) or whatever else?

Any hints or help will be greatly appreciated

edit://
For clarification: Being an EDM producer, I use only 2 outs (and a 3rd for the sub which is rerouted in the interface). Changing the latency won't solve a thing, because cubase goes out of synch (for whatever reason) in addition to high latency when writing stuff on MIDI controllers.

edit2:// yes, the profiles are set to steinberg's "performance" settings

[altunes]

Similar problem for me also.
I'll be very interested to see what develops along this thread.

[Cantankerous]

I too have noticed this, it doesn't take much to have the asio meter peak. It gets even worse when you are using bridged plugins, that really aggravates things. There are a good handful of threads around with similar topics, this is nothing new and I too am wondering what comes of the performance with future updates. I see absolutely no benefit to asioguard and wonder if it is actually hurting than helping.

[arise]

I wasn’t able to works with C7.01. My CPU was getting crazy with only a few midi tracks, no audio at all.

Yesterday I disabled all midi input and output of my soundcard, except the port i’m using for my keyboard and it now works perfectly.

[machete143]

Disabling "Asio guard" actually helped quite a lot. Also setting pre-loading to 4 seconds seems to reduce ASIO load.

Still, ASIO load is about 90% all the time and I get some glitchy stuff.


edit://
Okay, nevermind. It changed nothing. Still the same problem, seems like it would work but it only did for some seconds...

edit2://
On a sidenote, performance got way better from 6.5 -> 7

[altunes]

So perhaps it's not me then!
So glad I found this thread.
I'm having similar problems and wondered if I've got everything set up Ok.
I ran Cubase LE on an old Dell laptop for years and while understandably limited I knew these limitations and acted accordingly, but I've now treated myself to a brand new Macbook Pro and Cubase 7.
I've never had such a well equipped set up yet I'm having problems with constant CPU overload due to "audio drop-outs" even with no audio tracks and just an uncomplicated drum track (via GA), a bassline (Novation Basstation), one Padshop part, one Retrologue part and some very simple Halion Sonic SE textures.

My set up is: Cubase 7 which I'm running at 24bit 48KHz,
My Macbook Pro is the 13" late December 2012 version (OSX Mountain Lion, 2.5GHz intel core i5 with 4 GB 1600MHz DDR3)
And a Focusrite Scarlett18i6 interface. I'm only using instruments/plug ins included in the bundle at the moment so there's no 'third-party' issues to mess things up (Basstation excepted, it came with the Focusrite).

It has been suggested that I need more RAM - while I'm sure that would improve things for a more complicated arrangement, surely my set up should cope with a simple 4 minute pop song, hence I thought the problem was with me, or at least something I'm either doing or not doing, or perhaps not...

[D.B]

I have noticed this aswell and only when using steinberg instruments.
Doesnt bother me so much because I never really use steinbergs plugins or vstis, I find there are much better alternatives.

[TaniaRose]

I rolled back to 6.5 last night and so far today's work has been smooth. Hopefully they will get it fixed soon. I've wondered if the spikes happen when it's accessing the dongle. I keep trying to watch the light on the dongle to see if it blinks when the spike happens.

Updated fro C6 to Cubase7 in the studio...no problems. HAD Cubase Artist 7 on the laptop, and have had to roll back to CA6 because of this very issue. Updated the elicencer driver that came out a few days go, and though it's been BETTER, i still had to roll back to the previous version to work.

There's a definite regular spike, and i mean like-clockwork regular, causing serious peakload each time, and that's with no project even loaded. When even a single track of audio, or even midi for that matter is loaded, playback stutters and pops whenever the spike happens. No change in asio driver nor soundcard seemed to make a difference. Gave up in the end on CA7...hoping for some kind of fix in 7.0.2

[vivo]

for what it's worth:

I've just installed 10.8.3 beta (I have an Apple Dev account).

Cubase 7.01 projects are ~10% lower in cpu usage now. (With Asio Guard ON)

Using an RME FireFace 400 @128 samples

[TaniaRose]

The thing that i don't get is why there is sooooooo much difference between users...many say they are experiencing a very different shift BELOW what their previous metering was pre c7, and then others reporting the complete opposite. Surely it must be something other than ACTUAL cpu usage that is causing this spiking?

[ZeroZero]

System specs below.

Open Cubase. Do not load a project or empty template. Ensure no other applications are loaded. Disable all start up apps.

Load in Devices/VST performance app.

"Real-time peak" is dancing around, occasionally red lighting.

Situation worse when loading a project

My system is reasonably specced.

Anyone have any ideas?

Zero