|
07-09-2020, 10:01 PM | #1 |
Human being with feelings
Join Date: Jul 2020
Posts: 7
|
How to get Reaper to see MIDI events from an M-Audio Audiophile USB box
I have a Midipro midi keyboard controller connected to a mobo USB port on my Ubuntu 20.04 machine via an old M-Audio audiophile USB box. This hardware setup works fine with various standalone softsynths, and I can see midi events as expected with aseqdump. But when I select and enable the device in Reaper (v6.12c), even though Reaper sees it as hw:USBtm, and also knows whether it's turned off or on, it's either ignoring or not receiving any of the midi events from this input. Or actually it must be receiving *something* because when I hit a key on the midi keyboard, a small white square appears in the VU meter -- but it doesn't trigger any sound. (The virtual keyboard also produces the same white square when I hit a virtual key, but it also produces the expected note.)
For reference, the virtual keyboard works fine. (Is there perhaps a way of routing the physical hardware midi events into Reaper through the virtual keyboard?...) I'm also getting 'good' across the board from all the realTimeConfigQuickScan tests. Can anyone tell me what I might be missing or doing wrong? Or maybe if there's a workaround? Last edited by paulbee; 07-09-2020 at 10:34 PM. |
07-09-2020, 11:00 PM | #2 |
Human being with feelings
Join Date: Mar 2008
Location: Planet Earth
Posts: 9,098
|
If both look like midi data is coming in, could the midi channel be in play?
|
07-09-2020, 11:30 PM | #3 | |
Human being with feelings
Join Date: Jul 2020
Posts: 7
|
Quote:
Thanks for the suggestion. So, I have a TyrellN6 track set to: all midi inputs, all midi channels, which I think should mean that all channels should work, right? In any case, what I find is, I can switch to different channels on the virtual keyboard, and they all work. Conversely, whichever different channel I switch to on the minipro keyboard, I don't seem to get anything out of any of them. In another update, the white square in the VU meter is no longer appearing in response to hardware input. I'm not sure what I did to disable it -- or to make it appear in the first place either :-( Sorry, I'm very new to this Reaper software and I'm kinda lost... |
|
07-10-2020, 05:09 AM | #4 |
Human being with feelings
Join Date: May 2006
Location: Surrey, UK
Posts: 19,681
|
The white (or coloured, depending on the theme) indicated incoming MIDI. If you have not disabled it, then no square = no MIDI received.
Look at Preferences / Appearance / Track Control Panels "Show MIDI outpu7 activity ..." ("Output from where I do not know, is that a typo?). Also check the list in the User Guide, at 3.41.
__________________
DarkStar ... interesting, if true. . . . Inspired by ... |
07-10-2020, 07:08 AM | #5 |
Human being with feelings
Join Date: Mar 2008
Location: Planet Earth
Posts: 9,098
|
Might be worth looking in "Options|Preferences|Midi Devices" to verify your midi device shows up there and is flagged as enabled.
|
07-10-2020, 07:54 AM | #6 |
Human being with feelings
Join Date: Jul 2020
Posts: 7
|
Thanks guys.
Yup, the 'show midi output activity' box is checked. And everything on the 3.41 checklist is fine too as far as I can tell. The midi device is showing up on the midi devices popup, and it's enabled. What I have found though is that if I power up the keyboard and M-audio box, then start reaper and then aconnect 28 128 (where 28 is the midi keyboard irq and 128 is 'virtual rawmidi', which in fact is evidently reaper), then the midi keyboard works! Ie it sends midi data to the appropriate track just like it ought to. So I guess that's my workaround unless anyone has anything better? I have to say though that something must be very wrong if this is the only way I can get reaper to listen to the midipro/M-audio input! (fwiw if I do a midi reset or retry, the hardware keyboard is immediately lost, and I have to do another aconnect 28 128 to get it working again. This method also appears to completely bypass Reaper's midi dialog settings; hw:USBtm can be enabled or disabled and it makes no difference, the aconnect trick still works -- although ironically, if hw:USBtm *is* enabled I get an error that says the hardware is missing -- ironic because this kludge seems to be the only way I can get reaper to actually respond to it!) Last edited by paulbee; 07-10-2020 at 08:00 AM. |
Thread Tools | |
Display Modes | |
|
|