Ticket #328 (closed defect: invalid)

Opened 1 month ago

Last modified 1 month ago

Changing default output Device doesn't show any affect.

Reported by: Achim Assigned to: lennart
Priority: normal Milestone:
Component: pavucontrol Severity: normal
Keywords: Cc:

Description

If I change the default output device in pavucontrol it doesn't show any affect.

I would expect that all streams get moved to the new default output, or If I start a new stream that it chooses the new default output.

My goal was to stream all my audio from my laptop to my desktop computer. At the moment I have to move every audio stream manually.

pulseaudio 0.9.10 pavucontrol 0.9.5 pavucontrol 0.9.6 (compiled by myself, with the same behaviour)

Change History

07/26/08 18:01:09 changed 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 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 ;)).

07/26/08 19:19:05 changed by Achim

thanks for your hint coling,

I wasn't able to configure pulseaudio through the configuration files, that you have mentioned. But I was able to do the job with pavchooser and paprefs.

I only have one question or maybe something like an feature request.

How can I inhibit access from other computers in the same Network? Is it possible to do this through the GUI? Something like a quick tip that pops up and says "Hey, This computer wants to use your sound card / pulseaudio". Or Set it static, allow specific clients through IP addresses or DNS Name.

Thanks in advanced Achim

07/26/08 19:47:44 changed by coling

What you suggest is probably a good idea (re asking on the destination machine). But doing so will require some kind of notification and feedback system in pulseaudio daemon which does not exist just yet. I do want to write such a system into it at some point too (which would replace some features of padevchooser), but I've not really discussed these ideas with Lennart yet.

For now there is no GUI way to do it but if you see the Wiki, you can set an IP ACL on the native-tcp protocol module.

07/26/08 20:23:38 changed by Achim

  • status changed from new to closed.
  • resolution set to invalid.

Yes, a little pop-up on the destination machine. For example I want to connect my laptop to my Desktop, then the Desktop will show a little notification if I want to allow this connection.

Thanks for your help, I will leave it at the moment how it is. If I understand it right, I couldn't use paprefs to configure my soundcard / pulseaudio if I change the config.

I am looking forward to your notification system.

So I close this bug as it is actually no bug ;-)

Best wishes Achim