Export of images with adjustment layers fails
The export of images with layer adjustments fails consistently. The export results in an image that is divided into 6 fields, some of them blank (white) and others showing part of the image in false colours. I am running Capture One 9 on Windows 10 on a lenovo ideapad Intel Core i7 @ 2.2 Ghz 64-bit with 16GB RAM.
Can anyone point me to a solution to the problem 9other than support, which I have already contacted).
Can anyone point me to a solution to the problem 9other than support, which I have already contacted).
0
-
I think you owe the users here to tell what Support have suggested you and how it worked out, so they don't have to suggest the same things. 0 -
[quote="NN635079172050760248UL" wrote:
The export of images with layer adjustments fails consistently. The export results in an image that is divided into 6 fields, some of them blank (white) and others showing part of the image in false colours. I am running Capture One 9 on Windows 10 on a lenovo ideapad Intel Core i7 @ 2.2 Ghz 64-bit with 16GB RAM.
Can anyone point me to a solution to the problem 9other than support, which I have already contacted).
This has been an issue as long as there have been adjustment layers.
I have have experienced image corruption on export when using adjustment layers on several Mac and Windows computers. You get weird scrambled pictures opening in Photoshop that feature color artifacts and that point me towards graphics issues with either the use of the video card or otherwise. Don't go searching for answers in your own system (configuration), as I have had it with at least 5 different and up to date computers.
It happens on and off, and they only real solution is to delete the layer, close and start CO1 and create a new layer. But this becomes less and less credible as the editing possibilities on layers expand: some layer masks are hard to create and it is véry inconvenient to have to delete a layer and start over.
I am puzzled as to how this bug seems to have survived its way through at least 2 major version updates, I have never raised this issue with Phase one support, as it is vert hard to produce the artifacts on command, but it pops up with a predictable frequency nonetheless. It is in short a véry, véry nasty bug.
Chris0 -
Version 9 of CO1 still has the image corruption bug when using layers with multiple brush strokes.
Here is an export to photoshop of an image corrected for moiré with multiple brush strokes but only one single layer.
I guess I should open a support case over this, as this bug has been hanging on for quite some time now....
Chris
http://www.abnovembris.nl/A7r_DSC01508.jpg0 -
Chris,
I have never seen this. That said the GPU on my notebook is not accepted for OpenCL use as it lacks power.
Is it an OpenCL issue or do you see it even if OpenCL is disabled?
If you have an image that always fails I would be happy to have a look at is and try it out here.
The only time I have come across anything vaguely similar it turned out to be a single corrupt edit file in a session of about 2000 images. It kept throwing up errors all through the session edit until I spotted the bad thumbnail, deleted the edit and all was well. The Image re-edit without any problems The session-wide problems vanished.
Iirc that was back in version 6 days.
Using another application I sometimes see aspects of printed output that have similar characteristics. It struggles with the interface to my Canon Printer - especially where anything to do with scaling is requested. Capture One does not have such problems with printing, in my experience. However I think the problem with that editor related more to scaling.
Grant0 -
[quote="SFA" wrote:
Chris,
I have never seen this. That said the GPU on my notebook is not accepted for OpenCL use as it lacks power.
Is it an OpenCL issue or do you see it even if OpenCL is disabled?
If you have an image that always fails I would be happy to have a look at is and try it out here.
The only time I have come across anything vaguely similar it turned out to be a single corrupt edit file in a session of about 2000 images. It kept throwing up errors all through the session edit until I spotted the bad thumbnail, deleted the edit and all was well. The Image re-edit without any problems The session-wide problems vanished.
Iirc that was back in version 6 days.
Using another application I sometimes see aspects of printed output that have similar characteristics. It struggles with the interface to my Canon Printer - especially where anything to do with scaling is requested. Capture One does not have such problems with printing, in my experience. However I think the problem with that editor related more to scaling.
Grant
Grant,
I am just as surprised to hear that this is an unkwown issue for another CO1 user, as I have experienced it as long as I can remember with several Mac and Windows computers. It has been a reason not to put a lot of effort in a mask on a layer, as I continually run the risk of the image becoming corrupt on export/processing, and then I have to delete the layer and start all over again. But as the layer/mask functionalities are expanding, I would also like to safely work on layer masks, so I have finally opened a support case.
Yes, I have OpenCL on, but have a Nvidia 750ti graphics card with 2gb, so I am not under specced. I have 16gb RAM, and a SSD.
Let's see what support has to say...
Chris0 -
[quote="ChrisM" wrote:
[quote="SFA" wrote:
Chris,
I have never seen this. That said the GPU on my notebook is not accepted for OpenCL use as it lacks power.
Is it an OpenCL issue or do you see it even if OpenCL is disabled?
If you have an image that always fails I would be happy to have a look at is and try it out here.
The only time I have come across anything vaguely similar it turned out to be a single corrupt edit file in a session of about 2000 images. It kept throwing up errors all through the session edit until I spotted the bad thumbnail, deleted the edit and all was well. The Image re-edit without any problems The session-wide problems vanished.
Iirc that was back in version 6 days.
Using another application I sometimes see aspects of printed output that have similar characteristics. It struggles with the interface to my Canon Printer - especially where anything to do with scaling is requested. Capture One does not have such problems with printing, in my experience. However I think the problem with that editor related more to scaling.
Grant
Grant,
I am just as surprised to hear that this is an unkwown issue for another CO1 user, as I have experienced it as long as I can remember with several Mac and Windows computers. It has been a reason not to put a lot of effort in a mask on a layer, as I continually run the risk of the image becoming corrupt on export/processing, and then I have to delete the layer and start all over again. But as the layer/mask functionalities are expanding, I would also like to safely work on layer masks, so I have finally opened a support case.
Yes, I have OpenCL on, but have a Nvidia 750ti graphics card with 2gb, so I am not under specced. I have 16gb RAM, and a SSD.
Let's see what support has to say...
Chris
Chris,
I use masking quite a lot, often with several layers albeit, as I mentioned, absent any OpenCL since the Quattro K1000M is laughed out of court!
I run Win 7 Pro on a Dell Precision notebook Workstation. i7 processor from about 3 generations back, 2 SSDs on board (or sometime USB3 external drives) 24Gb RAM.
I see more than a few issues with Firefox freezing and Windows Explorer doing the same - both have to be killed more regularly than I like. But the only time I see issues with C1 is when I am also having problems with other applications or, occasionally, when I have accidentally used keyboard input when I had no intention of doing so and ended up with C1 trying to work out what I was instructing it to do whilst I had no idea where I might have taken it .... Quit and run can be the only option left in those circumstances! However it always seems to survive my abusive killings.
Have you tried investigating the log files to see if they throw up any indicators that coincide with the problem outputs?
Grant0 -
[quote="SFA" wrote:
[quote="ChrisM" wrote:
[quote="SFA" wrote:
Chris,
I have never seen this. That said the GPU on my notebook is not accepted for OpenCL use as it lacks power.
Is it an OpenCL issue or do you see it even if OpenCL is disabled?
If you have an image that always fails I would be happy to have a look at is and try it out here.
The only time I have come across anything vaguely similar it turned out to be a single corrupt edit file in a session of about 2000 images. It kept throwing up errors all through the session edit until I spotted the bad thumbnail, deleted the edit and all was well. The Image re-edit without any problems The session-wide problems vanished.
Iirc that was back in version 6 days.
Using another application I sometimes see aspects of printed output that have similar characteristics. It struggles with the interface to my Canon Printer - especially where anything to do with scaling is requested. Capture One does not have such problems with printing, in my experience. However I think the problem with that editor related more to scaling.
Grant
Grant,
I am just as surprised to hear that this is an unkwown issue for another CO1 user, as I have experienced it as long as I can remember with several Mac and Windows computers. It has been a reason not to put a lot of effort in a mask on a layer, as I continually run the risk of the image becoming corrupt on export/processing, and then I have to delete the layer and start all over again. But as the layer/mask functionalities are expanding, I would also like to safely work on layer masks, so I have finally opened a support case.
Yes, I have OpenCL on, but have a Nvidia 750ti graphics card with 2gb, so I am not under specced. I have 16gb RAM, and a SSD.
Let's see what support has to say...
Chris
Chris,
I use masking quite a lot, often with several layers albeit, as I mentioned, absent any OpenCL since the Quattro K1000M is laughed out of court!
I run Win 7 Pro on a Dell Precision notebook Workstation. i7 processor from about 3 generations back, 2 SSDs on board (or sometime USB3 external drives) 24Gb RAM.
I see more than a few issues with Firefox freezing and Windows Explorer doing the same - both have to be killed more regularly than I like. But the only time I see issues with C1 is when I am also having problems with other applications or, occasionally, when I have accidentally used keyboard input when I had no intention of doing so and ended up with C1 trying to work out what I was instructing it to do whilst I had no idea where I might have taken it .... Quit and run can be the only option left in those circumstances! However it always seems to survive my abusive killings.
Have you tried investigating the log files to see if they throw up any indicators that coincide with the problem outputs?
Grant
Grant,
So I tried disabling OpenCL, and indeed the issue then disappears. As it was always such an unpredictable, hit and miss image corruption, I did not really expect it to be the OpenCL enabling that was causing this, because then why on some images and simultaneosly not on others? A véry strange bug. But it does help: disable OpenCL, and the image corruption is gone.
It is not a solution however, and this should be looked into to fix. I have had it as said, on all my computers, and they are not to blame: I have zero other graphics issues.
It all looks like CO1 does not properly make use of OpenCL, at least not where layers are concerned.
Chris0 -
Hi, all,
thanks Grant. Turning off OpenCL does indeed "solve" the problem. I reported the bug to Support already but haven't received a reply yet.
Best regards to all of you,
Jörg0 -
ChrisM,
We use the same card here in many of our lower end desktops, but I can't seem to repro your corruption. Can you please send the following to Support:
- Complete set of Capture One logs ( C:\Users\[user]\AppData\Local\CaptureOne\Logs )
- An image file where you have made your adjustments, packed as an .EIP
- The recipe or all parameters of the recipe.0 -
[quote="Christian Gruner" wrote:
ChrisM,
We use the same card here in many of our lower end desktops, but I can't seem to repro your corruption. Can you please send the following to Support:
- Complete set of Capture One logs ( C:\Users\[user]\AppData\Local\CaptureOne\Logs )
- An image file where you have made your adjustments, packed as an .EIP
- The recipe or all parameters of the recipe.
Christian,
Thanks for responding. I am doing as you requested. The edits are nothing special, output recipe jpeg 100%, srgb, 300 px/in, 900px height. It's purely about the layers and/or layer masks.
I have done some more testing myself, because this is a véry obscure bug, and I have no idea how easy or difficult it will be to reproduce it. Some points:
-The image corruption happens ónly with layers with one or several mask(s) drawn.
-The image corruption may or may not disappear when restarting CO1, but will always re-appear when making more mask drawings. This is totally random behavior as far as I have seen: sometimes a restart solves things (temporarily), sometimes the image corruption maintains.
-The image corruption always disappears when switching off OpenCl.
-It happens mostly with multiple mask drawings, but on occasion also with a single mask drawing.
-It has happened on multiple computers, so is not system dependant.
-It has happened at least since version 7.
I hope your technicians can trace this down, because the inconvenience is most when you make complicated masks that take some time, although I have now determined with the help of Grant that switching off OpenCl allows you to export the image without corruption, so the workaround is temporarily switching off OpenCl. Not sure though how practical this is when batch exporting and you want the extra performance of OpenCl.
Chris0 -
Chris,
Just curious.
You mention an output size (900px height?) and presumably constrained by the height parameter. Are these panoramas (so possibly quite wide) or just regular ratios?
Your sample image posted earlier interests me. Especially the thin strip on the RH edge where the output result is different.
Using another application and only when printing (Canon printer driver - never tried with Epson or others) I almost always saw a similar effect, except that the rest of the image area usually looked OK, though not always to the size I had specified. In general the output, control over orientation and, well, everything, was utterly erratic UNLESS I deleted the printer instance an re-installed. Then one would get one chance to get it right ... but I digress.
If I took the trouble to crop the image and set sizing values in a way that meant there would be absolutely no scaling or dimension adjustment required for the print it was usually successful. A small amount of scaling would produce a strange "strip" of mangled image on the RH side of the print. The width could vary somewhat but seemed greater with more scaling involved. Sometimes, in the screen preview, I saw far more of the print area looking like the rest of your sample files bit not, afaicr, all of it.
Which is why I am wondering is maybe it is something to do with something specific in your settings that look innocuous but are not handled well by some part of the output process when OpenCL is involved or maybe some setting for the GPU.
Interestingly the other application I mentioned offers extensive layer functionality which I used a lot. I have not tested the results of attempting a print of an image with no layers using that software. I do not recall ever seeing an output to file exhibiting the corruption. The app does not make use of OpenCL.
HTH
Grant0 -
Grant,
No, the output recipe is not the cause, it happens with full size output also. So we can discard rescaling as a possible cause.
Chris0 -
[quote="ChrisM" wrote:
Grant,
No, the output recipe is not the cause, it happens with full size output also. So we can discard rescaling as a possible cause.
Chris
OK, sounds like one down then.
I wonder how many more avenues there may be to go down?
Grant0 -
Chris,
did you got your issue solved with OpenCl turned ON? (Turning OpenCl off is a not a solution in my eyes either...)
Thanks,
BeO0 -
[quote="BeO" wrote:
Chris,
did you got your issue solved with OpenCl turned ON? (Turning OpenCl off is a not a solution in my eyes either...)
Thanks,
BeO
Not yet, support is working on it.
I suspect it is caused by shortage of memory, because I had the exact same artifacts in the viewer when my system gave an out of memory warning (with 16 gb RAM). Moving the adjustment sliders shortly gave the image corruption artifacts in the viewer, after which the image returned to normal. So obviously the graphics card is not driven properly somehow, and faces a shortage of memory. With my limited computer knowledge, that is all I can think of.
Chris0 -
Thanks Chris. I would appreciate if you keep the thread updated whatever the solution (or no solution) is.
cheers,
BeO0
Post ist für Kommentare geschlossen.
Kommentare
16 Kommentare