M-audio Drivers Mac

0 views

Skip to first unread message

Enrichetta

unread,

Aug 3, 2024, 5:27:19 PM8/3/24

to tiotitenre

There are USB mixers that mix-down to stereo (or mono). The main advantage of multitrack recording is that you can adjust and edit the tracks independently or you can re-record the vocals or one instrument, etc., if you want to correct or change part without re-recording everything.

Unfortunately, the drivers for the M-Audio M-Track present multiple 2 channel devices rather than one multi-channel device. Currently, Audacity can only record from one device at a time, so that limits you to 2 channel recording.

I installed Ubuntu studio and tried to make it recognize the audio card m-audio 2496. My efforts caused me to lose my system and now I've done a fresh install and was wondering how I should make the system recognize this card the right way.

The box has BeBob hardware and requires that the firmware be loaded at boot time. Originally it required that the firmware be uploaded every time, but the last version of the M-audio driver for Windows allowed the firmware to be stored on the device even while powered off, but it still needs to have a signal sent to it at boot time to get it to load that firmware into the operational memory. I should mention that if I boot the machine into Windows the box works just fine and if I reboot from Windows into Tumbleweed without powering off the machine then the box also works in Tumbleweed, so I know that the hardware works with the current Linux drivers.

Here is the relevant page from the ffado mailing lists that describes the kick-start that I need to do.

In particular, what I need to accomplish is given as follows:
2. Send magic bytes to device with jujuutils
$ ./firewire-request /dev/fw1 write 0xFFFFC8021000 010000000000110100000000
I did a lot of searching and it would appear that jujuutils was renamed to linux-firewire-utils as per this link, but that package is not available on OpenSUSE.
-firewire-utils

Perhaps someone with a better understanding of the current audio drivers can help me out here. Has the support listed in the above links just not made it into the current kernel yet? The output of dmesg seems to indicate that it is configured to send the cue to load the firmware and that should get the unit working, but it was unsuccessful for some reason.

I did have a thought though: since the interface works perfectly OOTB on Debian 11 (5.15 kernel from backports) under ALSA, the method of controlling and communicating with it must already be known since ALSA and the driver the interface uses is free software, and therefore it should be theoretically possible to write a driver for it for macOS and CoreAudio. Right?

However due to lack of documentation from m-audio, reading the source-code of the Linux driver can help to understand how the device works and would make it easier for someone to write a driver for macOS.

i have the m audio 410 hooked to powered monitors and linked to a mac book pro with logic 7.2 i want to record vocals but i am unable to hear the instrumental through the headphones, the headphones are connected to the headphone port. how could i fix this problem??

Open the M-Audio driver panel, click the Output tab and make sure that "Phones" is not set to 'mute', make sure it's set to 'main' rather than Aux, and check to see if the correct source is selected (ie: Mon 1/2).

Hope that helps. Also, you can use that same panel to "mute" the output to your monitors so it's only outputting via headphones - which makes it nice for Vocals when you're in the same room as your computer system.

You will need to tell your Computer where the audio (and midi) will be going in and out. you will also need to tell your software (Logic) the same thing. Once all the settings are selected it should stay that way.

The computer settings are in the main System preferences under 'Sound' and Logic is in the 'Driver' section of preferences. Of course there is also the Audio/Midi set-up found in the Utilities section of the Computer Applications area.

Whenever you first start up your computer and you hear no sound through your M-Audio box, open iTunes and start a track playing, open M-Audio Firewire drivers panel and you should (hopefully) seem some level in the VUs, now click the "reset" button found on the right hand side of the M-Audio panel.

This forces the M-Audio hardware to reset, and provided an audio signal is passing through it, you'll suddenly hear it on output. There seems to be a bug with the current version of the driver - as I get the same problem all the time now, and never had it in the past using the same FW410 box.

I have an external audio interface (M-audio fast track c400). In order to get my macbook to recognize it (display in audio/midi setup), I have to reboot, which is a hassle. I have had other m-audio interfaces that were automatically detected when connected, and I'm pretty sure this one should be the same. Most posts around the internet suggest updating the OS or the software/firmware for the device. I have done all of those with no luck. I am currently running OS X 10.8.5.

Inspired by @sbugert's answer, I started looking into other system daemon's that might do the trick if restarted. As a shot in the dark I killed coreservicesd. This caused the OS to become visibly unstable and I was eventually logged out automatically. To my surprise, when I logged back in, my audio interface was recognized..

Based on that, I hypothesized that killing coreservicesd and logging out/in may be a possible (ugly) workaround. So I unplugged the interface and plugged it back in, and as expected, it was not recognized. So I killed coreservicesd and attempted to log out, however I could not get the system to log out due to the instability caused by killing coreservicesd. I eventually was forced to do a "hard" shutdown (i.e. holding the power button until it turns off). After booting up the macbook again, the interface is now recognized automatically every time I plug it in. I suspect that this "hard" reset may have solved the issue without all the shenanigans with the coreservices daemon, but I have no way to test that.

Here I have discovered that if I select another device before disconnecting the interface (Fast Track C400 too), I can connect it again later with no problem. But if I am using the fast track and then disconnect it, it can't connect again until restart it.

The problem may be less with the hardware and more with your choice of software; Audacity isn't exactly professional-quality, and it doesn't come with ASIO support out of the box for licensing reasons. See _Audio_Interface for more information.

I had this same problem using the M-Audio Driver.I did find a fix for this problem. This will, of course be dependent upon a couple of factors. The speed of your computer and the speed of your USB audio device (2.0, 1.0, etc.).

This is because the driver input and output info is installed when using the factory drivers, but ultimately this is not a problem since the tracks are still numbered, just something I wanted everyone to be aware of.

This link is for other drivers for your NUC. You will find there in addition to the Graphics Drivers, the following drivers: Management Engine Driver, ITE Tech* Consumer Infrared (CIR) Driver, LAN Driver, WiFi, BT, Audio, USB Type C Power Delivery.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.