Quote:
Originally Posted by blacksmith1
Dear Hitch,
Thank you so much for your reply
From inside Calibre, I clicked "Click to open" for the books. From there I open metadata.opf using text editor. All metadata for the three books are completely different. Kindly have a look at the attached screenshots
|
Well, that's weird. Presumably, the ASINs are all different, right, and the UUIDs? I'm not 100% sure how K4iOS segregates books, to be honest. As the process (create an AZK, sideload it via iTunes via Sharing, etc.) is such a bastard child, I have no real firm grip on what happens where. What I do know is that iBooks and the K4iOS app have both always had a serious caching issue, and I wonder if this is somehow related in some oddball way, even though it seems to be almost the opposite of that?
OR...I wonder if it's something that Amazon is doing, either overtly or negligiently, having to do with Calibre-built files?
What happens if you make an ePUB, from the MOBI, then build a proper MOBI file with that, using KP3, and then build the AZK? Do you have the same issue? That would be my next step, were I you. That way, you'd be "starting" with a MOBI from Amazon, effectively--NOT an AZW3 from Calibre. I suspect, although can't quite say why, that that's part of the problem.
I'd "convert" the AZW3 files to ePUB, using Calibre, drop the ePUB onto KP3, build the MOBI, and THEN build the AZK file and try it again, for all three, or at least two, to see if the overwriting continues. Amazon is not super-Calibre-friendly, and that could SOMEHOW be playing into it. I'm not even saying it's Calibre, per se; but there could be
something that Amazon's intake just doesn't love about those.
Hitch