Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

64bit or 32bit

Comments

7 comments

  • Permanently deleted user
    Not sure. They seem to be about the same, both slower than the CO 5.2.1.

    The 32-bit COP 6.0.1 seem to use less memory than its 64-bit brother.
    0
  • Roman Makhmutov
    Version 5 works much much faster than any version of 6.
    0
  • Paul Steunebrink
    Just a general remark, as for I have not done any comparison between CO5 and 6, in 32 or 64 bit, yet.

    When talking about faster or slower, always two questions pop-up: what and by how much? Is it the screen redraw, applying adjustments to selected variants, rotation, processing or opening the application you are talking about? Without such basic information, a discussion is rather pointless, while it could be very interesting indeed.

    In short: qualify and quantify your statement.
    0
  • Permanently deleted user
    Paul,

    I have not timed the processing which might not be that different. When one starts using a product, the interface snappiness is generally "perceived" as the ultimate speed of the product.

    With the keystone adjustment in use, moving from one image to another or just trying to resize KS adjusted images can have major impact on the responsiveness of the COP 6.

    With the Open CL enabled, the redraw anomaly can be quite disturbing. Consequently, the Open CL is turned off on my system after buying one after another "gamer" card to chase the Open CL dream. To be honest, it is not any faster with Open CL enabled as compared to the COP 5.

    To be fair, if one does not use KS adjustment, the speed between the two might be close. But this is the reason I wanted the CO 6. Without it one might as well stay with the CO 5. By the way a 64-bit application should be equal or faster than the 32-bit equivalent if it is written and built properly.

    I hope my reasoning makes some sense.
    0
  • Roman Makhmutov
    CO5 working faster than CO6 in these actions:

    1. Selecting many files and de-selecting.

    CO5 - almost immidiatly.
    CO6 - must wait up to 5-6 seconds until application will select items.

    2. Applying adjustments

    CO5 - almost immidiately.
    CO6 - lag up to 3 seconds.

    3. Changing preferences (WB, exposure, ETC)

    CO5 - same
    CO6 - lag up to 1-2 seconds.

    4. Switching between pictures, and picture redraw

    CO5 - same
    CO6 - lag from 1 to 3 seconds

    My system is 8GB Ram, Windows 7 64bit. Intel Core 2 Duo @ 3 Ghz 3 Ghz.
    Compared latest version of CO5 and CO6 (both v32 and v64)
    0
  • gregger1
    I can second the lag times cited here between C1 v5 and c6. It is noticeable and repeatable. And probably fixable.

    To the point that I was applying adjustments, seeing the preview / thumbnail update and not seeing results in the actual image... then attempting to apply another adjustment (and then noticing that the image actually updated). So, I tweak, sip something, wait...

    Image output processing appears to take longer on my machine.

    They've definitely changed a few things on how images get updated. I noticed doing "bulk updates" (multi-select, CTRL-Shift-V), that the updates appear to start from the end of your selection to the beginning of your selection (e.g. I select images 3 to 99, you would see images 99, 98, 97.... etc. until 3 update). Not sure if it happens every time, but I saw it enough times to notice it being a pattern. I think v5 went in the opposite direction.

    On the flip side, there are a lot of very small, but nice changes there that make things less aggravating to use. Things like:
    Undo actually works in the Contrast profile tool
    Contrast presets are "previewed" when you hover over the preset name
    Right clicking on a folder to set it to be the Output Folder no longer switches you to that folder. It just sets the folder and leaves you in your current folder.
    Folder / file system browsing appears faster.
    Output file naming is more powerful.

    There are a few other things that aren't really "feature" upgrades, just enhancements that help make things more usable.

    TTFN
    Gregg
    0
  • Roman Makhmutov
    Still there with our lag problems.
    0

Post is closed for comments.