|
Lag!
|
View this Thread in Original format
| Elfs1der |
What does everyone do when they have many VSTi's running at once and it starts to lag. I know I can render to an audio file but, doesn't it piss you off if you render to an audio file then later on down the road you don't like that specific sound. It gets really annoying to have to redo the sound over and over again to tweak it.
Any better ways of making my workflow a little bit easier?
By the way I'm running 96khz,24-bit |
|
|
| thecYrus |
- run at 44,1 khz and 16 bit
- use external gear
- use sampler
- optimze your workflow (reverb in send-busses, ...)
- use DSP-cards: powercore, uad-1, ..
- ... |
|
|
| Sonicstyle |
| buy a faster processor |
|
|
| Elfs1der |
| quote: | Originally posted by thecYrus
- run at 44,1 khz and 16 bit
- use external gear
- use sampler
- optimze your workflow (reverb in send-busses, ...)
- use DSP-cards: powercore, uad-1, ..
- ... |
- Do you always run at 44.1/16-bit when creating the song?
- I don't have any external gear. I wanna get some but thats not an option right now
- When using a sample like Kontakt, do you make a whole bunch of samples and then put them together like dance eJay or something. What I'm trying to say is how do you know whats gonna sound like what together? |
|
|
| thecYrus |
| quote: | Originally posted by Rob
Get ASIO drivers? |
that affects only the latency and not the performance...
| quote: | - Do you always run at 44.1/16-bit when creating the song?
|
yes.. that's the same quality as an audio cd| quote: |
- When using a sample like Kontakt, do you make a whole bunch of samples and then put them together like dance eJay or something. What I'm trying to say is how do you know whats gonna sound like what together? |
no i would sample every note in a specified key-range and use it like a normal synth.. |
|
|
| superddman |
I totally understand your workflow concerns. Some people swear by consant bouncing but like you said it yourself when it comes to going editing the bounced parts it becomes a nightmare.
In this case there is only one solution, FREEZE.
Freeze in reality bounces the track. However, you can also quickly unfreeze (unbounce) the track which is the main advantage over normal bouncing.
Nowdays, some sequencers have Freeze function built-in, in particular Cubase SX, Logic 6, Sonar 4 (not sure if 3 does), Samplitdue/Sequoia 8 (not sure if 7 does too), and there might be few more.
If you are using one of these sequencers then you are in luck. You just click the Freeze function on a chosen track/vst and it will be frozen.
If not, there is a very cool app called FX Freeze which works very similarly to builtin Freeze. It wraps all the chosen VSTs into its own shell. Then you will see the wraped VSTs in your VST list under your sequencer. When you insert wrapped VST into your project, it comes with extra buttons at the top which allow you to quickly freeze and unfreeze. However, the new version of FX Freeze works even better then the built-ins (imo). It comes with a new plugin called Track Freeze. What it does is you insert this Track Freeze plugin as the last effect insert in the mixer strip. Then press the Freeze button. The whole output of the channel will be frozen including synths, effects and samples. Then you quickly bypass synths and effects which will not use cpu anymore and just very little of RAM. In logic this is so fast because to bypass VST you just CTRL+click on its name in the mixer strip. |
|
|
| Elfs1der |
| What do you mean bounces the track? |
|
|
| UphoricNitemare |
| so the freeze function does exactly what? sorry i'm stupid |
|
|
| superddman |
freeze=render=bounce=export :D
The only difference between freeze and render/bounce/export is that with freeze you can unfreeze (unbounce/unrender/unexport) the track.
Unfreeze = going back to the original state before rendering/freezing/bouncing. |
|
|
| DJ Chrono |
The easiest solution is to buy a new cpu.
I used to lag reason with my tracks (on 1.7gHz), so I got a 2.6GHz processor. It ran perfect for at least a year, reason had no problems at all.. until two days ago when I actually managed to make it lag and stop playback again. 27 tracks, 61 seperate devices on the rack. I can just barely get it to play through the climax of the song, it starts to sound alittle glitchy, and drops playback if I have any other programs open. A 3.2gHz or so would be ideal for a heavy processor intensive setup like that one. |
|
|
|
|
