ti, 2010-01-05 kello 09:44 +0000, Colin Guthrie kirjoitti: > 'Twas brillig, and Tanu Kaskinen at 05/01/10 05:29 did gyre and gimble: > > If I listen to music with headphones and find that the volume is not > > perfect, I turn the music volume up or down. After this the volume is > > perfect. Then I switch the sink port to laptop speakers. After a while I > > plug the headphones back in. Regardless of what I did to the volume > > while using the laptop speakers, I very likely want the music to have > > the same volume that it had last time I used the headphones. > > > > Therefore, module-stream-restore has to save the stream volumes > > per-output. I propose that the database key is changed to have the > > following format: "<rolename>@<devicename>@<portname>". The last > > fragment is optional, since not every device has ports. The rolename is > > what is currently used as the database key; do not interpret the > > proposed key format so that I would propose that streams could be > > classified by role only. > > by "<rolename>" I presume you mean the current stream restore format > which can include a role-based rule or an application-based rule... Yes, that's what I mean. I tried to make that very clear, but communication is hard :) > The above format does not actually allow you to store volumes > per-application which would kinda suck. Why? If <rolename> is exactly the same as the database key format used today, I fail to see how any functionality could be lost. -- Tanu Kaskinen
