[SOLVED] what difference between pulseaudio, alsa and oss?

bateleur · 01-03-2017, 07:02 PM

Quote:

Originally Posted by sithun

thanks a lot. kmix is what i needed.

what action i must write to raise, lower and mute volume?

also i have a lot of special keys on keyboard (for e-mail client, homepage, search and many others) how can i know they code to add string like "key "<code>" <command>"?

Try this:

Code:

key "XF86AudioLowerVolume"      amixer -c 0 set Master 1%-
key "XF86AudioRaiseVolume"      amixer -c 0 set Master 1%+
key "XF86AudioMute"             amixer -c 0 set Master toggle

Of course you can change 1% to another number

sithun · 01-03-2017, 08:47 PM

Quote:

Originally Posted by bateleur

Try this:

Code:

key "XF86AudioLowerVolume"      amixer -c 0 set Master 1%-
key "XF86AudioRaiseVolume"      amixer -c 0 set Master 1%+
key "XF86AudioMute"             amixer -c 0 set Master toggle

Of course you can change 1% to another number

do not work. after i write it buttons start to change volume of line output but i use hdmi output

business_kid · 01-04-2017, 03:37 AM

Sithun, There's a painful but illuminating process called learning that you have yet to go through where sound is concerned. This isn't windows, but linux. The essential difference is that linux makes much fewer presumptions about what hardware it's operating on. You can, and have to configure stuff the way you want it. The X windows system operates under linux, & probably BSD, Solaris & HP-UX as well.

Open alsamixer, set the volumes there. Then run ' alsactl store'. That's what I do. There are man pages, and a little search like

Code:

ls -l /usr/*bin/alsa*

allows you to see what bits of alsa there are. There is also google.

Didier Spaier · 01-04-2017, 05:40 AM

Quote:

Originally Posted by business_kid

Open alsamixer, set the volumes there. Then run ' alsactl store'. That's what I do.

Since Slackware 14.2, you should use 'pavucontrol' instead of 'alsamixer'. And by default (i.e. with /etc/rc.d/rc.pulseaudio non executable) there is one pulseaudio process for each user, and alsactl store is not needed.

The learning process includes forgetting some know-how you learned but which is no more applicable - which makes it even more painful, alas.

sithun · 01-04-2017, 09:22 AM

success. solution is:
"pactl set-sink-volume 0 -1db"
"pactl set-sink-volume 0 +1db"
"pactl set-sink-mute 0 toggle"

thanks a lot for all answers!

business_kid · 01-05-2017, 06:37 AM

Quote:

Originally Posted by Didier Spaier

Since Slackware 14.2, you should use 'pavucontrol' instead of 'alsamixer'. And by default (i.e. with /etc/rc.d/rc.pulseaudio non executable) there is one pulseaudio process for each user, and alsactl store is not needed.

The learning process includes forgetting some know-how you learned but which is no more applicable - which makes it even more painful, alas.

Tell me about it! You saw what a job of work I made over a printer. Sound, Printing, & wifi/networking are areas where linux systems seem to be failing to do one job, and do it well(i.e. Cups, Alsa/PulseAudio, & NetworkManager). The response to a bug report seems to be to add another script or three. Lucky hard disks are so generous these days.

Is there good reference material on pulseaudio anywhere?

Didier Spaier · 01-05-2017, 06:51 AM

Quote:

Originally Posted by business_kid

Tell me about it!
...
Is there good reference material on pulseaudio anywhere?

See this article on SlackDoc.

It was written initially before the release of Slackware 14.2 that now ships pulseaudio, so you may skip the Installation chapter.