+ Reply to Thread
Page 1 of 2
1 2 LastLast
Results 1 to 10 of 15

Thread: Firewire 410 and 10.6 Snow Leopard

  1. #1

    Default Firewire 410 and 10.6 Snow Leopard

    Ok, after being pissed off that I cant use my audio interface, and the fact that I did a 10.6 clean install the day it released, i kicked my brain into over drive.

    I did manage to get it to work!

    Here is what I did:

    *** DO THIS AT YOUR OWN RISK! *** you break it, thats your fault, if your not comfortable doing this, wait until M-Audio releases a new driver.

    Downloaded and installed FireWire_OSX_1.8.4-3.dmg. I ignored the error and let it finish the installation.

    I then took the M-Audio FireWire.mpkg, right clicked and then clicked show package contents

    Drill down to contents, resources, packages and find the file called:M-Audio FireWire Kernel Extension.pkg, right click on that and select show package contents

    double click the item called archive.pax.gz. It should extract a file called M-AudioFireWireBeBoB.kext. It put it in my downloads directory, that is where I downloaded the FireWire_OSX_1.8.4-3.dmg too.

    Then, google "kext helper" and download it. The version I used was b7.

    Run Kext Helper b7, drag the M-AudioFireWireBeBoB.kext from where ever it was saved, into kext helper. I clicked the advanced checkbox, not sure if you need to do it or not. enter your password, and then click the run button at the bottom center.

    After that I went to Applications -> Utilities -> Disk Utility. Select your boot volume on the left hand side, and under first aid, click the repair disk permissions. Let that complete.

    I rebooted, and BAM! Audio interface is there, usable, and works like a charm.

    Let me know if you need any help!

    Thanks!

    Brian

  2. #2
    Join Date
    Jun 2008
    Location
    Seattle, WA
    Posts
    733

    Default

    This is almost identical to the workaround I was doing for the Profire 610/2626. The only differences is I didn't take the kext from the package, but rather from the system/library/extensions folder (it places it there even though the install fails)

    However, I have not been successful yet.
    ---------------
    Primary Recording Setup: Pro Tools HD1 / Lynx Aurora 16
    Primary Computer: 2008 Mac Pro 3.2Ghz/8x/16GB/8800GT
    Other Equipment: Several other Apple computers, and several custom built PCs, a large variety of pro audio equipment, and instruments.
    Experience with the following M-Audio products: Profire series/Projectmix IO/Firewire Family series(410, 1814, etc)/Axiom series/Axiom Pro series/Oxygen series/Fast Track series/+more

  3. #3
    Join Date
    Jun 2008
    Location
    Seattle, WA
    Posts
    733

    Default

    It shows the kext as registered, and its seeing the profire 610, but the control panel will not open. :-/

    ProFire 610:

    Manufacturer: M-Audio
    Model: 0x11
    GUID: 0xD6C0404400002
    Maximum Speed: Up to 400 Mb/sec
    Connection Speed: Up to 400 Mb/sec
    Sub-units:
    ProFire 610 Unit:
    Unit Software Version: 0x100D1
    Unit Spec ID: 0xD6C


    M-AudioFireWireDICE:

    Version: 2.1.2
    Last Modified: 12/16/08 10:34 AM
    Kind: Universal
    Architectures: i386, ppc
    64-Bit (Intel): No
    Location: /System/Library/Extensions/M-AudioFireWireDICE.kext
    Kext Version: 2.1.2
    Load Address: 0x8babd000
    Valid: Yes
    Authentic: Yes
    Dependencies: Satisfied
    ---------------
    Primary Recording Setup: Pro Tools HD1 / Lynx Aurora 16
    Primary Computer: 2008 Mac Pro 3.2Ghz/8x/16GB/8800GT
    Other Equipment: Several other Apple computers, and several custom built PCs, a large variety of pro audio equipment, and instruments.
    Experience with the following M-Audio products: Profire series/Projectmix IO/Firewire Family series(410, 1814, etc)/Axiom series/Axiom Pro series/Oxygen series/Fast Track series/+more

  4. #4
    Join Date
    Sep 2009
    Posts
    3

    Default

    Hmm. I also installed Snow Leopard and then installed the latest m-audio drivers and they work fine for the firewire 410... didn't really even need to do any sort of run around. The interface came up fine. Just make sure to uninstall the driver and then reinstall, restart the machine with the interface plugged in and voila. Lights on and functioning. I'm getting some funky results though when trying to output to certain monitors, but this may be my inability to understand some of this techy i/o stuff.

  5. #5

    Default

    Have you tried pulling the package for the pref panes out of the install and running it by hand? Im pretty sure there is a way to manualy install he preference panes too, just need to be in a specific place.

    Mine is working perfectly! I tried it in Logic and FCP w/o a problem. I have a pair of Alesis Montior Ones via an Alesis power amp connected to output 1/2. I have full volume control from the front of the 410, and from the control pannel.

  6. #6

    Default

    wow. thank you. this little trick seems to have worked for me and my 1814. I can't seem to open the 1814 control panel, but I can now get sound out of it from my itunes, and the OS can find it in the Audio Midi Setup! Delish. Installing my copy of Logic right now, hopefully I get the sound in as well. Either way, at least I can mix while I wait for these clueless cats to get a real driver out. I think I hear an Apogee calling....

    Cheers, and thanks again!

  7. #7
    Join Date
    Sep 2009
    Posts
    1

    Default

    I just registered on this forum to say: this posting should be a sticky!

    This got my Projectmix i/o back in action with OS 10.6.1.

    The only difference is that I used the "EASY INSTALL" button in the Kext Helper application. Trying it first with the "run" button did not work for me.

    Thanks again for a most useful post.

  8. #8

    Default

    This worked for my old Firewire Audiophile too. Thanks very much! I don't know how on earth you managed to figure it out, but you have saved me a lot of grief.

  9. #9
    Join Date
    Sep 2009
    Location
    brooklyn
    Posts
    3

    Default

    This worked for me, but only after I uninstalled the driver after following the directions above and then reinstalling the driver. When I reinstalled the driver, I didn't get the error anymore either! Thanks for the post...that is quite some work around!
    Model Name: Mac Pro
    Model Identifier: MacPro1,1
    Processor Name: Dual-Core Intel Xeon
    Processor Speed: 2.66 GHz
    Number Of Processors: 2
    Memory: 3 GB

    Software:
    Logic 9

  10. #10

    Default

    I too managed to get it to work by following the first set of instructions, uninstalling, and then re-installing. Praise God!

+ Reply to Thread
Page 1 of 2
1 2 LastLast

Similar Threads

  1. firewire 410 not detected on Mac os snow leopard
    By jlubeiro in forum FireWire Series
    Replies: 0
    Last Post: 01-24-2010, 11:02 AM
  2. Firewire Solo on Mac OSX Snow Leopard
    By marco.coiatelli in forum FireWire Series
    Replies: 11
    Last Post: 01-21-2010, 06:53 AM
  3. FIREWIRE 410 with Snow Leopard
    By uciel in forum FireWire Series
    Replies: 2
    Last Post: 09-16-2009, 04:27 AM
  4. FireWire Solo on Snow Leopard
    By robert.bulko in forum FireWire Series
    Replies: 11
    Last Post: 09-05-2009, 06:54 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts