During those two minutes my CPU is running at about 70% and everything is sluggish.ĪCDSee Pro: The speed of building up an image catalog (i.e. In Idimager it takes about two minutes for the queue to hit 0 every time I click on it. In Imatch it takes about one second to load the category. For example I have a category called Arizona that has 1200 images in it. So much so that it hard for me to use IdImager. IdImager: The overall speed of IdImager is much slower than Imatch.
Acdsee 16 vs acdsee 17 pro#
My conclusion is that both IdImager and ACDSee Pro show a lot of potential, but there are a few things that are keeping me from switching. I have been waiting two years for the new version of Imatch that is supposed to address most of my concerns and I am starting to lose patience. I have been testing out competing products to Imatch (IdImager and ACDSee Pro) to see if one of them is better and will be updated on a more regular basis.
Acdsee 16 vs acdsee 17 plus#
Things I dislike about Imatch are the interface, lack of built in version tracking, it does not import EXIF camera data into the database for quick searches, search function are too difficult to use, overall ease of use is not very good plus a few other things I can not think of now. I love the stability, speed, power of categories and scripting abilities (as a last resort) of Imatch. First, I have been using Imatch for the last two years and have always had a love/hate relationship with it. I have been testing out IdImager, ACDSee Pro and Imatch the past few days and I thought I would pass on my conclusion.
0 kommentar(er)
