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. ⚠️

Less crashes in version 6.x?

Simon Bolz
Hello,

I am still using Capture One 5.5. My machine is very fast (brand new) but Capture One crashes regularly on the simplest tasks. E.g. I just "deleted permanently" 2000 image files. Not only did it take 20 minutes (for deleting, why?) but also crashed 3 times. It crashed so hard that I couldn't even submit the crash report window that came up.

I'd update to Capture One 6 but I fear that those crashing issues have not been solved. It's just a feeling because from the first moment I used Capture One, I always found minor bugs.

So can anyone please tell me how Capture One 6 behaves in terms of reliability and crashes?

Thanks a lot!
0

Comments

6 comments

Date Votes
  • Paul Steunebrink
    CO 6 on Windows is currently experiencing stability issues in particular on Win 32-bits systems. This is due to the memory consuming new tools like keystone and local adjustments. My first advice is to use a 64-bit system, preferably with Windows 7, not Vista.

    Second, OpenCL issues seems not to have been ironed out completely, creating some havoc on both 32- and 64-bits systems as well.

    Due to my own very positive experience with CO 6 on Windows (Win7, x64) from its first release up until today, and from many others I know, you should not be scared off to try. It is best to do a 30-day trial on your system and find out. You can install and try CO6 next to your current CO 5 setup which will not be affected.

    And keep up-to-date with CO 6 updates when you decide to go with it.
    0
  • Permanently deleted user
    [quote="Paul_E" wrote:
    CO 6 on Windows is currently experiencing stability issues in particular on Win 32-bits systems. This is due to the memory consuming new tools like keystone and local adjustments..

    I don't believe it is (primarily) due to these new capabilities. I use 6.x express 32-bit (WinXP) and these features are not present. Also I get the 'out of memory' crashes when browsing (not even editing) images that have .cos settings only created in 5.x.
    0
  • Mark Caton
    I would be concerned that PO 5.5 is crashing - most people have found CO4 and 5 are stable, but problems occur only with CO6, and in partic on 32-bit systems as has been said.

    Since it is a new machine I would try to get the latest drivers, windows updates, bios updates, test your memory (is it compatible?, in the right slots, have you got enough?), page file setup, and check your disk connections. Lastly is your vga-card up to it - PO have published a list of compatible cards - CO6 uses the power of the card in ways that CO4 and 5 didn't - this is where a lot of issues have occurred if you look thru the threads here.

    Getting PO6 of itself won't fix any of these issues, but get them right first and you're on your way.

    Mark
    0
  • Mal3
    Mark:

    I've had frequent out of memory and app crashes also with v6 on my XP 32-bit rig ever since upgrading from v5 to v6. New computer coming with Windows 7-64bit, 24GB of memory and Radeon 5770 card. I do hope this upgrade will eliminate these issues.

    You mentioned "page file setup" in your last post. Can you elaborate on that? and suggested settings?

    Thanks for any imput
    0
  • Paul Steunebrink
    [quote="Alex1111" wrote:
    [quote="Paul_E" wrote:
    CO 6 on Windows is currently experiencing stability issues in particular on Win 32-bits systems. This is due to the memory consuming new tools like keystone and local adjustments..

    I don't believe it is (primarily) due to these new capabilities. I use 6.x express 32-bit (WinXP) and these features are not present. Also I get the 'out of memory' crashes when browsing (not even editing) images that have .cos settings only created in 5.x.

    As soon as you open an image with CO5-made adjustments in CO6, the adjustments are automatically converted to CO6 to support new kind of CO6 adjustments, whether you use CO Express or Pro 6.

    CO Express or Pro 6 is basically the same application with a single memory model. CO Express has some features disabled from the user interface but not internally.
    Let's do a small experiment to explain this: I adjust an image with CO Pro 6 and I make typical Pro-only adjustments like adj.layers and keystone corrections. Next, I open the image with CO Express 6. What do you think the image looks like? Yes, it is how I left it in Pro. All adjustments are applied in preview and even when I process the image!

    Therefore my assumption is that both users of Express and Pro are affected by the changes made in the program code to accommodate the new features.
    0
  • Permanently deleted user
    Paul,

    I understood that, but my estimation was that if there are no keystone adjustment there is (or should be) less processing - for example I recall when keystone was accidentally in the first release of v6 express if I used it it took more time for the preview image to be rendered vs. if I didn't make any keystone adjustments - so at least in that first release there was more 'computation' going on with keystone vs. none at all. Likewise if no dust spots points are added there is less processing need as well. Granted more 'computation' does not mean it takes more memory to do so.
    0

Post is closed for comments.