On Mon, 17.12.07 18:07, Ritesh Kumar (ritesh at cs.unc.edu) wrote: > > I'd say the intuitiveness depends on whether one's intuition > > says that the client connects to a sink (routing decision > > done at client connection time) or to the pulseaudio daemon > > (routing decision done at stream creation time). The > > asynchronous client API supports the view that client > > connects to the daemon, because the desired sink is supplied > > only when creating a new stream. > > > > I guess you are right... probably I will write a module on the lines of > volume-restore to achieve the effect I need. I seems intuitive to me because > the media player that I use (quodlibet through alsa-pulse), creates a new > stream for every song (I don't know the details but I am guessing that every > media player may need to do this because different songs can have different > sample rates/formats). This causes subsequent songs from the same media > player to move to a different sink if the default sink is changed... which > in my view is non-intuitive :). If you have loaded module-volume-restore than this should not happen, because m-v-r remembers the device/volume for the application using the application name as a key. And as soon as the new stream is created and the application name is recognized the default device/volume for its streams is restored. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4
