[pulseaudio-tickets] [PulseAudio] #328: Changing default output Device doesn't show any affect.

[PulseAudio]

#328: Changing default output Device doesn't show any affect.
--------------------------+-------------------------------------------------
  Reporter:  Achim        |       Owner:  lennart
      Type:  defect       |      Status:  new    
  Priority:  normal       |   Milestone:         
 Component:  pavucontrol  |    Severity:  normal 
Resolution:               |    Keywords:         
--------------------------+-------------------------------------------------
Comment (by coling):

 I don't think this is a bug really.

 The defined behaviour when setting a default is to only affect '''new'''
 streams.. In theory an option could be added to "move all streams to the
 default device" or similar, but there are probably legitimate cases when
 you don't want that.

 Also as module-volume-restore is active, it will restore an individual
 stream to the last sink it used... such streams are not considered new
 (hence my emphasis in the paragraph above), as they have been seen before.

 Simply removing the volume restore table and restarting pulse should mean
 that any stream that connects to pulse will be routed to the default
 device.

 Now, a couple of points:

 If you want all streams to go directly to your desktop, you can avoid a
 tunnel and just connect directly to the desktop's pulse daemon. You can do
 this via the PULSE_SERVER env var, x11 property or in the
 ~/.pulse/client.conf file (although note that in 0.9.10, client.conf takes
 second fiddle to the x11 props... I fixed this for 0.9.11 tho'). If you
 want a patch you can just grab it [http://svn.mandriva.com/cgi-
 bin/viewvc.cgi/packages/cooker/pulseaudio/current/SOURCES/pulseaudio-0.9.9
 -xprops-before-conf.patch?view=markup here].

 Secondly, there may be a bug in PA 0.9.10 that does not remember the
 default device selection over a reboot... if that's the case for you you
 can move the gconf module higher up in the default.pa... Debian fixed this
 first, and I just copied... Lennart, you may want to double check this
 yourself as I'm not sure it was fixed in 0.9.11 (blame sjoerd for not
 poking you about it if this is the case ;)).

-- 
Ticket URL: <http://pulseaudio.org/ticket/328#comment:1>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server