View Single Post
Old 06-16-2016, 01:13 PM   #6
anacreon
Guru
anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.
 
anacreon's Avatar
 
Posts: 978
Karma: 3475832
Join Date: May 2012
Location: France
Device: Elipsa, Sage, Libra 2
Quote:
Originally Posted by davidfor View Post
In all that, the only thing you have direct control over are the sideloaded books and the fonts. The database is dependent on the number of books on the device plus recommendations and others from Kobo. The dictionaries on how many you install.

The cover images you don't have direct control over. The device either downloads the images (for purchase kepubs and recommendations) or generates them for sideloaded books. For most of the sideloaded books formats, the cover is simply the first page of the book rendered and saved. For sideloaded kepubs, the covers are generated from whatever image in the book is marked as the cover image.

There are three or four sizes generated depending on the firmware version you are looking at. The sizes generated are fixed for the device. The images are generated as needed and stored for later use. You have no control over any part of this. But, you can sideload the images. The KoboTouch driver in calibre has options to generate and sideload all the cover images when the book is sent. The driver should be generating images similar to the firmware.

There are only two ways that I can think of to reduce the size of the images directory:
- Delete the generated images. This is only temporary as they will be regenerated as needed. But, if you keep all your books on the device, you could delete the images for books you have read or are not likely to read in the near future.
- Generate your own images to your own specs. The simplest way to do this would be to run calibre from source and change options used for generating the images. Or you could create a driver subclassed from the KoboTouch driver that does this. Either is easy to do, but I have now idea how much benefit it would be.

You can also do is what rroad suggests: Use an external SD card. The firmware doesn't save generated images for books on the SD card. But, if they are there, they will use them.

Another possibility is to change the internal SD card. People have put 32GB cards in their Glo's so they can store more books. Even a 4GB card will give you a lot more space.
Thank you for your explanations. I tried to delete books with big covers, and transferring them again after severely reducing the weight of the cover, with no success whatever. I suppose I'd have to do a hard reset, but can't be bothered. The SD card wouldn't be a solution since I keep the H2o and the Glo HD synchronized and the first has no slot, and I wouldn't be comfortable opening any device to change the SD card and doing all that needs doing (I read the thread about the process a while ago).

I'll have to do what I do with my iPod: once the 56 GB available (from the very expensive 64 GB I bought) are full, I have to delete some anytime I want to add new music. The beauty of the digital age is nothing is lost - I archive books or music on Calibre or iTunes, unlike those paper books I had to give or throw away, or all the vynil records.

@frostschutz: I do regularly compress the database, with very little impact on its size.
anacreon is offline   Reply With Quote