FS#31381 - [firefox] no sound in html5 video when using jack with alsa plugin
Attached to Project:
Arch Linux
Opened by Alexander (Slesarev) - Saturday, 01 September 2012, 18:49 GMT
Last edited by Ray Rashif (schivmeister) - Wednesday, 20 February 2013, 20:26 GMT
Opened by Alexander (Slesarev) - Saturday, 01 September 2012, 18:49 GMT
Last edited by Ray Rashif (schivmeister) - Wednesday, 20 February 2013, 20:26 GMT
|
Details
Description:
No sound in html5 video firefox 15.0 Additional info: firefox 15.0 all gstreamer and alsa packages installed and up to date; sound works perfectly everywhere else Seems that firefox is compiled without "--enable-gstreamer" Steps to reproduce: http://www.w3schools.com/html5/tryit.asp?filename=tryhtml5_audio or any html5 video |
This task depends upon
Closed by Ray Rashif (schivmeister)
Wednesday, 20 February 2013, 20:26 GMT
Reason for closing: Upstream
Additional comments about closing: See comments; please re-open if necessary.
Wednesday, 20 February 2013, 20:26 GMT
Reason for closing: Upstream
Additional comments about closing: See comments; please re-open if necessary.
I do not use pulseaudio.
(alsa+pulseaudio)
The jack is "jack2-multilib", it is routed through alsa with an exact copypaste of /etc/asound.conf from archwiki (https://wiki.archlinux.org/index.php/JACK#Playing_nice_with_ALSA)
I just checked whether it works without jack and got sound. Either I failed to actually disable jack when I was submitting this bug or some update partially fixed it. Sorry for confusion anyway.
Still it does not work with jack.
ff was inastalled first, then all plugins, than I tried all 3 variations of jack, deinstalling previous one before trying next, and stopped on just "jack2". Than I got all main alsa and gstreamer plugins and edited asound to get everything other than audio software running just following the precious wiki advices. Than I made full system update for some purpose on the day the bug was reported (ff was updated on that day for sure). That is about it.
I did not notice this bug before.
All other sound related issues may be of some importance to you: first, although it is not jack-dbus, I can't start it from qjackctl, but still jack_control command works - although as I understand it should not be like that. Patchage works fine. Also I have wineasio from AUR, which works fine.
Is there anything else I can add to this?
The important question is, did this setup work previously at any point of time? Or is this the first time you're using it in such a way?
It is most likely not a bug, but a problem with this setup. Either it is not configured correctly and we need to know how, or it does not work this way. I assume you have checked http://jackaudio.org/gstreamer_via_jack ? (provided Firefox does indeed use GStreamer for HTML5)
If qjackctl does not start normal jackd, please file a separate bug report. If you're using dbus, see https://wiki.archlinux.org/index.php/JACK#.22jack2-dbus_and_qjackctl_errors_:.22
Rødseth: Just the .asoundrc is enough to try and reproduce this, nothing else is needed. Use standard jack and jack2, not jack2-multilib or jack2-dbus.
edit: According to one source Firefox uses ALSA directly, and the plug-in should work for HTML5.
I went through all those pages (and surely more), and I absolutely like how jack is now controlled by jack_control (I like command-line interface more than overhauled qjackctl menus), although I still do not understand why it is like that.
The setup should have been working before, as I watched plenty of youtube videos and at least some of them should have been html5, I guess.
edit: According to Paul Davis from JACK, Firefox probably uses an explicit device name, rather than "default" (we make the plug the default in asoundrc).
"visit about:config and create the boolean pref "media.use_cubeb" and set it to false"
edit: removed steps to create the pref; misunderstood 'don't understand' as 'don't know what to do'.
"new backend uses float32 samples rather than sint16, which the JACK plugin may not support"
The jack plugin is not part of jack project (I asked specifically on jack project website), so who supports it? Is there any chance it may be fixed?
Since it's a corner-case issue and we have a workaround as well as some confirmation as to who upstream should really be in this case, I suggest we close this as upstream. Not really worth keeping it open as it'll receive little priority.