[bookport] Re: NAVIGATIONAL ODDITY, ANYONE ELSE SEEN THIS?

  • From: "David Bennett" <david382@xxxxxxxxxxxxxx>
  • To: <bookport@xxxxxxxxxxxxx>
  • Date: Wed, 9 Nov 2005 23:24:16 -0600

Yes, I've experienced this also. Still another oddity I've experienced is that the unit will occasionally decide to just stop reading--again, as you said, not in an MP3 file but while using Double Talk on a text-based file. When the unit stops, it's just as if the sleep timer has expired except that no message is given; and besides, I keep the sleep timer disabled most of the time. However, the unit doesn't actually shut off because no beep occurs and battery power does continue to drain. When I press "play," the unit immediately resumes playback.


David Bennett

----- Original Message ----- From: "Brian Buhrow" <buhrow@xxxxxxxxxxxxxxxxxxxxx>
To: <bookport@xxxxxxxxxxxxx>
Cc: <buhrow@xxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, November 08, 2005 10:17 AM
Subject: [bookport] NAVIGATIONAL ODDITY, ANYONE ELSE SEEN THIS?



Hello. I'm running Bookport firmware V2.1.
I've noticed a strange navigational oddity that I can't account for.
Sometimes, but not always, when I start reading a book with the built-in
Doubletalk, i.e. not an MP3, I find that the reading pointer doesn't stay
with me while I'm reading. That is, if I pause, hit a navigational key, or
otherwise interrupt the reading, the Bookport jumps back to the place I
began my reading session. If I use the navigational keys to jump forward,
the reading pointer stays with me through pauses, but as soon as I start
streaming the text again, the reading pointer stays where the streaming
began. the strange thing is that it is inconsistent on the same file. One
time, the reading pointer will track along with the streaming text, another
time it won't. It seems to happen most frequently as one reads further
into the file in question, but where it begins, and when, seem to vary. At
first I thought it was a problem with some particular books I'd loaded into
the Bookport, but now, I've noticed, it seems to strike rather randomly.
This problem does not affect MP3 files, either indexed or unindexed.
Anyone else experienced this behavior? Anyone else been able to more
definitely pin down when it happens and when it doesn't? I'll keep poking,
and see if I can come up with anymore data points, but I thought I'd ask
here to see if anyone else had experienced this behavior.


-thanks
-Brian






Other related posts: