Photoshop has more "under the hood" settings than Paris has catacombs, and the majority of its users probably have no idea what most of them do / were intended to do / may have done 32 versions ago. I include myself in that. However one that I WAS aware of, and which came to mind when I saw the responses above (thank you Greyfox, thank you Colorworks) was this one under (in Windows) Edit -> Preferences -> File Handling...; "Maximize PSD and PSB File Compatibility" which has the settings "Ask" (which I believe is the default, but it's a lie because it doesn't ask if you've previously clicked the "Don't Show Again" checkbox), "Always" or "Never".
I suspect that most people will just agree to do it and check the checkbox in the Ask dialog to never show it again.
I, knowing what it does, had it set to "Never" because:
(a) If you are ONLY working in Bridge and PS, you don't need it; and
(b) The file sizes, oh gods, the file sizes.
Let's take, for example, the shot in the example below. The original .orf (Olympus Raw, although it's from the OM-5 which is not yet supported, hint, hint ACDSee programmers) is 16 bit, 5184*3888 pixels, 18.4 Meg in size.
If I open that and do nothing beyond converting it to 8 bit and save it as a .psd. and do NOT select maximum compatibility, I'll still see the image in ACDSee. The size will, quite "normally" for Photoshop, expand hugely to 53.8 Meg. (230128_073156_P1280001_NoModsNoMaxCap8Bit.psd)
If I add a Brightness/Contrast and signature layer and save it again leaving maximum compatibility turned off, it expands slightly to 54.86Meg (230128_073156_P1280001). This is obscenely bloated, but expected for Photoshop. However I cannot see the thumbnail any longer.
HOWEVER! If I save a copy of that file with the adjustment layers but with maximum compatibility enabled, I can see the thumbnail. The price I pay, however, is that "obscenely bloated" becomes "grotesquely disk gobbling" and the size pretty much doubles to a bit over 103 meg (230128_073156_P1280001_MaxCap.psd) because essentially it's doubling up on the data in the image just to show you the thumbnail.
You really don't want to know what happens when Smart Objects are involved, save that Western Digital start rubbing their hands together in glee.
This is not ACDSee's doing. The dialog in question is enlightening:
Turning off Maximize Compatibility may interfere with the ... files IN OTHER APPLICATIONS. In other words, the file representation itself, which would be used by, say, Bridge, is not exposed. For "other applications" (including but not limited to ACDSee) they can only see the thumbnail if the file size is almost doubled to store a copy of the image. The only exception is when the image is nothing more than a copy of the original file resaved without significant modification in .psd format.
So... I could use it and see the .psds but it would come at a heavy disk price, ALTHOUGH a general idea of what is in the image would be right next door in the RAW file that the .psd was created from.
Leave a comment: