I’m trying to send midi cc messages to the meta from an Akai Force/MPC. I have tried Straight to the usb port and from a powered usb hub. I’ve done this in the past with other modules with usb midi, but the meta is not reading any cc and the Force is not detecting the Meta. I tried both the included adapter and a usb C to A cable.
I also tried to use a Roland um-one midi to usb interface, and that did not work either. The usb light was on and it mas getting midi messages(midi in lights up when the mpc is sending cc), but the led for the out did not.
MPC midi out >interface>usb a>adapter>MM
Maybe both are trying to act as a usb host and that’s why nothing happens? is there a way for the meta to act as a device?
so I dont have a Force/MPC, so the following is general.
MM current limitations to be aware of :
usb hubs are not supported
only supports USB devices i.e. MM is a USB host.
so you would have to use the USB B on the Force assuming this supports class compliant midi.
however, this may not work if the Force supports usb protocols (e.g. audio), depends if the MM enumerates this correctly.
um-one, Im surprised this does not work.
out light - if this is like other similar ‘dongles’ the out light will only come on if the MM sends midi - so not relevant here.
one question… if you use the um-one on a PC/Mac, how does it appear?
does it show up as ONE midi port or TWO (one for in, one for out).
if its two… then that could be the problem.
no the USB B socket and the um-one act as usb devices, and so should be working in the usb (host) of the MM.
no, the MM cannot act as usb device, so you cannot use the usb-a of the force.
so you would have to use the USB B on the Force assuming this supports class compliant midi.
It didn’t work, as far as I know, that port is only to connect it to a computer and it need to be engaged into computer mode.
however, this may not work if the Force supports usb protocols (e.g. audio), depends if the MM enumerates this correctly.
The force/mpc is usb audio compilant.
out light - if this is like other similar ‘dongles’ the out light will only come on if the MM sends midi - so not relevant here.
I’m trying to send midi from the force into the meta to map the knobs
one question… if you use the um-one on a PC/Mac, how does it appear?
does it show up as ONE midi port or TWO (one for in, one for out).
if its two… then that could be the problem.
one idea you could try is use an adapter like this usb to din one, which i can confirm definitely works solidly with the mm. you would need to send midi into that, from the trs<din jacks on the force
that adapter finally helped me to get a custom keyboard working with mm via its trs port:
hmm, the fact the UM-ONE is showing as two usb devices (ports in usb terms) could be the issue - it may be the MM is connecting to the first it sees, which might be the output. @danngreen would have to confirm that.
unfortunately, I suspect the only way forward on that is for the MM to allow device selection in the case where it sees multiple.
(this would be useful for other devices too)
personally, I know the Blokas Midihub work… and is a nice bit of kit - though goes beyond being just converter.
oh, I thought it was usb class compliant… but don’t know for sure.
(ofc, as above, even if compliant there still might be something else going on)
btw: @danngreen , it would be very useful if the MM displayed a quick popup with full device name when it sees a device connected… or perhaps in info menu?
this would us know if devices were enumerating correctly… and also if its just picking up an unexpected ‘port’.
perhaps if its in the menu, then that means later, it can be ‘extended’ to allow an alternative selection (when multiple are available)
Yes, I that’s what it does: it scans the interfaces in order and picks the first one with a class code it knows how to handle.
That would be useful.
I think it could scan all the interfaces, and if it only sees one that it knows how to handle (e.g. USB drive or a MIDI interface) then it picks that. If it sees more than one, then it shows a pop-up menu and you pick one. Regardless, there could still be a “report” in the System menu somewhere, showing what it found so you can debug.
yeah, I think for now this would be great…
but as I mentioned in dev topic, eventually, you’d want to be able to select multiple so you can support midi hubs.
however this makes most sense when you have the ‘midi modules’ implementations.
so ‘port’ just becomes another filtering parameter e.g. filter by channel, or device.
internally, you could combine with channel as both are just 4 bit (iirc) ie. 1-16 port, 1-16 channel - so just need 8 bit to describe.
as also mentioned, you’ll nee multiple (well at least 2), as its not uncommon to see input and output on different ports (like Roland um-one mentioned in this post. so you’ll need this when doing cv → midi.
I bought one of those adapters you mentioned but it doesn’t work. I’ve tried it from my Keystep 37 to the PC and Protokol but it doesn’t seem to pick anything up. I wasn’t the same company and it was only about £5 so I’ve bought one that is from the exact same company at £8 to see if they are different. Anyway, I’ll post here if it works.
I wasn’t the same company and it was only about £5 so I’ve bought one that is from the exact same company at £8 to see if they are different. Anyway, I’ll post here if it works.