Ok then lets call this another bug to be sure! There must be a maximum file size that the BS can handle right now since resume on startup works fine on smaller mp3 files.
----- Original Message ----- From: "Rod Gowen" <[email protected]> To: "Keith Gillard" <[email protected]>; "Candie Stiles" <[email protected]> Cc: "BookSenseXT" <[email protected]> Sent: Friday, September 04, 2009 10:06 AM Subject: Re: [GW-Booksense] Resume playbakc on startup Hi, I noticed this at once and have always used a bookmark to resume my reading since then. But it is still nice to be able to navigate in the MP3 books when they are one large file. Rod -------------------------------------------------- From: "Keith Gillard" <[email protected]> Sent: Friday, September 04, 2009 8:48 AM To: "Candie Stiles" <[email protected]> Cc: "BookSenseXT" <[email protected]> Subject: Re: [GW-Booksense] Resume playbakc on startup > Ok so that is one user other then myself who has experienced this > issue...Keith > > ----- Original Message ----- > From: "Candie Stiles" <[email protected]> > To: "'Keith Gillard'" <[email protected]> > Sent: Friday, September 04, 2009 9:34 AM > Subject: RE: [GW-Booksense] Resume playbakc on startup > > > Yes I've noticed this as well. After listening to a part of a large mp3 > file, I always place a bookmark where I left off in case this happens. > > -----Original Message----- > From: Keith Gillard [mailto:[email protected]] > Sent: Friday, September 04, 2009 11:32 AM > To: BookSenseXT > Subject: [GW-Booksense] Resume playbakc on startup > > Hi, > 1) I joined 172 files of an audio book into one large 25 hour mp3 file in > the audio books folder. > 2) BS recognizes the lenght of the file and can navigate through the file > with accuracy > 3) After shutting down and restarting the player, I find that Bs does not > resume to the last position stored on shutdown > > I experimented by shutting down and restarting the player severl times. > Each time the unit resumed to a differnt position in the book. > Note that bookmarks are recalled successfully. > > Has anyone seen this issue on large files? > I am hesitent to call this a bug since the original file has been > manipulated. Having said this I wonder if indeed the BS has a bug > regarding > > an accurate resume in a large file like 25 hours. > > Cheers....Keith > >
