Quote:
Originally Posted by chaley
- 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.
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? |
Yes, I use two machines, and I am syncing my dropbox library via dropbox. Also, when I disconnect, I always use the disconnect button in CC. I never just kill the processes on either device. I am using the most recent version of both programs.
I am seeing things that are similar to what you say I should expect, but not exactly the same.
1) If I change a custom column so that all metadata is impacted, I will get a full metadata transfer from C to CC the next time I connect on both machines.
2) As a subset of this, if I change a few books, they will all resend their metadata on the next connect.
3) If I change the ePub, it will get sent on the next connect, but only once. Not once per machine.
4) Each time I connect on either machine for the first time after connecting on the other machine, I get the "asking calibre what metadata it needs" for about 20 seconds, then I get the "sending metadata to calibre" where it sends all of the metadata for my whole library. This takes over a minute. Then it resends whatever metadata has changed on the other machine.
5) If I then connect on either machine where I haven't connected on the other machine, I get the "asking calibre what metadata it needs" for about 20 seconds. Then it sends whatever metadata has changed on the this machine.
This might not be a new issue. Connections do seem a lot slower these days, but I can't tell for sure when it started. I haven't bought it up because it was just an inconvenience, and I didn't wan't to bother you if everything was still working. I also suspected it might have something to do with my large library