I have:
Code: Select all
Audio Backend pulse
Moderator: trava90
Code: Select all
Audio Backend pulse
Code: Select all
autospawn = yes
Code: Select all
autospawn = no
Code: Select all
Audio Backend alsa
What would that bring to ALSA-only operation - which is what does not work currently?vannilla wrote:Have you tried using pulseaudio as-is, instead of making it a pipe to ALSA?
Sure, it's worth a try - it's just the kind of tries that I detest: everybody here swears that ALSA should work (and makes a monkey out of me when I insist it doesn't), irrespective of whether support for Pulseaudio is enabled or disabled. Well, if things are really so certain, then there is no need to experiment. Then ALSA should work and I have a misconfiguration in my ALSA.vannilla wrote:If that doesn't work, maybe simply add "-pulseaudio" to the USE flags? It's worth a try.
May - but did I? Besides, my asound.conf is one of the simplest possible: configure spdif to use device 0 of the PCH card, configure the default card to use dmix, configure dmix to use device 0 of the PCH card. Considering that device 0 of the PCH card is a) the system default and b) responsible for both front stereo and 2.1, as well as other output, all seems O.K. - notice the 'CARD=PCH,DEV=0' in the output of 'aplay -L':Your asound.conf is fairly complex, so, yes, you might as well have misconfigured it.
Code: Select all
aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
jack
JACK Audio Connection Kit
pulse
PulseAudio Sound Server
sysdefault:CARD=PCH
HDA Intel PCH, ALC668 Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC668 Analog
Front speakers
surround21:CARD=PCH,DEV=0
HDA Intel PCH, ALC668 Analog
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC668 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC668 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC668 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC668 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC668 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=PCH,DEV=0
HDA Intel PCH, ALC668 Digital
IEC958 (S/PDIF) Digital Audio Output
usbstream:CARD=PCH
HDA Intel PCH
USB Stream Output
hdmi:CARD=NVidia,DEV=0
HDA NVidia, HDMI 0
HDMI Audio Output
hdmi:CARD=NVidia,DEV=1
HDA NVidia, HDMI 1
HDMI Audio Output
hdmi:CARD=NVidia,DEV=2
HDA NVidia, HDMI 2
HDMI Audio Output
usbstream:CARD=NVidia
HDA NVidia
USB Stream Output
Who says that the pulseaudio USE flag might break ALSA-only setups? I suspect that this might be so. Nobody else has come with an explanation as to why this might be true. Everybody swears that his ALSA-only box works fine (with youtube videos in Palemoon) - but all of them have NOT tried to set the pulseaudio flag. So you might have an argument here from the practical side - from a rational point of view alone, there is no compelling reason to disable the pulseaudio flag (I suspect there exists one, but I am not sure: everybody who has managed to get an ALSA-only setup with newer versions of Firefox in the past, has done it by compiling with both --enable-alsa AND --disable-pulseaudio - this IS a compelling reason to ask me to disable the pulseaudio flag, but nobody has come with such an argument yet).if enabling pulseaudio breaks ALSA-only, disable pulseaudio
Who says they might do? And who says they might do so in sound? Sounds a very wild guess to me.Additionally, you added a bunch of custom flags to the ebuild. Who says they didn't break something?
Yes, as I also said previously, the gtk3 USE flag is hard-masked in the overlay - but I guess the mask was forgotten there. Otherwise, why is gtk3 offered as a flag to choose (as you can see in 'equery uses www-client/palemoon')?the use of GTK+3 might be at play, too. deu disabled that flag in the overlay, didn't he/she?
Code: Select all
--enable-alsa --disable-pulseaudio
How could I not?Walter Dnes wrote:Are you familiar with alsamixer, the command-line alsa "control panel"?
Nothing stands out. I'm getting into "clutching-at-straws" territory. A couple of other potential solutions from the Tools ==> Preferences ==> Advanced menusegmentation-fault wrote:How could I not?Walter Dnes wrote:Are you familiar with alsamixer, the command-line alsa "control panel"?
I don't see anything wrong there, do you? See attachment below.
I am running an PulseAudio-enabled build on an ALSA-only box and it works fine here (no problems with both MSE and normal HTML5 audio).segmentation-fault wrote:Everybody swears that his ALSA-only box works fine (with youtube videos in Palemoon) - but all of them have NOT tried to set the pulseaudio flag.
Yes, Pale Moon is not Firefox: b7274fd666e1bb33effc1425701f566bcaa6f7be.segmentation-fault wrote:Palemoon is NOT Firefox
Can you check if YouTube audio works when MSE is disabled (Tools > Preferences > Content > Video > Enable Media Source Extensions (MSE))?segmentation-fault wrote:So sound with ALSA only IS working, after all - but only in podcasts like the above and not in youtube.
That's hardly simple.segmentation-fault wrote: May - but did I? Besides, my asound.conf is one of the simplest possible: configure spdif to use device 0 of the PCH card, configure the default card to use dmix, configure dmix to use device 0 of the PCH card. Considering that device 0 of the PCH card is a) the system default and b) responsible for both front stereo and 2.1, as well as other output, all seems O.K.
Code: Select all
defaults.pcm.!card Generic
defaults.pcm.!device 0
defaults.pcm.!ctl Generic
There is a rational reason and compelling argument to try and disable that flag: to see if things work as expected.segmentation-fault wrote: Who says that the pulseaudio USE flag might break ALSA-only setups? I suspect that this might be so. Nobody else has come with an explanation as to why this might be true. Everybody swears that his ALSA-only box works fine (with youtube videos in Palemoon) - but all of them have NOT tried to set the pulseaudio flag. So you might have an argument here from the practical side - from a rational point of view alone, there is no compelling reason to disable the pulseaudio flag (I suspect there exists one, but I am not sure: everybody who has managed to get an ALSA-only setup with newer versions of Firefox in the past, has done it by compiling with both --enable-alsa AND --disable-pulseaudio - this IS a compelling reason to ask me to disable the pulseaudio flag, but nobody has come with such an argument yet).
Exactly my point: nobody does know, so the only way to be certain is to make a test run without those flags.segmentation-fault wrote: Who says they might do? And who says they might do so in sound? Sounds a very wild guess to me.
Because GTK+3 support is experimental, and people might want to build it for checking how things work out during development.segmentation-fault wrote: Yes, as I also said previously, the gtk3 USE flag is hard-masked in the overlay - but I guess the mask was forgotten there. Otherwise, why is gtk3 offered as a flag to choose (as you can see in 'equery uses www-client/palemoon')?
"Firefox Compatibility" has always been on here. Never changed it.Walter Dnes wrote: A couple of other potential solutions from the Tools ==> Preferences ==> Advanced menu
In the "Compatability" dropdown menu, select "Firefox Compatibility" mode. This has helped with other sound-related problems. Shut down Pale Moon and Re-start.
If that doesn't work, in the "Browsing" section, uncheck "Use hardware acceleration when available". Shut down Pale Moon and Re-start.
This and the link to b7274fd666e1bb33effc1425701f566bcaa6f7be actually make it pretty clear that it must be something on my end, not related to Pulseaudio, or the pulseaudio USE flag.yami_ wrote: I am running an PulseAudio-enabled build on an ALSA-only box and it works fine here (no problems with both MSE and normal HTML5 audio).
BINGO! WOW!yami_ wrote: Can you check if YouTube audio works when MSE is disabled (Tools > Preferences > Content > Video > Enable Media Source Extensions (MSE))?
From what I gather from my experiments, it is the top check box (Enable Media Source Extensions (MSE)), the one that controls MSE altogether, that has to be disabled. Enabling it alone (it is possible!), or with any one of its subordinate check boxes, results in no sound in the video.yami_ wrote:I wonder if only disabling MSE for WebM or MPEG-4 Part 14 would fix the issue. Without MSE some websites might refuse to work, or provide limited services (for example YouTube will only offer 360p and 720p if MSE is disabled).
Interesting. Unfortunately I hove no idea why the audio does not work for you with MSE enabled. In theory this may not be browser-related - there is a chance that the audio decoding fails for some reason (when MSE is enabled YouTube will stream audio and video separately, so an audio-only failure is possible). This is only my speculation and someone with more knowledge of UXP media components will be required to further diagnose this issue.segmentation-fault wrote:From what I gather from my experiments, it is the top check box (Enable Media Source Extensions (MSE)), the one that controls MSE altogether, that has to be disabled. Enabling it alone (it is possible!), or with any one of its subordinate check boxes, results in no sound in the video.
Maybe it tries to stream it to the wrong device and/or wrong card. See a previous post of mine for a list of all cards and their devices, as well as a link to my asound.conf that configures the device 0 of the PCH card.yami_ wrote:(when MSE is enabled YouTube will stream audio and video separately, so an audio-only failure is possible)
Code: Select all
palemoon -vv 1>>palemoon-output.log 2>>palemoon-errors.txt
Probably this:segmentation-fault wrote:Any debug options to start palemoon and see audio debugging messages
Code: Select all
term% palemoon -console