good old -6086, yes I did a search....

[Day2Daze]

So I have been taking files home from work to edit them and have been running into the dreaded -6086 "operating system helf off interupts for too long, try increasing h/w buffer size..". I only have the problems at home bc its LE.

My home system is:
Mac Pro Quad 2x2.66, 6gb ram, 1TB hard disk. Glyph 050Q 250 GB firewire drive OS X 10.4.9
Digidesign 003r factory, PT7.4, music production toolkit, clocking from my API A2D.


The 003 is plugged in firewire400 in the back of the computer, and the glygh is on the firewire 800 port in the back. The error happens every few seconds it seems, and doesnt matter if the session is on the firewire drive or the internal audio drive.

The error happens no matter what setting I have the h/w buffer at. What are ideal settings for a computer this powerful? Never messed with this before in HD land.

I heard someone say it might be related to plug-ins? I have mpt, factory bundle, melodyne, soundtoys demos (expired), antares demos ( expired), and the psp stuff.

Any ideas?

[albee1952]

Can you run the Glyph drive on a firewire 400 port. I have read that mixing 400 and 800 can cause problems with protools.

[Day2Daze]

I suppose, I just figured it would be faster on the 800. I can either daisy chain from the 003, or I can use the 400 input on the front. I am trying to bounce something and it keeps stopping with this stupid error that I have been dealing with the past few days. Been trying for the past hour to bounce down a 5 min song! I am about to stand up and pee on this 003!

I will try it now and let you know

[Day2Daze]

I suppose, I just figured it would be faster on the 800. I can either daisy chain from the 003, or I can use the 400 input on the front. I am trying to bounce something and it keeps stopping with this stupid error that I have been dealing with the past few days. Been trying for the past hour to bounce down a 5 min song! I am about to stand up and pee on this 003!

I will try it now and let you know

[Day2Daze]

hmm still having the same problem.

I did a test and was just using the import audio funtion to play some songs, and i got the error still. There was no audio in the session at all, i got the error just from auditioning audio to import. any other thoughts?

[Phil Ogden]

You say you've done a search. What exactly have you tried so far?

1. Anything running in the background (Airport/Bluetooth, Anti Virus)?
2. Firewire Networking off?
3. Different FW port?
4. Replacement (shorter) FW cable?

http://www.myspace.com/philogg

[jhamrick]

Been trying for the past hour to bounce down a 5 min song!

As a suggestion to finish your mix, until you can resolve the error. Don't Bounce to disk! If you have two voices available, bus your mix to a stereo audio track and hit record on the new track. If it fails during the mix, just go to the fail point (no need to start at the beginning), arm the new track and hit record again. Continue with the process until your final mix file is complete. Bounce to disk drives me insane when issues occur. This is how I do my final mixes, as long as I have the voices available. Once complete, select all your takes on the final mix track, consolidate them into one region...

Hope that helps.

[Day2Daze]

yeah that would work, so i dont have to keep restarting the bounce.

I have tried changing the fw port. I dont have airport or bluetooth on, i am connected to the net using standard cat5, doubt that has anything to do with it though. I think i might try reinstalling PT which i really, really do not want to do.

I haven't tried using a different firewire cable, could that really be it???

[Day2Daze]

yeah that would work, so i dont have to keep restarting the bounce.

I have tried changing the fw port. I dont have airport or bluetooth on, i am connected to the net using standard cat5, doubt that has anything to do with it though. I think i might try reinstalling PT which i really, really do not want to do.

I haven't tried using a different firewire cable, could that really be it???

[Dogcode]

Oh Yes...I`ve had issues the were resolved with a new FW 400 cable..

dog