Capture One Pro 10.2 Unusably Slow (problem disappeared)
The v10.2 program's user interface is almost unusable. I takes around thirty seconds or more to respond to a single mouse click or keystroke. This is because the process is using near 100% of all twelve logical CPUs.
System summary:
System summary:
OS Name Microsoft Windows 10 Pro
Version 10.0.15063 Build 15063
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-GF1J232
System Manufacturer System manufacturer
System Model System Product Name
System Type x64-based PC
System SKU SKU
Processor Intel(R) Core(TM) i7-3960X CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 4901, 2014-05-14
SMBIOS Version 2.7
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume10
Locale United Kingdom
Hardware Abstraction Layer Version = "10.0.15063.502"
Username DESKTOP-GF1J232\itcon
Time Zone Co-ordinated Universal Time
Installed Physical Memory (RAM) 64.0 GB
Total Physical Memory 63.9 GB
Available Physical Memory 53.3 GB
Total Virtual Memory 63.9 GB
Available Virtual Memory 51.2 GB
Page File Space 0 bytes
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not InstantGo, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
Name NVIDIA GeForce GTX 680
PNP Device ID PCI\VEN_10DE&DEV_1180&SUBSYS_83F01043&REV_A1\4&B16BFE2&0&0010
Adapter Type GeForce GTX 680, NVIDIA compatible
Adapter Description NVIDIA GeForce GTX 680
Adapter RAM (2,147,483,648) bytes
Installed Drivers C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumd.dll
Driver Version 23.21.13.8768
INF File oem8.inf (Section018 section)
Colour Planes Not Available
Colour Table Entries 4294967296
Resolution 1920 x 1200 x 59 hertz
Bits/Pixel 32
Memory Address 0xFA000000-0xFAFFFFFF
Memory Address 0xD0000000-0xD7FFFFFF
Memory Address 0xD8000000-0xD9FFFFFF
I/O Port 0x0000E000-0x0000E07F
IRQ Channel IRQ 32
I/O Port 0x000003B0-0x000003BB
I/O Port 0x000003C0-0x000003DF
Memory Address 0xA0000-0xBFFFF
Driver c:\windows\system32\driverstore\filerepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvlddmkm.sys (23.21.13.8768, 16.05 MB (16,832,760 bytes), 2017-09-12 15:39)
Name NVIDIA GeForce GTX 680
PNP Device ID PCI\VEN_10DE&DEV_1180&SUBSYS_096910DE&REV_A1\4&11D5388E&0&0018
Adapter Type NVxx, NVIDIA compatible
Adapter Description NVIDIA GeForce GTX 680
Adapter RAM (2,147,483,648) bytes
Installed Drivers C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvldumd.dll
Driver Version 23.21.13.8768
INF File oem8.inf (Section018 section)
Colour Planes Not Available
Colour Table Entries 4294967296
Resolution 1920 x 1200 x 59 hertz
Bits/Pixel 32
Memory Address 0xF8000000-0xF8FFFFFF
Memory Address 0xC0000000-0xC7FFFFFF
Memory Address 0xC8000000-0xC9FFFFFF
IRQ Channel IRQ 40
Driver c:\windows\system32\driverstore\filerepository\nv_ref_pubwu.inf_amd64_17a7729c4a220588\nvlddmkm.sys (23.21.13.8768, 16.05 MB (16,832,760 bytes), 2017-09-12 15:39)
0
-
Sorry to hear about your issue. I have an identical configuration with the exception of a GTX 1070 rather than 680. Capture One 10.2 is very fast and has become my choice for processing my D810 images due to performance issues with Lightroom. The only time I've experienced performance issues with C1 it has been an Nvidia driver issue and an update to the latest version was the cure. You might take a look at your Windows Event Logs to see if anything unusual is going on. You might also try temporarily disabling any anti-virus or malware programs.
Edited to add:
Since Windows Task Manager shows the CPU and Memory usage of all applications, processes, and services it might be worthwhile to check if anything else it taking a lot of resources when 10.2 performance is slow. Using open CL or not? Try changing this preference.0 -
Thank you, Luke. It is only C1's hogging CPU - not other processes - and I am using the latest nVidia drivers. I'll see if there is anything pertinent in the event log and report back. I have raised a support ticket. 0 -
openCL setting are set to auto. ("Capture One is using hardware acceleration").
C1 v10.2 is now regularly crashing. C1 catches the exception and emits the message - to elide and paraphrase - "Capture One has stopped responding" - within a bug-report dialog box.0 -
Using open CL or not? Try changing this preference.
I changed the CL preference to "Never" to no avail.0 -
[quote="Luke_Miller" wrote:
You might take a look at your Windows Event Logs to see if anything unusual is going on. You might also try temporarily disabling any anti-virus or malware programs.
I can find nothing pertinent in the event logs. I don't (knowingly) use anti-virus and anti-malware scam-ware; though Microsoft does like silently to turn their "protection" on.0 -
If you are using a catalog you might try creating a new one to see if that makes a difference. Failing that you could have a corrupted installation of 10.2. It would be worthwhile to run the Windows Memory Diagnostic. A memory problem can cause a variety of performance issues. 0 -
Capture One froze and locked-up the computer. After power-cycling and restarting Capture One it came up in trial mode; I had to re-enter my license code. Since then the program has been running normally. I unfortunately have no idea what caused this problem and why it went away, so I can't really say that it is "solved". 0 -
Could it be that it was busy (re)generating previews? Or setting up hardware acceleration? 0 -
[quote="John Doe" wrote:
Could it be that it was busy (re)generating previews? Or setting up hardware acceleration?
No, because previews are generated quickly and h/w acceleration set-up is rapid too - when the program is running properly. The machine has twelve logical cores, 64GiB RAM and dual GPUs. When these two events take place there is always a progress pop-up anyway, which there wasn't.0
Post is closed for comments.
Comments
9 comments