Pro Tools 6085 Error
Contents |
DAE error -6085 brings Pro Tools 9 to a halt...please help Avid. User Name Remember Me? Password Register FAQ Today's Posts Search Search Forums Show Threads Show pro tools hardware buffer size Posts Tag Search Advanced Search Go to Page... Page 1 of 2 1 2 aae 6101 pro tools 12 > Thread Tools Search this Thread Display Modes #1 05-16-2011, 01:36 PM lancemcv Member Join Date: Apr
Pro Tools 10 Playback Engine Settings
2010 Location: Rockland County, NY Posts: 429 DAE error -6085 brings Pro Tools 9 to a halt...please help Avid. I have done everything to get rid of this problem but nothing works, the only thing
Pro Tools Error 6101
that does work is to not use my MBox Pro 3. If I only use my mac pro as the playback hardware with PT 9.0.2 I don't get the error, if I do get one Pro Tools will continue to work. If I get the -6085 error with the M Box Pro connected to my mac pro the session then refuses to play back audio until I reset the hardware pro tools cache size or reboot the computer and relaunch pro tools, it does not however lock up the computer or pro tools just playback doesn't work. I have been through the mill with this. Any thoughts are welcome. It seems to be FireWire related. I only have the MBox connected to the rear port on my Mac Pro nothing else is connected. I have removed all non standard plugins as a test all plugins are up to date Still happens. Set up a separate user account just for PT still happens. Deleted digi data bases and prefs etc still happens. Have all the recommended settings the way they should be on my mac still happens. I am going to install a clean system on another drive and install PT 9 and then boot off it and see if it still happens then. I have never had issues like this with pro tools on my system ever. My old 002 was rock solid with PT 8.0.3 lancemcv View Public Profile Find all posts by lancemcv #2 05-16-2011, 07:04 PM Park Seward Member Join Date: Jul 2001 Location: Grants Pass, OR Posts: 4,283 Re: DAE error -6085 brings Pro Tools 9 to a halt...please help Avid. Need more info. R
Production Media Management Video Editing Video Post Production Music Creation Audio Post Production Live Sound Music Notation by
Pro Tools Error 6101 Fix
Industry Broadcast Pro Video Pro Audio Education Sports Government Corporate can't change buffer size pro tools Services Avid Global Services Overview Services Professional Services Certifications Training Avid Learning Partners Products Product Overview pro tools 12 buffer size Avid MediaCentral Platform Quick Links Media Composer Pro Tools Pro Tools | S6 System 5 Artist Series Audio Plug-ins Sibelius Interplay ISIS iNEWS AirSpeed See http://duc.avid.com/showthread.php?t=301104 All Products Special Offers Artist Suite Video (NLE) Audio (DAW) Notation & Scoring Pro Mixing Live Sound Media Suite Newsroom Management Asset Management Media Suite Modules Storage Suite Ingest/Playout Storage Automation Support Avid Global Services Overview Quick Links Audio Drivers Pro Tools Updates How To Videos Avid Product Warranty End Of Support http://avid.force.com/pkb/articles/en_US/Troubleshooting/en372471 Dates Support Plans Pay-Per-Incident Annual Support Plans Customer Care Sign Into Your Account Activate Your Product Register Your Product Download And Upgrade Search Knowledge Base Contact Avid Support Connect With Communities About About Us Press Room Management Connectivity Partner Program Channel Partners Co-Marketing Programs Contact Us Customer Association Careers Locations Investor Relations Terms & Legal < Back to search Results English Avid Knowledge Base DAE error 6101, 6085, 6081, 6096, or 1115 when using a FireWire interface with Pro Tools. AAE -6085 AAE -6101 AAE -6096 AAE -1115 Last Updated : May 31, 2013 Products Affected : M_Audio_FireWire_Interface, Pro_Tools_HD, Pro_Tools_LE, Pro_Tools_M_Powered DAE error -6101, -6085, -6081, -6096, or -1115 when using a FireWire interface with Pro Tools. PLEASE NOTE THAT YOU SHOULD ALWAYS TURN OFF YOUR FIREWIRE INTERFACE AND COMPUTER BEFORE CONNECTING OR DISCONNECTING THE FIREWIRE CABLE! FAILURE TO DO SO MAY DAMAGE YOUR EQUIPMENT! This may be caused by a poor firewire connection or high tr
Production Media Management Video Editing Video Post Production Music Creation Audio Post Production Live Sound Music Notation by Industry Broadcast Pro http://avid.force.com/pkb/articles/en_US/Error_Message/en328377 Video Pro Audio Education Sports Government Corporate Services Avid Global Services Overview Services Professional Services Certifications Training Avid Learning Partners Products Product Overview Avid MediaCentral Platform Quick Links http://blog.mattwoodward.com/2012/04/pro-tools-le-805-and-buffer-underrun.html Media Composer Pro Tools Pro Tools | S6 System 5 Artist Series Audio Plug-ins Sibelius Interplay ISIS iNEWS AirSpeed See All Products Special Offers Artist Suite Video pro tools (NLE) Audio (DAW) Notation & Scoring Pro Mixing Live Sound Media Suite Newsroom Management Asset Management Media Suite Modules Storage Suite Ingest/Playout Storage Automation Support Avid Global Services Overview Quick Links Audio Drivers Pro Tools Updates How To Videos Avid Product Warranty End Of Support Dates Support Plans Pay-Per-Incident Annual Support Plans Customer Care Sign Into pro tools 12 Your Account Activate Your Product Register Your Product Download And Upgrade Search Knowledge Base Contact Avid Support Connect With Communities About About Us Press Room Management Connectivity Partner Program Channel Partners Co-Marketing Programs Contact Us Customer Association Careers Locations Investor Relations Terms & Legal < Back to search Results English Avid Knowledge Base DAE Errors 6086, 6093 and 6085 during playback or recording in Pro Tools and Digi 002 or Digi 002R. DAE 6086 DAE 6093 DAE 6085 Last Updated : January 21, 2013 Products Affected : DAE Errors 6086, 6093 and 6085 during playback or recording in Pro Tools and Digi 002 or Digi 002R. This can be caused by installing Pro Tools to a drive other than your main system drive. This can cause a firmware update to not be initiated. To correct this, uninstall Pro Tools from the secondary drive and reinstall it to your main system drive. After reinstalling, launch Pro Tools - you should get a message to upda
Tools 8.0.5 on Windows 7 Home Premium 64-bit and was constantly getting the dreaded "H/W Buffer Underrun" error (-6085). I only ever record a voiceover track in Pro Tools (occasionally with a music bed in another track), but even with a small session such as that it would happen consistently, sometimes after only a few seconds, but at best I'd get 5 minutes of recording time before it would throw the error. It would also throw the error when bouncing a mix to MP3, and the length of the bounce didn't seem to matter much. To try and fix this I tried (almost) everything listed in Avid's Windows 7 Optimization Guide to no avail, and also scoured the far reaches of the interwebs looking for a solution with no luck, so I finally ponied up the $39 for a support ticket and gave them a call. (As an aside, Avid's support is top-notch. I was on hold for a while but once it was my turn I got exceptionally good assistance.) For reference the machine I'm using is a Lenovo G770, which has an Intel Core i5 (2.4 GHz), 8GB of RAM, and a 5400 RPM (yes, slow) drive. I also have a 1TB USB 3.0 USB-powered Western Digital hard drive attached to this machine, but regardless of if I recorded to the main drive (the one with Windows and Pro Tools on it) or the external drive the error would occur. At first I was a bit worried about the hard drive speed but Avid said it should be OK, but they did recommend that even if you use a USB drive it's better to record to an external drive. The other tidbit the support tech shared is that solid-state drives aren't yet recommended for Pro Tools recording. After the support tech ran me through most of the things I'd already tried, had me delete some preferences files, and then gave me some other settings to try, I was initially able to get a 10 minute stretch recorded without any problems so I optimistically tried to record some stuff for real, but after only about two and a half minutes the error occurred again. As what I thought was a last ditch effort I tried the one thing I hadn't yet tried since it seemed like a stretch: I disabled both my wired and wireless network cards. That, in combination with reducing the number of CPUs from 4 to 2 and setting the utilization to 90%, seemed to do the trick. Ultimately it may have only been the networking cards that were causing