Date: Wed, 2 Mar 2022 12:02:26 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Florian Walpen <dev@submerge.ch> Cc: Shane Ambler <FreeBSD@shaneware.biz>, freebsd-multimedia@freebsd.org Subject: Re: New FreeBSD port ALSA to JACK MIDI, a2jmidid Message-ID: <f5d73020-cf19-64f7-3626-f9b72e7713f9@selasky.org> In-Reply-To: <2239076.sMrx5ctUpN@z800> References: <a1f43e5a-5d1f-1980-e771-00a0064f74bb@selasky.org> <c60d14c9-a453-ecf7-3cae-6b74664a7bad@ShaneWare.Biz> <8c9be8ae-2169-17ad-27cf-be6e286d5bd3@selasky.org> <2239076.sMrx5ctUpN@z800>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/2/22 11:58, Florian Walpen wrote: > 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 Hi, > 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. That's correct, and that is an issue! > > Also it might be a bit confusing with audio/jack optionally depending on > audio/alsa-lib and alsa-seq-server on audio/jack... You for sure have a point. > >>>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? Some patches are needed in Jack2, to have OSS AUDIO backend with ALSA MIDI. Help is appreciated! > > 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. > --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f5d73020-cf19-64f7-3626-f9b72e7713f9>