|
Title: Understanding MIDI (especially on Linux) and troubleshooting Post by: falcon74 on December 11, 2019, 05:13:37 AM Having spent an evening trying to get Linuxband to talk to Qsynth using many hit-and-trial methods, decided to do it the hard way, i.e. by understanding the Linux MIDI workings a bit better. Especially, one of those things that confuses people are the abstraction layers, sound managers and how they interact -- especially given that there are multiple alternative ways of achieving the end goal of getting some sound out (or in), but with some side-effects (or not). How JACK, ALSA, PulseAudio, OSS interact, for what all, why is somewhat of a deep rabbit-hole that can take you to Wonderland or Oz or Narnia.
Two things which are really handy are:
Title: Re: Understanding MIDI (especially on Linux) and troubleshooting Post by: folderol on December 11, 2019, 03:09:39 PM Yes it can be quite confusing. However the actual software to hardware interface is ALSA. the rest sits on top. Personally, for my music machine. I never want pulse audio, so I actually delete the server (leaving the client there so that the other apps don't complain - just remain blissfully silent :)
I then either use ALSA directly, or Jack for more complex inter-connections. |