Quote:
Originally Posted by movieking
I happened to see a 16G card on sale during Boxing Day so I got it, knowing that I could use it in my camera if it didn't work for the reader. I've got about 2 gigs on the card, and the thing just takes forever to load. I've yet to actually get it to load, because I get frustrated with it and go back to the main menu. What kind of loading time should I be looking at? Is it the amount of material, the size of the card, or a combination of both? Would a 2G card with one book load in the same amount of time as a 16G card with the same one book?
|
The scan time when you insert a card into the reader or disconnect it from USB is dependent on the number of books on the card, not the sizes of the books.
From an earlier post I made:
Quote:
With 990 books on the internal memory, a scan takes less than 2 minutes. The performance problems only occur with large numbers of books on memory cards. Adding a memory card with 500 books triggers a scan which takes about 4 minutes. Adding a memory card with 1000 books triggers a scan which takes about 15 minutes. Get up to 2000 books on a card and the scan will take over an hour, 2600 books takes ~1h45m. There is some sloppy programming at work in the Reader software, and it suggests they never tested it with large numbers of books, to have such a strong non-linear behaviour.
This would suggest that the best way to use the reader for a complete library is to have a large number of small memory cards, and divide the library up in a logical way between them. With 500 books per card you are never more than 5 minutes away from a book.
As the time taken for the card scan seems to be related to the number of files, my current test is to combine all books in a series into a single lrf file, with a TOC jumping to the start of each book. The reader shows no problems opening or navigating a 10000+ page book, although the conversion time with txt2lrf increases dramatically as the size of the input file goes up.
|