02-29-2024, 05:29 PM
(This post was last modified: 02-29-2024, 05:40 PM by Jesse Johannesen.)
Hey Acnorytm, I apologize for not seeing your followup, the forum only shows me new posts once, then if I reload or go away then come back they disappear and there's no way to show all posts sorted by date. Sorry for that. If you ever need to be sure to reach me you can send me an email to Support@conductivelabs.com, I always see those.
In this case I think the issue is that either the Push3 or Shuttle system USB isn't fully compatible with our USB host ports. It sounds like a really strange one too, as usually things just don't work when this is the case, but to "sort of work" for "some things" is truly unusual. If we had one in the lab there is a chance we could use the USB sniffer to take a look under the hood, but we don't currently have access to one, and even then it usually requires that we convince the developer to make some change to the device code, which often doesn't happen. At the moment we are doing our best to keep track of these compatibility issues in a spreadsheet that we host so that people can at least get an idea of what will or will not work before purchasing. I'll post that link below. It sounds like at least there is a method that works for you, that's a relief.
It would be interesting to check where the issue is, and there may be a way. If you were to load an initialized patch on the MRCC and connect both devices via host ports, then route the Push to the Shuttle Control, and open the MIDI Monitor utility on the MRCC, you could see if the Notes are being received correctly by playing middle C and looking for note on / off events for MIDI note 60. If it says MIDI note 0 or something then we know that the Push is (likely) the device that is incompatible, if not then it's (likely) the Shuttle Control.
Here's that link:
https://conductivelabs.com/mrcc-usb-host...y-tracker/
In this case I think the issue is that either the Push3 or Shuttle system USB isn't fully compatible with our USB host ports. It sounds like a really strange one too, as usually things just don't work when this is the case, but to "sort of work" for "some things" is truly unusual. If we had one in the lab there is a chance we could use the USB sniffer to take a look under the hood, but we don't currently have access to one, and even then it usually requires that we convince the developer to make some change to the device code, which often doesn't happen. At the moment we are doing our best to keep track of these compatibility issues in a spreadsheet that we host so that people can at least get an idea of what will or will not work before purchasing. I'll post that link below. It sounds like at least there is a method that works for you, that's a relief.
It would be interesting to check where the issue is, and there may be a way. If you were to load an initialized patch on the MRCC and connect both devices via host ports, then route the Push to the Shuttle Control, and open the MIDI Monitor utility on the MRCC, you could see if the Notes are being received correctly by playing middle C and looking for note on / off events for MIDI note 60. If it says MIDI note 0 or something then we know that the Push is (likely) the device that is incompatible, if not then it's (likely) the Shuttle Control.
Here's that link:
https://conductivelabs.com/mrcc-usb-host...y-tracker/