04-14-2012, 02:15 PM | #61 |
Karmaniac
Posts: 2,553
Karma: 11499146
Join Date: Oct 2008
Location: Miami FL
Device: PRS-505, Jetbook, + Mini, +Color, Astak Ez Reader Pro, PPW1, Aura H2O
|
Concerning epubpack,are there ways to increase compression on the ebook, or is there only one standarized compression?
|
04-14-2012, 02:52 PM | #62 | |
Grand Sorcerer
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
|
Quote:
Dale |
|
Advert | |
|
04-15-2012, 11:04 AM | #63 |
Resident Curmudgeon
Posts: 76,007
Karma: 134368292
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
But even if you compress the ePub more, you still won't be able to get more per flow.
|
04-15-2012, 11:55 AM | #64 |
Karmaniac
Posts: 2,553
Karma: 11499146
Join Date: Oct 2008
Location: Miami FL
Device: PRS-505, Jetbook, + Mini, +Color, Astak Ez Reader Pro, PPW1, Aura H2O
|
I understand.
I just wanted to see if it would have any effect on hardware ebook reading devices (perhaps incompatibility?), or if one can make a book even smaller in overall size without downside. Unfortunately the open community concerning the engineering of these devices is very small. It would be nice if someone had some lab tools to test to see if battery life of devices is affected with a highly compressed VS low compressed ebook. There must be some sort of "perfect solution" (for lack of a better word in English) that one can have the best battery life and best compression in one package. The unfortunate part is that power consumption already is so low, and it's very hard to actually measure power consumption on ebook reading. |
04-15-2012, 01:34 PM | #65 |
Resident Curmudgeon
Posts: 76,007
Karma: 134368292
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Why not test it on your computer? Does it take longer to uncompress a ZIP file that has the best compression then a ZIP file that has normal compression? If the answer is yes, then it will also take more processor to do the uncompression and that equates to using more battery.
|
Advert | |
|
04-15-2012, 01:42 PM | #66 |
Karmaniac
Posts: 2,553
Karma: 11499146
Join Date: Oct 2008
Location: Miami FL
Device: PRS-505, Jetbook, + Mini, +Color, Astak Ez Reader Pro, PPW1, Aura H2O
|
Then again, if you reduce the filesize (compression to store), the device needs to activate the external SD card more to read data.(= lower battery life)
Do you think epubs are extracted on the fly (parts of them are extracted while you read/flip pages), or are they extracted completely as you open the book? Last edited by ProDigit; 04-16-2012 at 12:35 AM. |
04-15-2012, 02:00 PM | #67 |
frumious Bandersnatch
Posts: 7,534
Karma: 19000001
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
I believe the ZIP compression, unlike MOBI, is not random-access, that means that the contents must be uncompressed first before processing. It doesn't mean, however, that the full ZIP must be uncompressed, just the particular file (flow, chapter) that is being used, that's why some readers have size restrictions on this. Depending on the available memory, a given device might be able of storing the whole uncompressed book in memory, and so it wouldn't need to access the original epub file anymore, but other devices (or with larger books) may need to access again the compressed file every time you change flow (jump chapters, follow hyperlinks, etc.).
|
04-15-2012, 08:22 PM | #68 | |
Well trained by Cats
Posts: 30,397
Karma: 58055234
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
Quote:
|
|
04-16-2012, 12:36 AM | #69 |
Karmaniac
Posts: 2,553
Karma: 11499146
Join Date: Oct 2008
Location: Miami FL
Device: PRS-505, Jetbook, + Mini, +Color, Astak Ez Reader Pro, PPW1, Aura H2O
|
If what Jellby says is true, then it's actually beneficial to compress html books in chunks closer to 1x 280kB, instead of by chapter (having eg: 40-14 chunks of 7-20kB)
|
04-16-2012, 04:39 AM | #70 |
Addict
Posts: 233
Karma: 256666
Join Date: May 2008
Location: Italy
Device: iLiad, PRS-T3, Kobo GLO HD, Paperwhite 2, PB Ultra, Ony Boox Max
|
For that reason Calibre has an option (in converting to ePub format) to split output xhtml files so they will be of lesser size than specified value (default 260KB)
|
04-16-2012, 06:10 AM | #71 |
frumious Bandersnatch
Posts: 7,534
Karma: 19000001
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
I think ProDigit suggests the opposite: "compressing" several chapters together.
|
04-16-2012, 06:57 AM | #72 |
Wizard
Posts: 4,520
Karma: 121692313
Join Date: Oct 2009
Location: Heemskerk, NL
Device: PRS-T1, Kobo Touch, Kobo Aura
|
I would not be beneficial for speed. Turning pages or go to the next chapter will actually be a lot faster for small chapters than for large chapters.
|
04-16-2012, 07:40 AM | #73 | |
Karmaniac
Posts: 2,553
Karma: 11499146
Join Date: Oct 2008
Location: Miami FL
Device: PRS-505, Jetbook, + Mini, +Color, Astak Ez Reader Pro, PPW1, Aura H2O
|
Quote:
If I understand it right, It may take a little longer for a device to find a chapter in hundreds of chapters,compared to one in tens. Though the loading time of that chapter may be a bit longer, like you say, but the loading time of consecutive chapters within that chunk should be less. Meaning, in case of a large book, read in a linear line, one chapter after the other until the end of the book, is better to have larger files containing more chapters within a (~280kB) html; using in-document reference points to chapters. In case of a bible, concordance, or dictionary, small chapters should be preferred for the sake of faster loading time, and quicker able to find chapters; using the reference point of the beginning of an html page. I'm torn between using the toc.ncx or a selfmade HTML toc. The toc.ncx is fast, easy, but adds some code to the book. The HTML might be a little slower to browse around, can be made to look nicer (eg: in 2 columns, or at least away from the stock TOC layout, or something). But my biggest concern is how an ebook will handle once the TOC.ncx becomes very large (in case of a bible there are over 1100 chapters; a concordance even more,and a dictionary could have as much as 500.000 links (that is, if you want to reference each word)). In these cases it does make sense to start trimming on the toc file; or have very efficient code! |
|
04-16-2012, 07:50 AM | #74 |
frumious Bandersnatch
Posts: 7,534
Karma: 19000001
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
It seems some readers actually "typeset" the whole file before displaying it. That means there would be less reading and uncompressing, but more processing time to get the text available.
|
04-16-2012, 08:19 AM | #75 |
Karmaniac
Posts: 2,553
Karma: 11499146
Join Date: Oct 2008
Location: Miami FL
Device: PRS-505, Jetbook, + Mini, +Color, Astak Ez Reader Pro, PPW1, Aura H2O
|
|
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
new ereader wanted, but cant make up mind which... | loulou123 | Which one should I buy? | 10 | 01-20-2012 02:06 PM |
added epub, now wanted to get metdata | salines | Calibre | 12 | 11-24-2011 01:28 AM |
'Amazon couldn’t make a Kindle [in the U.S.] if it wanted to' | RockdaMan | News | 54 | 08-25-2011 09:39 AM |
Wanted: EPUB testbed e-reader - what's good and cheap | Greg Anos | Which one should I buy? | 4 | 10-11-2010 10:58 AM |
Just suppose | AlexBell | Kindle Formats | 4 | 04-06-2009 07:08 AM |