Things to note: alsamixer works, other applications with sound, like mplayer work, i do not have pulseaudio, i tried recompiling MOC, I tried deleting .moc from my home folder
You might try to start MOC via "mocp -SF" to see some additional error messages or even re-emerge it with USE=debug to enable debug mode (mocp -D). You might also check your .asoundrc file (and related to this AlsaDevice in .moc/config).
If I'm not mistaken, lack of mixers shouldn't be a problem. Seems the problem happens in fill_capabilities function, but I am puzzled why there is no detailed error message. When you run "mocp -D" you should afterwards check the log file "mocp_server_log", maybe something more is there.
You will need to set the MOC ALSAMixer1 and/or ALSAMixer2 configuration options to match your system's available mixers. You can try this out using the -O command line option on mocp to set them temporarily (see the manpage for details).
I also stumbled upon the new requirement that a mixer seems to be required now (since r2896).
See also my bugreport on the Debian bug tracker: https://bugs.debian.org/848577
I'm using bluealsa (https://github.com/Arkq/bluez-alsa), which allows using Bluetooth speakers with Alsa.
But in this case there is no mixer available. The volume is controlled on the hardware devices itself.
Can you please relax the mixer requirement again? Because now moc refuses to start, while it was still working fine until r2895.
Just found out that there is indeed a mixer available, but only after pairing with the device.
I'm using this mixer now, and moc is starting.
But I think it would be more comfortable to also allow not having a mixer set (if you don't want to control it with moc), so that you don't have to change the mixer names for different devices that you connect to.
tomaszg
Tue, 2016-11-29 19:08
Permalink
You might try to start MOC
You might try to start MOC via "mocp -SF" to see some additional error messages or even re-emerge it with USE=debug to enable debug mode (mocp -D). You might also check your .asoundrc file (and related to this AlsaDevice in .moc/config).
l0vot
Tue, 2016-11-29 23:45
Permalink
recompiled with debug enabled
My card doesn't have a mixer labeled PCM, previous versions of MOC did not seem to care.
tomaszg
Wed, 2016-11-30 09:41
Permalink
If I'm not mistaken, lack of
If I'm not mistaken, lack of mixers shouldn't be a problem. Seems the problem happens in fill_capabilities function, but I am puzzled why there is no detailed error message. When you run "mocp -D" you should afterwards check the log file "mocp_server_log", maybe something more is there.
jcf
Wed, 2016-11-30 20:55
Permalink
A Valid Mixer Name Is Required
You will need to set the MOC
ALSAMixer1
and/orALSAMixer2
configuration options to match your system's available mixers. You can try this out using the-O
command line option onmocp
to set them temporarily (see the manpage for details).l0vot
Thu, 2016-12-01 00:05
Permalink
thanks, that did it
ALSAMixer1=Headphone
in the config was exactly what i needed
deki
Sun, 2016-12-18 18:48
Permalink
Hi jcf,
Hi jcf,
I also stumbled upon the new requirement that a mixer seems to be required now (since r2896).
See also my bugreport on the Debian bug tracker: https://bugs.debian.org/848577
I'm using bluealsa (https://github.com/Arkq/bluez-alsa), which allows using Bluetooth speakers with Alsa.
But in this case there is no mixer available. The volume is controlled on the hardware devices itself.
Can you please relax the mixer requirement again? Because now moc refuses to start, while it was still working fine until r2895.
Thanks!
deki
Sun, 2016-12-18 19:00
Permalink
Just found out that there is
Just found out that there is indeed a mixer available, but only after pairing with the device.
I'm using this mixer now, and moc is starting.
But I think it would be more comfortable to also allow not having a mixer set (if you don't want to control it with moc), so that you don't have to change the mixer names for different devices that you connect to.