Midisport 4x4 Driver

[Mirtha Shikles]

Jordi Torres wow. My 4x4 is sitting around waiting to be dumped. If I had any spare ports on my iMac Id be more tempted than I am now but this looks just a little bit past my comfort zone to try it out. Going by the info at your link, the driver has a good pedigree though.

With the emergence of USB as a standard, MIDIMAN, later named M-Audio, was an early innovative manufacturer who created USB interfaces that would convert the digital MIDI protocol to/from USB. When I joined tomandandy Music Inc. in 1999, to work on an early AI based automated composition system, external MIDI devices were still needed for the synthesis of production quality sounds. The project was developed on NeXTStep/OpenStep, for which I had written a Roland MPU-401 (one of the first PC MIDI interfaces) driver as a contractor for them, before moving to the U.S. An early task was converting the project from OpenStep to run on beta versions of MacOS 10.0.0.

Since musicians tend not to be flush with cash to throw out perfectly good hardware because of a lack of software support, I have modified and updated my original code that was donated to M-Audio, to now compile as 64 bit versions on these latest MacOS versions, so MIDISPORT owners can continue to support and operate their hardware on the newer versions of MacOS. The code has been released as open source under the liberal MIT License. I hope this small contribution can help people continue to make music with old synths and share it with the world.

If you feel so inclined, the easiest option is to send donations via my PayPal address leigh AT leighsmith DOT com. But the fact that people are able to benefit from the driver, and continue to use the hardware to make music is reward enough for me.

When I plug in the device (midisport 11) I can see that the MIDISPORTfirmwaredownloader does appear in the activity monitor app (briefly). The USB light on the device does pulse slowly and continuously. Unfortunately it still does not appear in the audio MIDI Setup app.

I just want to say a big thank you! After I have upgraded my Mac to OS 13.2 Ventura, the old 3.5.3 driver that was running under Mojave did not work anymore. I have found your driver on github and I have installed it. Now my good old Midisport 44 works again! I am very grateful!

Which version of the driver did you use?

I am running Ventura on a new Mac Mini and cannot get it to work.Any additional setting to use, or enebla/disable some security features? (I am using a Midisport 88)

Hi man, I just came to say a big thank you, I just update my imac to Monterey from Big Sur and the previous midisport driver crashed all my system, I was looking for 2 days what was happening and at the end when I found it I was trying to find a driver to work and I came to your driver that was a huge relief, you saved me from a format that I was ready to do. Thanks again!

Please find v1.3.1 files, along with earlier versions, available for download at SourceForge. Please read the README for the installation process. For the MIDISPORT 22, you will not need to download the optional old M-Audio driver.

The latest version of the open source MIDISPORT driver is v1.3.1, which addresses a number of problems running on recent versions of MacOS. I would recommend downloading v1.3.1 and installing that as the first thing to try?

Usually you should be able to open the System Settings app, and under Privacy & Security you will see a notification about the MIDISPORTDriver installation, and you should be able accept the exception to get it to Open Anyway. I will look into the work and money required to properly sign the .pkg file.

In principle, if we can find a copy of the software and run it on a 10.6.8 system, we can probably use a USB packet sniffer software to determine what messages are being sent to the 88 in order to write an open-source tool to recreate those messages. The only thing I can suggest is for readers to investigate the original CD-ROMs that were shipped with the hardware and look for the software there. In principle, if there is a Windows equivalent of the remote manager software, that could also be inspected to identify the packets, using a Windows machine, perhaps more easily than using a Mac able to run MacOS 10.6.8. But as you suggest, the first task is finding the software as shipped by Midiman/M-Audio.

Hi Leigh.

Months ago I was testing my MidiSport 11 on my MACPro 3.1 with Monterey 12.7.2 and your driver 1.3.1 and it worked perfectly. After updating to 12.7.4 it no longer recognizes it, the LED does not turn on.

I have installed the driver on a Macmini with Monterey 12.7.2 and it works.

I have checked the files that have been installed on both computers and they are the same.

Are these all the files?

Nevertheless, when I try to update the POD 2.0 with Line 6 Monkey, even if I do what it say to do, it doesn't work and keeps saying "Could not connect to the POD 2.0. Please check all MIDI and power connections and click 'refresh' in the Tone Locker".

I got yesterday a new MacBookPro and I am having the same problem. However my situation is different: I need to update my PocketPOD's Flash Memory v 1. I did install the Line6 Monkey and Vyzex Pocket POD. In addition, I did all the steps to update the Flash Memory Version 1 in my PocketPOD and also I did check the connections, MIDI IN and MIDI OUT were properly working, which means all hardware was communicating each-other.

There seems to be a common problem. All of you that are having problems are using those inexpensive (let's just call them CHEAP!) LogiLink USB cables. For the most part, they do not work well with Line 6 devices. You might want to obtain USB MIDI cables that have been proven to work well; the M-Audio Midisport UNO cables, for instance.

Two weeks ago I've bought a Noname MIDI-USB Converter and it doesn't work. Yesterday I've bought a new one M-AUDIO MIDI SPORT UNO (because I've read this somewhere on these sites that this is the right one) and it doesn't work too. I'm using WIN7 64 and the newest driver for MIDISPORT downloaded directly from M-AUDIO sites. I've tried the connection on two PC's and the problem is the same.

Hi again, I won a small battle. Now i try WIN xp and the FLASH memory was upgraded successfully, but the LINE 6 Monkey still doesn't recognize installed version. The probleme with LINE6 Edit still remains. it doesn't recognize my POD2.0.

I am simply lost on this one, and would be sad to draw conclusion that i should have bought something else than my POD 2.0, wich i have spent HOURS with and enjoyed .. but i would love to take my POD to the next level :-)

Heck, I can't even get reguiar midi in midi out cables to connect! Just updated everything to Mavericks and Monkey 1.65, but all I get is a yellow question mark in a picture of a pod 2.0 Not a good time to pull this on me.

I am using an old WinXP box and the ole Pod V2 connects right up using the crappo chinese one or the M-Audio Uno 1x1. I know the usb/midi thing can be exceptionally frustrating when it doesn't work but don't give up hope. Start from the start. (I'm not at home so I may have something wrong - correct me fellas!)

2) Fire up L6Edit - Now if the Pod is not seen here you should go to L6E ''preferences" and select the USB/Midi for the 'ins and outs''. If your usb/midi cable is not showing up there - then you have to figure out why your 'puter is not seeing it.

Interesting is - I do nothing with drivers, cables or other stuff. Just run Line6 Editor or Midi Quest11 and computer doesn't see POD2.0. Run Podman 32 after that and works well... POD2.0 magically appears. So far, I think cheap MIDIUSB works well and this is a problem of software not device.

My opinion? Cheap cables are usually lollipop (sorry for language, but it fits well here). I was trying with friend to connect YAMAHA keyboard through cheap cables via USB and then software was going crazy, computer mause and computer keyboard were going crazy. After using better cable (YAMAHA in this case) everything is on it's place.

I have a similar issue. When I began I was unable to see the POD 2.0 through Edit or Monkey. I swapped cables to one made by Cakewalk, and while at first it showed no connection, after flipping a switch or two on and off I finally got it available through Edit, and I uploaded all the factory presets to my workstation (Windows 10) Monkey was updated this weekend, but still will not connect. I'll keep playing with it I suppose... I'm wondering, if I do get this working, is there someplace one can go and download different custom presets to the unit, I ondered if there is a repository of sounds and setups somewhere. Thanks...

Jackson - the #1 prob is the usb/midi cables as you found out. Windows 10 I don't have. Line 6 gear loves the M-Audio Uno so if you have access to one try that (updated drivers should be on their website).

Hi,

I don't know, if I understand you correctly, but if you want to use the keyboard just as a MIDI-Controller, all drivers are already contained in your Linux distribution ("alsa-drivers"). No vendor specific drivers are needed. USB-to-MIDI is class compliant normally.

3a8082e126