Antonio Chagin
Member
Jack thanks for the info. Most appreciated.
Great to see you here. Join our insightful photographic forum today and start tapping into a huge wealth of photographic knowledge. Completing our simple registration process will allow you to gain access to exclusive content, add your own topics and posts, share your work and connect with other members through your own private inbox! And don’t forget to say hi!
I absolutely agree that LR has more total resources for learning, but do you really need many resources or just a few good ones?I have LR4 and DxO-7 and I have used C1 in the past when it was included with my M8. Though I can’t say I’m proficient with any of them I can say that LR seems to be easier to use and navigate. It’s also much more supported on the web for learning and that’s important to me. Even so I decided to try this new version of C1v7 and all I can say is wow! The default NR compared with the other two is very impressive.
BTW: I'm using OS 10.8.2 on a 2009 MacPro Quad w/12gb of RAM with all three apps (C1/DxO/LR) running and so far I haven't crashed.
Tip for anyone who wants to keep a V6 version of the file. Open the session, select the file, Right Click, Clone Variant, upgrade the variant to V7. Now you have both versions.Hi Paul:
- good news: this is not the way a properly functioning installation of v7 works
- bad news: I can't explain why this is happening on your system. I'd suggest a clean install (removing the extra app support and pref files) and if it persists start a support case.
When a properly functioning v7 installation looks at an image that was adjusted in v6 it will be rendered effectively identically to the way v6 rendered it. ONLY when you push the "upgrade to v7" does it change, in accordance to the new math available in v7.
Jack: you in fact CAN revert an image that was upgraded to v7 back to the math of v6. Change preferences: default rendering to v6 and then create a "new variant" and (if desired) copy and apply the v7 upgraded settings to the v6 image (e.g. crop/rotation etc). This won't be a popularly used work around though given how universally better the v7 math is than the v6 math.
I thougt clone variant made a virtual copy of the file, not a duplicate. For example (at least in V6) you couldn't colour tag the variant different to the original as they were one and the same file. Would be good if all this has changed in V7?Tip for anyone who wants to keep a V6 version of the file. Open the session, select the file, Right Click, Clone Variant, upgrade the variant to V7. Now you have both versions.
Great news that Doug as this was never possible in V6. Shame you still can't give the variant a different name though eg. shotX-original and shotX-moody etc for quick browsing reference.A variant in v7 CAN be assigned a different color tag than another variant of the same file. Said differently selecting a variant and setting a color tag on that variant has no impact on the color tag of the other variants of that image.
I'd definitely appreciate the ability to accomplish that goal. But it would have to be done in such a way that the name of the underlying raw file was not obscured. The entire point is there is only one raw file, so anything that makes it less transparent that there is only one raw file will confuse many users.Great news that Doug as this was never possible in V6. Shame you still can't give the variant a different name though eg. shotX-original and shotX-moody etc for quick browsing reference.
Edit: I see now you are comparing v6 with v7(with v6 engine) and not v6 engine with v7 engine. Sorry for the confusion....sorry, didn't have the time to follow the post… but this is in addition to what i described before.
mostly with b&W conversions. first is v6 and second v7. anyone any idea ?
If maintaining the same look as before is important then you have two options:
- leave the image in v6 engine; it won't change one bit
- make a variant, upgrade the engine of the variant to v7, and adjust (manually) to match as much as two different engines can
Paul: again, that's not normal or expected. You're experiencing some bug. Either uninstall v7, go back to v6 for now and put your head in the sand and presumably it will be fixed. OR stay on v7 and start a support case so you can help them figure out what's going on with your installation (because it's not normal). I'd prefer the later since I've not seen this bug reported elsewhere it could be a pretty unique bug which, if you don't repot it, might not be fixed quickly. But of course your job is not software testing, so it's perfectly understandable if you just want to give up and go to v6 for now.ok, thanks Doug but I may give up at this point and see what the next iteration brings up…
one last try: mabe it's because of my faulty english… did you look at the picture ? the upgrade option is still there. the file is UNTOUCHED and left in the v6 engine. it is not upgraded to v7 engine. so it should be displayed like in v6.
and as you say: "leave the image in v6 engine; it won't change one bit" hey…. IT CHANGED… as one can see….
so end of the story up until now... using CAPTURE ONE 7 means you throw away all the adjustments/looks/styles you build up over the years ? that's the main point !!!