[MPlayer-users] Problem forcing mplayer to use "pulse"

[George R Goffe]

Reimar


Thanks for your response.

"doesn't seem to work" means, in this case, produces NO change in behavior. Mplayer STILL routes it's audio to the laptop speakers. YouTube and other sites accessed via Firefox route the output to my head phones. Mplayer used to do this too but on an older Linux platform (systems are consistently Fedora) currently Fedora 23 x86_64.


The head phones are accessed via USB hardware, their manufacturer is Logitech.

Do you need any other information?

Regards,

George...

[David Shochat]

This sounds like a problem I have had repeatedly, trying to build mplayer
in such a way as to include support for Pulse Audio. In my case, until I
figure it out each time, I get no audio at all. I suggest that you bring up
your config.log in a text editor and search for "pulse". You should see a
section beginning with:
============ Checking for pulse ============
At the end of that section you should see:
Result is: yes
But I suspect you will see a "no" here. In my case, the problem was solved
by installing a pulse audio-related development package. For most distros,
you must use a package with "-dev" or "-devel" in its name, since you will
need to compile and link against the library in question. On my Ubuntu
system, I think the missing package was libpulse-dev:amd64. I'm sorry I
didn't write down the one that actually got me past the error the last time
it occurred. Notice that the test code the configure script uses to check
for pulse audio support starts out with:
#include <pulse/pulseaudio.h>
On my system, that include file is provided by the package named above.
-- David

On Thu, Apr 7, 2016 at 1:50 PM, George R Goffe <

Post by George R Goffe
Reimar
Thanks for your response.
"doesn't seem to work" means, in this case, produces NO change in
behavior. Mplayer STILL routes it's audio to the laptop speakers. YouTube
and other sites accessed via Firefox route the output to my head phones.
Mplayer used to do this too but on an older Linux platform (systems are
consistently Fedora) currently Fedora 23 x86_64.
The head phones are accessed via USB hardware, their manufacturer is Logitech.
Do you need any other information?
Regards,
George...
_______________________________________________
MPlayer-users mailing list
https://lists.mplayerhq.hu/mailman/listinfo/mplayer-users

[stan]

On Thu, 7 Apr 2016 16:59:08 -0700

Post by David Shochat
Notice that
the test code the configure script uses to check for pulse audio
support starts out with: #include <pulse/pulseaudio.h>
On my system, that include file is provided by the package named
above. -- David

In Fedora, that file is provided by pulseaudio-libs-devel.

Also, in Fedora, the system defaults to using pulse, since alsa is
automatically routed through pulseaudio. So, anything sent to alsa,
including output from mplayer, will be sent to pulseaudio. However,
that doesn't allow access to the other features of pulseaudio, which
compiling with pulse will do, if the application supports those
features.

You should install the pavucontrol (fedora package name) application,
which is a graphical means of configuring pulseaudio. You can use it to
confirm how you have pulseaudio configured, and make changes.

[Reimar Döffinger]

Post by George R Goffe
Reimar
Thanks for your response.
"doesn't seem to work" means, in this case, produces NO change in behavior. Mplayer STILL routes it's audio to the laptop speakers. YouTube and other sites accessed via Firefox route the output to my head phones. Mplayer used to do this too but on an older Linux platform (systems are consistently Fedora) currently Fedora 23 x86_64.
The head phones are accessed via USB hardware, their manufacturer is Logitech.
Do you need any other information?

MPlayer's output with -v would be a good idea.
If you used "-ao pulse" and you still get sound from the speakers
(as opposed to no sound at all) that SHOULD mean that MPlayer
is using PulseAudio just fine, but it for some reason decides
to send the audio to the speaker.
In that case I'd preliminarily declare this a configuration problem with
PulseAudio, and not a MPlayer issue...