MOBI old, MOBI new, MOBI both

[ElMiko]

I have books in my calibre library in all three of the MOBI formats (new, old, and combo new & old). Is there anyway for me to do isolate via a search which books are in which one of those three formats?

[Gunnerp245]

Check Perferences-->Custom columns. I have a column called Format; whether it is a custom or already part of calibre, I do not remember.

[ElMiko]

Originally Posted by Gunnerp245

Check Perferences-->Custom columns. I have a column called Format; whether it is a custom or already part of calibre, I do not remember.

I have this column, too. Unfortunately, all three MOBI packets display simply as "MOBI". What I am wondering is if there's a way to reliably distinguish them when you have a couple hundred of each type floating around your library.

[BeeTee-Ess]

Hmm...

Just noticed some of my books are ORIGINAL_MOBI, some MOBI, some both.

Don't know the difference.

[Dopedangel]

Originally Posted by BeeTee-Ess

Hmm...

Just noticed some of my books are ORIGINAL_MOBI, some MOBI, some both.

Don't know the difference.

An original_mobi is created when you do a mobi to mobi conversion so that you do not lose your original ebook if something goes wrong in the conversion. Its sort of a safety feature. If you don't like a conversion just select original_mobi right click and you should get an option to go back to the original version.

[theducks]

Originally Posted by BeeTee-Ess

Hmm...

Just noticed some of my books are ORIGINAL_MOBI, some MOBI, some both.

Don't know the difference.

Original_(x) happens when you convert from-to the same format. That way you can (right-click) Restore, when the results of the convert are less than expected

[FizzyWater]

Originally Posted by Dopedangel

An original_mobi is created when you do a mobi to mobi conversion so that you do not lose your original ebook if something goes wrong in the conversion. Its sort of a safety feature. If you don't like a conversion just select original_mobi right click and you should get an option to go back to the original version.

Originally Posted by theducks

Original_(x) happens when you convert from-to the same format. That way you can (right-click) Restore, when the results of the convert are less than expected

You two owe each other a Coke!

[BeeTee-Ess]

Thanks, Dopedangel, theducks.

That's a neat feature.

I have just started doing mobi to mobi conversions to pick up the metadata at the start of my books, another neat feature.

[chaley]

Originally Posted by FizzyWater

You two owe each other a Coke!

What happened to the "jinx".

It has been a lot of years since I heard that phrase.

[theducks]

Originally Posted by FizzyWater

You two owe each other a Coke!

Hey, We try
Can I have some Rum in mine please

[FizzyWater]

Originally Posted by theducks

Hey, We try
Can I have some Rum in mine please

And a twist of lime!

[CWatkinsNash]

Originally Posted by ElMiko

I have this column, too. Unfortunately, all three MOBI packets display simply as "MOBI". What I am wondering is if there's a way to reliably distinguish them when you have a couple hundred of each type floating around your library.

Strange. I don't have a custom column, but I have formats in the tag browser. I've got MOBI (which is what standard azw's turn into on import), HTMLZ (ditto but for Topaz) and AZW3 (which I was assuming was both new and combo).

[DiapDealer]

Originally Posted by CWatkinsNash

Strange. I don't have a custom column, but I have formats in the tag browser. I've got MOBI (which is what standard azw's turn into on import), HTMLZ (ditto but for Topaz) and AZW3 (which I was assuming was both new and combo).

It can get a little hairy. A certain plugin that "fixes" your ebooks when you first import them into calibre is largely responsible for your situation being somewhat more "clear." Without that certain plugin assigning specific file extensions to certain (sub)formats (based on internal file details), you could simply wind up with a library full of AZWs (if you buy most of your ebooks from Amazon). And an AZW could potentially be Topaz, MOBI, or a stand-alone KF8 (depending on what device/app the file was originally downloaded to). For someone that creates/distributes their own ebooks with kindlegen... MOBI could be the regular old MOBI format, or it could be a joint MOBI/KF8 file. Calibre can also produce a stand-alone KF8 file or a joint MOBI/KF8 file that simply appears as MOBI (or it can create an AZW3—which should be a stand-alone KF8).

It's MOBI-Madness up in here!

[unboggling]

Originally Posted by DiapDealer

It's MOBI-Madness up in here!

Sounds like a movie with screaming teenagers…

(a rampaging whale?)

[CWatkinsNash]

Originally Posted by DiapDealer

It can get a little hairy. A certain plugin that "fixes" your ebooks when you first import them into calibre are largely responsible for your situation being somewhat more "clear." Without that certain plugin assigning specific file extensions to certain (sub)formats (based on internal file details), you could simply wind up with a library full of AZWs (if you buy most of your ebooks from Amazon). And an AZW could potentially be Topaz, MOBI, or a stand-alone KF8 (depending on what device/app the file was originally downloaded to). For someone that creates/distributes their own ebooks with kindlegen... MOBI could be the regular old MOBI format, or it could be a joint MOBI/KF8 file. Calibre can also produce a stand-alone KF8 file or a joint MOBI/KF8 file that simply appears as MOBI (or it can create an AZW3—which should be a stand-alone KF8).

It's MOBI-Madness up in here!

I thought about that after I posted, and it's nice to have that clarified. I guess I've been doing things a certain way for so long I momentarily forgot that it's not a stock process.

So tempted to make a joke regarding a big whale. Nice to know unboggling and I ended up in the same place.