is there anyway for this driver to work with a Midisport UNO?

[emperorbohe]

Just wondering, since support for the UNO also seems to not work as of Catalina. thanks!

[leighsmith]

If you connect the device to the Mac, then click the Apple menu, select "About This Mac", select "System Report", and then select the Hardware -> USB menu to display the device tree, do you see any devices listed as "Composite device" with a Vendor Id of "M-Audio"? If so, please post the Product Id which is listed?

[emperorbohe]

sorry for the late response! this is what I see in my System Report (I'll just attach all the info just in-case):

Product ID: 0x0150 Vendor ID: 0x0763 (M-Audio) Version: 0.14 Speed: Up to 12 Mb/s Manufacturer: M-Audio Location ID: 0x14400000 / 4 Current Available (mA): 500 Current Required (mA): 0 Extra Operating Current (mA): 0

[pentteri]

I'd like to see Uno support as well. In my case it does kind of work out of box with Big Sur 11.4, but I see a lot of dropped notes, and pitch bend and modulation wheels are very very choppy. Installing this driver does not change the behaviour in any way. Since it kind of works, maybe the data loss is some other problem in my Mac?

I have similar data as emperorbohe above, except very different version number

M-Audio MIDISPORT Uno:

Product ID: 0x0150 Vendor ID: 0x0763 (M-Audio) Version: 62.01 Serial number: 206833444E53 Speed: Up to 12 Mb/s Manufacturer: M-Audio Location ID: 0x14100000 / 2 Current Available (mA): 500 Current Required (mA): 400 Extra Operating Current (mA): 0

[Graefer]

My Midisport Uno works flawlessly with the driver. Big thanks to Leigh!! And shame to M-Audio not delivering such since years.

[SynthiaPayne]

+!

props to leigh!! synth

On 8/28/2021 3:27 PM, Graefer wrote:

My Midisport Uno works flawlessly with the driver. Big thanks to Leigh!! And shame to M-Audio not delivering such since years.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/leighsmith/midisport-macos/issues/21#issuecomment-907697477, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVZZKZC5YK3NEXQYGVQ6ZDT7FPFVANCNFSM5AHRRODQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[CarmeloPR]

I'm on Big Sur 11.6 and also contending with Midisport Uno. However, some folders listed in the instructions do not exist in my audio folder. The "extensions" and "launchdaemon". Ive run the install and it processed but nothing has changed and the folders still don't exist, so I'm assuming it don install. Sorry I am a newbie but if you got any direction I would DEEPLY appreciate it. I just want to get out of this rabbit hole and get back to creating. THANKS

[sixstringv]

I'm running Mac OS 11.5.1 with MIDIsport driver 1.3 installed and UNO connected direct to the iMac.

Here's what sys info has for my UNO: Product ID: 0x1011 Vendor ID: 0x0763 (M-Audio) Version: 1.21 Speed: Up to 12 Mb/s Location ID: 0x14600000 / 12 Current Available (mA): 500 Current Required (mA): 0 Extra Operating Current (mA): 0

So far the USB led pulses constantly. When a MIDI device is on the MIDI in led flashes. I opened Reaper Audio>MIDI Devices and enabled the UNO which was shown as disabled and after that it seems to work. The Mac AudioMIDI Setup app doesn't show it however. But at least it's working again in Reaper.

[emperorbohe]

i'm still on Catalina, i tried re-installing again since it looks like some of you have had some success. unfortunately it still does not work for me, i can get the midi out from my mac to sync to the external device, but the Midisport Uno still is not accepting anything if i try to midi in from my external device into ableton (the uno's midi in does not flash either) .

[petedottech]

Has anyone had any success with MacOS 12.6 (M1) and a MIDISPORT Uno?

M-Audio MIDISPORT Uno:

Product ID: 0x0150 Vendor ID: 0x0763 (M-Audio) Version: 62.01 Serial Number: Speed: Up to 12 Mb/s Manufacturer: M-Audio Location ID: 0x02140000 / 3 Current Available (mA): 500 Current Required (mA): 400 Extra Operating Current (mA): 0

I have tried the latest drivers v1.3.0, but with no success. The device is recognised, but does not transmit or receive and midi data.

Thanks in advance.

[leighsmith]

Assuming you installed the driver, the devices which are handled are listed in /usr/local/etc/midisport_firmware/MIDISPORT_devices.xml which can be displayed from the Terminal.app with:

cat /usr/local/etc/midisport_firmware/MIDISPORT_devices.xml

That shows that the M-Audio MIDISPORT Uno is not handled by this driver, since the product id of 0x0150 isn't supported. I understood the Uno's to be a USB MIDI class compliant device, and hence not need this device driver in order to operate properly, but I could be mistaken? Have you verified that the device doesn't work, without attempting to install the driver? If it doesn't work straight out of the box, then I can look into adding the support for the Uno devices.

[flavianh]

@leighsmith My Uno works very well on a MacBook Air 2017 running Monterey (12.6.1) but not my MacBook Air 2022 running Ventura (13.6.3). It seems to be using the generic USB driver on both machines, as evidenced by IORegistryExplorer Both machines show IOUSBHostFamily in the bundle.

I'm experiencing problems on Ventura, though, as the MIDI input is working fine, but the MIDI output is not. I was hoping your driver could be useful, but it seems this device is out of the normal product line you have in scope.

If it helps, here's my device information:

M-Audio MIDISPORT Uno:

  Product ID:   0x0150
  Vendor ID:    0x0763  (M-Audio)
  Version:  62.01
  Serial Number:    205B31455053
  Speed:    Up to 12 Mb/s
  Manufacturer: M-Audio
  Location ID:  0x01130000 / 3
  Current Available (mA):   500
  Current Required (mA):    400
  Extra Operating Current (mA): 0

I tried to reverse-engineer your configuration file and add

     <dict>
            <key>DeviceName</key>
            <string>MIDISPORT UNO</string>
            <key>WarmFirmwareProductID</key>
            <integer>0x0150</integer>
            <key>ColdBootProductID</key>
            <integer>0x0113</integer>
            <key>NumberOfPorts</key>
            <integer>1</integer>
            <key>ReadBufferSize</key>
            <integer>32</integer>
            <key>WriteBufferSize</key>
            <integer>32</integer>
            <key>FilePath</key>
            <string>/usr/local/etc/midisport_firmware/MidiSport1x1.ihx</string>
        </dict>

but no luck. Running /usr/local/libexec/MIDISPORTFirmwareDownloader /usr/local/etc/midisport_firmware/MIDISPORT_devices.xml, the command is still stuck at Looking for uninitialised MIDISPORTs with vendor = 0x763.

Thanks so much for the work you're doing for the community by the way, it's amazing!

[flavianh]

By the way, M-Audio claims the Uno has been tested and is supported on Ventura, both on Intel and Apple Silicon processors: https://support.m-audio.com/en/support/solutions/articles/69000824934-m-audio-macos-13-ventura-compatibility#Firmware-Updaters Maybe all the device needs is a firmware update...?

[flavianh]

I just had an email exchange with the M-audio support team, they insist that only Apple M1 "base-level Apple Silicon" (whatever this means) are supported by the Uno. The rest appears unsupported, and the hardware is probably obsolete.

I guess I'll have to return my purchase.

[battaglia01]

I'm having issues as well and have an M1 Max, so I'm not sure what on Earth "base level" means.