Massive problem: damaged imaged after export
Hi,
I use the Capture One 8.3.3. Trial (I think about switching from Bridge and Photoshop RAW Converter).
I get massive problems with exported images. Not matter what File-format or Colorspace I use. Everything is fine in Capture One, but after the export I get heavily damages images. Sometimes even totaly wrong color (i.e. only green tones)
Example:
http://postimg.org/image/4njokuod9/
Win 10 pro 64bit, geforce gtx 660, 4k monitor with dp cable, 16gb ram, i5 3550. All drivers are up to date. No other general problems with the system. Reinstalled all graphic drivers. Problem apears with CR2 and NEF files.
edit: Cameras are Canon 70D and Nikon D800.
This is realy awfull, I just can't use this program right now...
Any ideas?
(Sorry for my english and thanks in advance)
I use the Capture One 8.3.3. Trial (I think about switching from Bridge and Photoshop RAW Converter).
I get massive problems with exported images. Not matter what File-format or Colorspace I use. Everything is fine in Capture One, but after the export I get heavily damages images. Sometimes even totaly wrong color (i.e. only green tones)
Example:
http://postimg.org/image/4njokuod9/
Win 10 pro 64bit, geforce gtx 660, 4k monitor with dp cable, 16gb ram, i5 3550. All drivers are up to date. No other general problems with the system. Reinstalled all graphic drivers. Problem apears with CR2 and NEF files.
edit: Cameras are Canon 70D and Nikon D800.
This is realy awfull, I just can't use this program right now...
Any ideas?
(Sorry for my english and thanks in advance)
0
-
I've seen this on very rare occasion - likelyhood is hardware.
Try disabling the OpenCL acceleration for processing from prefs and try again. This can answer if the GPU is working ok.
If no improvement, try processing to another Hard disk. It could be it is failing to write properly.
If you need more help, suggest you drop support a line: http://support.phaseone.com0 -
Hello,
After upgrade to Windows10, I had the same issue!
Disabling the OpenCl acceleration for processing was the solution!
It seems its a Windows10 issue.
Before I upgraded I never had this problem.
Bram0
Post ist für Kommentare geschlossen.
Kommentare
2 Kommentare