28 Aug
2017
28 Aug
'17
1:40 p.m.
On Mon, Aug 28, 2017 at 06:02:26PM +0200, Thomas Brand wrote:
On Sat, August 26, 2017 16:20, Ralf Mardorf wrote:
I'm using ALSA's jack plugin to route sound from a web browser
to Jack. This works OK, but when using the back arrow in the
browser (i.e. terminating the web page that provided the sound)
the last buffer will be repeated for a time apparently equal
to Jack's timeout. The client that terminates in a not so
clean way in this case is ALSA's Jack plugin. This is easy
to reproduce.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
On Sat, 26 Aug 2017 10:33:42 +0000, John Rigg
wrote:
Hi, i'm sure i missed a lot of this discussion but i wondered if there can
be a single jack client c file that can trigger the issue. Such a client
will allow the specialists to accurately trace the problem with their
tools. I'm sure this will get (more) attention, and if the issue is
understood the chances it gets fixed are good. On 08/25/17 10:10, Ralf Mardorf wrote:
Repeating my own comments, I don't experience
this issue with jack
2
Possibly OT, but I have experienced similar behaviour with jack2.