Thread: Firmware 4.31.19086
View Single Post
Old 02-17-2022, 07:06 PM   #376
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: 47303826
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by PeterT View Post
I wonder if post import the Kobo has to process the books to extract the cover, and that it's that step is preventing the dismount?
The covers are generated as they are needed. Which means that three will be generated for the "My Books" tile after an import. And they might need to be generated for the collection/author tile in the middle on the right. The books at the top should already have the covers unless you replaced a book from calibre or updated the reading status of a book.

The cover generation not being finished would be a likely culprit. I'm not sure whether epubs or kepubs would be worse. For epubs, the RMSDK is used to render the start of the book at then generate the cover from that. For kepubs, the image marked as the cover is extracted and resized.
davidfor is offline   Reply With Quote