[pulseaudio-discuss] PA is very silent; doen't use the max hardware volume

[Alexander E. Patrakov]

2014/1/23 Nikos Chantziaras <realnc at gmail.com>:
> On 23/01/14 18:25, Alexander E. Patrakov wrote:
>>
>> 2014/1/23 Nikos Chantziaras <realnc at gmail.com>:
>>>
>>> On 23/01/14 17:42, Alexander E. Patrakov wrote:
>>>>
>>>>
>>>> 2014/1/23 Nikos Chantziaras <realnc at gmail.com>:
>>>>>
>>>>>
>>>>> It seems that PA refuses to use the maximum hardware volume of my sound
>>>>> card
>>>>> (Asus Xonar D1). As a result, the audio is very silent. I have the
>>>>> volume
>>>>> sliders in pavucontrol set to 100%, but PA only uses 40% (-20db) on the
>>>>> hardware mixer. [...]
>>>>
>>>>
>>>>
>>>> Which control are you raising? Maybe it is not in the default mixer
>>>> path known to pulseaudio?
>>>
>>>
>>>
>>> The control is named "Master Front".
>>
>>
>> Then it is indeed not in the default mixer path [...]
>>
>>
>> In order to work around it, you can try editing
>> /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf and other
>> conf files in that directory that are relevant to outputs. Find the
>> [Front] section in each file and duplicate it to say [Master Front] in
>> the header. Please report if this helps.
>
>
> I've now duplicated all occurrences of [Element Front] (grep -r "Front\]")
> with [Element Master Front]. I then did "pulseaudio -k" (I assume this
> reloads the paths). I verified that a new process was spawned (new PID of
> the pulseaudio daemon.)
>
> It doesn't help. The hardware mixer control is still not touched by PA.

Then we need the following to debug this.

1. pulseaudio -k ; pulseaudio -vv 2>&1 | tee pulseaudio.log

If it says "already running", just try again. It is a race vs
autospawn that you have to win to get a usable log.

2. The output of alsa-info.sh. The script is at
http://www.alsa-project.org/alsa-info.sh

-- 
Alexander E. Patrakov