Let me Handle this Pat. learn to use the Pavucontroler. I know what your going through and I know "stop" clicking the the little speaker icon and open the pavucontroler server port that processes to the correct device.
This is a learning curve. Have you noticed in kde that the mixer looks different.
You can say all you want but I been using Pulseaudio with slack going on 5 years and trust me Pat did it right. This is a learning curve.
You are a slacker and you will get it it.
Pavucontroler put an launcher in your bar.

sed -i 's/learning curve/plastic wrap/' https://www.linuxquestions.org/quest...ml#post5481631

Seriously, this is one of the reasons why pulseaudio fails so badly, it never ceases to have non-reproducible issues.

Non-reproducible issues implies that the problem is not understood, or isn't an actual problem in general but rather a local configuration issue of some sort.

If a bug report lacks sufficient information for a developer to reproduce the issue, whose fault is that really?

I've had exactly zero bug reports on PulseAudio that I can reproduce here, even trying to set things up wrong to break them. Clearly, either my machines or myself are magic.

3 members found this post helpful.

Not both?

I guess that's possible, too. Something has to be, anyway.

They're non-reproducible because none of them would have happened on a new install.

This one, for example, was caused by a stale ~/.asoundrc file. The other ones obviously were too.

For my part, I'd had an ~/.asoundrc that directed audio to the speakers (it would otherwise have gone to the HDMI). I knew to remove that as part of the update.

3 members found this post helpful.

Problem exist ,i can reproduce.


Put some file in mplayer , and now , do something to force system to a event ... and EVENTS OF SYSTEM NO SOUNDS (KDE)

Some times , if mplayer + YouTube , only one have sound...stop mplayer and YouTube Works, ;=)


But in other attemps i try audacity + mplayer can work at time.

Ardour = unusable , sound SLOWEST.

Pulseaudio , i hate you.

Here, I am using an updated version (current for years), mixing mplayer, amarok and system sounds. Everything works. But, accidentally using kmix seemed to have killed my kde (systray gone)... Reinstalled kde and all is well, kmix disappeared. (As did my Kontact setups, mail server data, and connection to DAV server). I didn't attempt (dare) to touch kmix since then.

Just observations, maybe connected to op woes? Or I just acted up dumb somewhere. I don't know.

Enjoy

Franz

So I figure out the problem, solve it, post that I solve it ... then posting on the thread skyrockets.

ereh sdarwkcab si gnihtemoS

Actually, I did fail to mark the thread as solved, so I guess it's my fault. I normally don't mark a thread solved until after at least a day has gone by, just in case. This time, I'll deviate from that and mark it solved.

By the way, just got ogg123 working. It defaults to pulse for some reason so "ogg123 -d alsa some_file.ogg" gets it to work. Adding a suitable alias statement in my .bashrc makes the fix cleaner. So yup, multi file playback all working fine now. Alsa is all good now. I know pulse is in there somewhere but it's staying out of the way.

OK, i say I`m sorry.

I fixed here , a bad config in media player/plugin point to alsa ..changed to pulse and all works now.


SOLVED!

1 members found this post helpful.

I'm running --Current.

I just started qmmp and played a stream.

Then I started xmms and played a different stream.

Both streams played correctly. I could not follow them, but I played them.

Be careful not to confuse sound hardware when comparing and troubleshooting ALSA with or without pulseaudio.

1. For many years I have disabled the motherboard sound and used a REAL ISA or PCI soundcard - such as Creative Labs Soundblaster. ALSA drivers are very stable for these (at least up to Audigy1). These cards are proper sound processors and do all the output mixing in hardware (and some can do input mixing). For 15+ years I never needed pulse, jack or .asoundrc to listen to multiple sound apps. Apps built with ALSA support "just worked." I disables the motherboard audio and/or blacklisted the unused module.

2. Most motherboard sound hardware (realtek, ac97 etc) are just DAC etc chips - the software driver provides all the functionality. Some of these are buggy, or are incomplete, in both hardware and software. This is why sound servers exist. Remember arts, esd? ugh. pulseaudio was supposed to fix all this.

3. Many sound chips now use snd-intel-hda, which is an interesting example. My current motherboard sound uses it, as do pretty much any Intel chipset. It works well but ONLY supports software mixing. ALSA decided to lump HDMI sound into the same driver. Thus, intel-HDMI and Nvidia-HDMI will use this driver, as does my x99 Haswell-E Wellsburg chipset, and so blacklisting is not an option. I chose a X99 chipset for an i7-5820k without integrated video so that I would have "fewer" issues - no intel-HDMI. If 2+ pieces or hardware use the same driver (analog, GPU HDMI, and maybe intel HDMI), you can run into situations where default CARD0 (hw0,0) is jumping around between analog and HDMI on every boot - or one app uses CARD0, another CARD1, or the device you want is hw0,7... This will need a .asoundrc to fix for the simple reason that apps like Firefox ALWAYS assume CARD0 (hw0,0) and/or either the app or ASLA is too stupid to figure out the correct default. Conversely, for a media PC. you may need an .asoundrc to ensure HDMI is always the default card and to select the correct HDMI device.

In my case, in 14.1 I needed an .asoundrc to get intel-hda to mix outputs from various apps (the SB audigy did this automatically) - and to make sure nothing flips to HDMI. There are lots of LQ posts on this. I also have front and back microphone inputs, so set up input mixing as well - and so Steam and mumble can share a microphone.

In Current (14.2), so far pulseaudio is smart enough to mix outputs and leave HDMI disabled (not connected) for ALSA coded apps. I haven't had a chance yet to give it a full workout.

The moral of this story: it is senseless to just post that app XYZ doesn't work, or multiple audio streams are wonky, with ALSA and/or pulseaudio, without also specifying the hardware and ALSA kernel modules you are using, and the specific sound apps. The advice needed is still hardware and compile option dependent. The way 14.2 and pulseaudio is configured, any proper ALSA aware apps should work just fine. Apps not built for ALSA will not work well. In the case of sox: you need to explicitly specify if you want to use alsa or pulse output, and sometimes the actual audio card since most systems now-a-days might have 2 (analog and HDMI).

4 members found this post helpful.