Why do "some tracks need to render in real time"

??

never done this before

In regards to the difference between an offline Vs. realtime bounce?

If you’ve a lot of sh!t going on in the individual track / overall tune, you can listen to it to hear for mistakes,pops, crackles etc… and if the computer is going slower, its a happier experience for the CPU… so less chance of automation being missed or fx going spazmo.

Thats my understanding of it

yeah there is definatley lots going on. so i should stop being a lazy bum and bounce some tracks to audio ?

Well… I suppose it depends what ya want.

If you want to commit to something - yeah.

Its probably handier sometimes to bounce synths or parts, whatever w/out eq or delay or reverb etc… if you might need to change it later.

If you are bouncing, watch out that you dont have them in the red. 

Stuff thats cool… bounce it - or bounce it with the fx that wont need changing.

I’d bounce what you need & then make a copy of your project - TRACK No.2 - then delete the channels that you bounced. You can always go back to the old project if you need to.

You’re cool, cos you can group your fx into racks & paste them onto the new audio track.

you also need to render in realtime if you are using any external equipment

[quote]phil johnston (12/03/2011)[hr]you also need to render in realtime if you are using any external equipment[/quote]



this

That will be it Phil. I used the external plug, recorded stuff in, but didn’t turn it off before rendering.