On Tue, Jun 30 09 at 2:48:45PM +0100, pondlife wrote:
> > If I understood Paul's objections correctly, the power off case was
> > exactly the special case (that's why I mentioned power off in the response
> > to you). Paul suggested, that, if the playlist ended "naturally", i.e.
> > played to the end (and hence playback stopped), and then the player was
> > switched off (manually or automatically through idle timeout), the
> > playback should NOT automatically start the next time the player is
> > switched on. We're talking about this particular case only.
> Ah, gotcha.
> Personally, I would want it to restart automatically in this case - because
> it would be consistent and (particularly) for use as an alarm clock. But I
> might have missed an earlier message giving a case where the opposite
> behaviour would be desirable, feel free to restate such cases for my benefit
I want my player, at poweron, to carry on doing what it was doing at
poweroff. Setting the start screen to WPS is currently close enough - if
I had a playlist going it will resume it, if not it will dump me on the
menu and I can start another playlist.
Having it resume the same playlist again would mean it would start
buffering and playing something that I never want to hear, slowing down
the dircache + tagcache load, which makes it take longer to browse the
db to pick the next playlist.
(and no, setting start screen to 'last screen' doesn't work, because the
poweroff button on ipod triggers 'stop' before poweroff and thus the
last screen is never the WPS).
Yes, it makes sense in the alarm clock case, but I've never used my
player as an alarm clock. :)
Received on 2009-06-30