ACDSee Pro 3 Beta - General Discussion

Back to Topic OverviewPost New Reply

Second beta release now available!

[closed] (38 posts)
1 2

  • Melanie Wood
    Community Manager

    When we asked you what you wanted from ACDSee Pro 3 and you responded with stability and performance! And stability and performance are what we've delivered.

    To download the second beta release of ACDSee Pro 3 Beta, visit www.acdseepro.com.

    Posted On August 11, 2009 - 05:34 PM (3 months ago) (Permalink to this post)

  • Marc Sabatella
    Moderator

    BTW, I just installed it, and for anyone wondering before doing so themselves, it *does* seem to inherit your database and all your settings & customizations from the previous beta build.  At least, it did for me, despite what the release notes say.  Your mileage may vary.

    Posted On August 11, 2009 - 06:50 PM (3 months ago) (Permalink to this post)

  • Melanie Wood
    Community Manager

    Thanks Marc!

    Posted On August 11, 2009 - 08:38 PM (3 months ago) (Permalink to this post)

  • Meier Two
    Member

    Where is the changelog ?

    Posted On August 11, 2009 - 11:48 PM (3 months ago) (Permalink to this post)

  • Chippy
    Moderator

    Installed, and a great build,way  faster.

    And I do not have any problems with NEF files, even with D-Lighting, either On or Off. :-))

    As Marc say's, everthing transfered over, No "re-doing " everything.

    {BTW this is on W7-64 bit RTM)

    Posted On August 12, 2009 - 02:34 AM (3 months ago) (Permalink to this post)

  • Sam Dring
    Moderator

    it *does* seem to inherit your database and all your settings & customizations from the previous beta build.

    Lucky you!  Settings not transferred and had to re-cat dbase.

    Interestingly (never seen this before) the cat files dialogue auto selected the start-up folder as the default for catting.  That is, having selected \...\2009 as start up folder, that folder alone was the default for cat files.

    Posted On August 12, 2009 - 09:20 AM (3 months ago) (Permalink to this post)

  • Heidi
    Moderator

    I am in the same boat as Sam.  No settings/db transferred.   The photos that I did process still process/with original.

     

    Posted On August 12, 2009 - 04:29 PM (3 months ago) (Permalink to this post)

  • Melanie Wood
    Community Manager

    Meier Two said:

    Where is the changelog ?

     The release notes are available on www.acdseepro.com

    -Mel

    Posted On August 12, 2009 - 06:06 PM (3 months ago) (Permalink to this post)

  • Marc Sabatella
    Moderator

    I started to wonder about something after posting the everything transfered over for me.  I had noticed even on the previous build that my db folder was in a folder called 30ProBeta2, and that there was a 30Probeta1 folder there too.  I'm wondering if that because I was part of the pre-beta "focus group" and that installed itself as 30ProBeta1, and then when the first beta came out, it noticed there was an existing 30ProBeta1, and therefore set itself up as 30ProBeta2, but the current build goes with 30ProBeta2 regardless of whether it already exists or not?  I'm guessing maybe its the same with registry settings.

    If this is true, or even close to true - it suggests you might be able to get the current build to use the existing db by simply pointing options->database at your 30ProBeta1 folder, or wherever your db was.  But it also suggests I might be skating on thin ice simply using my existing db with the new build if it wasn't designed to work this way.  And a simialr story on both counts regarding the registry - one could probably copy/rename the Beta 1 registry settings to Beta 2, but that might not actually be a fantastic idea?

    So far the only glitch I've seen is that WB settings I made in RAW processing using Beta 1 are not preserved in Beta 2 - they all revert to As Shot.  I can see by looking at the XMP files that the tags used for encoding the WB settings have changed, and I could probably write a Perl script to alter my Beta 1 XMP files to use the new method.  But it's also possible that would have happened automatically had I not been using a Beta 1 db?

    Posted On August 12, 2009 - 07:50 PM (3 months ago) (Permalink to this post)

  • Meier Two
    Member

    @ Melanie Wood

    Thanks.
    But I have asked for the (detailed) changelog and not a release note
    http://www.acdsee.com/offers/probeta/releasenotes2

    The only information about changes from Beta1 to Beta2 the release note contains:
    "The color of an image developed in Pro 3 Beta 1 may not match the image color if you open it in Pro 3 Beta 2 Develop mode as a result of an improvement to the Advanced color control algorithm."

    Ok it is still Beta, but I remember that ACD Systems even hides changelogs for official release versions or maintenance releases.
    I hoped for a change in ACD Systems information policy.
    Why can't ACD Systems do what almost every other serious software company does ?
    To declare these informations as top secret does not help to build (or regain !) confidence.

    Posted On August 12, 2009 - 11:48 PM (3 months ago) (Permalink to this post)

  • Melanie Wood
    Community Manager

    @Michael Meier

    there is nothing top secret and we do not hide anything. I can not provide a document that does not exist. 

    Posted On August 13, 2009 - 02:51 AM (3 months ago) (Permalink to this post)

  • QuBe
    Focus Group

    Marc Sabatella said:

    I started to wonder about something after posting the everything transfered over for me.  I had noticed even on the previous build that my db folder was in a folder called 30ProBeta2, and that there was a 30Probeta1 folder there too.  I'm wondering if that because I was part of the pre-beta "focus group" and that installed itself as 30ProBeta1, and then when the first beta came out, it noticed there was an existing 30ProBeta1, and therefore set itself up as 30ProBeta2, but the current build goes with 30ProBeta2 regardless of whether it already exists or not?  I'm guessing maybe its the same with registry settings.

     

    Here's my solution for all db location issues.
    I've located the ACDSee database, RIP cache, burn basket etc. on the separate partition (D:\ where all my images reside as well). (I also use this partition for my photoshop scratch disk, Bridge database and ACR cache.)

    This keeps things real simple. I point every ACDSee install, no matter what version, to this single ACDSee db and collection of caches.

    This is especially efficient since I run ACDsee off of 2 different boot partitions - an internet OS partition (that is 'disposable'), and a media partition where all my web dev and digital imaging apps reside. Both partitions have access to this third partition and the single db.

    I haven't noticed any problems so far through 2.0, 2.5 and all the betas, in fact newly added images while working in one partition show up in ACDSee in the other partition without having to generate the thumbs again.

    This perk aside, getting the caches and db to a seperate partition and out of the system OS saves location, backup and mantainance headaches for me. And also doesn't require any reg hacks.

    QuBe.

    Posted On August 13, 2009 - 03:53 AM (3 months ago) (Permalink to this post)

  • kShapero
    Member

    Just installed. My settings are intact. Whoopee!

    Posted On August 13, 2009 - 01:13 PM (3 months ago) (Permalink to this post)

  • Meier Two
    Member

    @ Melanie Wood

    Do you really want to tell me that even ACD Systems software developers have no changelog ?

    The question is: Why this document (a written public changelog) does not exist ?
    Because nobody writes it.
    And this leads to the final question:  Why no employee of ACD Systems has the instruction to write a public changelog ?

    If there would be a detailed changelog it would be much easier to find bugs and to help ACD Systems to improve their software products.

    In the longrun it is not a good idea to treat customers as if they are little children.
    And this is what ACD Systems does with these strange little release notes.

    Help us with a changelog and we can help you much better (to avoid a new fiasco as with version 2.5) !

    Professional or not professional ?
    That's the question !

    Posted On August 14, 2009 - 12:21 AM (3 months ago) (Permalink to this post)

  • RuthCT
    Member

    I just downloaded second beta and for some reason the trial serial number was never emailed to me.

    What if I made a typo when including my email address at the time of download?

    It expires in 2 days, but the problem is, I'm on the road and don't know if I will have access to the internet on Saturday.

    Posted On August 14, 2009 - 05:29 PM (3 months ago) (Permalink to this post)

  • RC Scoring Pro
    Member

    SUPER dissappointed that the cropping feature wasn't touched.  I left a detailed message a month ago with how to improve it.  If you have ever cropped 100 pictures in a day you surely have considered driving to ACDSee headquarters and confronting the designer of this feature. :)

    Posted On August 14, 2009 - 10:56 PM (3 months ago) (Permalink to this post)

  • sweetswel
    Member

    The more you work with ver. 3 the better it gets...cool...Mike 

    Posted On August 15, 2009 - 01:01 AM (3 months ago) (Permalink to this post)

  • Marc Sabatella
    Moderator

    RC Scoring Pro said:

    SUPER dissappointed that the cropping feature wasn't touched.  I left a detailed message a month ago with how to improve it.  If you have ever cropped 100 pictures in a day you surely have considered driving to ACDSee headquarters and confronting the designer of this feature. :)

    You never responded to my reply in that other thread, but actually, the crop tool changed a *ton*, in that now you can do it all nondestructively via Develop mode, and easily copy settings from one image to another.  Pretty much all the complaints you mentioned go away when using Develop mode as I described.

    Posted On August 15, 2009 - 03:16 AM (3 months ago) (Permalink to this post)

  • TDSAtlanta
    Member

    With regard to stability, it sure is consistent.  It does the same thing every I select a photo and click "process".  It shuts down.  100 percent consistent.  Therefore, if that isn't fixed, it is of no value.

    Posted On August 15, 2009 - 08:01 PM (3 months ago) (Permalink to this post)

  • Marc Sabatella
    Moderator

    Could you post one of the images that causes this so others can tr to reproduce the issue?

    Posted On August 15, 2009 - 08:02 PM (3 months ago) (Permalink to this post)

Subscribe to this topic via RSS

1 2

Topic Closed

This topic has been closed to new replies.