Midisport

[Qiana Thieklin]

Ihave a 2x2 midisport and can confirm it does not work with the organelle. I ended up buying an iconnectivity mio and works beautifully. Be weary of the cheap usb midi cables as there are lots of complaints about latency

The Organelle actually only work with class compliant MIDI devices. @fede so when you go to the system info screen on the Organelle, nothing shows up under MIDI? do you recall if you had to download or install anything for it to work on your computer?

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?

I am trying to run my Casio WK-1630 keyboard into my computer using an m-audio midisport uno. When I plug it into the usb port, one green light on the uno starts blinking. If I press a key on the keyboard, the midi 'in' light blinks once but then will blink no more upon further key presses. A couple times it worked for about twenty seconds. Every time I pressed or released a key the 'in' light would blink, which I assume is correct behavior.

I have installed and uninstalled drivers from m-audio up the wazoo. I've tried new ones and old ones. At one point Reaper was actually listing an input midi device (even though the uno wasn't working, Reaper apparently recognized the driver).

I've got an M-Audio Uno and I'm having some problems with it. Not yet totally sure the blame lies with the Uno but it's looking probable, and there are quite a few negative reviews and reports of issues with this device...

I recently bought the midisport uno interface with the intention of updating my Vetta HD to the Vetta II. I had to contact tech support because of a registration problem with the serial number. When I told him of my update intentions he advised me not to update, saying that if anything went wrong during the update procedure that my Vetta would become an oversized door stop. He said that it would have to be sent to the shop for repairs and that because of the age of the amp finding parts would be an issue. So now I have a conundrum about whether to risk an update. Has anyone heard of this problem before? Any unrecoverable crashes during an update? I've really been looking forward to performing this update for a while but now I'm afraid of losing everything if I do. Thanks in advance for any suggestions.

I'd hook it up and try reading some patches etc. though the cable. If all seems to be working well with it and the amp and everything functions as it should, then I'd go ahead with the upgrade after reading and gaining a full understanding of exactly what to do and when to do it.

For what its worth, the upgrade is not really that big of a deal. The tuner works better and other stuff like that but all the factory patches still pretty much suck in my opinion whether it's the new or old software but that's pretty typical of any make. Factory patches just generally suck no matter what factory they come from or what gear they're going into.

I've only used the Uno and I think it was the only recommended midi cable to use. For no more than they cost it's just not worth messin around with it. Do everything you can to ensure success from the onset.

Monkey no longer works as line6 disabled it. it was a web based tool that was unwise to implement in the first place as it added far too many places for bad things to happen in the updating process. Best to use an update file and a direct connection to the amp instead of adding a bunch of internet garbage to the chain.

So the M-Audio Midisport 2x2 looks like a good option ... but I'm worried that the box is listed as containing a CD with drivers (including Mac) ... which kind of suggests that it's not class compliant and it may not work with the iPad ?

Any ideas on compatibility of the midisport or else other suggestions welcome ... the immediate problem I'm trying to solve is combining 2 midi din signals for use on my iPad. (FWIW, one is clock and start/stop ... the other is just midi notes)

3a8082e126