From: Paul Louden <paulthenerd_at_gmail.com>
Date: Tue, 20 Jan 2009 06:10:33 -0600

alex wallis wrote:
> it just takes time with seek, stop, listen, as you have to waste a few
> seconds after stopping forwrding, to wait for the audio to resume
> playing, and then you have to listen to it for a second or so, and
> then resume going forward.
You still have to listen to it for a second or so when doing audible
seeking. During that second either it's *not* seeking so if you let go
of the key you're really there (in which case it's *exactly* the same as
seek-stop-listen-seek) or it is seeking, and if you are are the right
place, by the time you let go, you won't be.
>
> Plus for those people who don't want to use audible seeking, and I can
> understand that some people might not want to, a setting could always
> be put in place to allow it to be turned on or off.
This doesn't remove the fact that it's a significant added complexity to
the playback code. Features do have effects other than the obvious ones.
It makes the code harder to maintain, and uses binary size and RAM even
for people who won't use the feature.
> Besides, Iriver must have had there reasons for thinking it was a good
> idea, or else why would they have included it in the original firmware?
They could've also simply been wrong.
Received on 2009-01-20