MobileRead Forums - View Single Post - Calibre Companion: upcoming calibre 1.13 release forces full metadata send

chaley · 11-27-2013, 06:12 AM

I have changed calibre (and CC) to store metadata in calibre on a per-device basis. This change fixes several small problems. Examples:
- refreshing metadata on device change if the thumbnail size is different on the devices
- refreshing metadata when metadata is changed in calibre then sent to one device, then later another.
- confusion when identical books have different file locations on different devices

Other changes fix a problem that arises if the identical book is somehow added to CC more than once with different file names.

One consequence of the changes: the first CC connect after upgrading will do a complete metadata send to calibre. Keep that in mind when you choose when to upgrade.

If you upgrade calibre to 1.13 but have not upgraded CC to 3.2.5, the next CC upgrade will also force a full metadata send. You can avoid this by ensuring that CC is fully upgraded before connecting to the upgrading calibre.

11-27-2013, 06:12 AM	#1
chaley Grand Sorcerer Posts: 11,755 Karma: 7029857 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	Calibre Companion: upcoming calibre 1.13 release forces full metadata send I have changed calibre (and CC) to store metadata in calibre on a per-device basis. This change fixes several small problems. Examples: - refreshing metadata on device change if the thumbnail size is different on the devices - refreshing metadata when metadata is changed in calibre then sent to one device, then later another. - confusion when identical books have different file locations on different devices Other changes fix a problem that arises if the identical book is somehow added to CC more than once with different file names. One consequence of the changes: the first CC connect after upgrading will do a complete metadata send to calibre. Keep that in mind when you choose when to upgrade. If you upgrade calibre to 1.13 but have not upgraded CC to 3.2.5, the next CC upgrade will also force a full metadata send. You can avoid this by ensuring that CC is fully upgraded before connecting to the upgrading calibre.