I have a AMD 64 3000+ , 1Gig Ram, 80gig 7200RPM HD, and a EMU 0404 sound card....
I use cubase sx 2.0, with vsts like z3ta, vanguard, v-station, triangle II

After working on a trance project for a bit (maybe after inserting 9 to 10 vst instruments into the project)... the sound start lagging baddly as if im using my grandfathers 16bit ISA sound card to produce...

It says under VST performance CPU at 80 to 100 percent ... which obviously is the problem....
but what is the solution...

Is it really the CPU speed? More Ram? Better Sound card? can anyone help me so production gets laggless for me...

Thanks

I got the solution, no money, well for 30 days anyway

http://www.fxfreeze.com/

adios

I have same problem but i looked atthe software u provided a link too and what is it doing?

freezing parts of your track i dont understand it?

it 'records' all vst action into audio samples, so the vst's can be turned off and less cpu is eaten

this can be done manually too, but with fxfreeze its sooooo easy, everything goes automatic and when u want to tweak the preset just turn freeze off and freeze it again, time & effort saver

Is their any other Freeze vst's out there?

___________________
Siberian Sun "Forstbite" - Dedicated
Fred Baker "la parts des anges" Siberian sun remix - asot
Nautical Imagery "distant Dreams" Enhanced Recordings
Mannix -v- Kaymak "World gone mad" A State of Trance

Yes the problem lies with your CPU's power. It can't hang. I had the same problem until I bought a P4 Hyper-Threading proc (Basically a dual CPU). The bastard is a workhorse now. In the meantime, Cubase 2 has built-in freeze capability. Just hit F11 to bring up your VSTi menu and you will see next to the VSTi's name, for example Vanguard, there will be a little snowflake icon. Hit that, and Cubase will freeze the entire track. The track will gray out and you won't be able to do anything to it until you unfreeze the track.

This works well however it is time consuming. An easier method is if your track is nothing more than looping midi segments, export that track alone and import it into your pool was a wav file. Then remove the VSTi used to create the sound, freeing up more CPU power for you to use elsewhere.

___________________

-Facebook- -SoundCloud-

quote:

Originally posted by Magnus Yes the problem lies with your CPU's power. It can't hang. I had the same problem until I bought a P4 Hyper-Threading proc (Basically a dual CPU). The bastard is a workhorse now. In the meantime, Cubase 2 has built-in freeze capability. Just hit F11 to bring up your VSTi menu and you will see next to the VSTi's name, for example Vanguard, there will be a little snowflake icon. Hit that, and Cubase will freeze the entire track. The track will gray out and you won't be able to do anything to it until you unfreeze the track. This works well however it is time consuming. An easier method is if your track is nothing more than looping midi segments, export that track alone and import it into your pool was a wav file. Then remove the VSTi used to create the sound, freeing up more CPU power for you to use elsewhere.

Pentium 4 HT you say.....
what frequency (speed is it)? single or dual you say? and your saying an AMD 64bit 3000+ cant keep up with it? i didnt know a p4 ht would make that much of a difference over a 64bit amd

Cubase SX has always had a freeze function.. although not official..

I think Freeze function in SX 2 sucks.. badly.. it takes ages for it to freeze and so on..

what u need to do instead of "freezing" is..to export whatever u would like to freeze for instance a melody.. lets say its 8 bars long.. what u do then is that u put the markers on this melody so u get 16 bars of it rendered to audio.. then u cut of the 8 first bars of the 16 bars melody and u copy and past that along (which means all ur delay settings and stuff will be right) put the MIDI track in a folder.. press F 11 then just simply disable the VST its using..

if u later on feel the need to change anything on that melody u just enable that VST and viola..

___________________


http://soundcloud.com/subtara

quote:

Originally posted by digitalifeform Pentium 4 HT you say..... what frequency (speed is it)? single or dual you say? and your saying an AMD 64bit 3000+ cant keep up with it? i didnt know a p4 ht would make that much of a difference over a 64bit amd

Its a 3.2Ghz HT. HT is essentially dual processor. When I go to Task Manager, I see 2 CPU performance graphs independantly of each other. I've got a GB of ram as well. All I know is I got frustrated on my old computer, an Athlon XP 3000+, which also had a GB of ram in it. The 3.2Ghz HT can literally handle 2 times the amount that my Athlon XP could. I'm not sure if its the Hyper Threading that is responsible for this major performance increase but I'm thinking it is. Maybe the Pentium handles audio production code differently than an Athlon, but I'm not really sure.

___________________

-Facebook- -SoundCloud-

HT will only help if the software was written to use HT, but I would assume something like Cubase SX would use HT as it's a CPU hog.

So you're probably right, HT is likely helping a bunch.

thank guys... ill probably look into getting a HT processor. But just incase I decide to go with a MAC, what min specs you think I should get to keep things going smoothly? Dual 2.0 G5's? More? less?

They say 2.4 G5s processors are equal to P4 3.2 HT chips or better.

I don't know if is truth, but watch out, first check if the programs you have are compatible with Mac, unless you are planning to use XP as a sub-platform of it.

___________________
Der Mystik's Music