How to STOP the device communicating with Calibre?

[bandwagon]

I am looking forward for an option which allows me to stop the device communicating with Calibre.

Thing is that sometimes I just connect to upload a few books on to the device but Calibre first starts off with populating a book list from the device which takes 10-11 minutes, in my case. Is there any way to just upload the books through Calibre without it reading the book list on my device?

Thanks!

[theducks]

Originally Posted by bandwagon

I am looking forward for an option which allows me to stop the device communicating with Calibre.

Thing is that sometimes I just connect to upload a few books on to the device but Calibre first starts off with populating a book list from the device which takes 10-11 minutes, in my case. Is there any way to just upload the books through Calibre without it reading the book list on my device?

Thanks!

When you Connect the device it should add anicon to the toolbar. on this icon there is an option to configure the device (driver):
on the form, in addition to the template and formats, there may be an option to read metadata from files.

BTW if you let the search complete, it writes 2 files to the device (both have calibre in their name). these ID the device-Library and what was previously found, speeding up the process by only looking for changes upon the next connect. If you stop the search, use with multiple libraries, or delete the files things need to start over

[eschwartz]

Originally Posted by theducks

If you stop the search, use with multiple libraries, or delete the files things need to start over

Using with multiple libraries does not require starting over.

Why would it anyway???

[theducks]

Originally Posted by eschwartz

Using with multiple libraries does not require starting over.

Why would it anyway???

I think the table of found books (metadata.calibre) has a Library specific id number.

[PeterT]

Would connect as folder avoid the scan?

[eschwartz]

Originally Posted by theducks

I think the table of found books (metadata.calibre) has a Library specific id number.

Regardless, all books are still in the metadata file so it won't need to rescan them.

Also, calibre matches based on title/author matching. Not id. (Much more robust that way.)

In fact,

$ grep -F '"id"' /media/Kindle/metadata.calibre
$ grep -F '"uuid"' /media/Kindle/metadata.calibre
    "uuid" : "<uuid>"
...
...
...
$

Because id isn't even stored there. I am not entirely sure what the UUID does, although I think the Annotations plugin makes use of it. It certainly isn't used for matching.

[kovidgoyal]

matching is done on uuid, if no match based on uuid is found then matching falls back to title + author.

Everytime a device connects, calibre has to *list* all files on the device, but it does not read metadata for them if the metadata is stored on the device already.

Unfortunately, most MTP based devices are very slow at merely listing all files, not much calibre can do about that.

I suggest you let your device connect once, then right click its icon in calibre and configure it, telling it to only scan one or two directories on the device for books. That will greatly speed up connection times (assuming your device is an MTP based device).

[eschwartz]

Originally Posted by kovidgoyal

matching is done on uuid, if no match based on uuid is found then matching falls back to title + author.

Everytime a device connects, calibre has to *list* all files on the device, but it does not read metadata for them if the metadata is stored on the device already.

Unfortunately, most MTP based devices are very slow at merely listing all files, not much calibre can do about that.

I suggest you let your device connect once, then right click its icon in calibre and configure it, telling it to only scan one or two directories on the device for books. That will greatly speed up connection times (assuming your device is an MTP based device).

Makes sense that if the UUID matches the book is (pretty much) guaranteed to be the same. Should've thought of that (I'm pretty sure I knew it somewhere, anyway) -- but anyway, I knew it wasn't ids!

Bad idea to only ever match books when they came from the same library -- or worse, match the wrong books just because they got loaded from a different library with overlapping ids! Which is guaranteed to happen -- ids aren't even supposed to be unique except within one library.

[bandwagon]

Thanks a lot for all the responses.

I suggest you let your device connect once, then right click its icon in calibre and configure it, telling it to only scan one or two directories on the device for books. That will greatly speed up connection times (assuming your device is an MTP based device).

I barely get time to configure the device as it starts to list the items almost instantaneously. The message I get when I click on the device icon is

"Cannot configure device while there are running device jobs."

I'll try this time to wait for it to finish populating the list before I configure it.

[bandwagon]

As per suggestion, I have configured the device and selected just one folder which the device needs to read. It has reduced the communication time considerably. Thanks for all the help!

[speakingtohe]

Originally Posted by bandwagon

As per suggestion, I have configured the device and selected just one folder which the device needs to read. It has reduced the communication time considerably. Thanks for all the help!

Thanks for starting the thread.

Don't know if I will do this, but good to know.

Helen

[bandwagon]

Thanks for starting the thread.

Don't know if I will do this, but good to know.

Helen

Thanks, Helen. This is really helpful if one wants to upload a book or two in a hurry and also don't want any risk of device malfunctioning by just unplugging it without it having finished it's tasks.