Music media player for mac. Need help with your computer? At Boxaid remote computer repair we can help you with Windows or Mac problems such as slow performance or virus removal service at an affordable price. Mac computers are easy to use, for the most part. Aug 22, 2018 - You finished your mix -it totally rocks!- and now it's time to send it off for mastering but how? Sound familiar? Use the Selector tool to select the length of the session in the Timeline. Pro Tools File menu with Bounce to. And Disk highlighted. Mac Finder window opened to the Bounced Files folder.

Bounce Handler: This is what happens when Pro Tools is reading from and writing to the same drive at once. Fix it by connecting an external drive to bounce to Pro Tools might be the industry-standard software for sound production, but that doesn’t mean it always run smoothly.

And when things go wrong, it’s often in extremely obscure and frustrating ways. This is because Pro Tools demands a very specific environment and set of circumstances to operate properly – it likes well-ordered folders, FireWire connections, big mixing desks and lots of RAM. When it has these it’ll purr like a cat, doing everything you ask of it with minimum fuss. But pull it out of its comfort zone – like, for example, on a laptop without FireWire – and you’ll almost certainly start encountering problems. These problems are often expressed as error codes, with either limited information attached or none at all. Now, the response of any sane person is to plug the code into the manufacturer’s website, but Avid has no publicly available list of Pro Tools error codes, and the Knowledge Base is (we just have to say this) next to useless. In this Pro Tools tutorial therefore, we’re going to demystify some of the most common Pro Tools errors and show you how to fix them.

Call it a headache pill for your audio. In The Driving Seat Let’s start with one of the more common and irritating errors: -9073.

This usually occurs during playback (not too much of a problem) or export (a real problem). It’s accompanied by the message ‘DAE can’t get audio from the drive(s) fast enough. Your drive may be too slow or fragmented, or a FireWire drive could be having trouble due to the extra FireWire bandwidth or CPU load (-9073).’ This error can sometimes also manifest itself as the cryptic ‘Bounce handler cannot keep up (-9132)’. Both mean essentially the same thing, and both can be fixed with the same solution.

Pro Tools bounces down audio in real time. To do this effectively it needs to use a good chunk of your computer’s internal processing. If your session audio is stored on your computer’s hard drive or you’re bouncing your mix onto that drive, Pro Tools will freak out – especially if you have a lot of tracks and plug-ins or an extra-long session. The first solution is to raise the buffer size and dedicate more of your CPU to the program – both can be done in the Playback Engine, which you’ll find in the Setup menu. What the program really likes is for all session data to be stored on an external FireWire drive, while the program itself is stored on the computer. If you’ve got a FireWire drive to hand, then consider the problem solved: just copy your session folder onto it, open it and export onto the same drive. Drive Too Slow: If you’re not seeing the bounce handler error you might see this instead – the solution for that one works here too It’s when you don’t have FireWire that things become problematic.

Pro Tools – this is hysterical, by the way – isn’t tested with USB, so there’s no guarantee that errors won’t pop up if you use a regular USB external drive. Fortunately, in our experience, things tend to run smoothly as long as the drive is fast enough. By that we mean it needs to be USB 3.0 and it has to run at 7,200RPM (most drives these days do).