09-05-2007, 08:45 AM | #1 |
Bookworm
Posts: 113
Karma: 154
Join Date: Aug 2007
Device: Sony CLIE NX80V, PRS-500
|
TOO SLOW to open "Table of Contents"
I received my Reader last week and in love with it. It is not a perfect device as everybody knows. But with the hacks and other tricks people posted here, it has become a very useful device for reading books.
However, one thing is driving me crazy. It takes forever to open TOC if you have a little bit more items. I have a book with 82-item TOC, and it takes 5 minutes to open the TOC. I wouldn't be so mad if this happens only the first time you open it just as you open a new book on memory card and it takes a bit time to do the formatting. It happens EVERY TIME I open the TOC. It seems no caching is done for TOC. After you open a page from TOC and then press Menu to go back to it, it takes another 5 minutes to display the TOC. And worse, there is no way to get out of the wait (excluding a pin reset). You can only sit there to watch a frozen screen. This is an area I found that a paper book can handle 100 times faster than the reader. Without TOC navigation, reading is not as enjoyable since you can't jump around. <end of rant> |
09-05-2007, 09:45 AM | #2 |
Sir Penguin of Edinburgh
Posts: 12,375
Karma: 23555235
Join Date: Apr 2007
Location: DC Metro area
Device: Shake a stick plus 1
|
That's not normal. What book is it and what format?
|
Advert | |
|
09-05-2007, 10:15 AM | #3 |
Guru
Posts: 714
Karma: 1014039
Join Date: May 2007
Device: Sony PRS-500, Sony PRS-505, Kindle 3, Sony PRS350, iPad 64GB
|
I found that after reading and navigating a lot, my reader became sluggish too. But after the firmware update it became fast again... could be that the data for history, bookmarks and toc makes things slower and slower.
|
09-05-2007, 10:43 AM | #4 |
Bookworm
Posts: 113
Karma: 154
Join Date: Aug 2007
Device: Sony CLIE NX80V, PRS-500
|
It is a book generated from html by html2lrf (part of libprs500).
Operation Guide: 10 item TOC, 8 seconds Book 1 (html2lrf): 19 item TOC, 13 seconds. Book 2 (html2lrf): 33 item TOC, 17 seconds. Book 3 (html2lrf): 56 item TOC, 1 min 6 seconds. Book 4 (html2lrf): 82 item TOC, 4 min 5 seconds. I don't have other books with a long TOC which is not generated by html2lrf. Maybe somebody can post some timing numbers here. |
09-05-2007, 10:51 AM | #5 |
Out of print
Posts: 486
Karma: 1549538
Join Date: Jun 2007
Location: Madrid, Spain
Device: Sony PRS-500 (recycled), Pocketbook Inkpad X Pro
|
I just opened Dr. Thorndyke Omnibus, downloaded from here (formatted by HarryT, I believe): 78 item TOC, 1 or 2 seconds.
|
Advert | |
|
09-05-2007, 10:52 AM | #6 | |
Out of print
Posts: 486
Karma: 1549538
Join Date: Jun 2007
Location: Madrid, Spain
Device: Sony PRS-500 (recycled), Pocketbook Inkpad X Pro
|
Quote:
Sorry, I was trying to edit my previous post. |
|
09-05-2007, 10:53 AM | #7 |
Resident Curmudgeon
Posts: 75,981
Karma: 134368292
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
I have a book I've converted from LIT to LRF using Book Designer that has 47 entries.
It takes me between 1-3 seconds to bring up the ToC. I have the newest firmware and a bunch of hacks installed. |
09-05-2007, 11:08 AM | #8 | |
Bookworm
Posts: 113
Karma: 154
Join Date: Aug 2007
Device: Sony CLIE NX80V, PRS-500
|
Quote:
I may need to play with some of the html2lrf options when I have time to see if it can be improved. |
|
09-05-2007, 11:10 AM | #9 |
Resident Curmudgeon
Posts: 75,981
Karma: 134368292
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Tonight or tomorrow I'll try to convert that LIT to LRF using LIT2LRF and see how the ToC opens.
|
09-05-2007, 11:22 AM | #10 |
Out of print
Posts: 486
Karma: 1549538
Join Date: Jun 2007
Location: Madrid, Spain
Device: Sony PRS-500 (recycled), Pocketbook Inkpad X Pro
|
|
09-05-2007, 11:59 AM | #11 | |
curmudgeon
Posts: 1,487
Karma: 5748190
Join Date: Jun 2006
Location: Redwood City, CA USA
Device: Kobo Aura HD, (ex)nook, (ex)PRS-700, (ex)PRS-500
|
Quote:
The --baen switch strips these extra anchors from the html before (or maybe during) the conversion. Kovid added that switch for me a couple months ago to make the converter useful on Baen content. Xenophon P.S. The 'extra' anchors aren't useless, by the way. If you are reading in a browser in framed mode, they give you a sequential paragraph number as you mouse over text. This is a GOOD THING (tm) when reporting typos and bugs in the book. It's just that it is useless on the Reader. |
|
09-05-2007, 12:06 PM | #12 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
|
09-05-2007, 02:30 PM | #13 |
Connoisseur
Posts: 50
Karma: 374
Join Date: Aug 2007
Location: San Francisco
Device: Sony Reader PRS-500
|
I have noticed that with the emagazines I purchased from Fictionwise (Asimov's SF and Analog) it takes forever to open the Table of Contents using the Table of Contents button in the menu. The first time I tried it I thought the Reader had locked up. Conversely, if you use the table contents links that are included within the document there is no problem.
|
09-06-2007, 05:04 AM | #14 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
Fictionwise use "html2lrf" too. Perhaps it's something that that tool does that makes it slow? All the TOCs I've created with BD open instantly.
|
09-06-2007, 05:36 AM | #15 |
creator of calibre
Posts: 44,380
Karma: 23764838
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
It isn't the number of links in the TOC alone that determined load time. It's the structure of the book as well. What happens when you open the TOC is that the reader software calculates the page number of the destination of every link. If the book has too few page-breaks/too complex a block level structure, this operation takes too long.
This is just bad design on SONY's part, they should really be doing that calculation when a link is activated. LRF files created by html2lrf are much more complex than those created by BookDesigner, since html2lrf supports a whole bunch of block level formatting that BookDesigner doesn't. One technique that may speed up loading of the TOC is to increase the number of page-breaks. You can generate an LRS file with the --lrs option and count the number of Page elements to see how many page breaks the LRF file has. |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
how does the kobo make it's "table of contents" | soup | Kobo Reader | 5 | 08-17-2010 10:24 PM |
"Failed to open the file!" - Fictionwise non-DRM ePubs on Libre | Nakor | Ectaco jetBook | 6 | 03-04-2010 06:37 PM |
ePub-Sony 505 slow table of contents? | dordale | ePub | 7 | 01-31-2009 06:18 AM |
"Friction" is why e-books adoption is slow | Bob Russell | News | 243 | 09-05-2007 02:10 PM |
iRex iLiad reader too slow for "live" websites | Alexander Turcic | iRex | 24 | 06-07-2006 07:58 AM |