DAE Error (-9073)

[albee1952]

Originally Posted by Kbiastre

Hi,

Did the 10k rpm drive work? I'm plagued with 9073 errors.

Thanks.

I would not hold much hope for this being the solution. Many of us run large sessions on 7200 rpm drives(I'm talking 60-70 audio tracks) and don't get this error. Some things to consider: Post a Sandra report as you may have a hardware issue. Review the system tweaks and make sure you didn't miss any. Choose drives that use a large cache if possible(16 would be my dead minimum, 32 and 64meg being my preference for recording drives). Always run PT as admin and disable desktop composition when running PT(both these settings can be done in PT properties so its automatic).

[bad jitter]

Usually for this error quitting Pro Tools, unplugging and plugging the mBox2 back does the trick for some time. I never see this error on my HD rig.

[inphazeaudio]

Hello,
I did get a Raptor 10K drive.... SAME ISSUE.. my comp is Very much up to the task. GIgabyte MB, 16 gig Ram, Win 7 64, i7 Quad Core, 3.4ghz, all tweaked for audio. NO Internet, antivirus, All stripped down for audio.. runs like a dream with Cubase, Sonar,, NOT with PT.. even as mentioned with 10k drive.. oh yeah the OS is on a SSD. as well as Protools the program resides on the SSD, with audio on the 10k drive.. can't figure..

Example: did some tracking in Cubase... drums, bass, gtr,, now would like to use PT elastic audio, with warp tabs,... export all my (big woop) 18 tracks out of Cubase, all the same length.. to the 10k drive..so i can now import into PT...
create new project in pt, import the audio.. 18 mono tracks.. start some basic edits.. and BOOM DAE error -9073.. you've got to be kidding me..

Back to Cubase.. I have to get some work done.. to bad.. I hope some one at AVID is aware of this issue.. so far the only thing i see on the forum is more and more users getting this error.. Hello Avid.. help please.. hotfix maybe? would appreciate it. thanks.

[powerjoe]

Does this happen when using "Input Only Monitoring"?

I had the same problem, (along with insane stuttering, etc) and this fixed it for me.

Curious to hear if this helps at all...

[dtmprod]

I use 10k drives with my scsi system and never had a single problem with 7 & 8 HD. I would run 100+ tracks off a single drive. Haven't changed a thing when upgrading to PTHD 10. And I defrag on a consistent basis. Fortunately, these (-9073) errors seem pretty random and more a nuisance than a show stopper. But I would like to figure out what's going on. Increasing the cache size doesn't seem to help at all. And did all the usual trash prefs, etc.

[inphazeaudio]

just did a complete uninstall.. and reinstall.. trash prefs... and its seemed to help.. was able to run 18 mono tracks.. do some elastic time warp.. loaded a bunch of Degidesign 1176 comps.. to see if it would hick up.. no problems..
the only thing that i get is a temporary freeze.. for about 5 seconds every few minutes.. i wonder if its a auto save running in the back ground...
as soon as i start to load some UAD-2 plugins.. -9073.. start to re appear.. and i get hang ups.. couple of blue screens of death.. and not being able to save project..

so at this point i can run PT10.. but without plugin from UAD.. great!
i have two Quad UAD2 cards. that i use all of the time.. so much for mixing in PT.. back to Cubase.. starting to sound like a broken record.. i just would really like to FULLY use software that I paid.. much $$ for.. and use some very cool features like Multi Track Drum edits using Warp markers.. Cubase lacks in that department..

come on UAD and AVid.. lets get this stuff to work together.. please!

[Chris Watkins]

Is this not the case sensitivity issue again?

[inphazeaudio]

Originally Posted by Chris Watkins

Is this not the case sensitivity issue again?

what is the Case Sensitivity issue?? don't understand. thanks

[epiphone]

One other thought there is an article on the avid protools site about checking your firwire cable ? Have you substituted another cable ?

Good luck ! These illogical errors and workarounds drive me crazy !

Matt

[HassanDavis]

Hi guys,

I found that 32-bit float sessions error out long before they should. Logic Audio will run a session with 4 to 5 times the track count (on the same machine, no plugins).

So, now, when I import the raw audio from a Logic production session into Pro Tools, I select 24-bit. Pro Tools runs the session fine in this case.

I would love to use the same bit-depth I use in Logic Audio. So, this is a bummer.

I hope this helps!