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)

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 11-13-2012, 06:23 AM
darkgoob darkgoob is offline
Member
 
Join Date: Aug 2007
Posts: 48
Default Problem with Digi 002 Rack + Mountain Lion (Core Audio)

I saw this thread from a few days ago and was encouraged because I have been under the impression that 002 Rack is incompatible with OS X 10.8.x Mountain Lion.

On that thread it says if you download the latest drivers for the 002 Rack, then it will work with system audio as well as audio applications such as Adobe.

So I downloaded the drivers from this page using this direct link.

I have so far been able to successfully get MOTU Digital Performer to recognize my 002 rack; inputs and outputs are working.

HOWEVER, OS X will not allow me to play system audio or alert beeps through the 002. In the Audio MIDI Setup app, you can see the 002, and even select "Configure Speakers..." and see the whole list of outputs. However if you right click it in the list, and select "Use this device for sound output," then nothing happens. And yes, I am running the Digidesign CoreAudio Manager in the background, and yes, it does say, "Status: Connected @ 44.1k."

I can even change the sample rate successfully within the Audio MIDI Setup app. I just can't use it for sound output!

What gives?

My machine is a Mac Pro 5,1 (Mid-2009), with dual quad-core Xeon 2.26 ghz, 12gb RAM, 14TB hdd, OS X 10.8.2, NVIDIA 570 GTX. Thanks.

-=DG=-
Reply With Quote
  #2  
Old 11-13-2012, 07:20 AM
nst7 nst7 is offline
Member
 
Join Date: Oct 2008
Location: Cincinnati OH
Posts: 9,775
Default Re: Problem with Digi 002 Rack + Mountain Lion (Core Audio)

Besides setting it up in Audio Midi, you need to also go under "System Preferences", select "Sound" (the little speaker icon), then select your output tab and then your device (same with the input tab, etc.).
Reply With Quote
  #3  
Old 11-13-2012, 01:09 PM
darkgoob darkgoob is offline
Member
 
Join Date: Aug 2007
Posts: 48
Default Re: Problem with Digi 002 Rack + Mountain Lion (Core Audio)

Quote:
Originally Posted by nst7 View Post
Besides setting it up in Audio Midi, you need to also go under "System Preferences", select "Sound" (the little speaker icon), then select your output tab and then your device (same with the input tab, etc.).
Did that too. Didn't work.
Reply With Quote
  #4  
Old 11-17-2012, 10:00 AM
darkgoob darkgoob is offline
Member
 
Join Date: Aug 2007
Posts: 48
Default Fixed

Deleting M-Audio and Elevenrack drivers, and all related stuff from PreferencePanes folder in Library, then restarting, fixed it. I think it doesn't fully remove old versions of the driver upon installation.
Reply With Quote
  #5  
Old 12-24-2012, 10:51 PM
darkgoob darkgoob is offline
Member
 
Join Date: Aug 2007
Posts: 48
Default Re: Problem with Digi 002 Rack + Mountain Lion (Core Audio)

OK, now it's not working again. Same problem as before: power on the Digi 002 Rack. Launch Digi CoreAudio Manager. It sees the 002 rack just fine. Connects just fine. Open the Sound control panel. Select the Digi 002 Rack under Outputs. Close the Sound control panel. Now it doesn't work. So I open the Sound control panel again, and select Digi 002 Rack again. Still doesn't work.

However if I open up Reason I'm able to use it just fine. So I think the problem appears to be with the OS, not necessarily with the drivers. However I'd like a resolution to this...

-=DG=-
Reply With Quote
  #6  
Old 12-24-2012, 11:19 PM
darkgoob darkgoob is offline
Member
 
Join Date: Aug 2007
Posts: 48
Default Re: Problem with Digi 002 Rack + Mountain Lion (Core Audio)

Fixed it, here's how: I quit the Digi CoreAudio Manager, the System Preferences app, and the Audio MIDI Setup app. Then I force-quit coreaudiod in the Activity Monitor. Subsequently I re-opened Digi CoreAudio Manager and then I was able to select the 002 Rack as the Output and Input device. Now I can use it with iTunes, etc.

However I still was not able to select it for system alert playback! Weird.

I do think it has something to do with the freakin' sandboxing of OS X. This error appeared in the Console when it didn't work:


12/24/12 11:08:57.093 PM sandboxd[13899]: ([13898]) coreaudiod(13898) deny mach-lookup DigiCoreAudioServer

This was the associated "Full Report":


coreaudiod(13898) deny mach-lookup DigiCoreAudioServer

Process: coreaudiod [13898]
Path: /usr/sbin/coreaudiod
Load Address: 0x10f4c3000
Identifier: coreaudiod
Version: ??? (???)
Code Type: x86_64 (Native)
Parent Process: launchd [1]

Date/Time: 2012-12-24 23:08:57.006 -0800
OS Version: Mac OS X 10.8.2 (12C60)
Report Version: 8

Thread 0:
0 libsystem_kernel.dylib 0x00007fff957ad686 mach_msg_trap + 10
1 liblaunch.dylib 0x00007fff96c377c4
2 liblaunch.dylib 0x00007fff96c364d9 bootstrap_look_up3 + 69
3 liblaunch.dylib 0x00007fff96c36609 bootstrap_look_up2 + 40
4 CoreFoundation 0x00007fff9526b01c __CFMessagePortCreateRemote + 764
5 Digidesign CoreAudio 0x000000010fbf24eb NewDigiCoreAudioPlugIn + 7539
6 Digidesign CoreAudio 0x000000010fbf49e5 NewDigiCoreAudioPlugIn + 17005
7 Digidesign CoreAudio 0x000000010fbf0902 NewDigiCoreAudioPlugIn + 394
8 Digidesign CoreAudio 0x000000010fc02ff1 NewDigiCoreAudioPlugIn + 75897
9 CoreAudio 0x00007fff95a29765 HALPlugInManagement::CreateHALPlugIn(HALCFPlugIn const*) + 1063
10 CoreAudio 0x00007fff95a2889a HALPlugInManagement::Initialize() + 428
11 CoreAudio 0x00007fff95a286e1 HALSystem::InitializeDevices() + 9
12 CoreAudio 0x00007fff95a256ae HALSystem::CheckOutInstance() + 146
13 CoreAudio 0x00007fff95a5ca59 AudioHardwareBeMaster + 88
14 coreaudiod 0x000000010f5230c9
15 libdyld.dylib 0x00007fff9501e7e1 start + 0

Thread 1:
0 libsystem_kernel.dylib 0x00007fff957afd16 kevent + 10
1 libdispatch.dylib 0x00007fff965579ee _dispatch_mgr_thread + 54

Thread 2:
0 libsystem_kernel.dylib 0x00007fff957af6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8dac5cb3 _pthread_wqthread + 412
2 libsystem_c.dylib 0x00007fff8dab0171 start_wqthread + 13

Thread 3:
0 libsystem_kernel.dylib 0x00007fff957af6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8dac5cb3 _pthread_wqthread + 412
2 libsystem_c.dylib 0x00007fff8dab0171 start_wqthread + 13

Thread 4:
0 libsystem_kernel.dylib 0x00007fff957af6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8dac5cb3 _pthread_wqthread + 412
2 libsystem_c.dylib 0x00007fff8dab0171 start_wqthread + 13

Thread 5:
0 libsystem_kernel.dylib 0x00007fff957af6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8dac5cb3 _pthread_wqthread + 412
2 libsystem_c.dylib 0x00007fff8dab0171 start_wqthread + 13

Thread 6:
0 libsystem_kernel.dylib 0x00007fff957af0fa __psynch_cvwait + 10
1 CoreAudio 0x00007fff95a54cb5 HALB_Guard::Wait() + 75
2 CoreAudio 0x00007fff95a4635c HALC_ShellInfo::WaitForCurrentProcessInitialized() + 50
3 CoreAudio 0x00007fff95a4629b HALC_Object_PropertyListener + 28
4 CoreAudio 0x00007fff95a46253 _XObject_PropertyListener + 272
5 CoreAudio 0x00007fff95a4613c HALB_MIGClient_server + 106
6 libdispatch.dylib 0x00007fff965593fe dispatch_mig_server + 129
7 libdispatch.dylib 0x00007fff965550b6 _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fff9655729b _dispatch_source_invoke + 691
9 libdispatch.dylib 0x00007fff96556305 _dispatch_queue_invoke + 72
10 libdispatch.dylib 0x00007fff96556448 _dispatch_queue_drain + 180
11 libdispatch.dylib 0x00007fff965562f1 _dispatch_queue_invoke + 52
12 libdispatch.dylib 0x00007fff965561c3 _dispatch_worker_thread2 + 249
13 libsystem_c.dylib 0x00007fff8dac5cab _pthread_wqthread + 404
14 libsystem_c.dylib 0x00007fff8dab0171 start_wqthread + 13

Thread 7:
0 libsystem_kernel.dylib 0x00007fff957af6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8dac5cb3 _pthread_wqthread + 412
2 libsystem_c.dylib 0x00007fff8dab0171 start_wqthread + 13

Binary Images:
0x10f4c3000 - 0x10f592ff7 coreaudiod (253.17) <30CC89D4-54A4-3A58-8776-C258CC17E448> /usr/sbin/coreaudiod
0x10fbef000 - 0x10fc1afef com.digidesign.digidesign.DigiCoreAudioPlugIn (9.0 - 9.0f121) <E854AA6F-80C9-0B56-727E-443A7488AE16> /Library/Audio/Plug-Ins/HAL/Digidesign CoreAudio.plugin/Contents/MacOS/Digidesign CoreAudio
0x7fff8daaf000 - 0x7fff8db7bfe7 libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
0x7fff9501c000 - 0x7fff9501fff7 libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
0x7fff951a8000 - 0x7fff95391fff com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff9579d000 - 0x7fff957b8ff7 libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
0x7fff95a24000 - 0x7fff95a81fff com.apple.audio.CoreAudio (4.1.0 - 4.1.0) <B3198BD6-EA1D-3E5E-ADD4-37D8E6B72678> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x7fff96553000 - 0x7fff96568ff7 libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
0x7fff96c34000 - 0x7fff96c3cfff liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
Reply With Quote
  #7  
Old 09-09-2013, 03:12 PM
darkgoob darkgoob is offline
Member
 
Join Date: Aug 2007
Posts: 48
Default Re: Problem with Digi 002 Rack + Mountain Lion (Core Audio)

So this is a tricky one. I have gotten it to work but only using a third-party USB MIDI driver. I had to delete the avid ones. CoreAudio does not work either, but Pro Tools will run and work fine.

Now if I install the new v.11 drivers then CoreAudio starts working but then Pro Tools won't start, saying the device is in use. I'm doing some experimenting with removing the newer bundles from launchd using launchctl to see if that will free up the hardware. I got this to work a few times (had to power cycle the 002 rack too) but then I was getting buffer to small errors, seems throughput it horrific this way. My guess is that the other driver is still trying to use it.

However there does not seem to be a way to kextunload the newer driver... since it had dependent classes that remain in use. So this still is not really a resolved issue.

I'm very frustrated that in September 2013, when 10.9 is about to come out, we 002 owners do not have any way to run Pro Tools 8.0.5 and have full Core Audio support and MIDI support for the 002 Rack. I'm pretty upset about this. Then you want to charge us $400! to upgrade to the latest version 11, which by the way, does not even support the 002 Rack.
Reply With Quote
  #8  
Old 09-16-2013, 01:41 PM
darkgoob darkgoob is offline
Member
 
Join Date: Aug 2007
Posts: 48
Default Re: Problem with Digi 002 Rack + Mountain Lion (Core Audio)

Ok I got it to work. Steps:

1) Run latest Avid firewire driver installer for 002/003, 11.x.

2) Run PT 8.0.5 installer.

3) Remove the Digidesign MIDI drivers from /Library/Audio/MIDI Drivers, they are not 64-bit and don't work with OS X 10.8.

4) Now to run PT 8, you'll have have to remove com.avid.* item from launchd using the launchctl terminal command. Once in the launchctrl prompt you type "remove" followed by the bundle name you want to remove. To find the bundle name, type "list" and look for one that starts with "com.Avid." .. I don't remember what the whole name is. Do not run using sudo.

5) Now power cycle the 002 rack.

6) Launch PT 8. You can use the 002 just fine, except no MIDI port.



To use the 002 with other CoreAudio apps just restart the computer if you have closed the Avid bundle from launchd as in Step 4. Use the Avid device, not the Digidesign one, in Audio MIDI Setup or your DAW's prefs (like in Logic or DP). Alternately, you can go into launchctl and "load" the Avid driver config file from /Library/LaunchAgents. Restarting is easier. You probably want to power cycle the 002 rack at this point too.
Reply With Quote
  #9  
Old 02-11-2014, 06:25 AM
vanishers vanishers is offline
Member
 
Join Date: Jan 2014
Location: canada toronto
Posts: 4
Default Re: Problem with Digi 002 Rack + Mountain Lion (Core Audio)

very cool. thanks for posting this, Im having similar problem. could you explain step #4 with a little more detail?
Reply With Quote
  #10  
Old 03-16-2014, 01:19 PM
darkgoob darkgoob is offline
Member
 
Join Date: Aug 2007
Posts: 48
Default Re: Problem with Digi 002 Rack + Mountain Lion (Core Audio)

Quote:
Originally Posted by vanishers View Post
very cool. thanks for posting this, Im having similar problem. could you explain step #4 with a little more detail?
Yes I can.

Open Terminal app.

You will see a command prompt. It looks like this:

YourComputerName:HardDriveName YourUserName$ _
(_ is the cursor, yours may be a blinking I or a rectangular block, mine is set to an underscore symbol)

At this prompt you will type:

launchctl

Now you will see a command prompt that looks like this:

launchd% []
(the [] is actually a hollow rectangle)

Launchd is the "launch daemon" -- it's the part of Mac OS X is a unified, open-source service-management framework, starts, stops and manages daemons, applications, processes, and scripts -- including the drivers for the 002 rack. What we are going to be doing is telling launchd to forget about the drivers that we installed in step 1, so that they will unload. We need them to unload because they will conflict with PT8's own drivers for the 002 that load when you run PT8.

So at the launchd% prompt you will type:

remove com.avid.00family.helper

Then you power-cycle the 002 rack so that it returns to a fresh state. If you don't power cycle it, then it will continue to think that it's connected and it won't let PT8 make a new connection to it.

Then run PT8 and it can now make a fresh connection to the 002 rack. If you don't remove the com.avid.00family.helper, then the com.avid.00family.helper will make the connection to the 002 rack, preventing PT8 from doing so!

Hope this helps. Limping along with old hardware… damned if I'll buy a new one… if it ain't broke, don't fix it! But if it is broke, fix it!

-=DG=-
Reply With Quote
Reply

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
Digi 002 Rack, Mountain Lion and Cubase 7.5 Problem mickey976 FireWire and USB Audio Interfaces (Mac) 4 02-11-2014 06:27 AM
Problem! Mac OSX Mountain Lion 10.8.3, 002 rack, Pro Tools 10.3.4 krwin 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 10 04-22-2013 02:43 AM
Problems with midi core audio Manager // Mountain Lion jmlm macOS 1 11-15-2012 05:27 AM
Eleven Rack 1.1.1 Drivers & Mountain Lion MrBig1964 Eleven Rack 0 11-03-2012 08:48 AM
Mountain Lion~10.2 PT update or core driver updates only this week. onepercentfree macOS 0 08-19-2012 08:15 PM


All times are GMT -7. The time now is 04:42 PM.


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