[pulseaudio-discuss] Pulse and audio settings
Hello, With the new version of pulse (1.0-4) I hoped that pulse will somehow take care of my alsa settings which still is not the case. All settings, for example set with alsamixer, are discarded after reboot. Now I wonder what's the best way to define some settings such as mic and PCM level with pulse when pavucontrol does not offer such possibilities? Regards, Robert ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulse and audio settings
2011/10/19 Robert Orzanna : > Hello, > With the new version of pulse (1.0-4) I hoped that pulse will somehow take > care of my alsa settings which still is not the case. > All settings, for example set with alsamixer, are discarded after reboot. Indeed, pulse takes over the volume control. This is by design, so there's no point in hoping a new version of pulse will 'fix' this. PulseAudio saves the volumes and reapplies for new audio streams. Messing with volumes in the lower alsa layer directly is not advised. If you change volumes in pavucontrol or the gnome volume control, you'll see that they are preserved after reboot. > Now I wonder what's the best way to define some settings such as mic and PCM > level with pulse when pavucontrol does not offer such possibilities? Why would you want to adjust these settings outside of pulseaudio and in what way do the sliders in pavucontrol not suffice? Maarten ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulse and audio settings
'Twas brillig, and Robert Orzanna at 19/10/11 02:11 did gyre and gimble: > All settings, for example set with alsamixer, are discarded after reboot. Then your distro is broken. The alsa-utils packages ensures that alsa mixer values are saved on shutdown and restored at boot up. It's saved in asound.state which is kept in /var (nowadays). The latest alsa-utils even ships with systemd units to do this for you. Prior to standardisation with systemd, various different distros handled this differently so you'll have to ask your distro people about it. Ultimately tho', if you fire up an alsa mixer and make some changes, and run: "sudo alsactl store", it should wirte the file /var/lib/alsa/asound.state. Similarly "sudo alsactl restore" should read that state file and apply it. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/ ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulse and audio settings
>Why would you want to adjust these settings outside of pulseaudio and >in what way do the sliders in pavucontrol not suffice? I don't see any way how to adjust PCM which by default is set to 100 by pulseaudio. Hence, I must use alsamixer to reduce the distortions caused by the high PCM. >Then your distro is broken. Following Maartens response it is not, and overwriting alsa settings is a normal behaviour of pulse. >The alsa-utils packages ensures that alsa mixer values are saved on >shutdown and restored at boot up. It's saved in asound.state which is >kept in /var (nowadays). >The latest alsa-utils even ships with systemd units to do this for you. >Prior to standardisation with systemd, various different distros handled >this differently so you'll have to ask your distro people about it. >Ultimately tho', if you fire up an alsa mixer and make some changes, and >run: "sudo alsactl store", it should wirte the file >/var/lib/alsa/asound.state. Similarly "sudo alsactl restore" should read >that state file and apply it. Of course I can run alsactl restore after pulseaudio had completely started. But this is only a workaround since it is obviously not indented to overwrite pulse settings. Regards 2011/10/19 Robert Orzanna > Hello, > > With the new version of pulse (1.0-4) I hoped that pulse will somehow take > care of my alsa settings which still is not the case. > > All settings, for example set with alsamixer, are discarded after reboot. > > Now I wonder what's the best way to define some settings such as mic and > PCM level with pulse when pavucontrol does not offer such possibilities? > > Regards, > > Robert > ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulse and audio settings
'Twas brillig, and Robert Orzanna at 20/10/11 07:05 did gyre and gimble: > I don't see any way how to adjust PCM which by default is set to 100 > by pulseaudio. Hence, I must use alsamixer to reduce the distortions > caused by the high PCM. Oops, I didn't see this bit before due to HTML formatting :( (please try to use plain text if you can). This is a bug in ALSA. If high PCM values result in distortions then ALSA is either misreporting the dB values for the PCM channel or something else is going on. It is correct that PA uses PCM in it's mixer pipeline and this will not be changed. Any bugs need to be fixed properly where they occur, not papered over. You should report this via alsa-devel list. You can tell PA not to use PCM mixer but it requires that you load alsa module-alsa-sink manually and pass in the control= param (see the modules page on the wiki) which can get in the way of hotplug (you'd have to set your card to an input only profile so that you can load the sink manually in default.pa to ensure hotplug still worked). Hope that helps Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/ ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulse and audio settings
'Twas brillig, and Robert Orzanna at 20/10/11 07:05 did gyre and gimble: > Of course I can run alsactl restore after pulseaudio had completely > started. But this is only a workaround since it is obviously not > indented to overwrite pulse settings. I think you misunderstand. You should run this *before* PA starts. You were originally concerned about saving/restoring settings that PA does not alter or touch at all. This is exactly what alsactl store/restre handles. We don't touch any alsa settings that we specifically do not want to set in PA. If there is a specific problem in that PA *is* touching, but you reckon it shouldn't, then please clarify this with some examples (e.g. amixer/alsa-info.sh output and specific element names). Cheers Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/ ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
