ACDSee Pro 3 Beta - Bugs

Back to Topic Overview Post New Reply

Final 3.0 -- Bugs, Bugs, Bugs.

[closed] (17 posts)

Started by LV_Bill
Started on September 24, 2009 - 05:35 PM (1 month ago)
Latest reply from tdi (1 month ago)

LV_Bill
Member

I'm on the road, but excited enough that I installed the production release on my laptop. What a colossal disappointment! I can't believe I put in all that time and effort to find bugs......and only one was fixed in the final version. I'm really furious!!!!!

Clone........still locks up your system. Save As.......still doesn't work right. Still ugly black with no color options and no Esc Key. And on, and on, and on.

My advice: If you haven't bought it yet, DON'T!!!! If you have, consider it to be Beta 3 and use it for testing only.

Posted On September 24, 2009 - 05:35 PM (1 month ago) (Permalink to this post)
tdi
Member

I feel your pain Bill. I've said for a long time here that these forums are a colossal waste of time and effort. One little thing I reported was fixed, but it is a problem I reported with 2.0, never got fixed thru 2.5 or 3.0betas... amazed someone finally touched on it for the release (Thank you again Tony).

I've said it before and I'll say it again,... you may as well be talking to a piece of Wood.

Posted On September 24, 2009 - 05:45 PM (1 month ago) (Permalink to this post)
BrettB
Member

I haven't tried clone, and I missed that being reported as a bug on the forums - although I've never used 2.5 for cloning either. I'll try that once I'm loaded and would hope it would be patched pretty quickly.

I haven't had any problem with Save As and black provides a good contrast for the background. Dark grey would be my preference but it's not the end of the world. The Esc Key was discussed at length and I wasn't expecting a change there - again it's a habit I'd got in to but it's just something to get used to.

If these are major issues to you it might have been wise to wait and try the trial version before you bought - and I can't see how these are issues that make it suitable for testing only.

Posted On September 24, 2009 - 05:45 PM (1 month ago) (Permalink to this post)
Paulgul
Member

LV_Bill said:

Clone........still locks up your system. Save As.......still doesn't work right. Still ugly black with no color options and no Esc Key. And on, and on, and on.

Well I'm not sure you could class all these as bugs, more like features you would have liked and haven't got. The save-as seems to work ok with me, not sure what you mean when you say it doesn't work, it saves an image with a new file name and type of the users choice. I've been using it most of the day and haven't come across any bugs and seems to be working well.

Posted On September 24, 2009 - 05:51 PM (1 month ago) (Permalink to this post)
mgshn
Member

Paulgul said:

LV_Bill said:

Clone........still locks up your system. Save As.......still doesn't work right. Still ugly black with no color options and no Esc Key. And on, and on, and on.

The save-as seems to work ok with me, not sure what you mean when you say it doesn't work, it saves an image with a new file name and type of the users choice.

Isn't this the thing where someone, maybe not this user, wanted save-as to be able to overwrite an existing file and ACDSee refused to do that?

Posted On September 24, 2009 - 06:01 PM (1 month ago) (Permalink to this post)
Paulgul
Member

mgshn said:

Isn't this the thing where someone, maybe not this user, wanted save-as to be able to overwrite an existing file and ACDSee refused to do that?

I've just tried that and it seems to work ok. Used 'save as' to save a jpeg with the same name but different compression. It warned me the file existed and did I want to overwrite, then saved ok.

Posted On September 24, 2009 - 06:11 PM (1 month ago) (Permalink to this post)
Picture Man Photography
Member

The final release is published? For real? It isn't on their Products page!

Posted On September 24, 2009 - 06:31 PM (1 month ago) (Permalink to this post)
Picture Man Photography
Member

I've got beta releases for competitive products that are on their 4th and 5th Beta release. I'm surprised what with all the bug reporting that there is a release version of Pro 3 B2. Hum . . . That's scary, if true.

Posted On September 24, 2009 - 06:34 PM (1 month ago) (Permalink to this post)
BrettB
Member

I've tried the clone and no lock up on my system.

Some of the complaints are about features rather than bugs, but I get the impression there are some minor bugs. I expect more will show up in full use but that seems usual for most new software releases.

That's scary, if true

I can't say I'm scared by it though some irritation is a possibility. ; )

The pre-orders have been distributed and the full release will follow soon - according to Melanie.

Posted On September 24, 2009 - 06:41 PM (1 month ago) (Permalink to this post)
Melanie Wood
Community Manager

Today was preorder fulfillment. That's why some of you have the product and some don't.

-Melanie

Posted On September 24, 2009 - 06:41 PM (1 month ago) (Permalink to this post)
BrettB
Member

Just to add - I don't normally update software on release - I usually wait for the bugs to get sorted and to decide if it's really worth the upgrade (still on Photoshop Elements 3 and MS Office 2000).

In this case getting involved with the beta convinced me it was stable enough for my needs (certainly no crashes or lock-ups) and different enough to be useful.

I am only an amateur, however, and not relying on it for a living. I suspect I might be more cautious if it was my livelihood.

Posted On September 24, 2009 - 06:49 PM (1 month ago) (Permalink to this post)
newname
Member

What should one hold on a company that publishes a list of more than 30 known issues for the final release even before the final release is available itself. Ridiculous business.

newname

Posted On September 24, 2009 - 08:43 PM (1 month ago) (Permalink to this post)
Kernel
Focus Group

newname said:

What should one hold on a company that publishes a list of more than 30 known issues for the final release even before the final release is available itself. Ridiculous business.

newname

Good morning and welcome to our world!!
Eeach software (yes, as well Boeing and Airbus flight control software!) has bugs! Microsoft has lists with thousands of bugs when releasing a new OS!

The only question is how severe they are and how often they happen. I'm pretty happy with the stability of beta2; unfortunately did not have the chance to test final build yet...
I prefer having a company that is aware of problems and which is working on it. But for sure they will not be able have zero bugs. That's software business - accept it or leave it!

Posted On September 25, 2009 - 01:18 AM (1 month ago) (Permalink to this post)
LV_Bill
Member

Dear Fellow Beta Testers -   I returned home from my road trip late last night and just now read the reactions to my angry post about bugs in the Pro 3.0 final release. At first read, it's pretty obvious that I didn't state the facts very clearly and that a further explanation is called for. Here goes.

My angry reaction was supposed to be about one specific thing -- program errors detected and reported by myself (and others) that were NOT FIXED in the production release. My post had nothing to do with the discussion about [Originals] vs. [Developed].  And, it was unnecessary of me to throw in the jab about ugly black and Esc as those were merely "nice to have" features. The original post was meant to be strictly about unfixed programming errors.

I found and reported six separate programming errors over the course of the Beta 2 Test. Four could have been lived with, if necessary, because there were workarounds. One was actually fixed. However, two bugs were critical programming errors (deal-breakers) -- meaning that without a fix, I would not be able to use Pro 3.0 at all. These were what I called the Clone Bug and the Save As Bug.

The Clone Bug applies to Canon Raw files (CR2). If you attempt to use Edit/Repair Heal or Clone on a CR2 file, Pro 3.0 goes into a processing loop. My guess is that this has to do with CR2's previously Developed with Pro 2.5. Whatever it is, the heal and clone tools in 3.0 are unusable on my CR2 files.

The Save As Bug is a failure of Pro 3.0 program to "recognize" files it has created using Save As during Process mode. The files are created correctly, but cannot be viewed or accessed until the user performs the following steps:  Return to Manage, press F5, click on the new file, then click on Process.

Conclusion:  My workflow causes me to perform a lot of Heal and Clone functions which in turn leads to a vast number of Save As functions.  With the above two bugs not fixed in the final release, I'm left with two unacceptable workflow disruptions which effectively kill the viability of the entire product in my case.

This is not exactly what I had in mind as I devoted a large chunk of my personal time on testing Pro 3.0.   So, Yes, I'm still angry, very disappointed, and the proud owner of a piece of brand new software that I cannot use because of it's reported but unfixed programming errors.

Posted On September 25, 2009 - 04:32 PM (1 month ago) (Permalink to this post)
Erin
Developer, ACD Systems

LV_Bill,

I appreciate your help in finding the clone tool bug. I thought this issue had been fixed but it appears as though there are a few separate issues. We did fix one issue, but it appears as though there is still a problem with RAW images that have certain rotation settings, as well as RAW images processed with crop/rotate settings in Pro 2.5.

I will look into these other issues.

Erin

Posted On September 25, 2009 - 08:25 PM (1 month ago) (Permalink to this post)
LV_Bill
Member

Erin - Thanks in advance for looking further into the Clone Bug issue. If you need any actual files to recreate the problem, feel free to post back or e-mail me directly at Sumnerbi@aol.com.

I should emphasize, however, that it's the Save As Bug that is the real App-killer here. Please make sure that the appropriate people understand that. For Pro 3.0 to succeed, you must either make Save As operate normally as all past ACDSee versions have - OR - create a setup option (e.g. File Management) where the user can specify a choice.

Bill

Posted On September 26, 2009 - 02:40 AM (1 month ago) (Permalink to this post)
tdi
Member

You know... when Pro 2.0 first came out, I reported that using the repair tool, clone or heal mode, and going right up to the edge of the image, would cause the tool to 'stick' as tho you were still holding the mouse button down. Then if you click anywhere else, it undoes what you did. They didn't fix that in 2.0, or 2.x, or 2.5 or 3.0 beta1 or 3.0beta2 or 3.0 release 355 or whatever it is.

So I guess what I'm saying is, ya'll need to relax and just accept and realize that they aren't looking to put out software that really works, (there was a day long ago when they did) but they are just looking to hack some things together and get people to spend their money. Otherwise after umpteen releases they would have fixed bugs like that...

Posted On September 26, 2009 - 05:02 AM (1 month ago) (Permalink to this post)