Date: Wed, 2 Mar 2022 09:05:58 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Shane Ambler <FreeBSD@ShaneWare.Biz>, freebsd-multimedia@freebsd.org Subject: Re: New FreeBSD port ALSA to JACK MIDI, a2jmidid Message-ID: <e3c97438-e744-83c6-45a2-377353b4ff0d@selasky.org> In-Reply-To: <c60d14c9-a453-ecf7-3cae-6b74664a7bad@ShaneWare.Biz> References: <a1f43e5a-5d1f-1980-e771-00a0064f74bb@selasky.org> <c60d14c9-a453-ecf7-3cae-6b74664a7bad@ShaneWare.Biz>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/2/22 00:24, Shane Ambler wrote: > > On 12/2/22 2:15 am, Hans Petter Selasky wrote: >> Hi, >> >> My plan for MIDI support in FreeBSD is to use ALSA MIDI in user-space >> via CUSE. It has some pros and cons, but mostly pros. The a2jmidid fills >> the last hole, that JACK applications will automagically see USB MIDI >> devices. >> >> https://www.freshports.org/audio/a2jmidid >> >> Can be used together with latest version of: >> >> https://www.freshports.org/audio/alsa-seq-server > Hi Shane, > So I gather alsa now supports USB midi. Is there some advantage to > passing alsa midi to jack? or is this just to allow both to access the > same device. It is just for compatibility. > My experience is that jack has supported usb midi for some time, I > pathed lmms about six years ago to add support for jack midi so that I > could use a usb midi keyboard as that was the only thing I could get > working. Some applications use JACK, some use ALSA. I would say that ALSA is better delay-wise, but for most applications it doesn't matter that much. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e3c97438-e744-83c6-45a2-377353b4ff0d>