Capture One 8 - desperately unstable..?
Nothing new in this post, but - as has been mentioned by others - I'm finding v.8 unbelievably flaky.
I'm still in "test" mindset (although against my better judgement and usual habit, I've actually bought the software - didn't know how long the low upgrade price would stand), so I'm using a test session and small (< 200) sets of Raw files (Canon 70D files for the most part).
My machine is a relatively modest Win 7 64 bit quad core box with 8gb of RAM (still well above minimum spec); freshly rebooted, and using a clean install of v. 8, the highest number of files I've been able to convert so far before the software has hung up irreversibly (save for invoking Task Manager and killing it) is four.
I'm not overwhelming my system resources with multiple layers, umpteen instances of spot removal or anything else overly resource-intensive - just some basic global adjustments, for the most part - and I'm averaging two conversions before another complete, unresolvable freeze. No error messages, just a completely unresponsive Capture One.
My RAM is healthy, and nothing in Resource Monitor indicates a problem.
Capture One 8 is unusable for me as it stands.
I'll continue working at it, but if anyone else has seen this and has identified any potential solutions, I'd be glad to hear them.
I'm still in "test" mindset (although against my better judgement and usual habit, I've actually bought the software - didn't know how long the low upgrade price would stand), so I'm using a test session and small (< 200) sets of Raw files (Canon 70D files for the most part).
My machine is a relatively modest Win 7 64 bit quad core box with 8gb of RAM (still well above minimum spec); freshly rebooted, and using a clean install of v. 8, the highest number of files I've been able to convert so far before the software has hung up irreversibly (save for invoking Task Manager and killing it) is four.
I'm not overwhelming my system resources with multiple layers, umpteen instances of spot removal or anything else overly resource-intensive - just some basic global adjustments, for the most part - and I'm averaging two conversions before another complete, unresolvable freeze. No error messages, just a completely unresponsive Capture One.
My RAM is healthy, and nothing in Resource Monitor indicates a problem.
Capture One 8 is unusable for me as it stands.
I'll continue working at it, but if anyone else has seen this and has identified any potential solutions, I'd be glad to hear them.
0
-
Hi Keith
The only persistent issue I've got is that the crop tool is very screwy; whichever ratio is selected, it will arbitrarily stop me from dragging the cropped area in one direction or the other at some point, even if set to "unconstrained." Damn annoying.
Back to your stability issues, I imported 260 EM-1 RAW files into a new catalog today, selected 41 keepers, adjusted them - like you, mostly global adjustments apart from a couple where I had 1 or 2 gradient layers - and exported all 41 in one go as 16-bit Tiff files. No issue. Machine was booted first thing this morning and has gone on standby twice with C1Pro8 running and this catalog loaded.
My hardware; Gigabyte Z97 ITX motherboard, i7-4790 CPU, 16GB RAM, 500GB Samsung 840 Evo. XFX Radeon 7950 3GB Ghost Ed.
Ram in use: 8.6GB (C1Pro8, Photoshop CC '14, Spotify Premium, Chrome x4, Windows 8.1 Update 1)
Best
Neil0 -
Well, one solution would be to change the software team management...
Another one, would be not to buy, ALL users of C1, the C1 v8...0 -
[quote="pkurhieuyr" wrote:
Well, one solution would be to change the software team management...
...
How you test the software and to what degree is often driven by product management, or even a VP of marketing or a CEO. This is a critical function that Phase One has yet to master.
I know it isn't easy - I've had two companies who struggled with it before they mastered it.0 -
HI,
Just like to say I have been a beta tester for many products (not Capture One) and this is up there with the best first release I have seen. I have had a couple of minor irritants I have reported but nothing that is a show stpopper, of course I can only vouch for the following environments:
1. Win 7 x64 System with Intous 5
Sys : Intel i7-2720QM @20Ghz x 4, 8GB RAM
GPU: NVIDIA GeForce GT 540M, 1GB, OpenGL v4.4
2. Win 8.1 x64 System with Intuos Pen & Touch
Sys :Intel i7-4700MQ @2.40Ghz x 2, 16GB RAM
GPU: Intel HD4600, NVIDIA GT 745M, 4GB, OpenGL v4.4
I also use Lightroom 5.6, CS 6, DPP, various PSE versions, various filters, Perfect Photo Suite etc.
More than happy!
Don.0 -
Good to know that it's working well for some of you - that's encouraging.
I'm not the kind of user who automatically assumes that software misbehaving on my machine is automatically the fault of the software (unlike every user on the Lightroom forums, it seems! 😉 )
I'm IT literate enough to know that the complex interaction between software and machine can cause problems that are "just one of those things" - an unlucky combination of circumstances, rather than necessarily a bug per se - so I'll try a few more things locally before handing the issue off to Phase One with a support case.0 -
[quote="NN635338752454027400UL" wrote:
Hi Keith
The only persistent issue I've got is that the crop tool is very screwy; whichever ratio is selected, it will arbitrarily stop me from dragging the cropped area in one direction or the other at some point, even if set to "unconstrained." Damn annoying.
Heh! Cropping works perfectly here - I can drag the crop around the image all day long without any problems.0 -
My C8 install hasn't been unstable, but I have noticed it seems to lock up my entire OS while it kicks off rendering previews of a new directory. Can't switch programs, can't click anything, the only indication the OS is still alive is the moving mouse cursor. Once it gets started it seems to be OK, but there's that time shortly after it starts, but before it has made much progress, where it decides all the resources are for it, and it alone.
I haven't noticed it to be any faster than C7, and I have at least one error where it refuses to render an image, claiming that although I've edited it already, it can't be loaded. The same error occurs if you try to queue an image to render before a preview has been created, but in at least one occasion (so far) an image simply cannot be rendered at all.0 -
C8: NO Problems, very stable, fast like hell (Sessions with 200+ pictures) until now. Hope it remains like this.
Windows 8.1 X64 16GB
AMD FX 8350
Radeon HD 78500 -
Cool - thanks for the feedback, Wolfram. 0 -
[quote="NFG" wrote:
Once it gets started it seems to be OK, but there's that time shortly after it starts, but before it has made much progress, where it decides all the resources are for it, and it alone.
So this is when it's building proxies, perhaps?I haven't noticed it to be any faster than C7
Me neither - in fact subjectively (while it's working) it seems less responsive to slider movements, moving from image to image, etc. And this is with a very small preview size by default.
Onwards and upwards...0 -
There are so many reasons, how C1 8 work:
- which drivers (with which OpenCl)
- which video cards (with how many ram)
- which CPU with which instruction and feature sets
- how many RAM (which kind of)
- which HD/SSD; where are C1 installed? On HD or SSD
- which mainboard
I guess just saying it becomes faster/slower isn't precise enough.0 -
We've had shockingly positive reviews of stability from our client base.
8gb of ram is very low for high-end imaging in 2014 though. I don't know how many of the beta testers or in house testing would have been done with such little ram. I have no idea if this is the cause or not, but it's the only item from your post that stands out from different than our 6 in-house test computers and the distribution of systems among our client base.
Clearly there are not zero problems (check ANY software makers site a day after launch and you'll find lots of bug reports) but if you're having issues, just know they are not systemic or an indication that the software is poor - you just have some specific issue that can and will be fixed if you report it.0 -
At least three other contributors on this thread are on 8 gb, Doug - and they're doing fine. Bear in mind that I'm not currently stressing my system with my testing, and I'm not getting anywhere near maxing out my RAM when I'm using v. 8.
If you're suggesting that in actuality 8 gb is the de facto minimum system requirement, then it begs the question of why Phase One's published minimum system spec in the release notes is 4 gb.
I've got some more local things I can try before I admit defeat (I actually think that whatever's going on will be local to my machine): and I'm in communication with Phase One about this too, so I'll keep at it.
(I'd happily up the RAM on my machine incidentally, but the motherboard will only take a maximum of 8 gb),0 -
[quote="Wolfram32" wrote:
I guess just saying it becomes faster/slower isn't precise enough.
Very true, Wolfram - a very good point.0 -
[quote="Keith Reeder" wrote:
At least three other contributors on this thread are on 8 gb, Doug - and they're doing fine. Bear in mind that I'm not currently stressing my system with my testing, and I'm not getting anywhere near maxing out my RAM when I'm using v. 8.
If you're suggesting that in actuality 8 gb is the de facto minimum system requirement, then it begs the question of why Phase One's published minimum system spec in the release notes is 4 gb.
I've got some more local things I can try before I admit defeat (I actually think that whatever's going on will be local to my machine): and I'm in communication with Phase One about this too, so I'll keep at it.
(I'd happily up the RAM on my machine incidentally, but the motherboard will only take a maximum of 8 gb),
Sure thing. Not blaming the ram. Just trying to be helpful and pointing out the only specific avenue of exploration that I saw in your post. Given that so few of our customers (which I'll grant you are a specific subset of P1 customers in general so not necessarily all encompassing) are reporting issues I'm grasping at straws for why your experience would be so poor.
Speaking of minimums...
https://www.youtube.com/watch?v=U5YClmS3umk0 -
Thanks Doug, I appreciate any constructive input.
Here's a bloody funny thing: same machine, I created a new Admin user and installed Capture One 8 on the new account.
I've just been using it utterly without problem for the last three quarters of an hour, and have converted more files in that time than I've been able to get done on my main user account since I installed 8 on it. I haven't tip-toed around it either - I've rattled through files at pace, and I've been using spot healing and brushed-on local adjustments as well as a wide range of global adjustments, cropping and whatnot.
Fast too, on the other user: Canon 70D Raw files (some mRaw, some full sized) converting to 16 bit tiff, in under three seconds.
I'll need to think about the implications of this. Thoughts, anyone?
Suffice to say, performance and stability like I've seen tonight would suit me just fine. I know that 45 minutes isn't long really, but it's far longer than I've been able to use the software up to now.0 -
[quote="Keith Reeder" wrote:
Thanks Doug, I appreciate any constructive input.
Here's a bloody funny thing: same machine, I created a new Admin user and installed Capture One 8 on the new account.
I've just been using it utterly without problem for the last three quarters of an hour, ....
...
No real thoughts, except that I always install as an admin on my systems. These are the kind of issues that drive programmers nuts.
As an added thought, I've tried a few more high ISO files (Canon 60D). On some of those, the noise reduction was much better than on CO 7 or LR. Go figure.
I am now waiting for a fix to my Media Pro interface, and then I may be good to go in Sessions.0 -
I always install as Admin on my default user account too, Jim - the point here is that simply by installing on a different (Admin) user account I'm getting a much different user experience, and I'm not clear why that might be - it's the same machine. 0 -
Support case #? 0 -
While I'm in the Mac version, so it's not apples for apples, I've worked with catalogs of 10,000+ RAW files in v8, without issues. The importing is many times faster than v7.2.x for me, particularly when adding images from directories that already exist.
Could this be a session related problem? Does the same happen with your 200 images in a Catalog?0 -
Sorry, missed the new user fixing the issues post above.
Perhaps it's a issue of v8 importing the existing settings from v7, or existing caches?0 -
Keith,
I've installed V8 and other than a couple of minor odd things I need to revisit to be sure of what I did, it seems very sound and very stable.
I can't say I have noticed much of a speed difference BUT, if the suggestion of improved performance in the interactive speed stakes is likely to relate mostly to OpenCL I won't see anything as my GPU (Notebook) is not worth using anyway.
| don't doubt that a few glitches will surface at some point but right now it looks good to me.
None of that is likely to help you work out what the issues are in your original admin account but I hope it gives you some confidence that what you see in the new one is what you can expect to be working with.
Grant0
Post is closed for comments.
Comments
22 comments