Thread: Problem with Calibre Companion
View Single Post
Old 05-13-2013, 03:35 AM   #12
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,465
Karma: 8025600
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by DoctorOhh View Post
When I connected CC it sent the metadata of all 2100 books to calibre as normal, but usually calibre only sends to CC the updated metadata, most of the time a few books. This time it insisted on sending info on all 2100 books.

When that was done I sent a book to my Nexus then disconnected. I immediately connected again this time everything went as expected. CC sent the metadata to calibre and calibre didn't send any metadata back to CC, connection in about a minute and 20 seconds (Great!).

I disconnected then restarted calibre and tried again. This time calibre insisted on sending metadata on about 1700 of the 2100 books. I tried variations of this for an hour and after each calibre restart it insisted on sending metadata back to CC in progressively lower amounts. It has now leveled out at around 600 or so books after each restart of calibre, the number isn't steady.
It might help to describe how calibre decides to send metadata back to the device. It is a multi-layered decision.

Metadata is sent to the device if:
1) The unique ID of the book on the device does not match the unique ID of the book in calibre. This can happen if using multiple libraries and the same book is in more than one library.
2) The last modified date in calibre does not match the last modified date stored with the book on the device. This means that something in the book's metadata has changed. This is the most common case.
3) Calibre has a cover for the book but there is no cover on the device.
4) The size of the cover image generated by calibre does not match the size of the cover on the device. This will happen if you change the cover size option in CC.

My guess is that this has something to do with the last_modified date changing for some reason. One suspect is metadata backup. If you use Library Maintenance to force metadata backup of all books, all last_modified dates will be changed. This will force calibre to send the metadata to the device. The number of books progressively getting smaller is consistent with something like this.

Other actions also change the last_mod date. A large bulk update would do that, even if it doesn't actually change any metadata.
chaley is offline   Reply With Quote