> A definition of what is supposed to happen would be a start, any ideas
> where we might find one?
Ok, so here's a list of player prefs which are beying synchronized between
mysb.com and SBS:
activeFont
activeFont_curr
alarms
alarmDefaultVolume
alarmSnoozeSeconds
alarmsEnabled
alarmfadeseconds
alarmTimeoutSeconds
analogOutMode
audioSource
autobrightness
bass
clockSource
digitalOutputEncoding
digitalVolumeControl
disabledirsets
fxloopClock
fxloopSource
idleBrightness
idleFont
idleFont_curr
idlesaver
lineInAlwaysOn
lineInLevel
maxWMArate
minAutoBrightness
offsaver
playingDisplayMode
playtrackalbum
preampVolumeControl
presets
polarityInversion
power
powerOffBrightness
powerOffDac
powerOnBrightness
screensaver
screensavertimeout
scrollMode
sensAutoBrightness
stereoxl
transitionDuration
transitionType
treble
visualMode
volume
webproxy
wordClockOutput
plugin.audioscrobbler.account
plugin.audioscrobbler.accounts
plugin.audioscrobbler.enable_scrobbling
plugin.audioscrobbler.include_radio
(I hope their names make sense...)
When SBS is started/stopped it will request a list of prefs changed on mysb.com
since local values have been changed for the last time, and use whatever is
more recent, setting values on both ends to the same value. It will then start
polling mysb.com values every few minutes (from the code: "# Tell the client to
sync next in 20% of the time since the last change was made") overwriting older
with more recent values on either end.
If you change any of these values SBS will send values and their timestamp to
mysb.com or (or request values from mysb.com) and overwrite the older value
stored on mysb.com.
Andy might give more detail.
--
Michael
_______________________________________________
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/discuss
