CO 7.1 strange greyed out menus
I installed 7.1 and on all my pictures in the Lens Correction tab: purple fringing, distortion, sharpness falloff and light falloff were greyed out. On top under profile it said: none. When I changed this to generic all menus became active again. But now under profile the option none was gone!!! This is completely crazy, I would now have to change profile in lens correction for every single picture from none to generic! 😕
Cheers, Bob.
Cheers, Bob.
0
-
Bob,
The function of this tool is specific to the File type and available Metadata.
You can of course apply the settings to one file and then Copy/Apply to the remaining files so you don't need to set this tool on a Per Image basis.0 -
Thank you for your reply Drew.
Maybe I was not sufficiently clear in what I said. I came from 7.0.2 and there ALL files had profile set to generic. It is only after installing 7.1 that suddenly this changed to none. Moreover, how is it possible to have none in the menu and once you change it to generic the option none is suddenly gone. Something is clearly wrong here. Until this is solved it's back to 7.0.2 for me, I do not want to have to manually reset all files which were already post-processed.
I think this also shows that CO is in urgent need of a decent and complete system for setting defaults. I know there are workarounds, and partial options, but that is just what they are, workarounds. There should be a window in the preferences or elsewhere where you can set all your defaults to be applied to all pictures.
Cheers, Bob0 -
Bob,
I think it would be best if you created a support case and provided a File with the settings (COS) file so that we can help you. What you are describing doesn't seem right so it's clear something is amiss.
You're welcome to use 7.0.2 but until we can identify for you what you are describing there is no way we can ensure it will be addressed.0 -
Drew,
I do not know how that is going to help. If I look at the .cop file of any of the pictures with the wrong settings in 7.1 then it is precisely the same .cop file as the one created when the picture was loaded in C1, namely in May 2011! So that very same .cop file will give the right settings in 7.0.2 and the wrong ones in 7.1! Also it is not one picture that has a problem it is thousands of pictures!! Now what does change is the .cos file of the pictures, that you can easily see from the "date modified" info. So I will send a picture + .cop + .cos file.
Cheers, Bob0 -
Bob,
You're right, I simply typed too fast.
Please provide us with the RAW and COS file so we can look into this for you.0 -
Bob,
I had a look at the files and this behavior is not generic to the software. It is specific to your files and the Lens used. We'll look into it further but at present it seems related to a non-Sony zoom lens at the root of the error.0 -
Drew, I already replied to support too, but let me reply here. There can be no valid reason why software works in a particular way up to 7.0.2 and then suddenly when in 7.1 something goes kaput it is supposed to be the fault of a lens or a specific file. Anyone can understand that this is completely illogical. Moreover, the lens being a non-Sony zoom lens (my only lenses are Carl Zeiss ZA's) has nothing to do with it because the problem occurs with all my lenses (ZA Distagon 24, ZA Planar 85, ZA Sonnar 135, ZA Vario-Sonnar 16-35 and ZA Vario-Sonnar 24-70) and they all are Sony-Zeiss lenses.
The problem is very clearly a software problem of C1, why otherwise would there be no problem in 7.0.2? The problem is that 7.1 destroys the setting of the chosen profile for lens correction of 7.0.2 and replaces this with "none". That is probably because you have changed the code to have the lens correction profile set to "none" as default. That is OK, however *it should not do this with files which have been treated already and where the setting has been explicitly set to generic by the user*. I think it is as clear as crystal that this is a code error! Just imagine, tomorrow you decide that you will no longer have say "classic" as default for clarity but rather "punch". Would you then consider it normal that, the moment people upgraded all their files suddenly are changed to "punch" completely in disregard of what they had chosen?
That the whole thing is a bug also follows from the following. The software starts up, you load some files and the profile reads "none", you click the menu and choose anything from that menu, e.g. "generic". Now, you change your mind and don't want generic but want "none", oops too bad none has disappeared from the menu, you are stuck with generic or anything else that still is available!!
Cheers, Bob.0 -
Bob,
Yes, of course. The issue is a bug in the software, a very strange and specific bug that we will continue to look into. All information that we have, provided by you or sourced elsewhere (in the 2 1/2 hours since you brought this to our attention) points towards the issue relating to the use of that specific lens.
I don't have an answer as to why at the moment but we're working on it and thank you for the files/support case.0 -
Thanks Drew,
I just sent further info to support and hope they can get this resolved quickly.
In spite of all this, let me restate what I have said before: the support of Phase One, both here on the forum and the "real support" on the website is without par. Congratulations!
Cheers, Bob0 -
Hi,
I believe this is not just limited to the setup of the OP, I'm seeing the same with my Canon 5D mkII and ES 24-105 f/4 IS USM config. If you reset the Lens Correction Adjustments, the setting jumps back to the "none" setting.
Still this could be useful for newly imported photos where you might not want any corrections applied to, unless you set it specifically, but it is weird the this is applied to all images after an application update.
cheers,
Ron0 -
Ron,
We'd love to have some examples from you through a support case.0 -
Dust removal is greyed for me out when making an LCC from an IQ160 back. What a pain!
I'll submit a ticket.
Maty0 -
[quote="NN634463706897550622UL" wrote:
Dust removal is greyed for me out when making an LCC from an IQ160 back.
Maty, are you on CO 7.1?0 -
[quote="Drew" wrote:
Ron,
We'd love to have some examples from you through a support case.
Thanks for your reply Drew, as soon as I'm back at my studio, I'll provide you with the images.
cheers,
Ron0 -
I have a similar case when working with raw files from a P45+:
I'm opening an old project (originally created in C1 6, then worked on in C1 7.01) in C1 7.1
Now my LCC "Enable Uniform Light" slider is greyed out. Even if I remove the LCC profile and re-apply it fresh the slider stays greyed out and at 0% (was at 75%).
I kept the C1 7.02 application on my computer so I can still open the session and the LCC tool works fine there but 7.02 is instable and difficult to work with. I'm forced to stick to 7.02 until this is solved.
Best regards,
Ariel0 -
You really need to talk to Tech support.
I seem to recall some comments on various threads that suggest keeping older releases of V7 on the machine when installing 7.1 may not be a great idea.
Grant Perkins0 -
will do. thanks for the advice. 0 -
Very disappointed. In 7.1.1 the problem is still not solved. Back to 7.0.2.
Cheers, Bob0 -
Here is my version of this same problem...i imagine this is an issue for all using the LCC feature on CO7....the worst thing is i cant get it to work in 7.0.2... and cant move the files into CO6.....WHAT TO DO!!
i am able to process a LCC but unable to apply it to images....the color and uniform light is not corrected. in fact it is greyed out. inoperable... as i have seen there is much talk about this problem more that a month ago yet i see no solution. infact the only suggestion of using 7.0.2 didnt work either...new session etc.
platform: Alpa
rodenstock 32mm
q180
shot to card very big problem with this camera...must use LCC every time!!!!! thank you, need this asap...R0 -
[quote="Robert1262" wrote:
Here is my version of this same problem...i imagine this is an issue for all using the LCC feature on CO7....the worst thing is i cant get it to work in 7.0.2... and cant move the files into CO6.....WHAT TO DO!!
i am able to process a LCC but unable to apply it to images....the color and uniform light is not corrected. in fact it is greyed out. inoperable... as i have seen there is much talk about this problem more that a month ago yet i see no solution. infact the only suggestion of using 7.0.2 didnt work either...new session etc.
platform: Alpa
rodenstock 32mm
q180
shot to card very big problem with this camera...must use LCC every time!!!!! thank you, need this asap...R
Can you update to 7.1.1? I feel that the LCC-greyed-out issue is worked on since 7.0.2.
You might also renew the session file and remove the .cos file for the image to be sure.0 -
I recall my original problem:
I installed 7.1 and on all my pictures in the Lens Correction tab: purple fringing, distortion, sharpness falloff and light falloff were greyed out. On top under profile it said: none. When I changed this to generic all menus became active again. But now under profile the option none was gone!!! This is completely crazy, I would now have to change profile in lens correction for every single picture from none to generic!
Has this been solved in 7.1.2. I am still on 7.02 since this was not solved in 7.1.1.
Thanks for any info, cheers, Bob.0 -
[quote="picman2" wrote:
I recall my original problem:
I installed 7.1 and on all my pictures in the Lens Correction tab: purple fringing, distortion, sharpness falloff and light falloff were greyed out. On top under profile it said: none. When I changed this to generic all menus became active again. But now under profile the option none was gone!!! This is completely crazy, I would now have to change profile in lens correction for every single picture from none to generic!
Has this been solved in 7.1.2. I am still on 7.02 since this was not solved in 7.1.1.
Thanks for any info, cheers, Bob.
We haven't seen this issue during release testing. No matter what, a lot of other issues have been solved, so I would highly recommend you to update to the newest release.0 -
Thanks for the reply Christian. Normally I would certainly give it a try, however this sentence in the release notes scares me a bit:
Catalogs and sessions opened in Capture One 7.1.2 cannot be used by earlier versions of the application. Back up the relevant catalogs and sessions if the ability to go back to 7.1.1 is required.
Cheers, Bob.0 -
OK, I gave it a try. Duplicated a number of folders with pictures, duplicated my main session, installed and started up 712, created a new session, opened up all the files from the duplicated folders and YIPEE, all seems to be well. I am now also on OSX 10.8.3 and the problem with the disappearance of extra layers seems to be gone too. So at the moment all is well. Thanks again!
Cheers, Bob.0 -
[quote="picman2" wrote:
... and the problem with the disappearance of extra layers seems to be gone too.
This was an issue solved with 7.1.2.0
Post ist für Kommentare geschlossen.
Kommentare
25 Kommentare