Date: Sun, 17 Apr 2022 00:02:54 +0200 From: Florian Walpen <dev@submerge.ch> To: freebsd-multimedia@freebsd.org, Hans Petter Selasky <hps@selasky.org> Cc: Shane Ambler <FreeBSD@shaneware.biz> Subject: Re: New FreeBSD port ALSA to JACK MIDI, a2jmidid Message-ID: <2293974.bDOn7JOVgO@z800> In-Reply-To: <65a7345a-7feb-d553-4953-ea68e8acb022@selasky.org> References: <a1f43e5a-5d1f-1980-e771-00a0064f74bb@selasky.org> <70661440-cbff-b178-ca21-70b10e5f2798@selasky.org> <65a7345a-7feb-d553-4953-ea68e8acb022@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, April 16, 2022 6:31:37 PM CEST Hans Petter Selasky wrote: > On 4/16/22 18:29, Hans Petter Selasky wrote: > > On 3/2/22 12:02, Hans Petter Selasky wrote: > >>> 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? > > > > Ping, did you find to look into this? > > s/find/find time/ > > :-) > > --HPS Oops, sorry about that - I did have a look at the code, but then was cut off the internet for about a week (fiber cable broke in the neighbourhood)... ...and forgot to answer. Contrary to what I had in mind, the MIDI code in JACK is not a separate module, but is driven by the ALSA audio backend. Means we'd have to somehow drive it from the OSS backend in our case. Also the MIDI code is not too well structured nor documented, and it's hard to tell the exact timing requirements to drive it. So instead of creating a lot of work and maintenance Frankenstein'ing the OSS backend with the ALSA MIDI code, I suppose our efforts are better spent on ease of setup for a2jmidid and documentation. Sorry again for the delay. Regards, Flo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2293974.bDOn7JOVgO>