Date: Wed, 02 Mar 2022 11:58:49 +0100 From: Florian Walpen <dev@submerge.ch> To: Hans Petter Selasky <hps@selasky.org> Cc: Shane Ambler <FreeBSD@shaneware.biz>, freebsd-multimedia@freebsd.org Subject: Re: New FreeBSD port ALSA to JACK MIDI, a2jmidid Message-ID: <2239076.sMrx5ctUpN@z800> In-Reply-To: <8c9be8ae-2169-17ad-27cf-be6e286d5bd3@selasky.org> References: <a1f43e5a-5d1f-1980-e771-00a0064f74bb@selasky.org> <c60d14c9-a453-ecf7-3cae-6b74664a7bad@ShaneWare.Biz> <8c9be8ae-2169-17ad-27cf-be6e286d5bd3@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, March 2, 2022 9:09:39 AM CET Hans Petter Selasky wrote: > I'm wondering if it would be better to integrate JACK support straight > into alsa-seq-server . But then there might be some problems starting > and stopping jackd. Or I need to have a thread to wait for jackd to startup. > > --HPS Isn't alsa-seq-server meant to be run as root / RC service? AFAIK JACK clients and server have to be run by the same user. Also it might be a bit confusing with audio/jack optionally depending on audio/alsa-lib and alsa-seq-server on audio/jack... >From a user perspective, having ALSA MIDI support directly in JACK would be preferable, I think. I'll have a look into that, probably next weekend. Did you see any major problems there? Apart from that, I'm not opposed to any solution that works. With jack_umidi, alsa-seq-server and a2jmidid we already have some options, which is nice. Flo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2239076.sMrx5ctUpN>