Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER for Linux

Reply
 
Thread Tools Display Modes
Old 12-15-2019, 02:08 PM   #1
Celphor
Human being with feelings
 
Join Date: Jan 2013
Location: Austria
Posts: 73
Default Reaper Linux and M-Audio keyboards with ALSA

Hi,

there are several topics and threads here and elsewhere on the internet about the behavior of M-Audio Keyboards and Reaper for Linux using ALSA MIDI.

I spent hours of trying with my old Oxgene 8.

First of all MIDI messages only appear after doing a MIDI Reset on the keyboard (not in Reaper, this doesn't change anything).

amidi --receive or aseqdump -p always show fine MIDI Input

But not in Reaper. Monitoring the track with the JS Midi Monitor shows crippled input. Instead of Note On 90th, DFs and DDs are displayed as Status Bytes. One key hit shows 6 bytes instead of three, velocity and key number are in the wrong place.

But using JACK->ALSA->Reaper is fine.

So what might be the reason?

I assume it's M-Audio's way of omitting the status byte if it doesn't change with the next command and Reaper's raw MIDI input is not appreciating this two byte form.

Maybe there's a difference between raw and seq.

Any ideas?
Celphor is offline   Reply With Quote
Old 12-17-2019, 07:02 PM   #2
s wave
Human being with feelings
 
Join Date: Sep 2018
Location: Colorado
Posts: 250
Default

Look in your ALSA gui or configuration. I had trouble with Pulse when I started, in preferences auto suspended pulse?

In reaper...

Preferences>Device>Audio System | change to Jack or Alsa pulse dummy?

And Preferences>Device>Audio System | X auto suspend Pulse

what OS flavor are you using?
s wave is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 06:47 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.