Quote:
Originally Posted by kaufman
I have noticed one thing. It does the "sending metadata to calibre" where it sends all of the metadata a lot more often.
|
I don't see any reason why this would have changed.
There are several things that force CC to resend metadata to calibre
- Clearing cc's data or reinstalling. That causes CC to get a new unique ID, invalidating the old cache.
- Using more than one computer. CC's cache is kept on a per-machine basis. If you change books on one machine then metadata for those books will be sent to calibre when you connect to some other machine. This is true even though the date of the book on the device matches the date of the book in the library, because it does not match the date of the book in the per-machine cache.
- Deleting the cache file. I have no idea where the cache files are stored on macs or if there is something that will "clean up" from time to time. On windows they are stored in \Users\{userName}\AppData\Local\calibre-cache, and to my knowledge are never auto-cleaned.
- Killing calibre with a device connected. If calibre isn't given the opportunity to shut down the connection with CC then the cache will not be written.
For example, assume you use two machines (and I know you do), and that the libraries are synced somehow (don't know if you do this). Further assume that on machine 1 change the template of a custom column, create a new custom column, trigger a metadata backup, or change CC's cover size. Now connect CC. Calibre will send all metadata to CC. Now go to machine 2 and connect CC. CC will send all the metadata to calibre because what it has is not the same as in the cache. However, calibre should send no metadata back to CC because the newly cached copy and the copy in the library already match.
Does any of this match what you are seeing?