Date: Mon, 28 Feb 2022 11:52:56 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Florian Walpen <dev@submerge.ch>, freebsd-multimedia@freebsd.org Subject: Re: New FreeBSD port ALSA to JACK MIDI, a2jmidid Message-ID: <d053ffca-be60-84c0-f535-533c42341c62@selasky.org> In-Reply-To: <6031446.O1aUxXEVJ6@z800> References: <a1f43e5a-5d1f-1980-e771-00a0064f74bb@selasky.org> <d55c36c9-1151-aea4-4a18-37010b4d3fc8@selasky.org> <586816bd-4332-4a0c-ab4b-b798588514ff@selasky.org> <6031446.O1aUxXEVJ6@z800>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/28/22 00:09, Florian Walpen wrote: > On Sunday, February 27, 2022 9:41:03 PM CET Hans Petter Selasky wrote: >> >> You probably need to use aconnect to loop the events. >> > > If I shortcut the ALSA ports directly from a2jmidi_bridge to j2amidi_bridge > (a2jmidid didn't work), the MIDI data is returned within the same JACK cycle: > > Average latency: 3.92 ms (188.41 frames) > Lowest latency: 0.02 ms (1 frames) > Highest latency: 8.00 ms (384 frames) > Peak MIDI jitter: 7.98 ms (383 frames) > Average MIDI jitter: 1.99 ms (95.13 frames) > > I also tried to use a2jmidi_bridge and j2amidi_bridge on the umidi device, but > that failed. Maybe I did something wrong, the port arguments in aconnect seem > to only go from receiver to sender, as opposed to the description in the > manpage... > Hi, Thanks for testing! I'll try to look into this as time permits. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d053ffca-be60-84c0-f535-533c42341c62>