15 Jun
2016
15 Jun
'16
5:17 p.m.
On 06/15/2016 03:02 PM, hollundertee(a)gmx.net wrote:
On Wed, 15 Jun 2016 12:18:05 +0200
Robin Gareus <robin(a)gareus.org> wrote:
yep. The the actual browser processing is not RT-safe. There's a buffer
(and resampler) in between jack and the sandboxed browser/engine.
So web-audio javascript etc is not using elevated privileges, probably a
good thing, so it can't take down jack :)
On 06/15/2016 10:00 AM, Peter P. wrote:
This is barely believable. My experience so far was that browsers allow
practically no user control over audio whatsoever.
Given that browsers nowadays are audio/video players, game engines and
whatnot this is ridiculuous, but also understandable, since browsers
are supposed to be everything but the kitchen sink (or "die eierlegende
Wollmilchsau" to use this wonderful German term.
Web browsers are the very definition of scope creep.
You can't expect those things to do everything or anything properly. Hi list,
I have been search the archives and the web a bit and it seems
there is no easy way to route html5 audio playback from firefox
through jack on Debian testing.
Wait for another week or three.
Firefox/git features native JACK input & output since last week.
Largely thanks to Damien Zammit.
Cheers!
robin In which ff version is it supposed to be available? I
will try it but I
won't hold my breath.
I don't know.
Firefox (and other mozilla products) uses "cubeb" a Cross platform audio
library for audio i/o. JACK support was merged upstream there:
https://github.com/kinetiknz/cubeb
The --enable-jack configuration option for FF is still sitting here:
https://bugzilla.mozilla.org/show_bug.cgi?id=783733
If you can't wait, just compile your own firefox/iceweasel (apt-get
build-dep... ; apt-get source...)
ciao,
robin