Anti-chromatic aberrations do no apply for recipe process
Recently updated to 12.1.1.19. Clean reinstall. The program become absolutely unusable for me, because it is not possible to get rid of chromatic aberrations (purple single hairs). I checked it on my laptop with older version - 12.0.3.22, and its ok! So you, guys, just broke your program with 12.1.1.19 update beyond usability!
In the zip file (link to google drive below) there are:
-screen from the program (no purple hairs in preview);
-recipe made jpg v.12.1.1.19 (purple hairs always rendered irrespective of the checkbox "Chromatic aberrations");
-recipe made jpg v.12.0.3.22 (as it should be);
-original raw.
https://drive.google.com/file/d/1oYDeI3 ... sp=sharing
In the zip file (link to google drive below) there are:
-screen from the program (no purple hairs in preview);
-recipe made jpg v.12.1.1.19 (purple hairs always rendered irrespective of the checkbox "Chromatic aberrations");
-recipe made jpg v.12.0.3.22 (as it should be);
-original raw.
https://drive.google.com/file/d/1oYDeI3 ... sp=sharing
0
-
So you, guys, just broke your program
We guys on this forum are fellow users. Someone may have an idea to help, but you perhaps ought to contact Support to see if they can help.
Ian0 -
[quote="Ian3" wrote:
So you, guys, just broke your program
We guys on this forum are fellow users. Someone may have an idea to help, but you perhaps ought to contact Support to see if they can help.
Ian
I do not need an idea to help, as I wrote - 12.0.3.22 works alright, so just downgrade if you have the same problem. I provided this info in case somebody also gets screwed up by the developers as I got. If developers do not come to this forum, well, I've already wasted too much time figuring this out on my own and providing my own photos for analysis, I think I'm done for now. May be they will be more competent with v13 release.
BTW, I've installed 12.1.1.19 on the laptop (win10), the same behaviour for all pictures from any lens - but you need a picture where chromatic aberrations are actually present or there will be nothing to check whether C1 removes aberrations or doesn't. So it is not my main PC is buggy with 12.1.1.19, its the 12.1.1.19 is buggy (at least on two win10 machines).0 -
If developers do not come to this forum, well, I've already wasted too much time figuring this out on my own and providing my own photos for analysis, I think I'm done for now.
The developers have a well-established facility (support cases) for helping users sort out issues like this. It's probably more efficient than just posting in a forum - they can ask you for log files, sample images, etc. Also if users don't report things like this with support cases, how are they to even know that there is an issue to be addressed whether in 12.1.2, or 13.0?
Your choice, of course. If you only want to let off steam, then you have been able to do so.
Ian0 -
If I post it here, then everybody can see it and may be it can be helpful for somebody (surely would had been helpful for me), but if I submit a ticket, then nobody will see it (besides devs whose reaction is not always helpful). So I posted it here, but additionally submitting a ticket is just too much of a wasted time for me for a program which I paid money for, its not a community freeware to contribute to, its a pure professional proprietary soft. If devs care about their software then they will be reading forum on thier own web-site. Also, there is a difference between a small bug which is hard too repeat and you need to use special tools to track it and fix it, and a bug which just ruins all your photos every time when you export them, I'm sure they can repeat this bug without me, I've provided a raw file in the case it is a camera+lens related bug.
BTW, there is at least one more case of this:
Chromatic Aberration only visible on export/"edit in"
viewtopic.php?f=76&t=32215
The author reinstalled the program and the bug disappeared. Reinstalling does not help me (tried on PC and on the laptop).0 -
Just a note that there is a separate tool for Purple Fringing. It's NOT the Chromatic Aberration adjustment. 0 -
Never touched this tool but I will try it on the laptop where 12.1.1.19 is still installed later. But the thing is that the Purple Fringing is not visible on the preview (why would I use it if no purple fringing is visible no matter how I zoom/zoom out?) but it appears after making a jpg/tiff.
I remember when I check the "chromatic aberrations" checkbox in 12.1.1.19, or when I uncheck it, they (purple lighted hairs) appear for a second on the preview and then dissappear (only from preview). That's why I associated purple fringing with the chromatic aberrations, because the only way I can see (for a second) the purple fringing on the preview is when I check/uncheck this checkbox. Again, when I make a jpg/tiff out of the image they (purple lighted hairs) always there. On 12.0.3.22 purple hairs are always absent as it always was on v.11 (the first one I bought and then upgraded to v.12).0 -
Are you using a Process Recipe to create the outputs? (It hink you said you were but I want to confirm that.)
What are your settings for those options?
The Correction tools would have no effect on the output process compared to the edit as displayed on screen.
The Recipe Proofing option should give a good representation of what the recipe will deliver including the affects of different values for Output sharpening, etc.
If you are using the same recipe in 12.0.3 and 12.1 and seeing different output results just for the specific highlights (although there may be a top end exposure overall colour tint that would be very difficult to see easily in that image except in the hair.)
However the areas affected seem to be so specific that some sort of general tint change seems to be unlikely.
I would suggest that you create a Support Case if you have not already done so and discuss the problem with the Support Team. That way you will get some personal service for the problem and that would likely be far more effective use of your time than posting on the forum when there are a number of possible variables in play.
HTH.
Grant0 -
Yes, the same recipes (jpg/tiff srgb, nothing more) for older and new versions, as well as build-in recipes including the ones with different (other than sRGB) color profiles: no effect as to the removal of purple hairs.
Ok, may be later I will make a support ticket but any way after downgrating to 12.0.3.22 everything is fine. If I upgrade to a7r4, may be I will need a newer version, so it will be more relevant for me, because for now I can just stay on 12.0.3.22.0 -
[quote="NNN636477652643648348" wrote:
Recently updated to 12.1.1.19. Clean reinstall. The program become absolutely unusable for me, because it is not possible to get rid of chromatic aberrations (purple single hairs). I checked it on my laptop with older version - 12.0.3.22, and its ok! So you, guys, just broke your program with 12.1.1.19 update beyond usability!
viewtopic.php?f=11&t=5485
Rule 10:
Do not post a message merely to blow off steam or otherwise get something off your chest. This is a support, user to user help and resource area, if you have something to take up with a dealer then take it up with a dealer, if you have something to take up with Phase One then please take it up with Phase One.0 -
Do not post a message merely to blow off steam
This is a support, user to user help
I helped by describing the bug in details, providing the original raw file and telling which version of C1 does not have this bug and which does have, so somebody screwed-up like me will not have to spend half a day figuring things out after he/she/they realized that all their exported images are like sprayed with purple tint.
If you don't appreciate this, well, delete my post and if you want my account. No big deal for me.
Did not really understand this:if you have something to take up with Phase One then please take it up with Phase One
In my URL bar I see "forum . phaseone . com ", so I'm taking it up with Phase One, not with reddit or something.0 -
[quote="NNN636477652643648348" wrote:
If you don't appreciate this, well, delete my post and if you want my account. No big deal for me.
Did not really understand this:if you have something to take up with Phase One then please take it up with Phase One
In my URL bar I see "forum . phaseone . com ", so I'm taking it up with Phase One, not with reddit or something.
You still don't seem to get it: "you" in "if you want my account" appears to be addressed to Phase One, but the members of this forum who will read that sentence are users of the product, not the staff of the company.
Yes, the forum has been provided by Phase One for users' benefit, but they have clearly stated what the route is to seek help from Phase One staff for problems, and that is submitting a support case.
Ian0 -
[quote="NNN636477652643648348" wrote:
I helped
No, you did not - this is not where or how you raise issues.If you don't appreciate this, well, delete my post and if you want my account. No big deal for me.
And again - we're just users, so I can no more delete your post than you can claim that you read the rules before you posted.0 -
[quote="PavelH" wrote:
Just FYI. I imported your ARW file to C1 Pro v12.1.1.19, edited to get a similar appearance as your jpgs and processed to output sRGB jpg picture of the same dimensions. And ... no sign of purple hairs. So it seems that your issue is not a general bug of the last version.
Pavel
Thank you very much for trying. For me its repeatable on two win10 machines (a PC with intel cpu and amd gpu, and on Surface 4 pro). Actually not just repeatable, but inevitable and unfixable (on my own). That's about it. So, I made a support request to at least let devs know.0 -
[quote="NNN636477652643648348" wrote:
[quote="PavelH" wrote:
Just FYI. I imported your ARW file to C1 Pro v12.1.1.19, edited to get a similar appearance as your jpgs and processed to output sRGB jpg picture of the same dimensions. And ... no sign of purple hairs. So it seems that your issue is not a general bug of the last version.
Pavel
Thank you very much for trying. For me its repeatable on two win10 machines (a PC with intel cpu and amd gpu, and on Surface 4 pro). Actually not just repeatable, but inevitable and unfixable (on my own). That's about it. So, I made a support request to at least let devs know.
Well I have tried with V12.1.1 on my WIn 7 based system with an old and not very powerful NVidia GPU (which may or may not be used depending in the adjustment task).
I have tried The Proof view for all of the (often randomly created test recipes) foro output proofing and I have produced output jpg files at full scale and reduce size/compression with no sign of the purple hair in your example. (Nor did I spot any clear sign of Chromatic Aberration although I noted that C1 automatically applied adjustment for the lens/body/settings anyway.)
I think that without having the edit instruction files that you created to go with the image it would be possible to spend a lot of time experimenting and still not arrive at a conclusion.
It is probably something best left to the C1 Support team at this time since they will likely have had more exposure to other example of the anomaly and much more experience with ARW sourced files than I have.
Good luck. O would be interested to know the answer when you have one.
Grant0 -
The settings does not influence anything for me. Delete everything, clean reinstall of the C1 to the latest build, import one raw file, export with default srgb recipe - I got a picture with unremoved purple fringing. For some reason anti purple fringing just does not get applied on export, on preview it is applied. Do the same with older build (I only have a distributive of 12.0.3.22) - export looks exactly the same as preview with purple fringing never visible.
Again, this guy seems to encounter the same bug:
viewtopic.php?f=76&t=322150 -
[quote="NNN636477652643648348" wrote:
The settings does not influence anything for me. Delete everything, clean reinstall of the C1 to the latest build, import one raw file, export with default srgb recipe - I got a picture with unremoved purple fringing. For some reason anti purple fringing just does not get applied on export, on preview it is applied. Do the same with older build (I only have a distributive of 12.0.3.22) - export looks exactly the same as preview with purple fringing never visible.
Again, this guy seems to encounter the same bug:
https://forum.phaseone.com/En/viewtopic ... 76&t=32215
There is no purple fringing that I can see in the original file, therefore nothing to remove.
If you are seeing Purple Fringing in that sample image BEFORE YOU PROCESS IT then what you see on screen is not the same as what I see on screen even at the edit stage.
The link you provided suggests that the problem, for the other poster, was on his system (or some setting for his system) since re-installation worked. However you told us you have already tried the re-installation without success. So it worked for him but not for you and two people checking your file on their own systems do not have the problem.
If I had the problem I would probably be wonder about Windows updates (if I was using Win 10) and making sure that the OpenCL kernel for the the GPU drive had successfully been regenerated for V12.1 when it was installed. It should be checked and re-created if necessary with every start but on some rare occasions it seems the process can be 'blocked' for some reason or other.
You could probably check that quite quickly by going into the Preferences file and turning OFF Hardware Acceleration for Output. Then retry the output process to see what happens. It might be good to restart C1 as part of such a test.
If that produces no useful information than it may be best to see what the Capture One Support team can suggest.
HTH.
Grant0 -
I captured three screenshots as I was checking/unchecking the Chromatic Aberrations checkbox:
01. about to click checkbox - no purple fringing;
02. just clicked - purple fringing appears immediately after the mouse click;
03. 1 second after click - purple fringing disappears a second after the click.
https://drive.google.com/drive/folders/ ... sp=sharing
The view for 02 is the view which I will get upon export (irrespective of the checkbox and the purple fringing tool).0 -
[quote="SFA" wrote:
You could probably check that quite quickly by going into the Preferences file and turning OFF Hardware Acceleration for Output. Then retry the output process to see what happens. It might be good to restart C1 as part of such a test.
That's it! I do not know why I haven't tried it right away when you wrote it. Thank you! Without hardware acceleration this bug is gone! I gonna tell it to the support guys, coz all they did was sending me to here: https://www.phaseone.com/en/Search/Arti ... nguageid=10 -
[quote="NNN636477652643648348" wrote:
[quote="SFA" wrote:
You could probably check that quite quickly by going into the Preferences file and turning OFF Hardware Acceleration for Output. Then retry the output process to see what happens. It might be good to restart C1 as part of such a test.
That's it! I do not know why I haven't tried it right away when you wrote it. Thank you! Without hardware acceleration this bug is gone! I gonna tell it to the support guys, coz all they did was sending me to here: https://www.phaseone.com/en/Search/Arti ... nguageid=1
Ok.
Firstly look at this link
https://www.phaseone.com/en/Search/Arti ... nguageid=1
and especially the section "Rebuilding OpenCL kernels on Windows".
New releases of C1 will sometimes need to rebuild the kernel to make the sub-program fully aligned with the host computer's hardware and firmware set up (or after a GPU card change, etc.) and there can be times when this does no happen for some reason. If you are into reading Log files there are some that may indicate whether the expected process has run and what the observed outcome was.
If you delete the contents of the folder (or simply move them somewhere else if deleting worries you), on restarting C1 the Kernel should be rebuilt. This may take a few seconds or a few minutes depending on your machine. Then turn Hardware acceleration back on and see what happens.
If you still have a problem it may be worth looking for any updated drivers for your GPU. You may need to go to the GPU manufacturer's web site for the latest offerings. If you still have the problem AND you think you have the latest driver installed ... then try the previous driver instead. Sometimes new driver releases are not as useful as one would like.
HTH.
Grant0
La publicación no admite más comentarios.
Comentarios
19 comentarios