NIK Color Effex pro4 crashes after conversion with 9.1
Today I updated Capture One 9.03 to 9.1. As usual, my files are converted to 16 bit Prophoto Tiff- files into PS CS6 for applying further adjustments. However, NIK Color Efex 4pro crashes constantly before the PS-Plugin has finished the adjustments by displaying a crash message, encoded in a log file in the AppData user folder.
Please don't tell me that this is no C1-problem but a PS or NIK issue : I have done exactly the same steps with hundreds of tiff files after the conversion through C1 9.03, ver 8.x 7.x ..... without any problem. To test the integrity of the NIK Plugin, I applied Color Effex 4pro to some files that were processed through C1 ver 8 in the past and also just converted an original raw file through C1 ver 8 again without any problems when running Color Effex in PS afterwards. So the Plugin itself is just fine. Restarting the PC doesn't help either. OS is win7 ultimate, 16 GB RAM, Graphic card is a Nividia Geforce GTX 570 but I see no logical connection here since all is fine with the raw files of the same cameras processed through the previous versions. I have no idea which changes in the datas of the processed raw files cause these crashes. I don't know either if there have been some problems caused by the installation of C1 9.10 which was a nightmare too for the first time, btw. I experienced a black screen with issues of my USB Hub after the restart. I finally could start Windows again now but the issue described above is still there as it was before the restart. So far I have not seen any issue with the conversion through C1 9.1 itself, though. Any help to solve the problem is very much appreciated.
Wolfgang
Please don't tell me that this is no C1-problem but a PS or NIK issue : I have done exactly the same steps with hundreds of tiff files after the conversion through C1 9.03, ver 8.x 7.x ..... without any problem. To test the integrity of the NIK Plugin, I applied Color Effex 4pro to some files that were processed through C1 ver 8 in the past and also just converted an original raw file through C1 ver 8 again without any problems when running Color Effex in PS afterwards. So the Plugin itself is just fine. Restarting the PC doesn't help either. OS is win7 ultimate, 16 GB RAM, Graphic card is a Nividia Geforce GTX 570 but I see no logical connection here since all is fine with the raw files of the same cameras processed through the previous versions. I have no idea which changes in the datas of the processed raw files cause these crashes. I don't know either if there have been some problems caused by the installation of C1 9.10 which was a nightmare too for the first time, btw. I experienced a black screen with issues of my USB Hub after the restart. I finally could start Windows again now but the issue described above is still there as it was before the restart. So far I have not seen any issue with the conversion through C1 9.1 itself, though. Any help to solve the problem is very much appreciated.
Wolfgang
0
-
I had a similiar problem with an image i exported into Photoshop and then attempted to adjust using Color Efex Pro 4 in that as soon as it opened the .jpg image it turned a gastly shade of pink.
It's only happenen the once so far but Iv'e only tried it a couple of times so far.
I'm having problems exporting images as .jpg in that they are coming out vastly over-exposed when uploading to a popular critique website.
I suspect that since the update to v9.1 there's now a problem with the export feature.0 -
Richard, thank you for your comment. I probably go back to v 9.03 until further notice since I'm not willing to give up on Color Efex 4pro which has been an important tool in my workflow for a long time. In fact it's probably an export or signature problem so that the files have a 'marker' or whatever difference compared to previous conversions causing the crash and incompatibility with Color Efex.Though the NIK Plugins are pretty wide spread in the (pro)photo community I'm pessimistic that the issue will be addressed by PhaseOne in the near future since it's probably not on their priority list. However, I don't want to be stuck with my work. At first I was also thinking of reinstalling the NIK collection but that seems illogical and probably won't help at all because the Plugin works as it should after the conversion of the files by using the previous versions of CaptureOne Pro including v9.03. Beyond that I'm not sure if I still find the licence # of the NIK (Google) collection after that long time and thus would not even be able to use it with the previous conversions if I fail to dig it up. Anyway, if there's no quick and simple solution I will skip v 9.1, unfortunately. I've been a loyal customer for decades and have used all versions of C1pro from the start. Too bad, but it seems to me that I have to look for alternatives now since this obviously is another big cut within a short period after the OpenGL issue I experienced with Canon files and the Nividia Graphic card before the workaround was known.
Wolfgang0 -
Wolfgang,
Have you created a Support Case?
If not I would suggest you do. While many people here on the forum would be pleased to help it is a User to User forum, mostly, so deep technical knowledge of C1 and changes between releases will not be present.
What you describe about your upgrade installation is worrying. I would suspect that something has not worked correctly for all situations.
I have installed alongside 9.0.3 and I am currently running 9.1 as a trial as I usually do. The installation went through without problems.
Have you by any chance recently updated Windows with the latest patches - and perhaps not restarted at the time?
I had some small problem with the last Win 7 update on re-start. Interestingly that update (for me) included an MS .NET revision and I think C1 may also have included a .NET revision which had me wondering if there were some anomalies in the timing of updates on my system.
In your situation I would try another installation (or perhaps a "repair" installation using the Windows Software management tools) to see if that changes anything for the good.
The C1 Support Team should be able to identify to you what they would need to be able to check whether the installation process identified any problems during its execution.
HTH.
Grant0 -
Grant,
thank you for your suggestions. Though I had good experiences contacting the support team in the past, I haven't created a support case yet. Since the crashing of Color Efex 4pro in PS isn't directly connected to the appearance or look of the raw conversion itself (which is ok) and I neither haven't experienced a problem with the handling of C 9.1 so far, I was (and still am) a bit skeptical that the support members would feel themselves responsible for an issue regarding the NIK filter after the successful conversion. On the other hand, since many users probably know and use the NIK- (now so-called Google) -collection including Color Efex, I have been hoping that they could share their experiences after the update to C1 v9.1. Anyway, I will certainly try to get help via the support route, too.
As to Windows, all recent patches and updates were successfully done and all restarts required, too. So I don't see any problems in this regards. The black screen and USB error messages after the restart which I had mentioned in my last post evidentially were caused by an internal malfunction of my A3+ printer. which is connected on one of the USB ports. So it obviously was a coincidence that this simultaneously happened to the restart required after the installation of C 9.1. Windows now runs smoothly again. Therefore it's still the crash of Color Efex 4pro that urgently needs to be addressed.
Wolfgang0 -
Hello Wolfgang,
I think that when a problem is quite easily repeatable and does not occur for earlier versions it makes sense to let a support team know about the problem although as you have written, expecting an immediate solution to the problem may be optimistic.
Nevertheless if they get a number of reports of strange things that sound similar there may at some point be a Eureka! moment that ties them all together and identifies a way to investigate.
By the way, one of the strangest problems I ever heard about - one that took a long time to identify a cause - involved a printer.
A business analysis system sitting on a Windows network working quite happily. One of about ten similar workstation installations.
Suddenly it stopped working correctly. It happened to coincide, more or less, with an point release update of the application. Strangely the other workstations still worked correctly. What could it be?
After a lot of investigation over many weeks it turned out to be a problem with a printer. The system was not normally used to print anything much but had a default network printer defined. For some reason, unconnected with the application that exhibited the problem, the default printer had been changed to point to a different device. Something obscure within the application - I forget what but possibly related to some unused (by the operator) facilities to print graphs in a graphical style - was being checked against the registered default printer and after the change the check did not like what it found. Somewhere in the "handed-off" chain of software applications from several sources that were all in the chain the processes would hang. No error message - just a hang.
Nobody made the connection to the printer selection change - I mean, why would you?
I'm not trying to suggest that you printer is the problem. It's just that you mentioned it and I recalled the unusual story. It is the sort of story that stick in the depths of memory and may just one day act as a stimulus that help a diagnostic process to find the source of an obscure problem by encouraging people to consider things that seem to have no relationship to the problem being investigated.
Grant0 -
I encountered similar problem with Silver Eflex. In C1, there is option to store the TIFF as zipped. I vaguely remember that Nik Silver Eflex does not like zipped TIFF.Turn it off and hope you good luck. 0 -
I've reported this problem together with my export problem and technical support have said there is a bug and they'll look into it. 0 -
Thank you Richard, I'm about to create a support case, too and attach the crash log. I also posted the issue over in the NSN forum, and the technical editor supposed a memory problem with Color Efex when running C1 plus PS plus Color Efex. He has no problem applying Color Efex after the conversion with C 9.1 on his 32 MB RAM machine. But I tried to open a file I yesterday had processed through C 9.1 in PS and applied Color Efex after a fresh start of my PC without any other program running simultaneously besides PS CS6 and experienced the same crash. C1 wasn't opened at this point at all. If I repeat that with a file converted with C 9.03 or C 8 there's no problem with Color Efex at all. So it's definitely no memory problem. I hope that PhaseOne will find and solve that bug VERY soon.
Regards
Wolfgang0 -
[quote="Wolfgang1" wrote:
If I repeat that with a file converted with C 9.03 or C 8 there's no problem with Color Efex at all. So it's definitely no memory problem. I hope that PhaseOne will find and solve that bug VERY soon.
Hi Wolfgang,
Could you please make both TIFF files (the one created with v9.03 and the one created with V9.1) available from some server? I'd like to do some research about the differences between both files. Please make sure they are converted using the same output options.
MfG0 -
Problem confirmed here.
TIFF files generated by C1 9.1 systematically crash NIK filters. TIFF files generated by Lightroom or DxO Optics Pro don't have any problem with these filters.0 -
Hi Samoreen,
I have no answer yet from PhaseOne regarding the support case opened the day before yesterday. Therefore I de/re-installed the NIK suite on my PC without a solution of the problem. In the first step I reinstalled the version 1.2.8. I had got from Google last June and which has worked fine with C1 v9.03 or v8.x to date. By then, I had no crash anymore but the preview of Color Efex and the output was total crap, see here:
Depending on the concrete file the Brillance/Warmth Filter in Color Efex came out totally washed out, pink or even black (no filter adjustments were made). So I then deinstalled the NIK collection for the second time and reinstalled the latest version 1.2.11 I had got directly from Google today. I also made sure that there were no remains of the previous versions in the PS Plugin folder or elsewhere. In the result Color Efex crashes again as before whenever it is applied on files processed through C1 9.1.while it works fine again with files previously coverted with C1 9.03 or 8.x. BTW, I experience these problems, too, if I process the raw files to JPEGs through C1 9.1, then shut down C1 and just open the file in PS CS6 and start Color Efex without any other program running simultaneusly. So it's definitely no memory problem in my view and pretty annoying since I'm stumped by now and stuck my work. I consider going back to v9.03 if PhaseOne doesn't communicate a solution VERY soon.
Wolfgang
PS: If you still want me to provide Tiff files processed through v.8 and 9.1 let me know (Presently v9.03 is not installed anymore since it was updated to 9.1, of course) That said I think we will have to wait what PhaseOne will say. They got the crash report from me, too.0 -
Under the TIFF format, there is an option to choose between uncompressed or zip. I picked uncompressed and have no problem editing the TIFF from C1 9.1 with ColorEflex and SilverEflex.
I remember starting from V9, the default for TIFF is set to zip and I experienced crashing problem before 9.1.
BTW One can run ColorEflex or SilverEflex direcly without going through PS. Just click the .exe will run them standalone. This would also help to isolate the problem.0 -
[quote="Wolfgang1" wrote:
PS: If you still want me to provide Tiff files processed through v.8 and 9.1 let me know (Presently v9.03 is not installed anymore since it was updated to 9.1, of course)
Hallo Wolfgang,
Yes, I'm still interested if this is not bothering you. I'm a former software engineer and I have some tools handy that could help us understand the differences between the 8/9.03 and the 9.1 versions of the TIFF files. Using the same output parameters in both cases is essential for the comparison.
It's just out of curiosity because only P1 can fix that, you're correct.
MfG0 -
Hi, [quote="NN231609UL" wrote:
Under the TIFF format, there is an option to choose between uncompressed or zip. I picked uncompressed and have no problem editing the TIFF from C1 9.1 with ColorEflex and SilverEflex.
Same problem here with both the compressed and uncompressed versions of the TIFF file.[quote="NN231609UL" wrote:
BTW One can run ColorEflex or SilverEflex direcly without going through PS. Just click the .exe will run them standalone. This would also help to isolate the problem.
Correct. I have tested both modules : the plugin in Photoshop and the executable from Lightroom (Lightroom doesn't actually have real plugins - it is just calling the executable, passing it the path of the TIFF file on the command line). In Lightroom, I had of course imported the TIFF file produced by C1 9.1. Same result (crash) in both cases.0 -
Got it!
The problem occurs when using the "Embed Camera Profile" option. No problem when specifying another profile like Prophoto for example.0 -
[quote="Samoreen" wrote:
The problem occurs when using the "Embed Camera Profile" option. No problem when specifying another profile like Prophoto for example.
I never set this option myself. So I'm wondering whether the installation of version 9.1 changed the default ICC Profile in the output settings for the TIFF 16-bit Full Size preset?0 -
WOW, that's great news. Thank you for all your efforts, Samoreen !! I just checked the conversion with v 9.1 and the output setting changed to Prophoto and bingo - no problem with Color Efex. So I can confirm your findings.
Furthermore, I checked that setting in my C1 8.3 installation and in fact it's set to Prophoto there ! If I change it to "embed camera profile", the problem with the processed Tiff file and Color Effex occurs there too (no crash, though but total crap with pink and green colors). So there's certainly a conflict with the color filter if the ICC output is set to the "embed" option. As said I cannot check the ICC setting in 9.03 anymore since this version was updated to 9.1 on my PC. But it's very likely that it was set to Prophoto, too, since there were no such problems with the converted Tiffs. I haven't manually manipulated anything in that output setting either and don't know why this obviously is changed during the installation of v 9.1. Only P1 can answer that but I still haven't got a feed back regarding my support case, unfortunately.
Best regards and thank you again for your great help !
Wolfgang0 -
Nothing has changed in 9.1 for the default Process Recipes or my own recipes as far as I can tell.
I changed the Export recipe and tried that too. Nothing changed in the defaults after closing and re-opening C1.
The only place I can see that allows allocation of the Camera Profile is the recipe definition. It appears at the top of the list of available ICC profiles. So it may be possible to set it inadvertently and not notice?
One possible difference is that I have installed 9.1 alongside 9.03 rather than replacing it.
Grant0 -
My guess is that it's related to a more general issue. Other users in my environment have noticed that too : when upgrading to a new version, some options are not retained. This can be observed for example with the ICC Profile field in the color tab. After the upgrade, the profile is reset to the generic profile. A buddy of mine has to systematically reset the "language" option after each update.
Next time, I'll have a look at what happens with the ICC Profile setting in the output tab.0 -
[quote="SFA" wrote:
Nothing has changed in 9.1 for the default Process Recipes or my own recipes as far as I can tell.
So it may be possible to set it inadvertently and not notice?
Well, two of us in this discussion appear to be sure to have not touched this option and to have set it in a previous version to Prophoto.0 -
[quote="Wolfgang1" wrote:
Best regards and thank you again for your great help !
Keine Ursache. Ich mag Bugs jagen 😄 .
Grüsse aus Samoreau, Frankreich.0 -
[quote="Samoreen" wrote:
I never set this option myself. So I'm wondering whether the installation of version 9.1 changed the default ICC Profile in the output settings for the TIFF 16-bit Full Size preset?
Just got the following answer from the support:
We have found several similar cases and confirmed the issue to be occuring when the profile is embedded. We have reported a bug to R&D that recipes are being changed automatically from previous settings.
So if I read this correctly, the profile in my process settings was correctly set to Prophoto but was reset to "Embed Camera Profile" after the update, as I suspected. This was also probably the case for Wolfgang.0 -
[quote="Samoreen" wrote:
[quote="Samoreen" wrote:
The problem occurs when using the "Embed Camera Profile" option. No problem when specifying another profile like Prophoto for example.
I never set this option myself. So I'm wondering whether the installation of version 9.1 changed the default ICC Profile in the output settings for the TIFF 16-bit Full Size preset?
Well, it seems that this problem (which appeared in version 9.1, was described in case #215241 and was acknowledged) is still there in version 10. After the upgrade, the ICC profile in my recipes were replaced with "Embed Camera Profile" which doesn't make sense. How long will it take to fix this ?0
Post is closed for comments.
Comments
23 comments