dolomick wrote: What a hassle. Since pretty much all DAWS do timestretching nowadays and that is Ableton's claim to fame, I might have to agree with this. I don't like having to bounce around DAW's as it kills the creative flow, requires maintaining multiple project files, etc.
As for sdfak1234's bounce and print workflow, I'm fine with that... BUT... once the audio is bounced, and you want to add a few fx to the newly bounced audio and reprint again... isn't this issue continually cropping up? I suppose what you must do is then manually align the newly printed audio as soon it is rendered? I think I am beginning to see how to work around this timing issue if I were so-inclined, thanks! Not saying I AM so-inclined, however. But I'll consider it.
only if you had automation on the lane, then a new fx would throw it off, you'd have to bounce first then add the fx then automate that, then bounce again... very very constraining, but straight audio effects will compensate fine, one way around the automation issue is to not use automation, I actually do avoid it nowadays, I'll use alternatives, maybe max4live effects will be useful for automating because they should be compensated, but they never seem that precise to me, also I use a lot of internal envelopes, love the multis in massive, omnisphere, harmor, etc but otherwise everything kinda relies on capturing 'live' moments and editing them, I like that part of live actually, but I can do that in cubase quite easily now, it used to be a bitch, and the bounce/print editing I can do in cubase is faster and better quality actually, easier fades, nice timestretch, built in variaudio...
So yeah people work around these issues as best they can, my rule these days is that if I'm automating, I'm recording everything as sound and editing.... it's annoying using freeze too because that also compensates.
