CaptureOne v20 does not always apply saved defaults
Before I open a support ticket on this I thought I'd see if I was missing something....
I shoot with a Sony a6000 and a Sony a6500. I am finding that C1 v20 applies saved defaults (curve, clarity, etc.) to new images from my a6500 but not from my a6000. Am I missing something?
Paul
I shoot with a Sony a6000 and a Sony a6500. I am finding that C1 v20 applies saved defaults (curve, clarity, etc.) to new images from my a6500 but not from my a6000. Am I missing something?
Paul
0
-
Were the defaults for the A6000 saved and flagged as defaults for the camera?
Were they set up in V12 and have they been carried forward to V20?
In WIndows you should find the Default settings files here.
C:\Users\[User Name]\AppData\Local\CaptureOne\Defaults
By tool (folder for each tool) and then by camera.
If you see relevant looking field in there for both cameras then maybe it would be worth comparing the names of the files to see if they match (one assumes) the names of the cameras identified in the Base Characteristics tool.
HTH.
Grant0 -
As Grant pointed out, you perhaps saved new defaults while working with an A6500 raw file. Note that these new defaults are specific for that camera and you have to redo the work for your other camera(s).
Summary: adjustments defaults are camera-specific.0 -
1. I had saved defaults for both cameras in v12 and they were working correctly.
2. When I upgraded from v12 to v20, I am fairly sure that initially neither camera's previously saved defaults were being applied to new images. However, after I re-saved defaults for both cameras C1 is now correctly applying the saved defaults to new images from the a6500 but not to the a6000. If it matters, the upgrade from v12 to v20 was a bit funky since I had v20 beta installed and had to uninstall it and reinstall v20. Until I uninstalled v20 beta, my fresh v20 non-beta would report as beta. This might have wiped my defaults, but does not explain why freshly saved defaults are not being applied to new images from the a6000.
3. Per the above, yes I have saved defaults for both cameras in C1 v20. Defaults for the a6500 are being applied. Those for the a6000 are not.
5. If I manually apply defaults for the a6000 to new or previously edited images, they are applied.
3. app data/local/captureone/defaults/curve and app data/local/captureone/defaults/clarity both show appropriate *.codefault files for the a6000 and a6500. The filenames are SonyA6000.codefault and SonyA6500.codefault. The revision date for SonyA6000.codefault is yesterday so it appears to have been properly saved.
4. I don't know if this is related, but should you be able to highlight multiple images from the same camera, select "apply defaults" and have them applied to all images? They are only applied to the first image selected.
Time for a support ticket? Fortunately, the bulk of my shooting is on the a6500 so this is an annoying issue but not a serious one. To me, anyway.
Paul0 -
If you go to one of the codefaults files for the 6000 and open it with Edit what information does it list? 0 -
SFA wrote:
If you go to one of the codefaults files for the 6000 and open it with Edit what information does it list?
SonyA6000.codefault contents:
<?xml version="1.0"?>
<SL Engine="1200">
<E K="Clarity" V="18.2741107940674" />
<E K="ClarityMethod" V="3" />
<E K="ClarityStructure" V="18.2741107940674" />
<E K="Name" V="SonyA6000" />
<E K="StyleSource" V="Clarity" />
<E K="UUID" V="07D1DB34-4C52-401A-AABE-EF83DA8B04E7" />
</SL>
SonyA6500.codefault contents:
<?xml version="1.0"?>
<SL Engine="1300">
<E K="Clarity" V="18.2741088867188" />
<E K="ClarityMethod" V="0" />
<E K="ClarityStructure" V="18.2741107940674" />
<E K="Name" V="SonyA6500" />
<E K="StyleSource" V="Clarity" />
<E K="UUID" V="1D725415-245E-4B0D-AAF6-055DFD20C14D" />
</SL>0 -
This is speculation.
The default shown for the 6000 seems to to ba associated with the Processing Engine for V12 (1200) whereas the 6500 file seems to show 1300 (V20 as marketed but V13 as a working project and internal naming.)
On that basis I would be tempted to wonder whether that holds any significance for what you are seeing.
Have you as yet imported any 6000 images into V20?
The defaults are normally applied at Import (or, for sessions, possibly at first Edit given that importing is not a requirement for sessions.)
Grant0 -
1. As an experiment, I edited the "1200" parameter in the a6000 codefault file to "1300" and saved it. The default was still not applied to new images.
2. I then reset the defaults for a6000 in the clarity and curve function (which actually deletes the codefult file). I then re-saved the defaults for curve and clarity and now they ARE being applied to new images.
So it would appear that there was some incompatibility in codefault files from v12 that prevented them from being applied in v20?
As a precaution, I manually deleted all default files and then saved them again.
Paul0 -
pgoelz wrote:
4. I don't know if this is related, but should you be able to highlight multiple images from the same camera, select "apply defaults" and have them applied to all images? They are only applied to the first image selected.
Yes.
Defaults apply to new images plus those selected when applying the new defaults when saving them.0 -
Paul_Steunebrink wrote:
pgoelz wrote:
4. I don't know if this is related, but should you be able to highlight multiple images from the same camera, select "apply defaults" and have them applied to all images? They are only applied to the first image selected.
Yes.
Defaults apply to new images plus those selected when applying the new defaults when saving them.
Well.... it doesn't work. And hasn't since at least late in the v12 era too. I click the first image in a series, shift click the last, then click "apply defaults" for (for example) curve or clarity and the defaults are only applied to the first image in the series. Ditto for highlighting a series and then changing the curve manually. ??
This may depend on whether there have been any previous adjustments.... I'll have to test some more. But I know it didn't work when I tried it multiple times.
Paul0 -
It seems that the Edit all selected variants option is not working correctly, assuming it is enabled. Do you encounter this with other operations as well, processing for example, that only the primary variant is processed? 0 -
Paul_Steunebrink wrote:
It seems that the Edit all selected variants option is not working correctly, assuming it is enabled. Do you encounter this with other operations as well, processing for example, that only the primary variant is processed?
Yes, definitely either "edit all selected" is broken or we are not understanding how it is supposed to work. However, there have been a couple times in v12 and now in v20 when "edit all selected" did work and I am not fully aware of what the difference was. I think it might have something to do with whether or not there have been previous adjustments and/or default settings applied. I'll try to remember to test that the next time I import a batch of images.
Paul0
Post ist für Kommentare geschlossen.
Kommentare
11 Kommentare