System Idle is running at full tilt while trying to use C1 P
Why is System Idle Process running at full speed (99%) when I'm trying to use C1 Pro v6.2 64 bit, fairly high spec computer.
CaptureOne.exe properties are showing it set to Normal
CapturePro.exe*32 shows "Above Normal"
COCIManager.exe*32 shows "Normal"
This makes the program even less instantaneous than it usually is!
Any answers?
I'm probably best raising a support case with Microsoft
CaptureOne.exe properties are showing it set to Normal
CapturePro.exe*32 shows "Above Normal"
COCIManager.exe*32 shows "Normal"
This makes the program even less instantaneous than it usually is!
Any answers?
I'm probably best raising a support case with Microsoft
0
-
In Windows, the System Idle Process represents the total sum of processor resources which are currently NOT in use. Due to your high spec system, processor utilization is fairly low, hence the idle process very high. You can't get healthier than that! 😉
As soon as you start pushing your system with a considerable workload the System Idle Process will decrease when other processes start using this resource (when processing images for example).0 -
Thanks Paul, but when the System Idle process was running, I was trying to edit a job of nearly 600 images and while I was trying to do this, CaptureOne was very sluggish indeed (lots of the spinning ball of death) 0 -
[quote="NN122830UL1" wrote:
Thanks Paul, but when the System Idle process was running, I was trying to edit a job of nearly 600 images and while I was trying to do this, CaptureOne was very sluggish indeed (lots of the spinning ball of death)
Reverse your logic: because Capture One was not utilizing the processor fully (or to a greater extend) for whatever reason, the System Idle Process showed a high percentage. Note that the System Idle Process is not a running process. It is an indicator only or what is not in use.0 -
I gather your point is that Capture One should be using more of your available resources to run faster instead of being so sluggish. 0 -
Something like that, Coach 0 -
[quote="NN122830UL1" wrote:
CaptureOne was very sluggish indeed (lots of the spinning ball of death)
Isn't the spinning ball of death a Mac thing?
❓ ❓0 -
[quote="SteveCase2" wrote:
[quote="NN122830UL1" wrote:
CaptureOne was very sluggish indeed (lots of the spinning ball of death)
Isn't the spinning ball of death a Mac thing?
❓ ❓
😂 Another feature stolen/borrowed/copied?0 -
I'm not really sure what you're getting at.....................but for sure, sluggish and crashes and errors are a CaptureOne thing, not Windows or Mac or hardware.
The only thing that seems to surpass the amount of reports of users experiencing errors and crashes and problems with this program seem to be about half a dozen guys going into the several thousands of posts continually saying there is nothing wrong with the program.
I dont know about anyone else, but when I for instance, move a slider, in any program, I expect the result to preview immediately, not to have to wait a second or so for the program to catch up!
That is even before I go into things like the histogram in Levels, disappearing, etc and needing a program restart to bring back.
I note there are no solutions to the Auto and Auto phenomenon but I dont expect any because that too is yet another program error.
How long must users actually wait before this program works, even on high spec machines, let alone on machines with the minumum suggested spec?
And what is this philosophy of denial from the handful of posters who continually say every problem and error experienced and reported by users has nothing to do with the errors in the program itself??
Dont get me wrong, when the program works, its great. However, given that one of its boasts is its speed, the fact that editing (not "developing") is so slow, even on a quite powerful machine, is very frustrating and disappointing,to say the least, and the fact that a supposed, very established program is riddled with so many faults, is very infuriating.0 -
[quote="NN122830UL1" wrote:
I'm not really sure what you're getting at.......
Don't let yourself get distracted or carried away in your list of issues if some guys have a bit of fun (not related to you or your issue by the way). Instead I hope you get a better understanding about the meaning of the System Idle Process.0 -
I think you are right.
When it works it is far superior to photoshop or lightroom. Just doesn't work all the time. Since I'm not in a rush I just wait and do something else while the program does its thing. Can't push it or it freezes and has to restart.[quote="NN122830UL1" wrote:
I'm not really sure what you're getting at.....................but for sure, sluggish and crashes and errors are a CaptureOne thing, not Windows or Mac or hardware.
The only thing that seems to surpass the amount of reports of users experiencing errors and crashes and problems with this program seem to be about half a dozen guys going into the several thousands of posts continually saying there is nothing wrong with the program.
I dont know about anyone else, but when I for instance, move a slider, in any program, I expect the result to preview immediately, not to have to wait a second or so for the program to catch up!
That is even before I go into things like the histogram in Levels, disappearing, etc and needing a program restart to bring back.
I note there are no solutions to the Auto and Auto phenomenon but I dont expect any because that too is yet another program error.
How long must users actually wait before this program works, even on high spec machines, let alone on machines with the minumum suggested spec?
And what is this philosophy of denial from the handful of posters who continually say every problem and error experienced and reported by users has nothing to do with the errors in the program itself??
Dont get me wrong, when the program works, its great. However, given that one of its boasts is its speed, the fact that editing (not "developing") is so slow, even on a quite powerful machine, is very frustrating and disappointing,to say the least, and the fact that a supposed, very established program is riddled with so many faults, is very infuriating.0 -
I'm running C1 6 Express on a high-spec studio PC, Windows 7 and it runs very slow indeed. For example 5mns to 'load' a folder of 4500 images. When I scroll through the folder the C16 hijacks the CPU taking between 40-100%, then eventually freezes. It is the ONLY piece of software I have had speed/freeze problems with. And yes I do use other image catalogue software to process the same folder and no, they are not slow nor do they hijack the CPU. Nuff said really. 0 -
[quote="NN634457481338026019UL" wrote:
...
And yes I do use other image catalogue software to process the same folder and no, they are not slow nor do they hijack the CPU. Nuff said really.
I would not consider calling Capture One 6 an image catalogue software; to the contrary. You could use Media Pro among others for that purpose.
CO6 is a raw conversion software that takes a detailed look at each raw image at first opening while it builds so-called previews to work faster when you start making adjustments and process them into TIFF or JPEG files. Despite your hardware specs CO6 is never flying with over 1000 images in a folder. As it is not a cataloging software this is in general not considered a problem.0 -
OK, so I used inappropriate terminology but the other programmes I referred to also process RAW files, export them etc. as well as 'cataloguing' any accessed folder of images. Also, I'm talking about C1 6 as being grounded. Flying isn't in the equation.
Enough of the quips though... Are you saying that, in order to use C1 6 effectively, you mustn't attempt to access folders with more than a few hundred files in it? That would put a real glitch in my work-flow, since I keep all original RAW files in one folder.0 -
[quote="NN634457481338026019UL" wrote:
...
Are you saying that, in order to use C1 6 effectively, you mustn't attempt to access folders with more than a few hundred files in it? That would put a real glitch in my work-flow, since I keep all original RAW files in one folder.
Yes. Depending on your hardware - in particular RAM and HDD speed are at stake once the previews are generated - you should consider working with amounts of images in a folder between a few hundreds up to a thousand max.
I don't know whether your 'all raw files' relate to all files of a day, week or longer time span but if so I would advise to break it up in shorter time intervals like a folder per day.0 -
Not ideal then. I'd normally use virtual folders to split the files up into sorts based on date taken, style, job number etc.
Under the conditions outlined above about 45% of RAM is used of which C1 6 has taken about 20-25% But what about the maxxed out CPU. Why might that be?
My system spec is:
Dell Studio XPS
Intel Core i7 2.7 GHz CPU
6Gb memory
64 bit
Windows 7 Service Pack 1
1 Tb hard drive
300Gb external drive0
Post is closed for comments.
Comments
15 comments