peterw;483462 Wrote:
> I think the opposite change is needed; I think Radio should be *less*
> intelligent. AFAICT, the preset logic is something like
> >
Code:
--------------------
> > Try to keep track of which preset buttons have been assigned
>
> When a preset button is pressed briefly
> If there's nothing assigned to that button, do nothing
> Else
> Turn Radio on
> Tell the server (SBS or MySB) which button was pressed
> SBS/MySB tells Radio what to tune, etc.
--------------------
> >
> So if Radio forgets a preset has been assigned, it does nothing. If
> the problem you're seeing is due to Radio somehow forgetting which
> buttons have been assigned, then pushing even more logic to Radio
> won't help; you need to address the underlying cause of forgetfulness
> (and if you fixed that, the current model should work fine).
>
> I think it would be safer to mimic the slim/dumb model of older gear,
> e.g.
>
> >
Code:
--------------------
> > Do NOT try to keep track of which preset buttons have been assigned
>
> When a preset button is pressed briefly
> Tell the server (SBS or MySB) which button was pressed
> SBS/MySB tells Radio to turn on, what to tune, etc.
--------------------
> >
>
> Right now there are two possible causes for forgotten presets: 1)
> SBS/MySB sync messes up what the server thinks the presets should be
> and 2) Radio forgets that a preset has been assigned. Making Radio
> dumber would take the second failure out of the picture. And it would
> result in simpler code -- a bunch of Radio/SqueezePlay code could
> disappear, and the SBS/MySB side would need only a single line of code
> added ("if (! $client->power() ) { $client->execute(['power','1']);
> }").
>
> Next time this happens to you, try turning Radio "off" with a quick
> tap of the power button, and then press the preset. If Radio turns on,
> then the problem is in SBS/MySB. If Radio stays powered off, then
> somehow it has forgotten, and the bug is more likely in Radio's
> firmware (though not necessarily; it's possible that SBS/MySB could be
> giving it bad info somehow).
The radio still needs some kind of user interactive feedback to at
least tell the user that it is aware of a button having been depressed.
This can't sit around waiting several seconds or the user might get
confused about whether the button push was recognized and the user ends
up pushing a button again.
At a minimum the radio firmware needs to have an info balloon pop up on
the client side that says "preset 1 selected" and then further
interactions could be between the radio and the server for what
information about that preset needs to be loaded, further info for the
user (what the name of the playlist being loaded is, station
information, etc).
Currently if I select a preset button for one of my playlists there is
about a five second delay time before the radio does *anything* and
during this time there is no feedback to the user at all; Which can lead
the user to feeling that the radio is broken, is slow, or has failed
them.
--
jmpage2
------------------------------------------------------------------------
jmpage2's Profile: http://forums.slimdevices.com/member.php?userid=41
View this thread: http://forums.slimdevices.com/showthread.php?t=70268
_______________________________________________
Radio mailing list
Radio@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/radio
