Cannot get my camera's ICC profile to stick
Under Quick-->Base Characteristics, I must select my Canon 20D's ICC profile (or a Magne Profile) every time I start up C1 -- how do I get it to "remember" my camera profile -- the older version of C1 remembered it.??
(I am a new user -- and I could not locate the answer in the manual)
MikeSp
(I am a new user -- and I could not locate the answer in the manual)
MikeSp
0
-
It is not possible in CO4 to preset a certain profile with a camera as preference. This is a feature request done by numerous users already and we'll have to see what Phase One is coming up with in an update release. 0 -
[quote="Paul Steunebrink" wrote:
It is not possible in CO4 to preset a certain profile with a camera as preference. This is a feature request done by numerous users already and we'll have to see what Phase One is coming up with in an update release.
Are you sure? I also thought so at first, but when I look at the ICC profiles it states generic and A700 underneath...and when I manually select the A700 ICC profile colours do not change at all...so isn't the profile not selected automatically anyway?
regards,
Bernd0 -
[quote="ausgezeichnet" wrote:
[quote="Paul Steunebrink" wrote:
It is not possible in CO4 to preset a certain profile with a camera as preference. This is a feature request done by numerous users already and we'll have to see what Phase One is coming up with in an update release.
Are you sure? I also thought so at first, but when I look at the ICC profiles it states generic and A700 underneath...and when I manually select the A700 ICC profile colours do not change at all...so isn't the profile not selected automatically anyway?
regards,
Bernd
The Generic <camera> profile is selected automatic indeed with the raw file. But in case you have more profiles for a specific camera, CO4 currently does not allow or enable you to set a preferred profile as default.
Among some users there has been confusion regarding the Generic profile in that they overlook the fact that it is generic but specific for their camera type and not generic in general.0 -
Paul--I appreciate your answers, but wonder IF it is possible for a minor future update to include a way to have C1 v4 default to the same camera ICC profile (from the selections) every time C1 starts up -- it would be the same profile that most of us use on EVERY image processed -- it is a royal PITA to (at my tender age) remember every time I start up C1 v4 OR even when chosing a new batch of images to process that I need to AGAIN go back and put in the camera's ICC profile-- that was not necessary in C1 V3.84 (That is one of the reasons that I find myself reverting back to the earlier version of C1 -- it works faster for me. YMMV. Perhaps this is because I am using a PC instead of a Mac...
Cheers,
MikeSp0 -
Mike, as Paul has said, this 'profile not sticking' issue is one of the 4 or 5 big complaints from users since the release of Beta1.
It is been complained about many times, and we are all waiting to see if the moaning is going to bear any fruit with the next version of V4.
All we want are 4 or 5 'trivial' features to be retained from v3. Not much to ask you would think!0 -
[quote="MikeSp" wrote:
[...]
even when chosing a new batch of images to process that I need to AGAIN go back and put in the camera's ICC profile
[...]
Perhaps this is because I am using a PC instead of a Mac...
[...]
Mike,
Any help to emphasize a request is always welcome, but I think it can't be that bad as you describe.
If you start CO4 again, whether to view or re-process your images, the adjustments which include the camera profile should still be there.
And I did not notice any difference between PC and Mac regarding this profile behavior.
My workaround is the following routine:
- open folder in CO4 with new images
- set correct profile for first image
- select all images (Ctrl+A)
- copy and apply adjustments (=only profile change) to all images (Shift+Ctrl+C, Shift+Ctrl+V respectively)
Continue working as nothing happened 😊0 -
Paul,
Yes, we have all to find workarounds for these 'missing' v3 features. They can all be worked around, but the question asked many times is 'why should we have to'?
Iain
PS. Another workaround to this particular issue, is to rename your favourite profile as the default profile name for your camera, e.g CanonEOS5D-Generic.0 -
Iain,
Personally I am less focused on the 'why should we have to' question. I just create a workaround or deal with a limitation in another way (sometimes we have to accept things how they are) and put my energy and creativity in something else to achieve rewarding results. It is my intention not to depend to much someone else' quirks.
In the end, it is the manufacturers business case. The better the product, the more users and buyers.
Regarding Phase One and it's CO product: using it since v1 my experience is that it is an odd niche product, very nice though, it has to go a long way but eventually they will get it right. It takes time, a lot of time (and therefore faith and patience from their users).
Hope this is not to philosophical. 😊
Stay tuned.0 -
[quote="Paul Steunebrink" wrote:
Iain,
Personally I am less focused on the 'why should we have to' question. I just create a workaround or deal with a limitation in another way (sometimes we have to accept things how they are) and put my energy and creativity in something else to achieve rewarding results. It is my intention not to depend to much someone else' quirks.
Paul, I am not 'focussed' on 'why we should have to', I am simply asking the question. I and all other users have obviously had to find a workaround for the missing features otherwise we wouldn't still be here on this forum trying to help others. For example, I suggested the renaming of profile as a workaround to the particular problem being discussed here.
The issue here is - as you well know - that CO has 'lost' some of the simple features that made it so good from a workflow point of view in the transition to v4. The moans have not been about new features that PO could have incorporated - that would be different - they have been about high-productivity features that we had all become used to in v3LE.[quote="Paul Steunebrink" wrote:
Regarding Phase One and it's CO product: using it since v1 my experience is that it is an odd niche product, very nice though, it has to go a long way but eventually they will get it right. It takes time, a lot of time (and therefore faith and patience from their users).
and that is the point above. They had got it right in V3 already! Why have some of the important features been left out in v4?
I'm afraid I'm still mystified by this whole subject!
Iain0 -
Consider this post another request to allow for the user to attach a default profile to a particular camera model. Too many "workarounds" make for a bogged down workflow. 0 -
I am a very new user to C1-4.01. I am evaluating the product as an alternate to Camera Raw within my CS3 work flow and possibly paving the way to an update to the Pro depending on features, ease of use,.....
I have been attracted to this product on the basis of reports on the quality of the conversion and the ease of use of basic adjustments - in other words make life easy with great results within a very specific and narrow scope. I have also been warned off in many forums about the poor support received from the company and the lack of feed-back, timely updates..... I do not have any preconception of what to expect in terms of the features present in previous version so I am starting fresh so to speak.
My expectation is for a converter that has limited functionality but does what it does well, fast and very easily for the operator. My first look has been positive.
The issue of C1 not defaulting to the default camera profile on a "per camera basis" seems irksome and unnecessary. Devil is in the details. I think that to meet its own self-process image, the company should have no choice but fix this. As I said limited features but these have to be perfect, otherwise there is no way that the product can survive the like of Camera Raw/Lightrooom, Silkypix, ......... and compete for my $$$.
Cheers,0 -
[quote="imacken" wrote:
Mike, as Paul has said, this 'profile not sticking' issue is one of the 4 or 5 big complaints from users since the release of Beta1.
It is been complained about many times, and we are all waiting to see if the moaning is going to bear any fruit with the next version of V4.
All we want are 4 or 5 'trivial' features to be retained from v3. Not much to ask you would think!
Interesting - I've just opened a support case for this, after installing 4.6.3 for the first time, after using 3.7.7 for ages.
I use a Magne Nilsen profile for my Canon 5D, and it's a pain to have to select it each time.
Fortunately, I'm a low-volume user and use Photoshop CS3, so I can just ask C1 to 'embed' its own camera profile in the TIF output file, instead of converting to a working space. Then do 'edit->assign profile' in PS to insert the profile I want into the TIF file, then convert to whatever working space I want e.g. ProPhoto RGB. But these are things I didn't have to do, or think about, with C1 3.x. BTW I prefer to convert to working space in PS, instead of in C1, as the Adobe Color Engine (ACE) is reputed to be better than the one built into the Windows OS (I'm on XP SP3).
Having a preset on the Base Characteristics options in Quick tab shouldn't be difficult: the other options like Exposure already allow for presets. I just hope that P1 look at the number of support cases raised and put this in some time.0 -
As Paul said...sometimes changes are because of user problems/requests. While your workflow might want this seting to be sticky, others might have support issues with it if they forget to reset the profile. And to reitierate, if you use a third party profile 100% of the time and don't want to deal with the default PhaseOne profile...renaming should work (and I haven't tried doing that)....the program does not need to be changed to accomplish that (unless renaming doesn't work in the anticipated manner.
Also, placing something here in the user-to-user forum is not the same as creating a support case and requesting a feature change. If most users request something similar, it's generally released.
Here, in a multiuser environment, sticky profiles were not a boon...however, we managed to deal with the issue....and can again if there's a concensus.0
Post is closed for comments.
Comments
13 comments