Quote:
Originally Posted by davidfor
Where on earth do you get that idea from? Not from the person who maintains the driver, especially as I have already explicitly stated that calibre reads the database on the device.
Calibre does maintain a file on the device. That is used to make it faster to load the books and to help where matching the metadata between the book on the device and in the library does not work for some reason. Removing this file, doesn't really harm anything.
If these books are being loaded by the Kobo Cloud service, and calibre cannot find them, then it means that Kobo Cloud is doing something. And looking at the code, it appears to be faking an SD card and putting the books on that. Luckily for them, it fools nickel into loading books from it, but, doesn't fool nickel enough to for when the device is connected to a PC. If you look at the details of one of the books in nickel, the file name will probably start with "/mnt/sd". If so, that is the reason the books are not being found.
There are ways they could do this without faking the SD card. There are other ways to get nickel to look for new books that would be compatible with the drivers in calibre.
|
You are a lifesaver, I too was under the impression that calibre does not use nickle database and simply creates its own database, and was having issue with books on device not appearing in calibre library.
I use koreader and was just exporting books using calibre without opening nickle to sync the changes, which resulted in the aforementioned issue of mismatching books. Connecting to the pc with nickle and then allowing it is scan for changes solved my issue.