Pro Tools 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 ca
issue Previous Issues Subscribe Advertise Search ReviewsArticles Search Search TechniquesArticles Search PeopleArticles Search Sound AdviceArticles Search Music BusinessArticles Search Articles Search You are hereHomeTechniques Troubleshooting Your Pro Tools System Pro Tools Tips & TechniquesSoftware > DAW > Pro ToolsPublished May 2005By Mike ThorntonWhatever computer recording system you use, the chances are it's going to fall over sooner or later, and Pro Tools is no exception. So before you call the technical support line, take a look at Sound On Sound 's guide to diagnosing and fixing the most common faults. For the first of our Pro Tools workshops, we're going to look at http://duc.avid.com/showthread.php?t=127308 some of the most common problems that can occur when you're using the program — usually when you're in a crucial session, or up against an immovable deadline! As you've probably found, Pro Tools has a habit of generating some rather cryptic error messages when things go wrong, so firstly, let's see if we can demistify some of these. * DAE error 9035 This can come up for one of http://www.soundonsound.com/techniques/troubleshooting-your-pro-tools-system two reasons. One is that the drive that you use for audio (and you aren't using the drive that has your operating system and applications, are you?) is getting close to full. The best way to resolve this is to use a different drive with more space on it. Failing that, clear some space on your audio drive by backing up some old Sessions and then deleting them. To stop this error message returning you may also need to defragment your drive, so that the empty space on your drive is all in the same place rather than scattered across the drive in little pieces. However, if it's an emergency and you don't have time to clean up your drive properly, you can get some short-term relief from this error by reducing the Open Ended Record Allocation to a smaller value. This is done by going into Preferences in the Setup menu; in the Operations tab, set the recording allocation to 30 minutes or less.A quick fix for errors relating to lack of hard drive space is to change the Open Ended Record Allocation to a fixed value. The other reason this error message can appear is if a Pro Tools Session (or files within a S
Database Merchandise Music Biz Articles Tips & Techniques Video Vault Directory / Jobs Posting Guidelines Support Us events competitions newsletter classifieds reviews deal https://www.gearslutz.com/board/music-computers/189433-dae-9035-error-pro-tools.html zone gear database Best Studio Gear More Chat Room Merchandise Tips http://dae.error.9035.winadvice.org/ & 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 I would like to join pro tools 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 7th April 2008 #1 Deadheart Gear pro tools error 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 too slow (is it a Mac drive?) . Check "ignore ownership on this volume" in the di