[bookport] Re: Bug or feature -- section tracking?

  • From: buhrow@xxxxxxxxxxxxxxxxxxxxx (Brian Buhrow)
  • To: bookport@xxxxxxxxxxxxx
  • Date: Fri, 3 Mar 2006 13:51:08 -0800

        Hello Robert.  I think you hit the nail on the head.  Further
experimentation with V2.1.0.28 reveals that the problem persists until
Bookport reads past the first index boundaryin the new section.  That is,
the reading pointer always points at the chunk of text just read, not the
text that's being read.  That being the case, the firmware works fine, or
seems to.  My problem was that I was jumping to the next section while the
first block of text in the new section was still being spoken.
Thanks for clarifying this issue for me.
-Brian


On Mar 3, 12:38pm, "ROB MEREDITH" wrote:
} Subject: [bookport] Re: Bug or feature -- section tracking?
} Brian:
} 
} We have been unable to reproduce this problem. You might want to try
} resending the original file to a different folder. (We want to keep the
} old book around, in case the new book works.) See if this solves the
} problem.
} 
} Also, have you factored in the lagging pointer problem? I don't think
} the pointer would lag as much as two sections, but I guess it could if
} the sections are close together. We believe we have mostly fixed the
} lagging pointer in this beta, but it requires that you resend the
} problem books.
} 
} Rob Meredith
} 
} >>> buhrow@xxxxxxxxxxxxxxxxxxxxx 02/28/06 09:20PM >>>
}       hello.  I've just taken the plunge and installed Beta
} V2.1.0.28.
} Previously, I was running Release 2.1.0.  I've been playing with some
} text
} files with section markers in them, and I notice one thing that seems a
} bit
} strange.
} 
}       The section markers these texts contain are the ones utilizing
} the 1+4
} keys for backing up to the previus section and the 3+6 keys to move to
} the
} next section.  If I jump to a section of text, using the 3+6 keys, and
} read, and I read beyond the subsequent section boundary, the next time
} I
} press the 3+6 keys to move to the beginning of the next section,
} rather
} than moving me to the beginning of the section following the section
} I'm
} currently reading, the Bookport moves me to the beginning of the
} section
} following the section I previously jumped to.  Let me illustrate with
} an
} example.
} 
}       Suppose I have text containing sections 1, 2, 3, 4 and 5.
} After I begin reading, at the beginning, I press the 3+6 keys to jump
} to
} the beginning of section 2.  Now, I read continuously, eventually
} passing
} through section 2 and into section 3.  At some point in section 3 I
} decide
} that I'm done with that portion of the text, and I press 3+6 to go to
} what
} I think should be the beginning of section 4.  Instead, Bookport moves
} me
} to the beginning of section 3.  Pressing 3+6 again moves me to section
} 4 as
} expected, but I'm surprised it doesn't just move me to the beginning of
} the
} next section relative to my current reading cursor.
}       I'm sure the 2.1 code would have jumped me to section 4 in this
} scenario, and I can reload the 2.1 firmware if people want me to
} verify
} that, but I'm wondering if this is a deliberate design change, or a
} consequence of other changes.
} -thanks
} -Brian
} 
} 
} 
} 
>-- End of excerpt from "ROB MEREDITH"



Other related posts: