Thread: Any way to make scanning for new books quicker?
View Single Post
Old 04-05-2022, 12:37 AM   #17
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 LivresInOz View Post
Overall the problem remains unsolved. Even if I add a SINGLE BOOK, it still takes AGES to scan for new books ("importing content").
Are you saying the import takes a long time? Or it takes a long time until the import starts? My experience with adding a single book to my Clara HD is roughly what @DNSB mentioned. The import take is short enough that I can miss seeing it. This is on a device with 9455 books. How long it takes does not seem to be dependent on how many books are on the device.

But, what @DNSB did not mention is how long it can take until the import screen is displayed. There is a background process that runs shortly after disconnecting looking for changes. It also removes any missing or changed books from the devices database. This can take a couple of minutes on my Clara HD. Sometimes I get surprised as I start using the device without thinking and have the import screen popup. On devices with less books, such as Libra H2O with 1175 books, the scan is quick and not very noticeable.

As to sending the books when using KOReader, that will bypass nickel scanning for books. And if never use nickel, that is fine. But, in that case, you also need to use one of the other connection methods as the KoboTouch and KoboTouchExtended drivers read the database. They do not scan the device for books. Books are only considered to be on the device if they have been imported by nickel. That is not going to change. If you do not use nickel, then you need to use a driver that is compatible with the way the reading app you are using handles books. That would partly solve the issues you are having in the other thread, but, there would probably still be some issues with the way you have the author names. What they are I could not say as I do not use the other drivers and have settled on the simplest way to handle authors.
davidfor is offline   Reply With Quote