Slackware Pulseaudio Html5 player freeze and fast play

Drakeo · 08-14-2015, 06:29 AM

I have for a long time maintained my own pulseaduio in slackware. I know many people frown on it as I do. Some of todays media tools really work well with a complete full install of Pulseaudio with pulseaudio volume control.

Then M$ bought skype and required pulseaudio and even more instead of just compiling against the headers and leaving alsa alone they did the unthinkable took away some options.

Reason I use it is for Multi-media. Simple Screen Recorder works well with pulseaudio and jack. And of course skype. For many of my multimedia stuff pulse can be turned off at times.

As you know Firefox has gone to html5 as default. and firefox 40 you know longer have the switch to flash player as default. it will load flashplayer if that is the only way.

For people with pulseaudio installed you will find that Alien Bobs Chromium and Pats Mozilla-firefox and Seamonky will have issues with html5 player.

During the build they do not enable pulseaudio. the build it self does not link to any bianary. it just calls onto the /include/pulse headers.

This allows it to create the cubeutilities. The alsa-plugins right now do not play well with pulse and html5. I am not sure why.

I suggest if your in the same position as I am. You may want to use the firefox latest repackage script use the latest firefox or rebuild firefox from Pat's script and take out the disable pulseaudio.

And when building Chromium chromium has it's own pulse headers. Hope this helps people that have installed pulseaudio and the alsa-plugins.
hope this helps.

dugan · 08-14-2015, 11:15 PM

I have a -current Pulseaudio installation right now, and both browsers are working fine. I'm using an .asoundrc file from Arch:

Code:

pcm.!default {
  type pulse
  fallback "sysdefault"
  hint {
    show on
    description "Default ALSA Output (currently PulseAudio Sound Server)"
  }
}

ctl.!default {
  type pulse
  fallback "sysdefault"
}

Drakeo · 09-02-2015, 04:25 AM

Yes I am sure it does.

I use something close to that it does the same thing. This not a problem. This is about browsers built without pulseaudio enabled. And the latest alsa-plugin does not work for the html5 player if pulseaudio is installed. If this happens this was the steps I took.
I no longer maintain pulseaudio for a group I did admin for that used slackware. But I did learn pulseaudio and alsa audio very well.over the 8 years up to pulseaudio 6.0. what part of this was about making a default device.
What part of this even calls on making a default device. This has nothing to do with making a default user device.
You have a clue why Pat does not enable pulseaudio during his KDE build. And what this causes to systems that use pulseaudio device for default.
Your pretty smart sit down and compile Pat's kde build with pulseaduio enabled. Trust me you will see the difference.
you may want to comment out M3B till after the build. their is a always a hitch with that one.

Ever wonder why the KDE team has a pulseaudio enabled build.