Pro Tools Dae Error 9035
Mbox, Digi 001 (Mac) DAE error -9035 encountered User Name Remember Me? Password Register FAQ Today's Posts Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 01-26-2005, 12:10 AM proaudionyc Member Join Date: Jan 2005 Posts: 3 DAE error -9035 encountered Here's my set up: G5 dual 1.8 10.3.4 > 002 > PT6.4LE The Problem: I am getting this message when trying to playback multi-track files that were originally recorded on an older version of PT ONLY. All of my recent or new sessions work perfect. These older files were recorded in PT 5.x LE through a 001 and although I can currently view the waveforms, etc., When I go to play them back with my 002, I get this error. I have also noticed that within these older files the input and output(s) seem to want to read from the equipment they were originally recorded on, meaning the names of those sources remain. Does anyone know how I can enable these tracks to play. I can even edit any of the files but cannot playback or for that matter record. Any help would be appreciated!!!! Remember all the current files work like a charm. But its these older ones I now need to work with. Thank you. This is pretty much an exact opposite problem that another user just posted in this forum. Hopefully both of our problems can now be solved. Grateful and thankful for any and all help. proaudionyc View Public Profile Send a private message to proaudionyc Find all posts by proaudionyc #2 01-26-2005, 07:44 AM Brent Flash Member Join Date: Jun 2004 Location: Louisiana Posts: 214 Re: DAE error -9035 encountered Here is some info from the answer base. It may help. 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 wit
have a Whole Session that i'm trying to Play , but After i recorded guitar into the session and tried to go but and Play it " Dae error -9035" come up on the screen and i couldn't play the session , How Do i fix that ? I'm working with the Mbox Pro tools Le 6.2.2 Joseph Hanna01-23-2005, 02:14 AMThe -9035 error can occur for many reasons on Mac OS X and WinXP (see Answerbase articles 26115, 26300, 26662, http://duc.avid.com/showthread.php?t=127308 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 https://www.sweetwater.com/forums/archive/index.php/t-7789.html 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. 58gretsch02-06-2005, 07:51 AMTry defragmenting your audio drive. The audio drive may be near capacity. Or open a new session and import everything into the new session. Don't name the session with characters such as ,> / * 31 character limit. Powered by vBulletin Version 4.2.2 Copyright © 2016 vBulletin Solutions, Inc. All rights reserved.
Database Merchandise Music Biz Articles Tips & Techniques Video Vault Directory / Jobs Posting Guidelines Support Us events competitions newsletter https://www.gearslutz.com/board/music-computers/189433-dae-9035-error-pro-tools.html classifieds reviews deal zone gear database Best Studio Gear More Chat Room Merchandise Tips & Techniques Video Vault Directory / Jobs Support Us Today's Posts support us FAQ advertise our advertisers Search This Thread Search This Forum Search Gearslutz Go Advanced Home The Forums Music Computers DAE 9035 error Pro Tools Login / Join Join with Facebook Username pro tools I would like to join I am already a member Password Remember Me? Connect with Facebook Quick Links Today's Posts Mark Forums Read Open Contacts Popup Networking Contacts Social Groups User Control Panel Edit Avatar Edit Your Details Edit Options Miscellaneous Subscribed Threads Your Profile User Tagging Statistics DAE 9035 error Pro Tools New Reply Thread Tools Search thread pro tools dae 7th April 2008 #1 Deadheart Gear interested Thread Starter DAE 9035 error Pro Tools I'm running an M-Box 2 on a Intel 2Ghz computer. Everytime I start protools and play any audio the DAE 9035 error comes up. This happened just after I repaired disk permissions with Discwarrior 4. I read in another forum that this problem might occure after doing so but there was no suggestion as how to solve it. I re-installed pro tools and even re-installed OSX and the problem still remains. What should I do? I have a school assignment due for next week so I'm getting quite stressed out... Share Quote 7th April 2008 #2 Deadheart Gear interested Thread Starter Oh... and I just discovered that the sessions on my internal harddrive work perfectly well but the ones on the external doesn't. Also if I import the sessions from my external to my internal harddrive they seem to work... hmmm... Share Quote 7th April 2008 #3 Volodia Lives for gear Your external drive may be