First: You have to excuse my poor English. I do my best - but if that is not enough I urge you to correct me.
-
I have made a few tests. It doesn't matter if it is compressed or uncompressed NEFs. What matters is if the NEFs are developed ore not AND if there are generated RAW previews ore not.
The problem does not occur with JPEG or TIFF images. ACDSee handles them without any annoying re-cataloguing.
Well, I don't really know if cataloguing is the right word to use. But as you all know ACDSee counter (counts from 0-100%) down at the right end of the status bar. When you first enter a folder ACDSee "catalogue" the files. The counter starts to work its way from 0 to 100%. That of cause steals some resources but when done ACDSee can work with full speed again. It's possible to interrupt the "cataloguing" in manage mode by for example opening an image in view mode. And when you return from view mode to the folder in manage mode the "cataloguing" process should continue from where it was.
At least that is the case when I tested this on folders with TIFF or JPEG images.
If you leave the folder in order to visit another or just ending your work in a properly catalogued folder ACDSee don't need to "catalogue" it again. The next time you visit the folder ACDSee just perform a quick comparison of the content to see if there have been any changes. Normally there are no changes and the process is finished in the blink of an eye.
Now to THE PROBLEM that I have with ACDSee:
I work with Nikon NEFs (that is the Nikon raw format) and I use the compressed version of NEF format. It has almost the same detail and quality as the uncompressed NEF format (at least I se no difference - so its good enough for me). And it has the advantage of being much smaller in MB. As I said before this give room for more images on my memory cards and faster import when I get home from a mission.
Marc thought that my problems might have with the compression to do but I have tested both compressed and uncompressed NEFs now and I can't find any difference.
What my test now have convinced me of is that the problem only occurs with developed NEFs.
Developed or undeveloped TIFF and JPEG images have a good behaviour and gives me no headache. And undeveloped NEFs behave good too.
AND NOW to the problem:
When I open a folder with developed NEFs ACDSee always perform the "cataloguing" procedure. Every time! Or maybe it's just the quick check - but extremely slow...
And every time I switch to view mode an back to manage mode a new "cataloguing" procedure starts. And its so heavy that CPU activity peaks at 99% and ACDSee freezes for one or a few seconds. The counter actually seam to freeze too. During the freeze I can't scroll in the browser and I cant open an image to view mode (or anything else). When CPU activity drops ACDSee is on the go again. The counter disappears in a snap, I rarely se it count up to a 100%. I guess the check is done very quickly as soon as there are room for it in the CPU.
If I try to quickly switch between manage mode and view mod back and forth I get stuck every time I return to manage mode. The opening of the image in view mode is no problem. Its when I return to manage mode and the "cataloguing" starts that ACDSee freezes due to the peaking processor.
I have noticed that if I don't let ACDSee generate any RAW previews in the [developed] folder. The problem with CPU peaking and ACDSee freezing gets much less noticeable. I have to force ACDSee quite hard to get a freeze. But the problem with "cataloguing" every time I enter the folder or return to it from view mode (or for that sake edit or develop mode) is still annoyingly present.
So the problem occurs when I work with developed NEFs and gets worse if I let ACDSee create previews in the [developed] folder.
Undeveloped NEF files with no previews work fine. No problems at all. But if I force ACDSee to create RAW previews for these undeveloped NEFs the problem starts. The slow and tiresome repeated re-cataloguing of the folder starts and CPU activity peak and ACDSee freezes...
TIFF and JPEGs work fine too - even if they are developed. But, if I have got it right, the develop of TIFF and JPEG aren't really a develop. It's actually a form of edit. The original is moved and stored in the [Originals] folder. The one in the main folder is a saved copy with the develop settings applied to it. So it's quite different from how the NEFs are handeled.
With NEFs we have the XMP files and the previews that seam to mess things up.
And I guess I have to ad: My NEFs are from Nikon D200.
And finally: I unchecked the "Display embed database information reminder" option with no change in the behaviour of the problem.
Now I don't know what to do.
That's about where I stand now - knowing a little bit more but still not knowing anything that solves the issue.
Posted On October 10, 2009 - 01:24 PM (1 month ago) (
Permalink to this post)
New Content Since Last Visit
No New Content Since Last Visit
If you do, when you return, it goes right back to work making thumbs.
