|
|
|
|
|
|
Q:
None of the other solutions for the DAE Error -9035 (in Pro Tools) are working for me. What else might I try?
A:
The -9035 error can occur for many reasons on Mac OS X and WinXP (see Answerbase articles 26115, 26300, 26662, 27679). Here are some of the more unusual causes and workarounds:
- Unsupported SCSI card; check compatibility information. - Audio files were manually removed (outside of Pro Tools) while the session was still open. - Bouncing to multichannel format. Try bouncing to a file format other than multi-mono. This will force Pro Tools to convert after bounce. Also try choosing a destination other than your session audio files folder. - The Mixer is passing data regardless of whether there is audio on the track or not, so the more tracks you have open the busier the PCI bus. The way to stop this is to mute tracks when they are not needed and turn on "Mute frees voices". - This was seen with Pro Tools LE 6.1 sessions that were created on ATA drives, backed up to Avid LANshare, and restored back to ATA drives. At the time of this writing, Pro Tools does not support LANshare. - Corrupt fades can cause this. Trashing the fade files (and thus forcing Pro Tools to recalculate them) may resolve the issue. - In one case disabling FileVault resolved the problem.
Other Popular Articles:
I'm still getting DAE error -9035 with Pro Tools 6.4 on Mac OSX. DAE -1103 error accompanied by Unable to acquire audio hardware message in Pro Tools 6.4 with AVoption|V10. Is the Korg D1600mkII compatable with Windows 98 or ME? How do I get the Korg D1600mkII into USB mode? Why isn't my Korg D1600mkII showing up on my Windows PC? |