On Sunday 20 May 2018 03:25:24 deloptes wrote:
> wofgdkncxojef@... wrote:
> > -_- yea ok i got it. i wasn't using pulseaudio. YASD
> > the mute problem is in the other mixer....
> > So mute doesn't work properly in that mixer and volume short cuts don't
> > work in pulseaudio....
> >
> > under pulseaudio.
> > in kdcop void increaseVoume(int deviceidx)
> > works if i put 0 in the field......
> > so...... it's kmix fault, it doesn't launch the function when a global
> > shortcut is used.....
>
> kmix may not be perfect, but with perfect setup it should work for you as
> well.
>
> I think you should check your setup with pulseaudio and kmix - perhaps
> after installing pulseaudio and rebooting, check master channel and
> shortcut bindings. I don't know if pulseaudio is required for kmix to work
> properly - in my setup it is in use. In theory it shouldn't be required. I
> asked only because I see here Mixer0 and Mixer1. Without PA it would be
> just one Mixer0. The logic however applies the same way.
> If it works in kdcop, it works in kmix (you trigger a kmix function in
> kdcop). It looks like kmix does not capture the event.
>
> Mute,Vol.up/down is toggled by XF86AudioMute, XF86AudioLowerVolume,
> XF86AudioRaiseVolume. The question is if, when you press mute,Vol. up/down,
> those signals are emitted. All of this is pure X. kmix will just react on
> those events.
>
> Start xev, press button and check if you see something like below (but I
> guess you will see them, because you reported that OSD is visible)
>
> KeyRelease event, serial 40, synthetic NO, window 0x5e00001,
>     root 0xd2, subw 0x0, time 240395191, (421,-195), root:(450,672),
>     state 0x10, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume),
> same_screen YES,
>     XLookupString gives 0 bytes:
>     XFilterEvent returns: False
>
> KeyRelease event, serial 40, synthetic NO, window 0x5e00001,
>     root 0xd2, subw 0x0, time 240406943, (421,-195), root:(450,672),
>     state 0x10, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume),
> same_screen YES,
>     XLookupString gives 0 bytes:
>     XFilterEvent returns: False
>
> So then make sure the global keys are configured properly in kmix.
>
> if nothing helps, try stopping kmix remove config files, start kmix and
> check config.
> ~/.trinity/share/config/kmixrc
> ~/.trinity/share/config/kmixctrlrc
>
> regards

i confirm, the buttons work in xev.

i already did that with the config files.

even if i redefine vol-up/down as "a" and "b"
it still doesn't work under pulseaudio.
but it always wotks in the other mixer.

I think that unmute is bugged inside the other mixer
ignore that.

maybe it fails to get the right id for the function
void increaseVoume(int deviceidx)
when the global shortcuts are used.
To be pressice, it suceeds the first time, it fails the rest.
decrese volume seams to work only one, after the increase button was pressed.
The first time you press it, nothing seams to happen.

I can controll the volume just fine with the system tray icon.
lol, i could wright a little script to use dcop to controll the volume with 
the buttons.