Re: M Audio Firewire 410 Driver Download Mac
Towanda Tuning
Apple dropping on-going development for FireWire devices that were supported with the Core Audio driver standard is a catastrophe for a lot of struggling musicians who need to both keep up to date on security updates that come with new OS releases, and continue to utilise their hard earned investments in very expensive and still pristine audio devices that have been reduced to e-waste by Apple's seemingly tone-deaf ignorance in the cries for on-going support.
Probably not the first time you gurus have had someone make the logical leap leading to a request for something like this, but I was wondering if it might be somehow possible of shoe-horning the code used in previous versions of Mac OS that allowed the Mac to speak with the audio features of such devices to run inside the Ventura version of the OS.
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 very sad and very worried because im update my MacBook Pro to Mac OS to ventura and my very expensive firewire audio stuff stop working, It worked in Monterey with the "dongle-chain" Thunderbolt 3 adapter -> Thunderbolt 2 Adapter -> Firewire Adapter-> Firewire 800 to 400 adapter
I been the same, I had several Echo AudioFire audio interfaces, and suddlenly all gone because Ventura does not include the AppleFWAudio.kext what allow Core Audio FW devices to be recognized as Audio available interface for the OS.
Install the legacy firewire drivers yet? I would not expect different performance between 10 and 11. Also bios settings can be important, like preventing throttling and or energy saving (also on the pcie buss). Also just installing win10 might be a solution, you could even try to boot your old system boot drive and see what happens.
Good luck!
Agreed - it really is. I actually only use firewire for CueMix (MOTUs control app), the I/O from the MOTU 828MkII goes via ADAT to an RME RayDAT PCIe card. Just go RME and never have to worry about drivers again!
I tried to get a 2626 working on Windows 10 some years ago, but it was unstable, and was only useful for configuring the device, and even then I had to uninstall the driver afterwards as it was making Windows 10 unstable.
The USB-MIDI driver is, as the name implies, a MIDI-only connection via the TO HOST USB connector. It transmits MIDI data in both directions via a single USB cable. You can use it to record XS8 keystrokes and controller motion onto MIDI tracks in a DAW/sequencer running on your computer, and play back MIDI tracks from the computer to the XS8 synthesizer engine. In essence, what MIDI sequencing is all about.
The last official driver release was in 2008 (OSX Leopard), while Windows users were cut off in 2003 (XP/Vista). A beta driver for 64-bit Windows did surface at some point before it was all over, and it has since been modified by clever enthusiasts to run on modern systems.
The mLAN connectors of the XS8, as mentioned in your other post, can transmit both digital audio and MIDI bidirectionally with a single cable (16 mono/8 stereo out from the XS, 6 mono/3 stereo in, as well as 3 MIDI In/3 MIDI Out ports).
Henry:
THANK YOU, for a clear, concise answer!! :)
I downloaded all the Windows drivers from Yamaha, last night. Going to get the Mac drivers tonight in case I need to buy a Mac.
Let me ask you, would I be successful in attempting to connect my Motif XS8 to my Windows XP Service Pack 3 computers through FireWire? I just bought 2 more dedicated Windows XP 3 Machines and install discs for SP 1, SP 2 and SP3. I also bought 3) FireWire audio/midi interfaces on eBay.
The XS and XF both use the same driver for FireWire connection to your computer, with the same FireWire controller compatibility issues, so chances are exactly the same. The only difference between them in this respect is that the XF does not have the older mLAN mode option.
Due to a problem with the default FireWire (IEEE 1394) driver in Windows 7, MOTU FireWire audio interfaces may exhibit symptoms such as audio artifacts or dropouts during audio playback or recording or while an audio client program uses the driver program. This issue has been reported to Microsoft, and a change to the MOTU FireWire audio driver that will avoid the problem is planned if a patch from Microsoft is not available when the next MOTU driver update is released.
This is a long shot but I thought someone may have encountered a similar issue.
I've recently bought a new windows 10 machine. My ucx is crashing windows when used in firewire but works fine as usb. I read that reverting to the fw legacy drivers in windows should solve this but every time I try to swap them through the device manager it crashes windows. Ive granted all permissions and cant see anything else obvious. Has anyone encountered anything similar?
Thanks.
Long ago that I used FW with Win7 and old UFX .. but ...
AFAIR the change to use the legacy driver you do in the Firewire driver.
And for this the Recording Device does not need to be active.
Maybe try whether its possible to activate the legacy driver without having the interface online.
Sorry to hear about your issue. All that I can add is that I'm able to run FW Legacy drivers under Win10 x64 1909 with no problems. I forget the FW card I have, but it is the TI chip. Is your FW card a TI chip or the VIA? Have you checked to make sure the card is firmly seated in the PCIe socket? I've had issues with smaller cards like that remaining seated when you tighten the screws down to secure to the case.
I eventually found I had to double click on the .msi file, and while it appears to install the driver, all it really does is create a folder named "1394 OHCI Compliant Host Controller (Legacy)" in your C:/Program Files (x86) folder, and deposits the necessary driver files there - one set for 32 bit and for 64 bit Windows systems - you'll need to know which you're running.
Here is what has been working for me so far. With the latest update, I thought my card was a goner. I figured out the fix for the latest windows 10 19041! I spent a few hours today to figure out a new last step involving using device manager installing a the driver 61883.
Second, install the legacy driver and change controller settings to use it instead of the driver provided by Windows (device manager). Note that you might have to do this again after installing an new Windows feature update.
The ALSA firewire stack is part of the Linux kernel. That means most interfaces will be detected automatically. This is great for listening to music, playing games, and making the occasional video call.
UPDATE: I got my 16.0.2 working as a 16in/16out audio interface over firewire on Catalina. Turns out, during the installation of the firewire drivers, apple's new security features disable the drivers on installation, with no warning!?
but i can't get jack configured to use the alternative firewire driver (ffado) -
after some more research and experiments i found that newer kernels include snd_dice - a build in driver for the dice based cards that work together with alsa.so now i know why it works 'out of the box' - that is cool!but as i written above - this has stability issues in my setup. (most likely the used firewire chip in my laptop - a Ricoh Co Ltd - R5C832 PCIe IEEE 1394 Controller plays a crucial rule in this.. as fare as all the info i found TI chipsets should work much better)
A while ago Clemens Ladisch started working on FireWire drivers in ALSA. LGW contacted him and asked several questions about the ongoing work and the outlook. We also contacted FFADO developers for insights on the past of the project, the ALSA activity and possibilities of collaboration between the two projects.
The team has seen a lot of changes over time. David Wagner and Pieter Palmers are no longer active. A lot of work is currently done by Jonathan Woithe, Adrian Knoth and Arnold Krille, and most recently Philippe Carriere contributed a lot of code to the Focusrite driver.
However, none of us have the necessary kernel programming knowledge to make this work. Clemens has started work on a proof-of-concept driver, and the intention is that once complete it can be used by us as a template for the implementation of streaming engines for the different devices we support.
The only major difference between this and the present situation is that our streaming code will reside in the kernel instead of in our repository. In this respect the situation will be similar I expect to ALSA itself: the ALSA project manages both the in-kernel driver plus a bunch of related userspace utilities.
aa06259810