Easy-to-follow video tutorials help you learn software, creative, and business skills.Become a member
It would be great if we could always do our work on the most current and powerful computers available. But the fact is that computers get old, software gets more powerful, and when an older computer meets new software you might have trouble keeping up, especially if it's a content creation program like Audition, where you might have dozens of tracks of audio playing simultaneously as well as effects applied to those tracks that Audition is rendering on the fly. I'm going to switch to fx, and earlier I touched on this Pre-render button that you can see here on each track and also if you're in the Mixer, you'll see it here as well.
It's the same button in both places. Now we saw earlier that some effects take up more processing power than others. For example, I'll add in an effect to this guitar track, I'll choose Reverb > Full Reverb. And again, I'm getting this message telling me that the selected effect might not be suitable for real-time playback because it's either CPU-intensive or high-latency. If I Click OK it adds it, but I can see that it's in red here. Now, I'm working on a relatively fast computer, and it's not going to have a problem rendering this effect. But if you are noticing performance issues in your playback, you can Click the Pre-render button.
Let's go ahead and close this for a moment. When you Pre-render an effect, Audition creates a temporary WAV file of the track with all the effects applied, and it plays that track when you listen to the mix. That way, you don't have to spent CPU power processing the effects on the fly each time. Now, you might have noticed that a little Progress Meter showed up right next to the track name while it was doing the rendering. Each time you make a change to the track, whether it's by adding another effect or simply moving the clip--let me just drag this to the right a little bit. You can see it's now rewriting the track, and that lets you know that Audition is creating that WAV file each time.
I'll move it back and you'll see it render again. There it goes. But each time it does this every change you make will result in Audition creating a new version of that temporary WAV file. Again, if you have a relatively modern and fast computer, you might not have to worry about this. But if things are a bit sluggish for you, you can give Pre-rendering a try. As you saw it takes a couple of seconds for the WAV file to be written and a lot of that depends on how long a particular track is. But Pre-rendering should solve any playback issues you may have. Now if you find you no longer need pre-rendering-- maybe you remove the effect altogether-- it's a simple matter to just turn this off, so Audition isn't writing a new temporary file each time you make a change to the track.
Get unlimited access to all courses for just $25/month.Become a member
73 Video lessons · 16633 Viewers
130 Video lessons · 18353 Viewers
110 Video lessons · 10006 Viewers
71 Video lessons · 13673 Viewers
Access exercise files from a button right under the course name.
Search within course videos and transcripts, and jump right to the results.
Remove icons showing you already watched videos if you want to start over.
Make the video wide, narrow, full-screen, or pop the player out of the page into its own window.
Click on text in the transcript to jump to that spot in the video. As the video plays, the relevant spot in the transcript will be highlighted.
Your file was successfully uploaded.