Calibre Companion prerelease 3.2.0c

[chaley]

CC prerelease 3.2.0c has been published and will available soon to people who are members of the CC prerelease program.

This prerelease contains minor changes. As before, it is likely to be what is released to the general public in approximately a week, once we have had some testing time with it running with the next calibre release (1.6).

Prerelease 3.2.0c has the following changes:

• Account for Amazon's Kindle for Android app using a different folder for books, and for it using .prc as its preferred extension.
• [BUG FIX] Fix crash where the folder depth of a CC book folder exceeds approximately 100. Folders structures that deep cannot be scanned.
• [BUG FIX] Reset the grouping drawer after a search so that the book counts are correct.

Prerelease 3.2.0b has the following changes:

• Show a message if the user taps download all in CC's content server interface and calibre is not sufficiently up-to-date.
• [BUG FIX] Reduce a timeout to avoid very rare "Application not responding" errors.
• [BUG FIX] Fix a problem with the new faster wireless device protocol when no books were available.

Note that a full metadata exchange cycle will be required when calibre is updated to 1.6. The cache file format in calibre has changed to reduce the memory footprint.

Prerelease 3.2.0a had the following changes:

• Uses a book cache on the calibre side to avoid sending metadata from CC to calibre during wireless device connections, reducing initial connection time by up to a factor of 10. This change requires calibre 1.5 released 26/9/2013. Note that you will not see the improvement until after a successful connection. CC will continue to work with older versions of calibre, offering no performance improvement.
• Provides a "Download all" menu item in the content server, permitting you to download all the books in a category such as all books by an author or a series. This change requires calibre 1.5 released 26/9/2013. If calibre has not been updated, this function should do nothing.
• [BUG FIX] Don't incorrectly erase the current grouping specification from the title bar.

[DoctorOhh]

Originally Posted by chaley

• [BUG FIX] Reset the grouping drawer after a search so that the book counts are correct.

Verified fixed.

Originally Posted by chaley

Note that a full metadata exchange cycle will be required when calibre is updated to 1.6. The cache file format in calibre has changed to reduce the memory footprint.

Thanks for the heads up.

[chaley]

I think I know the answer, but it is worth asking: is anyone having problems with calibre 1.6 and CC 3.2.0c?

[Sefiriot]

Nothing that looks like a problem on my end here at any rate. Excellent speed of metadata transfer in the latest full cycle (after upgrade to calibre 1.6). I've also noticed that browsing by tags actually seems to work a little bit faster since the 3.2.x release, even when there's over 10k books on device, though possibly it's also the upgrade to Android Jelly Bean that's had this salutary effect.

And best of all I've not had my CC database blow up in my face in weeks, which of course is something I am very happy about.

[PatNY]

Originally Posted by chaley

I think I know the answer, but it is worth asking: is anyone having problems with calibre 1.6 and CC 3.2.0c?

Just tested, and I can't connect as a "Wireless Device" .... the connection gets stuck at "Waiting for calibre"

However, connecting to the content server works just fine. And, thanks for putting in the tweak to adjust compression levels there.

OS: Windows XP on PC; ICS 4.0.4 on Nook HD

--Pat

[chaley]

Originally Posted by PatNY

Just tested, and I can't connect as a "Wireless Device" .... the connection gets stuck at "Waiting for calibre"

However, connecting to the content server works just fine. And, thanks for putting in the tweak to adjust compression levels there.

OS: Windows XP on PC; ICS 4.0.4 on Nook HD

--Pat

Could you send me the two debug logs, one from CC and one from calibre? For the one from CC, please change the email address to cc_debug_log at charles dot haleys dot org or I won't get it until my son forwards it to me.

Also, did you update calibre on Friday, or on or after Saturday?

[PatNY]

Sorry, Charles, it's a false alarm. Everything works fine. Remembering how you said that a full metadata exchange would be needed with 1.6 and also how long it took to first sync right after you added the option of large thumbnails to the book details page in CC, I tried once again and just let it run this time. I timed it too. It took 11 minutes for the first sync, and I have just 373 books on my Nook right now. The good news is that subsequent syncs -- when no books need updating -- take just about 20 seconds.

I was too impatient, once again.

--Pat

[DoctorOhh]

CC connected as a wireless device fine for me. On my 10,000 book library it took about 10 minutes the first time, as you said it would because of 1.6 changes. The second connection took only 21 seconds. I am running on the second 1.6 release of the week.

[chaley]

Originally Posted by PatNY

I was too impatient, once again.

--Pat

Been there and done that.

[chaley]

Originally Posted by DoctorOhh

CC connected as a wireless device fine for me. On my 10,000 book library it took about 10 minutes the first time, as you said it would because of 1.6 changes. The second connection took only 21 seconds. I am running on the second 1.6 release of the week.

Thanks.

Have you had a chance to try the portable version? I am hoping that my changes to how memory is used has fixed the problems you were having. No rush ...

[DoctorOhh]

Originally Posted by chaley

Have you had a chance to try the portable version? I am hoping that my changes to how memory is used has fixed the problems you were having. No rush ...

I just connected it to calibre portable. I'll let you know how it comes out.

[DoctorOhh]

It worked fine with the 32 bit portable version. I had the same stuff loaded up on my machine and it took just below 10 minutes to reestablish the cache. Previously I was never able to fully create the cache without error. Upon connecting it the second time it took 19 seconds to connect.

Whatever you did seems to have worked great.

[chaley]

Originally Posted by DoctorOhh

It worked fine with the 32 bit portable version. I had the same stuff loaded up on my machine and it took just below 10 minutes to reestablish the cache. Previously I was never able to fully create the cache without error. Upon connecting it the second time it took 19 seconds to connect.

Whatever you did seems to have worked great.

Excellent. I was unable to make it fail, so I wasn't sure that I actually fixed it.

Thanks for taking the time to test it!

[jackie_w]

No problems for me, either