[bookport] Re: SPOKEN MINUTES TIMER IS EXTREMELY GENEROUS

  • From: "Otto Zamora" <8zamora@xxxxxxxxxxxxx>
  • To: <bookport@xxxxxxxxxxxxx>
  • Date: Wed, 19 Oct 2005 17:57:04 -0400

Hello,

Interesting, thought this might be the case, but until now, I thought it was
just me.

Otto 

-----Original Message-----
From: bookport-bounce@xxxxxxxxxxxxx [mailto:bookport-bounce@xxxxxxxxxxxxx]
On Behalf Of Brian Buhrow
Sent: Wednesday, October 19, 2005 4:15 PM
To: bookport@xxxxxxxxxxxxx
Cc: buhrow@xxxxxxxxxxxxxxxxxxxxx
Subject: [bookport] SPOKEN MINUTES TIMER IS EXTREMELY GENEROUS

        Hello.  I have long suspected that the spoken minutes timer does not
necessarily reflect an accurate picture of how long the Bookport has
actually been running.  Today, I discovered one way to cause the spoken
minutes timer to be completely bamboozled.  I suspect this is not the only
way, but I thought I'd share and see if anyone else notices the spoken
minutes timer's inaccuracies.
        While I don't consider this a serious bug, it does call into
question the total number of hours folks are actually getting out of their
batteries.  At least, I assume that I'm like others, and have been reporting
my battery life as given by the spoken minutes timer.  If that's true,
battery life claims may, to paraphrase the warning on convex mirrors mounted
on side view mirrors of cars, appear to be longer than they actually are.

        Here are the details.

Firmware version: 2.1

How to repeat:

1.  Install an indexed MP3 file on the Bookport.

2.  Select the installed file.

3.  Check the minutes spoken timer and note the number it gives you.

4.  Return to the reading key pad.

5.  Without pressing the read key, press 7 and 9 a few times to jump from
page to page of the MP3 file.  This should cause a few seconds of the
beginning of each page to be played.

6.  Do this 2 or three times, in either direction.

7.  Check the spoken minutes timer again.  Results may very, but in  my
case, I was able to add 100 minutes to the spoken minutes timer with just a
few keystrokes.

Anyone else notice this behavior?

        I suspect the bug lies in the act of skipping through an MP3 file.
Some how, the time offset of the next navigational marker in the MP3 file is
added to the spoken minutes timer, rather than timing the actual running
time of the  synth or the mp3 engine.

-Brian




Other related posts: