There is a growing thread on the Digidesign User Conference on 9019 and 9031 errors on Pro Tools 8.0.3 It was started by Nathaniel Reichman asking…
Since moving from the various 8.0.1 releases to 8.0.3, I frequently get the message:
“DAE is having trouble keeping up. Your disk may be too slow…firewire, etc., etc. (-9019)” which is followed by a beachball and then: “DAE error -9031 was encountered.”
And this repeats until we quit the app and relaunch. Sometimes hours go by with no problem, sometimes we get this 3 times in an hour. We haven’t seen this in PTHD, only on the PTLE/CPTK system listed below. We tried trashing databases and volumes folder.
After some system and workflow checks Reichman confirmed…
Nothing has changed in my typical post workflow or drive usage since PT 7.3.
Thanks for posting, but I really doubt the non-contiguous file theory. If that were true, none of my projects would have worked with any version of Pro Tools. For now, I blame the .3.
“Garnoil” responded….
Ok, so it must be .3. I am on 8.03 and although I had one massive, annoying, problem (0922 too many files corruption), 8.03 *at least for me*, has been a great improvement. I run HD2 and push it to the limit, I mean 192 voices (160 tracks+) + full HD film at 2k resolution. So far, so good but of course there are lots of bugz to fix, some worse than others. Good luck!
Then Digi Tech Support weighed in…
I see you have an eSATA hotswap tower in there – is that what you’re using for playback/record? If so, have you tested with other drive types?
9019 is a drive error related to drive communication speed – we usually see it on PC’s where drives are not in DMA mode.
The 9031 error is usually related to having illegal characters in the drive, file or folder name – is that possibly the case here (keep in mind that previously fudged illegal character acceptance is no longer possible, so what may have ‘worked’ before no longer will)?
Reichman responded….
Yes. And I know it’s not officially approved, but it’s performed flawlessly every since PT 7.3 on a G5. I thought I cleaned out all of my illegal characters in the PT6-7 transition. Thank you for writing back so quickly. I’ll report back if I learn anything.
The “smpkeys” chipped in….
I just experienced this same problem. I’ve been on 8.0.3 for about 2 weeks and have not seen this, however , tonight I was using the playlist lanes view for the first time, and that’s when it occurred. All my drives are internal SATAs – 1 for OS, 1 for audio, 1 for samples. Not using any video in my session, and no illegal characters. Reichman – have you found a solution with your setup?
Reichman replied…
Haven’t found a solution yet, primarily because it is happening infrequently now. Occurred once yesterday when opening an AudioSuite plug-in window.
Every time it does happen, it will continue persistently until I save, quit and restart PT.
When I get out from under this mountain of work, I’ll try another drive type for a while and see if that helps.
For the record PT 8.0.3 is really stable. For PT8 doubters, now is the time to get on board (is Frank Kruse reading this?)
Digi Tech Support came back with a request…
Can you guys do something for me – after you experience the error, quit Pro Tools as soon as possible after it, then send me your LogFiles folder from inside your Pro Tools folder. Zip it up and send it to: vi [at] digidesign [dot] com. Put the thread number (265212) and ’9031′ in the subject of the message.
“Sunzate” added…
I’m getting these errors right now with a midi-only session, controlling the PLAY EastWest orchestral plug-in. Never seen it before today. Recently updated to 8.0.3. Let me know how I can help.
Then “Oroz” asked…
I’m getting the DAE error -9031 a lot! Can you further explain what do you mean by illegal characters in the drive? How can I solve it?
Digi Tech Support replied…
Your Pro Tools Reference Guide has a list of unsupported characters. You should make sure that no drive, folder or file name contains any of those characters.
This error on Mac is also caused by incorrect drive format. I would recommend backing up your audio/video drives and erasing them using the Disk Utility, then copy the data back and test again.
Oroz asked…
Do you think that it may be because I’m recording to a partition (dedicated to audio) of the internal drive? If so, would a USB external drive be a solution? Since I’m on an iMac there’s only one Firewire 800 port. I have read successful stories from guys using USB drive as an alternative but I’m not sure.
Digi Tech Support replied…
Recording to a partition or to a USB drive is not recommended or supported and definitely could be a cause for these errors. Please see the General Troubleshooting thread for more details. With an iMac that has only one FW800 port, get a FW800 to FW400 cable to connect to your drives and interface.
smpkeys posted…
Just happened to me again on Saturday. This time when it happened, I was changing the output of a channel. Digi, I’ve zipped and sent my log file using the directions posted earlier. One more thing – I had trashed prefs about 2 hrs before this crash.
So a couple of lessons from this thread. You cannot use USB drives for Pro Tools sessions. USB needs processor time to negotiate the data transfer on and off them and does it when it gets round to it. Where as Firewire has dedicated chips on the interface to manage the data transfer in a timely manner.
You must have correctly formatted drives irrespective of what platform you are running on. On the Mac platform that must be Mac OS Extended with journalling. I recommend you format your drives with Disk utility rather than any 3rd party formatting software.
Check the characters that are used for naming anything. Drives, folder, file names.
Mike is Pro Tools genius and an award winning ‘audiomeister’, defined as ‘a person of great skill and authority in sound’. His vast array of credits include music (from classical to rock), drama and documentaries across all the BBC Radio networks, as well as audio post production for video and TV, ‘new media’, live sound, commercial CDs, DVDs and podcasts, helping clients tell their stories with sound. He has been described as "an oasis of calm in a stormy creative world"; "quick, creative & easy to work with"; "always going the extra mile"; and "invests himself in the success of your project"’.show me less content in the footer
show me more content in the footer
Seven radio producers – all based in the north of England – have joined forces to launch a new co-operative venture – ‘Radio Wizards’. It’s equally remarkable that their aim now is to work together on every kind of sound production... except radio!
"It’s taken over a year to get to this point," says ‘wizard’ Mike Thornton, "but now we’ve got a viable business plan, we’ve launched our website and we’re already starting to attract commissions. As a facilities provider we decided to facilitate this partnership and set them up with a web site to help kickstart this excellent partnership."
April 8, 2010 at 7:51 pm
I’m having the same issue, and just cropped up today after I was experimenting with elastic pitch changes.
April 18, 2010 at 6:02 am
I`m having the same problem. It seams to be certain sessions and when I hit play back. I have a mac pro mbox2 pro. 8.0.3.
Having to restart pro tools everytime and some times it keeps happening again and again. Anyone found a fix yet?
Cheers, Paul
April 21, 2010 at 6:32 pm
Happens on PC, too. HD6. Gotta quit and re-launch and good to go again.
April 24, 2010 at 1:32 pm
I’m having the same two errors repeatedly three times yesterday and twice today so far. 9019 and 9031 since moving to 8.0.3 cs2. Never seen this behavior before. I’m on a mac 0S 10.5.8, internal SATAS, all correctly formatted. I went as far as copying my session with audio to a clean new drive. Also moved my sample content (NI Battery, and Stylus RMX) to the same new drive. I’m still getting the errors.
June 2, 2010 at 8:45 pm
I too get the same errors. I’m on a macbook and ext firewire HD all setup according to the PT referene manual, no illegal characters or anything. Any news concerning this issue? it’s really getting on my nerves.
August 1, 2010 at 1:51 am
Same problem here. Most times with big sessions, but sometimes not at all. Very frustrating.
August 5, 2010 at 9:33 am
All of which is keeping me on 8.0.1cs2, which is of little consolation for those who have jumped. Mike.
October 9, 2010 at 1:38 am
9019 and 9031 errors regularly with PT v8.0.1cs2. Major pain in the tail.
And then Digi slaps us in the face with this Native HD stuff before FIXING what they broke. -ug!
October 9, 2010 at 1:40 am
Let me clarify – I DO get the 9019 and 9031 error with PT v8.0.1cs2 – after waiting for the messages to be able to be clicked off, I CAN save my work and close PT, but attempting to play will force the errors again!
November 30, 2010 at 1:57 am
Same happens to me dave B. I can save the work but it wont play. Happened for the
first time today and I’m on a deadline for a project.Running 8.0 on Windows. Been using
for over a year no prob. Please help.
June 11, 2011 at 7:35 am
I get the same message (9010) on PT 8. But the same sessions run perfect on PT 7. I’m running a PC with 2 operating systems. tools 7 on one and tools 8 on the other. Tha data is being accessed from the same hard drive.SATA drives. Seems to be PT 8 issue. any suggestions?
June 11, 2011 at 7:37 am
Error message should read 9019 on my previous comment