M-Audio Midi Driver Removal / PT 2024

[ejinbc]

OP and others

A really good solution for folks on a budget is to get an older Eucon control surface - Avid Artist Mix. These are available on CL for around $300 per 8 channels (e.g. https://spokane.craigslist.org/msg/d...735802031.html). The Euphonix software is absolutely worth using - layouts alone make it worthwhile. Add an old iPad and you are set.

Oh oh, I hope I haven't awoken the AVID accountants so they stop supporting older Eucon interfaces to sell more premium S1s.

Musician on a Budget

ejinbc

[unkJE]

M-Audio (Axiom AIR 32 Min + Axiom Pro 49) work in Pro Tools 2024.3.1 (Windows) if you install the Command 8 Driver (with or without a Digidesign Command 8)
... first go to MIDI Studio Setup - Save Session - Reboot - then Peripherals - Save Session - Reboot - launch Pro Tools


Legacy Hardware Drivers
Control Surfaces
• Command|8 Driver for Mac:
Drivers are installed by Pro Tools software installer
Command|8 drivers for Mac OS X are automatically included as part of the Pro Tools 9 (and upwards) software installation
• Command|8 Driver for Windows:
For Command|8 users on Pro Tools 9 (and upwards), download the Command|8 Driver v9.0 for Windows =

https://akmedia.digidesign.com/suppo...0v90_69592.zip

After installing the Command 8 Driver, this message appears:
https://drive.google.com/file/d/1pOn...ew?usp=sharing
… hit ‘Enter’ – later you’ll be given the option to stop future messages …


MIDI Studio Setup – Axiom AIR Mini 32
https://drive.google.com/file/d/1QKB...45Z-LwWAu/view
In Pro Tools Setup > MIDI > MIDI Studio, set
Manufacturer: None
Model: None
Input Port: MIDIIN2 (Axiom A.I.R. Mini32) [Emulated]
Output Port: MidiOUT2 (Axiom A.I.R. Mini32) [Emulated]
Save Session
Restart computer
Launch Pro Tools



MIDI Studio Setup – Axiom Pro 49
https://drive.google.com/file/d/1sU8...lHe8qLmBx/view
In Pro Tools Setup > MIDI > MIDI Studio, set
Manufacturer: None
Model: None
Input Port: 2- Axiom Pro 49 MIDI In [Emulated]
Output Port: 2- Axiom Pro 49 MIDI Out [Emulated]
Save Session
Restart computer
Launch Pro Tools


Pro Tools - Peripherals
https://drive.google.com/file/d/1CzY...ew?usp=sharing



Recommend making a back-up copy of all the Avid Controllers from:
C:\Program Files\Avid\Pro Tools\Controllers
… and for Windows users - a copy of the Command 8 Driver


Today’s eBay (you don’t need a Command 8 for the above to work – just the Command 8 Driver)
US $125 - Digidesign Command 8 Audio Mixing Controller DAW Controller MIDI
https://www.ebay.com/itm/226148224066

[smurfyou]

Doesn’t that just achieve general MIDI data, not the control surface function? What does the Command 8 driver have to do with anything?

EDIT : just looked at your Peripherals picture. So these two pass the same commands that Command 8 used? And you've tested this?

[unkJE]

Originally Posted by smurfyou

Doesn’t that just achieve general MIDI data, not the control surface function? What does the Command 8 driver have to do with anything?

EDIT : just looked at your Peripherals picture. So these two pass the same commands that Command 8 used? And you've tested this?

Tested on both keyboards - using the Axiom Pro 49's Faders to Learn MIDI CC to control Mini Grand's Level/Model etc - without my Command 8 connected.
MIDI Studio Setup gave access to the keyboards' IN & OUT - gave me the option to choose M-Audio

Axiom Pro 49 – MIDI IN
https://drive.google.com/file/d/13y7...ew?usp=sharing

Axiom Pro 49 - MIDI OUT
https://drive.google.com/file/d/1ZvE...ew?usp=sharing



... love to know if it works on Mac, too!

[unkJE]

Originally Posted by Benny_Cha_Cha

In the same boat here. Removing the driver has blown up my workflow for mixing by breaking both V-Control Pro and Mulligan. I wouldn’t be upset if PT offered those functions in-house. But they don’t. Please fix this Avid. Telling us to use the ancient, ancient HUI protocol is not helpful.

Hi Benny

Wondering, if you used the workaround shown in Post #62, could you then use both V-Control Pro and Mulligan? Workaround works here on Windows 10 for both Axiom AIR 32 MINI and Axiom Pro 49 with Pro Tools 2024.3.1
https://duc.avid.com/showpost.php?p=...6&postcount=62


To all M-Audio keyboard owners: does this workaround work for you?

I’d like to make a list to submit to AIR Music Technology, of any M-Audio keyboards that still “won’t work” with this workaround … thank you!

[unkJE]

You don’t need a Command 8 for the workaround in Post #62 to work – just the Command 8 Driver

… just noticed this bargain is still listed on eBay:

US $125 - Digidesign Command 8 Audio Mixing Controller DAW Controller MIDI
https://www.ebay.com/itm/226148224066


Command 8 works with Pro Tools 2024.3.1 on Windows
Command 8 Setup Guide for Windows 10
https://duc.avid.com/showthread.php?t=427889

[Benny_Cha_Cha]

I just read post #62 and it doesn't seem like this would solve the issue for Mulligan or V-Control Pro, both of which depend on the M-Audio Keyboard driver specifically. I have a Mac, so I can't just install that driver and it does not come up in the Peripherals window. The issue is that both apps use the "plugin mapping" feature. If I'm missing something, please let me know.



In any event, I know Leigh at ReFuse is working on a new version of Mulligan that doesn't need the M Audio driver.


12.2023 works fine for me in the meantime...

Originally Posted by unkJE

Hi Benny

Wondering, if you used the workaround shown in Post #62, could you then use both V-Control Pro and Mulligan? Workaround works here on Windows 10 for both Axiom AIR 32 MINI and Axiom Pro 49 with Pro Tools 2024.3.1
https://duc.avid.com/showpost.php?p=...6&postcount=62


To all M-Audio keyboard owners: does this workaround work for you?

I’d like to make a list to submit to AIR Music Technology, of any M-Audio keyboards that still “won’t work” with this workaround … thank you!

[unkJE]

Originally Posted by Benny_Cha_Cha

I just read post #62 and it doesn't seem like this would solve the issue for Mulligan or V-Control Pro, both of which depend on the M-Audio Keyboard driver specifically. I have a Mac, so I can't just install that driver and it does not come up in the Peripherals window. The issue is that both apps use the "plugin mapping" feature. If I'm missing something, please let me know.



In any event, I know Leigh at ReFuse is working on a new version of Mulligan that doesn't need the M Audio driver.


12.2023 works fine for me in the meantime...

According to Avid, the M-Audio Driver is automatically installed on Mac – in Windows I can see the M-Audio Driver (M-Audio Keyboard.dll) in C:\Program Files\Avid\Pro Tools\Controllers

Can you check to see if you have it – sorry, I’m Mac-ignorant.

Before setting Peripherals, go to MIDI Studio Setup – when I click on the IN and OUT, I can choose M-Audio Axiom Pro 49/AIR Mini32

Reboot

Then I go to Peripherals, choose Command 8 (unconnected, with only the Driver installed) and can choose M-Audio in the drop-down Menu for IN and OUT

Reboot

Works on Windows ...

I contacted reFUSE earlier today and asked them to test this workaround for both V-Control Pro and Mulligan ... will post if answered ... here's hoping!

[atticmike]

Here's to when Avid removes the next old driver reFuse Software is going to use to connect Mulligan *cheers*

Originally Posted by Benny_Cha_Cha

I just read post #62 and it doesn't seem like this would solve the issue for Mulligan or V-Control Pro, both of which depend on the M-Audio Keyboard driver specifically. I have a Mac, so I can't just install that driver and it does not come up in the Peripherals window. The issue is that both apps use the "plugin mapping" feature. If I'm missing something, please let me know.



In any event, I know Leigh at ReFuse is working on a new version of Mulligan that doesn't need the M Audio driver.


12.2023 works fine for me in the meantime...

[smurfyou]

Originally Posted by unkJE

According to Avid, the M-Audio Driver is automatically installed on Mac – in Windows I can see the M-Audio Driver (M-Audio Keyboard.dll) in C:\Program Files\Avid\Pro Tools\Controllers

Can you check to see if you have it – sorry, I’m Mac-ignorant.

Before setting Peripherals, go to MIDI Studio Setup – when I click on the IN and OUT, I can choose M-Audio Axiom Pro 49/AIR Mini32

Reboot

Then I go to Peripherals, choose Command 8 (unconnected, with only the Driver installed) and can choose M-Audio in the drop-down Menu for IN and OUT

Reboot

Works on Windows ...

I contacted reFUSE earlier today and asked them to test this workaround for both V-Control Pro and Mulligan ... will post if answered ... here's hoping!

But that's still using the Command-8 protocol and just assigning it to the MIDI I/O on your M-Audio keyboard. As if you weren't using the Command-8 through it's own USB port. I don't think that will help here unless for some reason the Command-8 and M-Audio control protocol is compatible. (Either way Command-8 isn't available for Silicon Mac users)