Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Legacy Products > 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac)

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
  #1  
Old 09-11-2005, 11:20 AM
Jon B Gamble Jon B Gamble is offline
Member
 
Join Date: Sep 2005
Posts: 4
Default Standalone CoreAudio Driver (Tiger) can\'t see 002R

I updated to Tiger and installed the Standalone CoreAudio Driver 6.9.2cs2. As a result my 002R (free from power harness problems) cannot be seen by Digi's CoreAudio Manager application, can't be selected as an I/O device, and can't be used. I've tried all the permutations of preference deleting, permission repairing, and reinstalling. I've seen and appreciated the sticky "Troubleshooting" FAQ but unfortunately it didn't help.

I have seen DUC posts from 2 other LE users so far (both with MBox) claiming the same symptoms after updating to tiger and 6.9cs2. Here's what I get from CoreAudio Manager:

Digidesign HW: Unsupported Device
Status: Not Connected (HW in use)
Channels: N/A
Attached Clients: 0
Buffer Size: 512 (disabled)
All UI is disabled except Prefs, Connect, and Quit. Clicking Connect results in nothing happening. There is no error reported but the UI stays in the same disconnected state.

Keep in mind this reflects the behavior after I deleted /Library/Preferences/.GlobalPreferences.plist.. The digi CoreAudio Manager was formerly reporting accurate details about my 002 rack under Tiger (such as that it was a 002 rack). I hoped this was evidence that the app was at least "seeing" the hardware but then I realized It was just picking up stale data from /Library/Preferences/.GlobalPreferences.plist left over from last friday, when I was still blissfully running 10.3.8 and the 002 still slept in the bedroom. Now it sleeps on the couch.

I've tried 2 different firewire cables, both known to work with other devices. Apple System Profiler can see the 002 on the firewire port and query basic info about it. Digidesign CoreAudio Manager cannot.

I have seen examples of other people being very satisfied with this new driver so it's hard to imagine there isn't a workaround here. I'm hoping the issue is related to the fact that it's been quite awhile since I've run an actual pro tools installer (i bought the 002r to run Logic on years ago, i'm too lazy to continually order new pro tools cds as a proactive keep-my-002-firmware-up-to-date measure, hey how about putting a complete pro tools 6.9 le installer up for download)

Is there a combination of buttons on the front panel that I can hold to reset my 002R's firmware? Does anyone have ideas on what could be wrong with my configuration?

Thanks in advance.
Jon Gamble
Reply With Quote
 

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
CoreAudio Manager/Standalone Driver for Tiger, Kernel Panic when launched Dustin Coffey 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 5 06-29-2012 06:04 PM
Standalone CoreAudio Driver for Tiger Avid 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 78 01-11-2007 10:26 AM
Standalone CoreAudio Driver for Tiger has issues Garissimo 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 5 03-17-2006 10:36 PM
Standalone CoreAudio Driver for Tiger Avid Pro Tools TDM Systems (Mac) 0 09-02-2005 07:21 PM
Standalone CoreAudio Driver for Tiger Avid General 0 09-02-2005 07:12 PM


All times are GMT -7. The time now is 01:06 PM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com