I'm sure I'm missing a very simple tick box here, but when I'm working on a project and I'm stretching and pitch-changing files, and I choose "rendered" as opposed to "Real Time"; how can I tell Audition to save the rendered files, so that it doesn't have to re-render them every time I open the project?
I'm sure there will be other suggestions but two ways for you to try would be:
Work in Waveform view and hit Save or Save As once you have the changes you want. (I prefer Save As so I can keep a clean copy of my original for when I change my mind.)
In Multrack View get all the effects you want done then do a mixdown, even if it's only a single track (obviously saving the mixdown with an appropriate name). This'll give you a new track with all your effects already done.
Many thanks. Meaning no disrespect of course, but I do hope there are other suggestions too!
A big project may have 10 or 15 or more instances, across a number of tracks, some clips lasting a less than a second. Would I really have to render and re-import every instance individually? I consider this something of a major flaw, then.
Once I've individually selected "Rendered" against an effect, or have run "Render all Stretched clips", my project now has all the right clips in the right places, fully rendered.
Surely it must be possible to save that state, to return to next time? If it isn't, that's simply crazy!
Perhaps you could give a bit more information about your project and what you're trying to achieve?
All the render command in Audition does is "lock" a certain effect in place to ease the pressure on you CPU while you work. It's not intended as a way to finalise a project like in Premiere Pro (making the name pretty confusing to PP users).
Thanks Bob. Let me explain the problem another way.
I start a new project. I record or import a wave. I time-stretch the wave, I select "Rendered (High Quality", and the little clock symbol appears for a couple of seconds or so while the wave is rendered. Now when I hit play I hear the rendered wave.
I now enclose the project. I immediately reopen the project. As soon as the project reopens, up comes the little clock symbol again while the wave is rendered. I then close the project again. I re-open the project again, and once again I have to wait a couple of seconds while the wave renders. This is the issue I'm talking about. Surely it must be possible to save the project in such a way that when I close and reopen it, it loads the rendered wave, rather than having to re-render it on every opening of the project.
Any thoughts anyone can offer would be much appreciated, cheers.
Aidan this is the way that Audition 3 worked, it saved the rendered file in a folder at the project directory called locked files. CS6 and later appears to rebuild the rendered file everytime you open the session. This works around a few problems, like:
1. Start a session
2. Render a file
3. Save session
4. Rendered file is saved off
5. Now edit the unrendered file outside of the session, maybe in another DAW.
6. Reopen the session
7. Now the rendered file is still being played, even though the underlying file has been completely changed/altered by some other DAW.
But it's point 5 that concerns me.
I just looked at a recent large project. It consisted of 48 audio tracks. I started counting up how many files I'd made pitch or time changes to and which would therefore need rendering, and when I got to 30 I gave up counting. And some of those, too, also are tiny, fraction-of-a-second, files; extremely difficult to isolate out of context. Opening every single one individually would take literally many hours of work.
The reason for creating this thread and looking for a solution to this problem is that when I have a project such as the one above, with a large number of altered files, opening it can take several minutes. If for any reason I have to close a project to reference something else and then reopen it, that can be a go-away-and-make-a-cup-of-tea-and-come-back process! Most annoying.
I believe it's just that your workflow doesn't match the Audition philosophy.
In Audition, real time effects in multitrack view are non destructive and not meant to make any permanent changes to your original file. That's the province of the Waveform (Edit) View where edits are permanent.
The "render" feature is not meant to be an actual part of the production process. As I said earlier, it's just a temporary "lock" (indeed, in older versions of Audition it was called locking an effect) to take the pressure of the CPU when working. However, it leaves your original file intact in case you want changes later.
None of this helps your particular situation of course--it's just an attempt to explain where the Audition theory of workflow is coming from. When I have a bunch of CPU intensive processes to the point where my computer can't keep up (and that's fairly rare these days) I just finish the effect in Waveform and "Save As". Frankly, it's not many more keystrokes than using the render button.
As I said, maybe somebody else will have something I haven't thought of, but I'm out of ideas.
Many thanks indeed for your thoughts, Bob. I have several years of Premiere Pro behind me, so I guess that explains where my own work philosophy comes from, and I completely concur with you regarding Premiere's more permanent "Rendering" vs Audition's "lock". That said, though, a locked effect is clean and of higher quality than "real time". A rendered file has indeed been created and is indeed being read by Audition, so my argument remains that Audition should be able to remember that rendered file when returning to the project.
However, again thank you for your help. I guess at the end of the day there's nothing wrong with "go-away-and-make-a-cup-of-tea-and-come-back" waiting periods. I'm one of those people who sits down at the computer… and five hours later… If Audition forces me to stand up and stretch my legs once in awhile, that's probably ultimately better for me than saving rendered files would be!