mirrors/pulseaudio
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pulseaudio/pulseaudio.git synced 2025-11-14 06:59:53 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

alsa-mixer: Add DecibelFix section to the profile set config file format.

Browse source 
This commit only implements the parser, the decibel fix data is not yet used
for anything.
This commit is contained in:
Tanu Kaskinen 2011-03-11 13:34:24 +02:00
parent 4cd90d9e32
commit 4842077a1e
4 changed files with 297 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

61
src/modules/alsa/mixer/profile-sets/default.conf
View file

@ -16,17 +16,27 @@
; Default profile definitions for the ALSA backend of PulseAudio. This
; is used as fallback for all cards that have no special mapping
; assigned. (and should be good enough for the vast majority of
; cards). Use the udev property PULSE_PROFILE_SET to assign a
; different profile set than this one to a device. So what is this
; about? Simply, what we do here is map ALSA devices to how they are
; exposed in PA. We say which ALSA device string to use to open a
; device, which channel mapping to use then, and which mixer path to
; use. This is encoded in a 'mapping'. Multiple of these mappings can
; be bound together in a 'profile' which is then directly exposed in
; the UI as a card profile. Each mapping assigned to a profile will
; result in one sink/source to be created if the profile is selected
; for the card.
; assigned (and should be good enough for the vast majority of
; cards). If you want to assign a different profile set than this one
; to a device, either set the udev property PULSE_PROFILE_SET for the
; card, or use the "profile_set" module argument when loading
; module-alsa-card.
;
; So what is this about? Simply, what we do here is map ALSA devices
; to how they are exposed in PA. We say which ALSA device string to
; use to open a device, which channel mapping to use then, and which
; mixer path to use. This is encoded in a 'mapping'. Multiple of these
; mappings can be bound together in a 'profile' which is then directly
; exposed in the UI as a card profile. Each mapping assigned to a
; profile will result in one sink/source to be created if the profile
; is selected for the card.
;
; Additionally, the path set configuration files can describe the
; decibel values assigned to the steps of the volume elements. This
; can be used to work around situations when the alsa driver doesn't
; provide any decibel information, or when the information is
; incorrect.
; [General]
; auto-profiles = no | yes # Instead of defining all profiles manually, autogenerate
@ -55,6 +65,35 @@
; skip-probe = no | yes # Skip probing for availability? If this is yes then this profile
; # will be assumed as working without probing. Makes initialization
; # a bit faster but only works if the card is really known well.
;
; [DecibelFix element] # Decibel fixes can be used to work around missing or incorrect dB
; # information from alsa. A decibel fix is a table that maps volume steps
; # to decibel values for one volume element. The "element" part in the
; # section title is the name of the volume element.
; #
; # NOTE: This feature is meant just as a help for figuring out the correct
; # decibel values. Pulseaudio is not the correct place to maintain the
; # decibel mappings!
; #
; # If you need this feature, then you should make sure that when you have
; # the correct values figured out, the alsa driver developers get informed
; # too, so that they can fix the driver.
;
; db-values = ... # The option value consists of pairs of step numbers and decibel values.
; # The pairs are separated with whitespace, and steps are separated from
; # the corresponding decibel values with a colon. The values must be in an
; # increasing order. Here's an example of a valid string:
; #
; # "0:-40.50 1:-38.70 3:-33.00 11:0"
; #
; # The lowest step imposes a lower limit for hardware volume and the
; # highest step correspondingly imposes a higher limit. That means that
; # that the mixer will never be set outside those values - the rest of the
; # volume scale is done using software volume.
; #
; # As can be seen in the example, you don't need to specify a dB value for
; # each step. The dB values for skipped steps will be linearly interpolated
; # using the nearest steps that are given.
[General]
auto-profiles = yes