Quoting sander <[EMAIL PROTECTED]>:
> My understanding the way it is now: > > remote volume down pressed->Squeezebox: Volume down > Squeezebox->SlimServer: Is this OK? > SlimServer->Squeezebox: It's OK. > Squeezebox: Volume down It's more like: 1. Squeezebox->SlimServer: irport received 7689807f 2. SlimServer: ok, that's the voldown button, looks like that's been set by the button mapping preferences to be the voldown function for "common" mode. 3. Slimserver->Squeezebox: send mixer command volume down, send graphics update for visual feedback of volume change. However, step 3 could just as easily by any number of alternate commands depending on which functions have been tied to a volume change or various player states: synced players, shadowed players, muted, paused, playing or off, analog or digital volume control, screensaver state. That doesn't even get into what might happen when any number of plugins present or future. Steps 2 and 3 are completely flexible and open source. Jumping from 1 to some specified action (such as a volume change) would be an end run around that flexible and open source. It would either mean closing doors and open up a number of issues with those who would want to have the flexibility back. Rearranging the architecture, while not impossible, probably isn't feasible. Tuning performance and improving the latency of the server is always a goal, but it is also something that is available to anyone at any time to match their means/needs. -kdf _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
