C1-11 doest use much GPU?
http://www.andywee.com/pictures/c1.jpg
as above.it seems C1 will use the GPU that is powering the display mainly.
I get a different result if I turn on intel GPU , nvidia gets used more.
not to mention with iGPU on, capture1 is quite sluggish also.
woops i forgot to mention this is when I am exporting to TIF.
as above.it seems C1 will use the GPU that is powering the display mainly.
I get a different result if I turn on intel GPU , nvidia gets used more.
not to mention with iGPU on, capture1 is quite sluggish also.
woops i forgot to mention this is when I am exporting to TIF.
0
-
Unfortunatly you cannot use the Task Manager's graph, as it doesn't seem to monitor OpenCL usage on the GPU. You can use a utility like GPU-Z or similar instead. 0 -
I had a possibly related problem: since I updated my nVidia graphics drivers (using DDU) for my GTX 1080 Capture One seemed to default to my Intel onboard GPU (GPU 0 in my task manager), whereas other programs default to my dedicated GPU (GPU 1).
I confirmed this using MSI Afterburner as a monitoring tool: my GTX 1080 was sitting idle at 140 mhz when rendering previews and when exporting files. I tried a complete Capture One clean install and I also then tried forcing a re-assessing of the GPU by deleting the ImageCore folder under in ProgramData but C1 would still be sluggish and not use my main GPU.
I eventually noticed that if I created a new variant and I selected it, it would fire up the main GPU. I ended up resetting all images from the session I was working on and it indeed fixed the problem: the dedicated GPU was fully used (@ 1600 mhz +)once again. This is really weird.0 -
After doing more testing I found out the culprit: the dust removal tool.
Simply resetting this particular setting makes my GPU go from idle (139 mhz) to almost full power (1693 mhz).
Is this a bug?0 -
[quote="Charles O." wrote:
After doing more testing I found out the culprit: the dust removal tool.
Simply resetting this particular setting makes my GPU go from idle (139 mhz) to almost full power (1693 mhz).
Is this a bug?
From memory the dust removal tool is CPU only and somewhat process intensive if you have a lot of dust spots being removed. Therefore processing response will be slower and the GPU less loaded. Potentially much less loaded.
Would that explain what you see?
Grant0 -
From memory the dust removal tool is CPU only and somewhat process intensive if you have a lot of dust spots being removed. Therefore processing response will be slower and the GPU less loaded. Potentially much less loaded.
Would that explain what you see?
I remember stopping using the dust removal years ago in v9 because I noticed it was CPU hungry indeed (I prefer spot healing in Photoshop for this matter), but in my latest session I decided to use it once again just to remove a nasty speck of dust before client proofing, and this is what I think was causing my GPU issues.
I only used one "spot" per photo, and applying it makes the GPU go to idle; and then resetting the setting wakes up the GPU once more!0
投稿コメントは受け付けていません。
コメント
5件のコメント