Bounce or Print

[bonzerboy]

I use several VI and find issues sometimes,,, so instead of having several VI open want to make audio tracks.. is it better to print or bounce the track,

Would this also apply tp printing or bouncing a final mix before mastering?










k

[Top Jimmy]

Why not freeze?

Otherwise...

Everybody Just Bounce!

[cwsand]

Originally Posted by bonzerboy

I use several VI and find issues sometimes,,, so instead of having several VI open want to make audio tracks.. is it better to print or bounce the track

I prefer to Commit Up To the VI plugin so that I'll have an audio track to work with - mainly because I just prefer working with actual audio tracks when mixing. Plus, it's good to have the VI printed in case for whatever reason the VI becomes unavailable at some point. You still have the MIDI/Instrument track you can go back to if you Commit, the only downside is that if you make changes to plugins after the VI or have automation on the audio track, you have to make sure to copy the changes back and forth.

[bonzerboy]

So is there better quality if you print then bounce or the vice versa ?

[Sardi]

Originally Posted by bonzerboy

So is there better quality if you print then bounce or the vice versa ?

No.

It’s just workflow. Sound is the same.


Sent from my iPhone using Tapatalk

[bonzerboy]

thanks,, I thought so but wasn't sure because someone told me printingthe track in real time was the wat to get all your automation correct and that bounce could mess up automation.

[cwsand]

Originally Posted by bonzerboy

thanks,, I thought so but wasn't sure because someone told me printing the track in real time was the wat to get all your automation correct and that bounce could mess up automation.

I have had VI's audio messed up when bouncing a mix or even freezing or committing - like glitches in the audio or tails cut off - another reason I like to commit them to audio and make sure the audio track is perfect so that you don't have to worry about it later.