'Twas brillig, and Ng Oon-Ee at 15/02/10 09:13 did gyre and gimble: >> Wait no longer! >> >> http://colin.guthr.ie/2010/02/this-is-the-route-to-hell/ >> >> Col >> > A nice read Colin, thanks. > > /me also wonders whether all these 'restore' options need to be made > much more transparent. At the very least with a checkbox somewhere > saying "save per-stream routings". I believe in the simplest use cases > (internal laptop speakers or BT headset on the move, USB headset at > home), it would be advantageous to be able to specify that stream > routings should NOT be saved, but that a device preference should > instead be used. Well I think there are two cases here. With BT headsets we can use something like module-intended-roles to automatically move phone calls to the headset. This works currently and because it's an internal API we can (and do) pass a flag with the stream move call to say "Don't save this". Currently this would mean that the stream-resotre db's device field is not saved, but the future version would be that it would disable the auto-adjustment of the priority list. The ability to not save is something we do not expose in the public API. > Of course, this is up to those who write the code (and I believe the > same thing could be achieved by NOT loading module-stream-restore). I > know that it would cover about 90% of my personal use-case though. With the above in mind re the internal ability to disable saving on a per-move basis may push that 90% up to even higher :) Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
