On 30.12.2017 13:55, Tanu Kaskinen wrote: > On Sat, 2017-12-30 at 13:09 +0100, Georg Chini wrote: >> On 29.12.2017 21:28, Georg Chini wrote: >>> On 29.12.2017 13:49, Tanu Kaskinen wrote: >>>> There's still the problem that once the HDMI sink is available again, >>>> streams won't be moved there automatically (unless module-switch-on- >>>> connect is loaded), but I think that's a lesser problem than keeping >>>> streams connected to a silent sink. >> >> >> For what it's worth, I think the real fix is to make it more explicit >> when streams are "default-routed" and when their routing has been >> overridden by the user. Then all default-routed streams could be easily >> moved whenever the default sink changes. I think this needs UI changes >> as well, because otherwise it will be confusing. UIs that provide per- >> stream routing control should show when a stream has been manually >> routed, and it should be possible to return the stream to the "default- >> routed" group. I don't expect to work on this any time soon, so this >> only slightly relevant to the present discussion. >> I still think that it would be sufficient to consider all streams on the default sink as default-routed. Even if a user moves a stream manually to the default sink, the purpose is probably that the stream plays on the default sink and not that it plays on that specific hardware. From a user perspective I would not expect that some streams stay on the old sink when the default changes, on the contrary I would find it rather annoying. Anything not playing on the default sink is user-routed. This avoids the necessity of a per stream extra flag and simplifies the stream move logic. But as you said above it's not relevant at the moment.
