M Audio Firewire Solo Driver For Mac Os X
Sofia Gilcrease
audio interface driver
What's new in this version:
Updated Family Release Driver Now includes ProFire LightBridge. Improved MIDI Performance Fixed a problem where the 1.6-1174 driver uninstaller in 10.4.4 displays error 5370 and does not remove files Fixed a problem with FireWire MIDI output latency time in driver 1.7.1 Fixed "ProjectMix I/O MIDI Application" for upgrading the firmware on the PMIO with driver 1.7.1 Fixed a problem where FireWire Audiophile Analog 1/2 in "link and pans" d...
That means you are using MME host in Device Toolbar. See if using Windows DirectSound or Windows WASAPI host avoids the need to change the sample format of the audio. Also make sure you have the latest Windows 7 drivers for your device from the M-Audio site - here M-Audio.
Gale Andrews wrote:
That means you are using MME host in Device Toolbar. See if using Windows DirectSound or Windows WASAPI host avoids the need to change the sample format of the audio. Also make sure you have the latest Windows 7 drivers for your device from the M-Audio site - here > M-Audio> .
Here's the weird part. I can get it to work fine by using an AC adapter to power it and using a USB adapter to connect it. However, when I try to use a firewire to connect it to my computer (how it's supposed to work), the computer recognizes it and even picks up the sound in the sound menu. But then when i select it in Adobe Audition (in the audio hardware section), no sound is picked up by the microphone when recording.
If the control panel does not open, this issue is directly related to the software package of the ASIO device.
So some developers have integrated that feature in their software, but some not.
Often there is as well an override function of the sample rate related to these devices, which is definitely an error because the ASIO standard does not support this. The result will be that you think you have got a transpose change while you have exported your audio- mixdown, But this is not the case. The Cubase project is correctly setup at a current sample rate, but the ASIO device is not playing back the correct sample rate. This is related to a bad ASIO driver and maybe its Windows Media driver as well.
(Some devices have as well a hardware switch for the sample rate, which also overrides the project sample rate.)
Cheers,
If I try and run jack using "firewire" as the driver, the computer either instantly reboots, or, very occasionally, simply powers off. This is very disconcerting and I hope I'm not damaging my system in any way. If I could get to the point where I could actually start jack then I could probably take it from there.
I am using a firewire cable to connect the m-audio to the computer, just like the grey one in your picture, I presume. I got the exact same box. I have a mic in input 1 in m-audio. I get a signal and can see the clip react.
Thx for the great tutorial. I am new to linux, so far I have my linux all setup except this firewire solo.. this is really killing me haha, I am still trying to make it work. good tutorial tho :) Thx man.
I found my answer on another site. If I follow these steps I am able to get audio out: 1) Plug the Firewire Solo into my Mac and boot up; 2) Plug in a power supply to the Solo; 3) Shut down the Mac and disconnect the firewire cable; 4) Attach the Solo to my Linux machine and boot up, without unplugging the power supply from it.
1)Even when having the realtime kernel (Ubuntu 9.04 latest kernel), being in the disk and audio groups in all ways imaginable
(tomas@tomas-desktop:$ groups tomas
tomas adm disk dialout cdrom audio plugdev lpadmin admin sambashare firewire)
, having edited the limit.conf to have the @audio and @priv entries, am I still not able to run JACK as a normal user. Can you think of any other thing i might be missing?