Quote:
Originally Posted by Doitsu
I've already tested this. Mobipocket Creator will indeed compile source files with audio files in them without error messages, however, the resulting .prc file won't work with the Kindle for Android/iOS apps and probably won't work with audio-enabled eInk Kindles either. (I no longer have my K3, so I can't test this hypothesis.)
Do you remember what device/app you tested your client's .prc file with? |
Uh....no? I
think it was KP, Doits, not devices.
(Thinking....)...wasn't the issue that you
couldn't test, on iOS? That the damn thing had to be published, first? You had to point and pray, essentially, other than KP? You tested the files themselves, encoding them, and then simply built the book. You FTP'ed it, and if God was VERY VERY happy with you, it worked on the downslope? Isn't that right?
The problem was, (is) IIRC, that if you built a "regular" mobi, the KF8 version of the book was delivered, when a buyer bought. As KF8 didn't support embedded audio/video, you were SOL. BUT, the KF7 devices didn't support embedded audio/video. So, you had to build a KF7-only mobi, test it on KP (only) and then FTP the file to Amazon. Amazon would do whatever gimmicky crap it is that they do, in the Publishing Workflow, and THEN, the formerly-KF7 file would be delivered to Fire purchasers (now Fire HDX, etc.).
Yup. Having kicked the dust off my gray matter about this, yup, I think that's correct. That's the sitch. The only way to see the embeds, prior to FTP, is on KP.
Hitch