Cubase SX CPU spikes when soloing only?
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
Here's something I've been wondering for awhile about Cubase SX:
I can be plugging along with a normal-size project, with Kontakt, probably another synth, about 10-20 insert FX and about 3 FX Channels, and the CPU will be averaging about 40%. But as soon as I hit "Solo" on any track, the CPU spikes to the top and the audio engine breaks up, like in a bad crash.
Then I hit solo again, and everything's back to 40%.
Is this denorm? If so, how do I tell which plug is causing it?
Specs: Intel P4 2.6ghz, Cubase SX 2.2, Echo MIA PCI card, 1G RAM, WinXP Home, Kontakt 1.5, Hardcore Bass
Most common FX: TC Compressor/De-esser (v3.1), TbT plug-ins, Bionic Delay
I can be plugging along with a normal-size project, with Kontakt, probably another synth, about 10-20 insert FX and about 3 FX Channels, and the CPU will be averaging about 40%. But as soon as I hit "Solo" on any track, the CPU spikes to the top and the audio engine breaks up, like in a bad crash.
Then I hit solo again, and everything's back to 40%.
Is this denorm? If so, how do I tell which plug is causing it?
Specs: Intel P4 2.6ghz, Cubase SX 2.2, Echo MIA PCI card, 1G RAM, WinXP Home, Kontakt 1.5, Hardcore Bass
Most common FX: TC Compressor/De-esser (v3.1), TbT plug-ins, Bionic Delay
- KVRAF
- 2686 posts since 5 Feb, 2004 from Nevada City, California
what audio interface you usin.?
-
- KVRist
- 157 posts since 15 May, 2005
It could well be that a plugin suffers the P4 denormal problem, where it uses more CPU when not in use (or dealing with small values, than when it is in use processing audio.
You could try bypassing plugins (which stops them processing) and then test the solo, that would probably confirm the theory.
Bas.
You could try bypassing plugins (which stops them processing) and then test the solo, that would probably confirm the theory.
Bas.
- KVRAF
- Topic Starter
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
So that is the denorm problem? Damn. I guess there isn't a list somewhere of denorm plugs...man, that sucks. Remind me why I don't use a Mac again??
I use both an EchoAudio MIA and (at work) and EchoAudio Darla24. I'm not terribly happy with either of them, but I'm not sure if that's got anything to do with it.
ford442 wrote:what audio interface you usin.?
I use both an EchoAudio MIA and (at work) and EchoAudio Darla24. I'm not terribly happy with either of them, but I'm not sure if that's got anything to do with it.
-
- KVRian
- 882 posts since 12 Mar, 2002 from London - UK
Because it would be easier and cheaper to simply get a CPU and updated plugins that don't suffer as badly from denormal problems than it would be to replace an entire machine + software??bduffy wrote:Remind me why I don't get a Mac again??
- KVRAF
- Topic Starter
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
Yeah, that would be the reason.cold c wrote:Because it would be easier and cheaper to simply get a CPU and updated plugins that don't suffer as badly from denormal problems than it would be to replace an entire machine + software??bduffy wrote:Remind me why I don't get a Mac again??
Superwave Performer...isn't that SynthEdit? I'm beginning to suspect Bionic Delay... Are there a lot of problems with SynthEdit stuff, or is it the SE programmer's fault?
-
- KVRian
- 882 posts since 12 Mar, 2002 from London - UK
I don't know, most of the synthedit stuff I use is MIDI only, and I use an AMD based machine so it is probably less noticable when it happens with any plug.bduffy wrote: Are there a lot of problems with SynthEdit stuff, or is it the SE programmer's fault?
As Bas suggested above, try isolating the problem with bypass or the off button to see which plug (if any) is causing the 'spike' on solo.
- KVRAF
- Topic Starter
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada