search

leighsmith / midisport-macos

M-Audio MIDISPORT USB 64-bit MIDI device driver for MacOS 10.14+
Other
124 stars 7 forks source link

Confirmed Working in Ventura (intel) #43

Open FreQRiDeR opened 1 year ago

FreQRiDeR commented 1 year ago

V1.3.1 confirmed working perfectly with Ventura 13.2 on InTel. Monterey 12.4 also. Thanks!

Chuzzwuzza commented 1 year ago

Also M2 Mac Mini Ventura Midisport Anniversary 4x4

danfoley commented 5 months ago

How did you get the anniversary edition working? My Mac doesn't seem to power it on. Should the light come on at all when it's connected. I'm thinking maybe my 2x2 is just dead.

Chuzzwuzza commented 5 months ago

Will only light up when driver initiated

Kind Regards

Keith

@. @. @.*** 07709517072​

Sent from Proton Mail Android

-------- Original Message -------- On 5/24/24 12:15, Dan Foley wrote:

How did you get the anniversary edition working? My Mac doesn't seem to power it on. Should the light come on at all when it's connected. I'm thinking maybe my 2x2 is just dead.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

Chuzzwuzza commented 5 months ago

Special drivers for Mac they are open source do a search on github I forget the name find out later when home from work

Kind Regards

Keith

@. @. @.*** 07709517072​

Sent from Proton Mail Android

-------- Original Message -------- On 5/24/24 12:15, Dan Foley wrote:

How did you get the anniversary edition working? My Mac doesn't seem to power it on. Should the light come on at all when it's connected. I'm thinking maybe my 2x2 is just dead.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

aleksibovellan commented 5 months ago

My 2x2 Anniversary worked in M1 iMac OS Sonoma 14.5 just by installing these midisport-macos drivers, rebooting, and then connecting the USB device (to a powered USB hub in my case). The 2x2 interface starts its pulsing LED right after booting. However, there are occasional problems with weird MIDI timing, and sometimes the interface seizes to work if a screensaver or sleep mode kicks in. But those problems clear after a separate unplug-replug every now and then.

Perhaps these problems might be related to the "product ID" number somehow in the interfaces or something, but I'm sure @leighsmith is on the case when he can and will.

productid

How did you get the anniversary edition working? My Mac doesn't seem to power it on. Should the light come on at all when it's connected. I'm thinking maybe my 2x2 is just dead.

danfoley commented 5 months ago

I don't even see a USB 2.0 hub. Just a 3.0 hub. The open source is installer thing has a install hardware thing maybe I need to do that.

leighsmith commented 5 months ago

The anniversary editions are supported in the /usr/local/etc/midisport_firmware/MIDISPORT_devices.xml file. Specifically, for the 0x01050 device as shown on the screenshot posted by @aleksibovellan (thanks Aleks!). So if the MIDISPORT LED is not pulsing, two scenarios are possible:

  1. The MIDISPORT firmware downloader is not running as a daemon, and therefore is not noticing the uninitialised MIDISPORT anniversary device, which identifies itself as ProductID 0x1050. If the firmware downloader is running, it will download the firmware to the MIDISPORT, and reset the device, which will then run, start the LED pulsing, re-enumerate itself on the USB bus, and report itself as Product ID 0x1051.
  2. There is a bug in the downloading which means the downloading and reset is not completing.

To check if the first scenario is the case, in Terminal.app, you should be able to run the command: ps aux | grep midi, which should show if the firmware downloader is running as a daemon, for example, on my system:

root               350   0.0  0.0 34251884    460   ??  Ss   Tue08pm   0:00.49 /usr/local/libexec/MIDISPORTFirmwareDownloader /usr/local/etc/midisport_firmware/MIDISPORT_devices.xml

As has been reported in other issues, you can run the firmware downloader from Terminal.app and see if when the MIDISPORT is plugged in, it will then do the downloading. But only if the MIDISPORTFirmwareDownloader is not running as a daemon. Otherwise, you will have two servers attempting to respond to connections, and there is a good chance they may block each other. So use the ps command above to verify the downloader isn't running, before trying to run the command locally. To do so, you should be able to simply run (without the MIDISPORT connected):

/usr/local/libexec/MIDISPORTFirmwareDownloader /usr/local/etc/midisport_firmware/MIDISPORT_devices.xml

Then plug in your MIDISPORT.

If you get error messages, or you don't see the MIDISPORT boot, after plugging it in, that is more likely the second scenario. In which case, paste the error messages you get here.

If you see the firmware downloader running using ps, but no downloading occurs, to diagnose it further, it's probably best to kill the daemon and running it locally, and then we can determine why the daemon isn't running. To kill the downloader daemon, use the process id, the first integer, printed by ps, i.e. 350 in the example above for example:

sudo kill -9 350

If you've never run sudo before, you'll get a lecture and need to enter your password. You can then run the downloader as above. You should see similar diagnostics as:

Reading Hex loader firmware Intel hex file: /usr/local/etc/midisport_firmware/MidiSportLoader.ihx
Looking for uninitialised MIDISPORTs with vendor = 0x763
Found MIDISPORT 1x1 in cold booted state.
Reading MIDISPORT Firmware Intel hex file: /usr/local/etc/midisport_firmware/MidiSport1x1.ihx
Downloading firmware.
Booted MIDISPORT 1x1

To exit the firmware downloader, which will sit waiting for further devices connected, use ^C.

leighsmith commented 5 months ago

I don't even see a USB 2.0 hub. Just a 3.0 hub. The open source is installer thing has a install hardware thing maybe I need to do that.

You will only see a USB 2.0 hub listed in your system report if you have such a hub connected to your machine. USB 3.0 is the newer standard, so if you have a 3.0 hub connected to your Mac, you will see that displayed instead. Or, if you are using a USB-C to USB-A cable, you will not have the MIDISPORT device connected to a hub, and will need to look at the onboard devices, listed in the USB device tree by System Report.app

Obviously the key point is to look at all USB devices which are listed in the system report, and look for devices which have a Vendor ID of 0x763. If you don't see anything listed, then you don't have a functioning device, because, at minimum, it should identify ("enumerate") itself on the USB bus as having that Vendor ID.