I have an AMD 1 gHz processor and 300MB of RAM. I created a song using only VST instruments, there are 8 drum tracks and about 8 tracks with sounds, 1 audio track. I applied Insert effects to 5 of them 2 effects for each track and VST performance shows CPU usage of 100%. How could be this be? Is there anything I can do?
My computer hangs every time I get to the middle of the song.

Well...some vsti's/plugins eat more cpu than others...
but stick to this..:

-Make sure your windows is on a seperate partition and get rid of internetexplorer.

-The only thing installed is your Sequencer and the plugins/vsti's

-Use newest ASIO drivers for your soundcard (you should increase latency when dropouts ocur...)and use a 'good' soundcard ofcourse

-Set cubase to high priority for audio...

-Try to use send fx in stead of inserts...

well... there can be more...

WaveShaper

Thanks for advice, WaveShaper.
Cubase is the only program I have open.
I also have CDR-W installed but it should not effect it.
I have Delta44 as my sound card. I got the drives from the CD that cam with the card.
Set cubase to high priority for audio - How do I do that?

I meant the only program on your windows...
You can make three partitions...one for music...one normal windows...and a third DATA(you won't see the windows partition not running...)

you can chage priority in the audio configuration window (I can't check cubase because of dualboot)
and than change priority to scheme 4 or highest priority...

WaveShaper

Thanks, I'll try that.

Everybody gets spiking sooner or later.

I have a workround if it's any use:

- Sketch out your tracks without any fx till the tune sounds right. Usually the cpu can handle this.

- Apply compression, fx, mega-tweaking or more cpu intensive voicing, whatever, to one track, then lay this track off to audio (export function on master mixer). Audio tracks are easy on cpu.

- Switch off the VSTi and fx you've just been using. This brings cpu down again. You can also mute the midi track too so you don't get confused later on by which tracks are on or off.

- Layoff all the tracks to audio one at a time. It's a but like recording a band ... one at a time.

- All VSTIs should now be switched off, all midi tracks muted, and just your audio tracks remain. These should play fine. If they don't, go to Options/Audio and increase the buffer size.

- Now you can mix your tracks as audio with fx etc ... just like a band.

- You might need to layoff your audio tracks to a single master track if you're short of cpu for the final master fx (stereo width, reverb? multiband compression, saturator etc).

I'm sure there are other ways to maximise cpu, but this works for me.

Thanx, kevvvvv. This sounds like a great solution. What if I export all midi as audio and apply all the effects to audio tracks. This should not eat up as much memory correct?

Kevvv, interesting descovery. I exported my VST track dry and applied the same effects to an audio track. It ate up the same CPU resources as a VST did. I guess I have to apply all effects first and them export.

Hi Waveshaper!

Explain me please, whats the difference between send- and insert effects, upon CPU usage? (Aha, may it be the limited number of them, i.e. more tracks share the same fx?)

AndrewW,

You're right ... forgot to mention switch off VSTIs ... whole point (-:

I don't always lay off dry though.

I try to think how a performer would record, eg, a "guitarist" would want his chorus or phaser in there at the beginning.

And thinking ahead, it's cpu-friendly to do comp and eq where possible in advance.

The more you can do before you lay off, the better.

If anyone else wants to chip into this thread, please do.

After all, we all spike sooner or later.

Just wondering, what VSTi's are you using on your 8 tracks. Is this 8 different VSTi's or one multitimbral. I'm almost using only VSTi's on a PIII850mHz, and can easily get much more than 8 tracks. The times my CPU get in trouble is when I use high polyfony with long decay-sounds, like pianos, used with the sustainpedal.

I've found that optimizing the VSTi's, can free CPU usage, like setting pianosounds to a limit of 16 voices, and always play basses monofonic. Guitars always only 6 voices ( maybe not right, but i think its the real polyfony of a guitar ) Since almost all VSTi synths also have the ability to set the number of voices, always set the limit to what you actually use.

If the FX's are eating your CPU, try to use send FX's where it's possible, and collect simulare FX's to a submix (group-channel)

Thanks alot for all your comments, guys, but the I can't import my freaking tracks now. I export it fine, but when I go to import, it crashes on Redrawing Image dialog. I tried like 10 times with different tracks and no luck. Please help. Oh, I have VST/32 R1.

RMH,

Whether to apply fx before or after laying off to audio is a cpu juggling act, spreading its usage.

Some practical examples:

- compression/limiting often can be applied before laying off. This can save cpu later, in the audio stage.

- ditto eq. You know that a sequence or an acoustic guitar is going to have the bass rubbed out, so eq first before laying off.

- All the live synth knob tweaks are obviously done first, before laying off.

- comb filters and striking fx (frohmage, distortion, autopanning etc) that you know you want to keep are likewise done first.

- On the other hand, delay and reverb (unless it's special) can be left until later, and then in the group channels, saving cpu.

- ditto with eq de-muddying and refining. Comes last.

At each stage I save as a different .all file so I can backtrack in case I discover a mistake later on.

I've just run up a track using 16 Pentagons and a DR-008 using this technique. It all come through without falling over drastically, or forcing me to compromise.

The final mastering stage involved another lay-off to audio for multi-band comp etc.

I'm not suggesting my technique is a recognised method or a pro-short cut.

It's just what I've been forced to develop in-house to stop cpu spiking killing off a song, and killing me off with it .... aaarrgghh!

RMH,
after you export your dry VSTi tracks and have them on the arrange window, TURN OFF YOUR VSTi'S !!! You can also mute your midi tracks, as they are not used anymore. Now these dry tracks plus VST FX should not eat as much CPU. If it's the same as before, as far as CPU usage, there is something not right about your system. But what I've said here, should solve your problem. Although rendering the whole song at once is so much easier and takes a lot less space on the hard drive.