Thread: Touch Kobo touch - what size for cover image?
View Single Post
Old 08-11-2012, 10:18 PM   #7
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Canorka View Post
If you use Calibre I find that loading the book onto the Kobo, unplugging for processing, plugging back in and resending the book once, maybe twice, eliminates the white borders. Doesn't matter what the size of the cover image is. I have around 330 sideloaded books on my Kobo and the covers for all of them fill the entire screen because of this method.
Yes, that should work. I've been looking at the code for the driver, so here is an explanation.

With the current driver, calibre will upload four versions of the cover. They have the following suffixes in the names and sizes:

" - N3_LIBRARY_FULL.parsed" - 355*530
" - N3_LIBRARY_GRID.parsed" - 149*233
" - N3_LIBRARY_LIST.parsed" - 60*90
" - N3_FULL.parsed" - 600*800

But, it only uploads the covers if the Kobo Touch already knows about the book. This means you have to:

- Configure the driver in calibre to upload covers
- Put the book in the device
- Disconnect the device and let it process the book. The device adds the book to its database. With firmware 1.9.17 it also generated the above images in those sizes. With 2.0.0, it only generates the covers the first time it needs to display them.
- Reconnect the device and open calibre
- Use calibre to send the device again

Now we get to a difference between the firmwares. For 1.9.17, the device creates and use all four of the above images. From memory, the "N3_FULL.parsed" version is used when the device sleeps. For 2.0.0, only the first three are create. And it uses "N3_LIBRARY_FULL.parsed" when sleeping. I'm not sure if it is displaying this image centred on the screen, or stretching it. I can't quickly find a cover that would prove it one way or the other the other.

As it happens, I did an experiment with this yesterday. I renamed one of the N3_FULL.parsed images to N3_LIBRARY_FULL.parsed. So, I had a 600*800 image in place of the 355*530 image. The device used this with no problems and it filled the screen when it was sleeping.
davidfor is offline   Reply With Quote