return to tranceaddict TranceAddict Forums Archive > DJing / Production / Promotion > Production Studio

Pages: 1 [2] 3 4 5 6 7 
so what do you guys do to save CPU? (pg. 2)
View this Thread in Original format
dj jasonF
quote:
Originally posted by Chronosis
Instead of more RAM, you could have bought a decent audiocard that's designed for producing. Creative cards are usually more for gaming and multimedia, so they may cause trouble when running big audio programs.

I can recommend M-Audio cards.



an audiophile or delta is in my plans yes. but does it really help? i mean i dont need low latency for keyboards and stuff.
DRM
i use a couple of techniques to save my comp from collapsing as i hate to bump to wav too. Say i make a lead or pad in albino and its a huge hog on cpu when playing it all back together i will drop out two of the 4 osc's (preferably ones that dont alter the sound too much) and also maybe take off a couple of cpu hogging fx. This usually gives me enough of a chance to atleast listen to the thing all the way through without it maxing out and although its not the full sound it will give u a very good idea of how it sounds plus u can tweak till ur hearts content.
Dickie-T
quote:
Originally posted by DRM
i use a couple of techniques to save my comp from collapsing as i hate to bump to wav too. Say i make a lead or pad in albino and its a huge hog on cpu when playing it all back together i will drop out two of the 4 osc's (preferably ones that dont alter the sound too much) and also maybe take off a couple of cpu hogging fx. This usually gives me enough of a chance to atleast listen to the thing all the way through without it maxing out and although its not the full sound it will give u a very good idea of how it sounds plus u can tweak till ur hearts content.

yeah but you need a good memory that way, otherwise you will forget to turn those oscs back on when finalizing the project and then youve got a crappy production with cheap sounds
Storyteller
Good thing my sequencer automatically turns off VST which don't produce any sounds at the given time. This way have VST instruments won't use any cpu when they don't need to. Other than that I've got no problem running about 8 decent VST instruments, and a load of (vst) effects.
(amd2500+ processor here btw) I usually don't need any more than that, and my cpu actually never lags out.
/I\
fxfreeze is pretty cool ... I dont have any major fx on when im composing but turn them on at the end, before i do that i will up the buffer size on my mia midi to give my cpu a chance to catch up with all those fx on :D
/I\
storyteller, what sequncer r you using ? Im using SX and the thing just seems to hog cpu resources with inactive vsti's :(
[Alpha]Dave
I prefer to bounce all of the stuff to wave and arrange the whole track with allt the loops. If I want to change anything I just open the project with all the midi stuff and then bounce the specific file to wave and import it to my arranging-project.
That workds for me. :D
dj jasonF
quote:
Originally posted by [Alpha]Dave
I prefer to bounce all of the stuff to wave and arrange the whole track with allt the loops. If I want to change anything I just open the project with all the midi stuff and then bounce the specific file to wave and import it to my arranging-project.
That workds for me. :D


you dont "save" cpu that way if you can have all the vsts in one project then why export? most of the times the fx dont eat half as much as the actual instruments anyway
Chronosis
Just out of curiosity, I did some testing on my setup.
I could run 15 vanguards with the preset "Welcome" without crackling sounds, 16 was too much.

Hardware:
2GHz AMD
1GB RAM
M-Audio Delta 44

Software:
Windows XP
Cubase SX
John
quote:
Originally posted by Chronosis
Just out of curiosity, I did some testing on my setup.
I could run 15 vanguards with the preset "Welcome" without crackling sounds, 16 was too much.

Hardware:
2GHz AMD
1GB RAM
M-Audio Delta 44

Software:
Windows XP
Cubase SX


i tried 20 v-stations with different standardpatches and it ran fine here. couldn't be bothered to try more :)
i did have the usual latency but that's because i have a 9 yrs old creative soundcard at the moment (H)

DJule
You can freeze your tracks but it doesn't save that much CPU. It's better to keep the MIDI File and the preset of your synth and to bounce it. If you keep the MIDI File and the Preset file you'll be able to do every new changes you want.

Don't forget that having a high polyphony would take a lot of CPU. Try to put your FX in the send section instead of having them in the Insert section.

Having a lot of RAM and a good CPU is the first thing to check.

Having a good sound card and good buffers doesn't change a lot of things about the CPU. You can have CPU problems with the best soundcard and no problems with the cheapest one.
/I\
true and doesnt matter what the soundcard is :D

but upping your buffer size during post production helps to aleviate cpu spike problems :D
CLICK TO RETURN TO TOP OF PAGE
Pages: 1 [2] 3 4 5 6 7 
Privacy Statement