Open rtega opened 3 months ago
Some aditional info: amidi -l
shows:
Dir Device Name
IO hw:3,0,0 Keystation 88 MK3 Keystation 88
IO hw:3,0,1 Keystation 88 MK3 Keystation 88
According to this thread on linuxmusicians the naming convention in the kernel changed after kernel 5.11 thus confusing a2jmidid.
This looks to be a bug in a2jmidid.
I compiled the daemon from source here and the issue is already resolved on this latest version but not the ubuntu 22.04 version that I used before. I'll file a bug against ubuntu then. I see that this has been solved with pull request #5 .
Actually there never was a new release/tag after the fix had been merged. The last release still shows the behaviour you described. Unless Ubuntu wants to pull in the fix manually...
If you had a look at the conversation for the PR you know @nedko pointed out it would possibly break existing scripts and sessions because of the changes to the port naming convention. So as a result he didn't want to merge it into his re-adopted (for the lack of a better word) reverse-fork.
I still use the a2jmidid-git
package from AUR, but I still would like to have this fixed in a future release (whoever might tag it). I'll see if I can find some time after the holidays to build the switch to optionally disable the fix for old setups.
Thanks for your comment. I didn't look at the comment as it fixed the issue in my case.
The M-Audio Keystation Mk3 has two ports on it's Alsa device: one for the keys on the keyboard and the second for the control and transport buttons. When running the command
a2jmidid -e
this generates the follow messages:This also gives the following message on the jackd side:
This renders the control and transport buttons unusable unless you manually setup a bridge. Using the -u option does nothing to solve this problem.