[arch-general] Doubts with 'apulse'
Hi, if this queries must go to some other specific places (forums, AUR, etc.) please let me know so I move them there. 1. According to the instructions in [1] «it is necessary to exclude /dev/snd/ from Firefox' sandboxing by adding it to the comma-separated list in about:config → security.sandbox.content.write_path_whitelist», but right now I'm using '$ apulse firefox' without that exclusion and seems to work fine. Maybe that's outdated? (My system is updated.) 2. According to [2] «to allow ALSA programs to play while JACK is running edit (or create) /etc/asound.conf» with this: # convert alsa API over jack API # use it with # % aplay foo.wav # use this as default pcm.!default { type plug slave.pcm "jack" hint.description "Jack Audio" } Now, when I installed apulse, I got this instruction: «For using PulseAudio emulation create a proper .asoundrc: $ cp /usr/share/apulse/asoundrc.sample ~/.asoundrc». Is there any relation or conflict between those two files? BTW, I simply forgot to follow that apulse indication, but it seems to work fine anyway. Maybe it's not necessary? Thanks a lot. [1] https://wiki.archlinux.org/index.php/Firefox#Multimedia_playback [2] https://wiki.archlinux.org/index.php/JACK_Audio_Connection_Kit#Playing_nice_...
Why do you need apulse to get firefox using alsa as backend? Perhaps you can take a look at [3] -- Javier [3] https://wiki.archlinux.org/index.php/Firefox/Tweaks#Get_ALSA_working_back
On 4/7/20, Javier via arch-general
Why do you need apulse to get firefox using alsa as backend? Perhaps you can take a look at [3]
-- Javier
[3] https://wiki.archlinux.org/index.php/Firefox/Tweaks#Get_ALSA_working_back
I tested that, but, sadly, it doesn't work. With that tweak, for instance, can't get sound coming from soundcloud.com or the mic working/capturing sound, both things that work with 'apulse firefox'. Should I do something else beyond/after 'security.sandbox.content.syscall_whitelist' → '16' ? Thanks
I stopped using firefox with apulse a long time ago, since firefox support for ALSA and Jack works, it's just a PITA to use firefox for audio and video. As for ALSA support, it often happens, that you need to close all tabs and sometimes even firefox completely, before you can open a single tab with working audio output, not to mention the Jack support oddities.
On Thu, 9 Apr 2020, at 17:59, Ralf Mardorf via arch-general wrote:
I stopped using firefox with apulse a long time ago, since firefox support for ALSA and Jack works, it's just a PITA to use firefox for audio and video.
As for ALSA support, it often happens, that you need to close all tabs and sometimes even firefox completely, before you can open a single tab with working audio output, not to mention the Jack support oddities.
For me, Firefox + ALSA works well. But I don't use software mixing (dmix, dsnoop) and let Firefox take exclusive control of the ALSA device when it wants to play audio. Perhaps this setup would work better (unless you want/need software mixing of course), and it's worth trying? It should be noted that ALSA is full of quirks and doesn't hide messed up sound hardware/drivers from the client application (while Pulse/Jack do a good job in doing so, by design). To illustrate this, it's enough to browse the mpv bug tracker for ALSA issues. Given that the ALSA sound backend is deprecated anyway, it's no surprise that some things don't work and won't likely ever get fixed.
Op di 7 apr. 2020 04:21 schreef riveravaldez via arch-general < arch-general@archlinux.org>:
Hi, if this queries must go to some other specific places (forums, AUR, etc.) please let me know so I move them there.
2. According to [2] «to allow ALSA programs to play while JACK is running edit (or create) /etc/asound.conf» with this: [...]
Now, when I installed apulse, I got this instruction: «For using PulseAudio emulation create a proper .asoundrc: $ cp /usr/share/apulse/asoundrc.sample ~/.asoundrc».
Note that these are different filenames. /etc/asound.conf is a system-wide setting (settings for all users on the system), whereas ~/asoundrc is only for the current user (~ refers to the homedirectory for the current user). Is there any relation or conflict between those two files?
Usually the file in the homedir (~) will overrule any global (/etc) settings. They may be merged, but the global one could also be ignored if a personal one exists. It might be wise to inspect the contents of /usr/share/apulse/asoundrc.sample as that is an example config. Mvg, Guus
participants (5)
-
Guus Snijders
-
Javier
-
Jens John
-
Ralf Mardorf
-
riveravaldez