XnView vs. ACDSee: Slow..? (Part 2)

Ask for help and post your question on how to use XnView Classic.

Moderators: helmut, XnTriq, xnview

User avatar
jaqian
Posts: 61
Joined: Sat Feb 14, 2009 10:03 pm
Location: Dublin, Ireland
Contact:

Post by jaqian »

Thanks for that interesting and informative reply, I won't try and quote you here :)

It'll be interesting in a year or two to see how well XnView has developed. I might it a very exsiting product as its the only free application that really atempts to be a descent DAM for amateur photographers. I find Picasa to be a strange experience and its too cutsie to take seriously. Also it has no photo import and rename facility.

Its alos great that we can ask Pierre for bug fixs and updates etc :)
Sony Alpha α100 (Silver)
Linux Mint 7
Blutarsky
Posts: 8
Joined: Wed Mar 10, 2010 6:09 pm
Contact:

Re: XnView vs. ACDSee: Slow..? (Part 2)

Post by Blutarsky »

I am an old ACDsee 3.1 viewer user, unmatched in terms of speed, but I'm currently using Xnview 1,97,3.

About the 30 professionals working on it, well... it may be now, but at that time I' believe the current owner of Acdsystems was coding the dude by himself.

There was a lot of talking about ACDSee speed at that time.... if I'm not wrong, I remember that the author rewrote from scratch jpeg decoding, directly in Assembly [x86] language, not in Visual C/Delphi language as the majority of the developers used to do, mostly using prebuilt image graphics libraries....
mrwul
Posts: 343
Joined: Tue May 25, 2010 7:01 pm

Re: XnView vs. ACDSee: Slow..? (Part 2)

Post by mrwul »

[*]Manipulation of ALL metadata (EXIF, IPTC , XMP and user defined);
[*] user defined mapping of database properties to/from metadata fields, and user control of update timing - immediate (slower, safer), batch (better control), background (faster, less control);
[*]Ability to define the metadata fields that are to be kept in the "database", so that if I need to search all images on EXIF date/time taken, including those on offline or nearline storage, then I would have EXIF data/time taken in the database;
One of the things that ACDSee (Pro version) is doing fairly well: batch set exif/iptc info.
I have shortly glanced on other applications, but think ACDSee is pretty much ahead on this.
Users might even go as far as to merely set a few words under ACDSee's caption - and then batch 'copy' that to to other
ACDSee database fields (keywords, notes, categories, whatever) and also to EXIF/IPTC and even rename files after the caption.
So you more or less know what the file is about when using Explorer (detailmode).
After renaming the files, you can change back the modified date after Exif-shooting date.
I think other apps are either not having all this flexibility, or are fairly limited or it is quite complex.

That having said: ACDSee may be (very) slow when loading a large database.

And also ...
I have experienced ACDSee to be unstable at regular intervals: it may run fine for weeks and then all of a sudden may get you by surprise and produce an "ACDSee has encountered an error and will now close"-error.
This error usually cannot be solved.
Ah well, I admit, it cán be solved: just simply and totally uninstall ACDSee, try and find all relevant ACDSee registry-entries and remove them, also remove ACDSee's folders on C-drive etc.
Then reboot and re-install it again. After that you will be happy to go thru all the different settings again (tools/options), like
where to find the database, what to display under the thumbnails, custom view, etc.
Simply because ACDSee has no tool to save/restore a configuration, so you need to 'set' them again.
With some luck it will be okay again.
Until next time.
That's why you'd better have printscreens of all these settings available for future purposes.
Upgrading is always a drama - I know!

Oh... You won't get much help on issues like above.
Even 30 programmers cannot explain why photos, taken by the same camera, on the same session, all of a sudden show a shooting time of 0.123456 sec instead of 1/nnn, i.e. you may take 3 photos of one subject, 2 photos have 1/nnn the other one
0.123456 s. You may send the photos to ACDSee support, they recognize the issue. That's it.
(I am very sorry to let myself go too much here!)

Anyway.. as for XnView:
** What I am really missing in XnView is a similar kind of 'batch set' info like within ACDSee...

I have disabled ACDSee as my default viewer.

Just my 2 cents...

==
Post Reply