hi
i would like to know when will be available a patch to correct some bugs ?
thanks
ps i'm undecided about upgrading

hi
i would like to know when will be available a patch to correct some bugs ?
thanks
ps i'm undecided about upgrading
It's pretty unusual for ACDSee to pre-announce patches. So far, there have been only a couple of fairly minor bugs reported, so I kind of doubt they'd be trying to put out anything imminently. There have been a fair number enhancement requests, of course, but those typically don't get addressed in patches.
Marc, I must disagree. There is at least one major bug relating to selection of images for processing that a few have reported to tech support and upon which they are actively working. I hope that there will be a patch for this, and any other bugs, very soon.
Well, I guess what's a minor bug to one may be a major bug to another, it depends on the overall impact it has on individual users.
Personally I find having to re-sort 3 times after saving each a new image version a complete pain. If I'm careful, and do things in a particular order, it only adds three keystrokes (M End F), but having to repeat these for after EVERY image I edit really does get tiresome. (If I forget, and do things in the "wrong" order, I have to find the image again myself, which really slows things down.)
Of course, other users with a different workflow may never meet this bug at all. (BTW this one isn't new, it was noted in Beta 2 but not fixed in the release version: http://community.acdsee.com/forums/topic/selection-lost-when-sorting-after-adding-image#post-43366 )
I have seen the sorting bug John mentions, but I do consider it relatively minor, because it doesn't come up very often for me and isn't particularly difficult to workaround when it does. I could see how someone with a different workflow might perceive it otherwise. As for a bug with "selection of images for processing", that's a new one on me, but I gather from what Philip says that it's been submitted and being worked on, so great. I can't common how minor or major it might be, since I don't know what it is.
But FWIW, the sorts of issues I've seen personally or that I've seen reported here all strike me as similar in severity to various issues that generally went unfixed for long periods in previous of releases (and similarly for other products) and we've learned to live with or workaround. I'm obviously not saying they aren't worth fixing - just that *to my knowledge*, there are no issues that I would think of as being the sort that would require an imminent patch, based on historical standards for that sort of thing and my own experience with the product. Patches seem to come out no more than every few months for ACDSee as well as most other products I use, and hence are perpetually in a state of having a few bugs that may or may not get addressed in the next patch but are basically perfectly usable as is. I see Pro 3 as being comfortably within that broad description. But then, I have no idea what this selection of images for processing bug might be, and it's obviously possible there are other issues I'm not aware of. So I guess I'm saying, if you believe there are such issues, you should definitely make sure people are aware of them.
Of course, I don't work for or speak for ACD, so my opinion means nothing here - don't take it as any sort of official statement. Just one fellow user's read of the situation.
Yes Marc, but as a Moderator - and an extremely knowledgable one - your "opinions" matter far more than those of we lowly Members. In this case, I have to agree with John Radcliffe. There are some bugs in Build 355 that really should be addressed immediately.
My particular pet peeve is the incorrect pixel dimensions on cropped images in Manage. Because I have image dimensions displayed with each thumbnail, this is particularly blatant. This is also the kind of silly and easily fixable error that can diminish the reputation of an otherwise breakthrough product release.
IMHO, Bill
Marc, to clarify the bug that I, and a few others have reported to Tech Support. Within a folder that has multiple image types, and/or large image files sizes, Manage will show all the files. View will show what it considers to be image files, including large files and HDR files. If I select an image file (raw or jpg or tif) and then select process mode a DIFFERENT image will appear in the window for processing or sometimes processing will be attempted on an invalid image. I've just also noted now that in Manage the properties pane will show some, correct, data but on selecting an image to see in view mode the WRONG properties will be displayed.
I believe that this problem has something to do with browsing a folder that has included non-image files or very large image files that ACDP3 can't process. To me, and I suspect a few others, this is a fundamental problem with the software that requires fixing immediately. Not that it'll stop me perservering with an excellent application - but then I'm not a professional relying on it for my livelyhood.
about your experience
which are the nasty bugs?
And what about adding unsupported RAW formats? When will a patch come that supports NEF files from Nikons D300s? Adobe already supports the new NEF's!
Marc, to clarify the bug that I, and a few others have reported to Tech Support. Within a folder that has multiple image types, and/or large image files sizes, Manage will show all the files. View will show what it considers to be image files, including large files and HDR files. If I select an image file (raw or jpg or tif) and then select process mode a DIFFERENT image will appear in the window for processing or sometimes processing will be attempted on an invalid image.
Interestingly, I just ran into a similar situations last night, but the circumstances were different - it was just a folder with PEF (Pentax RAW) files. I'm not sure what triggered this, but the other thing I noticed is that there were no XMP files for quite a few of the images, despite the fact I had applied a metadata template that includes EXIF and IPTC on import. When I discovered that, I ran a Batch Set Information operation to set those same fields, and that fixed everything.
Anyhow, sure, there are bugs; didn't mean to imply otherwise. From where I sit, 3.0 is actually less buggy and more stable than 2.5, but different people using different features will see it differently, of course. So yeah, I'd expect patches to continue to come at roughly the same rate they always have, but I wouldn't expect ACD to provide any sort of timetable any more than they have in the past.
Anyhow, sure, there are bugs; didn't mean to imply otherwise. From where I sit, 3.0 is actually less buggy and more stable than 2.5, but different people using different features will see it differently, of course. So yeah, I'd expect patches to continue to come at roughly the same rate they always have, but I wouldn't expect ACD to provide any sort of timetable any more than they have in the past.
may you make some exmples about 2.5 vs 3 bugs
Guys let me agree about buggy 3 release. I had to disinstall after a couple of hours.
1) Immediately after cataloging, a lot of images are not recognized from the disk. In other words, the images seems missing, and browsing, the database ask me if remove the info from the DB or not. Images are obviously present and was recognized 5 minutes befor during the scanning.
2) search panel graphic corrupt. I'm using Win7 x64 with latest ATI drivers. not able to perform a search
3) Lot of [developed] directory created without having done any operation, a part browsing images (no developed images at all)
4) a lot of images deleted without any reason.
Crazy sw this. Let me go back immediately to 2.5
I've had none of these issues - although I realise that won't make you feel any less frustrated!
There is always a possibility that their are conflicts on your system, but a report to Customer Support would be an option, if you haven't already - i have found them quite responsive in the past.
However well the Beta is tested, for any software, once it hits the real world all sorts of unforeseen things show up.
If I hadn't Beta tested Pro 3 and found it stable on my system, and hadn't liked the changes (well most of them) then I would have waited a while until I had upgraded in the hope that any bugs get sorted. It's why I also think it's wise to try a trial version to see how it runs on your system.
Good luck getting it sorted.
1) Immediately after cataloging, a lot of images are not recognized from the disk. In other words, the images seems missing, and browsing, the database ask me if remove the info from the DB or not. Images are obviously present and was recognized 5 minutes befor during the scanning.
Hard to say what exactly what went wrong here, but without still having the software installed, there isn't much that can be done to help track it down. Could be a bug, but could just as easily have been a misunderstanding.
3) Lot of [developed] directory created without having done any operation, a part browsing images (no developed images at all)
If you ran the catalog operation, one of the things it does it is generate previews in that folder. That's not a bug- that's a documented feature (you can turn it off by unchecking the appropriate box when beginning the operation).
4) a lot of images deleted without any reason.
Again, without still having the software installed, it's hard to say what happened, but I can pretty much guarantee ACDSee didn't delete anything you didn't ask it to delete. I'm guessing you simply misunderstood something about what happened. You might want to try reinstalling and paying close attention to what is going on, and post more details.
HI,
I did a new installation, in the same laptop (Lenovo w500) Win7 x64.
Now I'm working on a copy of the picture database, so no worry for strange behaviour.
First thing I noticed, problem n.1 is not happened anymore. This after the image copy from the win 7 default image folder (by operating system) to a directory in the root of second partition (D:). Could be a file permission issue? Strange because it was working with acdsee 2.5 and was not happening on all files.
Problem n.2, the garbage in the search panel is still there, search cannot be used.
Problem n.3 at the moment still haven't created any new folder, nothing changed in the configuration, so don't understand what's was happened in the previous installation.
Problem n.3 Images are still there. I'll let you know.
said that, at the moment the main issue is the search panel
thanks
Claudio
attached a screenshot of search panel
Claudio
I do believe at least one other person was seeing something similar with the search pane, so hopefully that's already been reported to support, but you might consider submitting a support ticket yourself too (link to Support at top left of this page).
FWIW, I was getting similarly weird results for a minute when I tried using Selective Browsing recently (not something I use often), but I can't reproduce it now. I think it might have had something to do with the fact that Ihad two instances of the ACDSee processes running at once. I don't suppose that's the case for you also?
BTW, it occurs to me if it appeared images were deleted but you are seeing them now, then it could be you had inadvertently applied a filter.
can I open the ticket also if I'm running the trial ?
I don't think so
Claudio
You're probably right. I'll make sure the right people see your post.
ok, thanks
Claudio
Subscribe to this topic via RSS
You must log in to post.