Always have to re power cycle 003R.....

[Mark Reis]

I have a 003r and 002r that both exhibit this error. Both of these systems are 2x2.66 dual core xeon machines with 2GB Memory.

Tried cables, no other applications running. It seems to me like Digidesign is aware of the problem and has even witnessed it, but not interested in fixing it at this time.

[68topls]

I own an 03R+ and I'm on a quad 2.6GHZ mac pro with 8 gigs of ram. When I first got my 03 it did exactly what people in here are stating. Unable to leave sessions on with no activity, and coming back the next day having to recycle. I couldn't even update the firmware on the 03 because of this issue. I changed to a shorter "high end" cable and removed the hard drive connected to the back of the 03 's fire wire port and that solved all of my issues. Now I did end up purchasing an additional fire wire card but I was running out of ports. I have both large and small sessions that last long periods of time. Think one four or five minute song or an entire church service with 4 or 5 songs, prayer, announcements etc. with an hour sermon. All having different types an channels for mics, piano, etc. Just because your mac is set not to go to sleep doesn't mean it doesn't spin down hardware. Some of the new hardware vendors are building code into their hardware. IE the new "green" hard drives spin them selves down. I work for a very large hardware vendor and have to understand that some times you can chase "problems" that aren't really "problems" and you must prioritize the problems you do see....................

[Dogcode]

Originally Posted by Mark Reis

I have a 003r and 002r that both exhibit this error. Both of these systems are 2x2.66 dual core xeon machines with 2GB Memory.

Tried cables, no other applications running. It seems to me like Digidesign is aware of the problem and has even witnessed it, but not interested in fixing it at this time.

Ya...I think we all know that digi has seen this. I also have the Mac Pro 2 x 2.66 machine which has been certified by digi for quite some time now.

Frustrating isnt it.

Dog

[Tomas Chinchilla]

Originally Posted by 68topls

I own an 03R+ and I'm on a quad 2.6GHZ mac pro with 8 gigs of ram. ...... I changed to a shorter "high end" cable and removed the hard drive connected to the back of the 03 's fire wire port and that solved all of my issues.....................

I have gone thru 4 firewire cables, hell I changed computers and went from an iMac to a MacPro and even switched to internal hard drives (All), and I am still experiencing issues.

The only thing left to do for me is to buy a TI firewire card for the macpro.

[ChuckS]

Saw this thread and I have the same issue with leaving the 003R on overnight, but I also get a crash and the 003R reboots itself. The crash does not happen every time, but the reboot does. When the crash does not happen, I have to force quit PT. Maybe this portion of the crash log will give someone some insight as to what is happening.

Process:         Pro Tools LE [1126]
Path:            /Applications/Digidesign/Pro Tools/Pro Tools LE.app/Contents/MacOS/Pro Tools LE
Identifier:      com.digidesign.ProToolsLE
Version:         8.0.0cs2 (8.0.0f323)
Code Type:       PPC (Native)
Parent Process:  launchd [144]

Interval Since Last Report:          318507 sec
Crashes Since Last Report:           2
Per-App Interval Since Last Report:  10262 sec
Per-App Crashes Since Last Report:   1

Date/Time:       2009-05-29 08:13:06.455 -0400
OS Version:      Mac OS X 10.5.7 (9J61)
Report Version:  6
Anonymous UUID:  19DD5ADD-F9D9-4DCF-8E78-5617E73BE85D

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread:  0

Thread 0 Crashed:
0   ???                           	0000000000 0 + 0
1   com.apple.framework.IOKit     	0x9505eb0c IODispatchCalloutFromCFMessage + 564
2   com.apple.CoreFoundation      	0x902613fc __CFMachPortPerform + 184
3   com.apple.CoreFoundation      	0x902837c4 CFRunLoopRunSpecific + 2484
4   com.apple.HIToolbox           	0x9301e9d8 RunCurrentEventLoopInMode + 268
5   com.apple.HIToolbox           	0x9301e764 ReceiveNextEventCommon + 264
6   com.digidesign.framework.DFW  	0x007f4730 DFW_EventLoop::SleepUntilEvent(std::list<DFW_EventID, std::allocator<DFW_EventID> > const&, double, bool, DFW_EventRef*) + 148
7   ...gidesign.framework.ProTools	0x01cc8a54 0x1bc6000 + 1059412
8   ...gidesign.framework.ProTools	0x021b2930 Cmn_TypedException<L10N_ExceptionData>::Cmn_TypedException(Cmn_TypedExceptionCode<L10N_ExceptionData> const&, L10N_ExceptionData const&, Cmn_StackDump*) + 1101228
9   ...gidesign.framework.ProTools	0x02322418 Cmn_TypedException<MA_OSErrData>::Cmn_TypedException(Cmn_TypedExceptionCode<MA_OSErrData> const&, MA_OSErrData const&, Cmn_StackDump*) + 28920
10  ...gidesign.framework.ProTools	0x02695f44 Cmn_TypedException<MA_OSErrData>::Cmn_TypedException(Cmn_TypedExceptionCode<MA_OSErrData> const&, MA_OSErrData const&, Cmn_StackDump*) + 3648548
11  ...gidesign.framework.ProTools	0x02696238 Cmn_TypedException<MA_OSErrData>::Cmn_TypedException(Cmn_TypedExceptionCode<MA_OSErrData> const&, MA_OSErrData const&, Cmn_StackDump*) + 3649304
12  ...gidesign.framework.ProTools	0x0269889c Cmn_TypedException<MA_OSErrData>::Cmn_TypedException(Cmn_TypedExceptionCode<MA_OSErrData> const&, MA_OSErrData const&, Cmn_StackDump*) + 3659132
13  com.digidesign.framework.DFW  	0x0079076c TCommandHandler::PerformCommand(TCommand*) + 148
14  com.digidesign.framework.DFW  	0x00784744 TApplication::ProcessEvent(TEvent*) + 52
15  com.digidesign.framework.DFW  	0x00784588 TApplication::WakeUp() + 104
16  com.digidesign.framework.DFW  	0x00807314 TApplication::GetApplicationVersionString() + 2520
17  com.apple.HIToolbox           	0x92ff5b0c DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1488
18  com.apple.HIToolbox           	0x92ff4ca4 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 468
19  com.apple.HIToolbox           	0x92ff4ac0 SendEventToEventTargetWithOptions + 56
20  com.apple.HIToolbox           	0x93024a4c ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 312
21  com.apple.HIToolbox           	0x92ff5f60 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2596
22  com.apple.HIToolbox           	0x92ff4ca4 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 468
23  com.apple.HIToolbox           	0x93011bc8 SendEventToEventTarget + 56
24  com.apple.HIToolbox           	0x9308036c ToolboxEventDispatcher + 88
25  com.apple.HIToolbox           	0x9307c8a8 RunApplicationEventLoop + 168
26  com.digidesign.framework.DFW  	0x007f3e10 DFW_EventLoop::RunApplicationEventLoop() + 16
27  com.digidesign.framework.DFW  	0x007848c8 TApplication::Run() + 64
28  ...gidesign.framework.ProTools	0x027d45dc LaunchProTools + 1756
29  com.digidesign.ProToolsLE     	0x00009c34 0x1000 + 35892
30  com.digidesign.ProToolsLE     	0x000035f4 0x1000 + 9716
31  com.digidesign.ProToolsLE     	0x000032f8 0x1000 + 8952
32  ???                           	0000000000 0 + 0

I have the rest if anyone is interested.

[The Dougfather]

Just too add, i've experienced short term disconnects as result of IK Multimedia plugins. I've found the issue to be far more prominent on a powermac than on the Macbook pro. As discussed, resolved by dropping down by 1 processor core.

It would nice of Digi could give IK a real kick up the ass with regards to their non real time code. I've spent a s**t load of cash on IK plugins for Pro Tools and they really but a downer on the Pro Tools experience.

I've never suffered long term disconnects, then again i see no reason to leave my 002R switched on when i'm not using it.

[USBnoGood]

Originally Posted by DigiTechSupt

I'm not sure what to tell you - I'm guessing it may be something specific to your computer.

how important is this to you? how much time is worth it to solve a problem that is already easily taken care of by flipping a switch off and back on again?

I *hope* this was a joke....

[chrisdee]

I'll have to chime in also experiencing this problem. However I don't have a 003, but a Mbox2 Pro. It can dissconect only a few minutes after boot, even without entering Pro Tools 8.0.1 at all. By the way this happened to 8.0csx also.

The workaround for me is to dissconnect the firewire cable form my Mbox 2 Pro and stick it in again.

The problem is not critical, but nevertheless annoying because it happens almost every time i boot. I boot the computer every day I come from work, and turn it off for the night.
Now whether this is the os fault or Mbox, I have no idea, so I'm not going to point any fingers.

But Digidesign, if the engine in your car stopped every time it was running idle, would you try to do something about it, or just let it be ?

[BRH]

Originally Posted by USBnoGood

I *hope* this was a joke....

I think that was really good advice. Macs used to need a restart every 4 hours or so (OS 7...8..9) while working on intensive editing programs. (take a break, save and restart) Just liked everything brought out fresh again. Still use this method....and I don't let mine run when not in use, although I did at a facility.

[captainhook]

For me, it's just not a matter of turning it off and on, I wish it was as simple as that.....

I have tried every firewire cable, shorter firwire cables, PCIe firewire cards and everything else I can think of.

However, like another user on this thread, I need to make sure every morning that I unplug the firewire cable from the 003R and put it in the other slot (It doesn't work if I put it in the same slot) and then fire up pro tools.

The real annoying part is if I forget, I have to wait for protools to get up to the "peripherals" load, let it hang there for a couple of minutes, then shut down protools. RESTART my Mac and then fire everything back up again. Meanwhile my client thinks - oh oh - are we going to crash all day like this - I am already 10 minutes into my session!

The thing is, I also have a Fireface 800 runnning Logic and Cubase. They open flawlessly time and time again. What happens after I open up Logic and Cubase is a whole other story

So, for me, it's not a minor inconvenience, it's probably a good half hour a week if I forget to move the firewire cable over in the AM. (Which means climbing beneath my console.