Bug #7246

Persistence preset: default sound card

Added by mercedes508 over 3 years ago. Updated over 3 years ago.

Status:ConfirmedStart date:05/14/2014
Priority:LowDue date:
Assignee:-% Done:

0%

Category:Persistence
Target version:-
QA Check: Blueprint:
Feature Branch: Easy:No
Type of work:Code Affected tool:

Description

In order to ease the use of the right audio card, we could have a specific persistence preset, for users not to have to either redo it manually each time they boot, or do too geeky things.


Related issues

Related to Tails - Feature #6873: No sound because of multiple sound card Confirmed 03/07/2014
Blocked by Tails - Bug #7245: Find out the best way to select the default sound card Confirmed

History

#1 Updated by intrigeri over 3 years ago

  • Category set to Persistence

#2 Updated by intrigeri over 3 years ago

  • Status changed from New to Confirmed
  • Parent task deleted (#7245)
  • Type of work changed from Research to Code

#3 Updated by intrigeri over 3 years ago

  • Blocked by Bug #7245: Find out the best way to select the default sound card added

#4 Updated by mercedes508 over 3 years ago

the "Alternative method":
https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture#Alternative_method
in the "Set the default sound card" section of the ArchWiki's page
about ALSA. This has worked reliably, especially combined with
Dotfiles to mae ~/.asoundrc persistent, through the 2 or 3 user
support cases I took care of.

Note that things may differ once we're on Wheezy. IIRC, on Wheezy,
audio output is routed via PulseAudio (that itself speaks to ALSA) by
default, that might pick a different default output device, and ask
ALSA to use that one. I expect 1. we'll see regressions (people who
have their preferred output picked by default in 1.0, but not in 1.1);
2. we won't hear about improvements (people who had their
non-preferred output picked by default in 1.0, but the "right" one in
1.1).

With PulseAudio, I believe one can choose the default output device
graphically. Not sure we install the needed package(s) to do this in
the devel branch. I expect one can make this persistent via
~/.config/pulse/client.conf (not sure if the whole directory can
safely be made persistent, given it contains the PulseAudio cookie;
maybe dotfiles are in order).

I'm not sure if the best way to address this on Wheezy is to configure
PulseAudio, and make its configuration persistent, or to configure
ALSA, and make its configuration persistent.

#5 Updated by sajolida about 3 years ago

  • Related to Feature #6873: No sound because of multiple sound card added

Also available in: Atom PDF