Random duplicate clone variants
I use an external app for editing my NEFs, and before upgrading to v22 it was pretty reliable.
Now, however, I keep getting random duplicate TIFs, as if I have two variants, but I've only ever hit EDIT once and never cloned the image in Capture One.
It happens to maybe three or four out of 20 edited images, and I haven't been able to work out why yet. There's only one TIF file in the folder with the NEFs, but two variants.
The details of the two variants are identical: same timestamp, same EXIF details, etc. There's two thumbnail files, but only one each .cop and .cof files.
So, it's made a second thumbnail and thinks there's a variant, but there was never a request for one and the two variants don't differ.
What's up with this?
-
> NFGphoto: ...the two variants are identical...
Run a sha256 (or similar) check on the image files to prove they are identical. Same metadata shown in Capture One may not prove much.
0 -
C1 is showing two variants for one file. There's no second file to run a checksum on. ¯\_(ツ)_/¯
0 -
> NFGphoto: ...never cloned the image in Capture One
Capture One's clone variant function creates a variant, it does not create an image file. A variant is a set of adjustment data kept in Capture One's database. Even an unedited image has a set of adjustment data. Capture One basically reads an image file and applies a set of adjustment data to show you an image. A single image file and multiple sets of adjustment data means Capture One can show you multiple "variants" from that image file.
In a straight forward scenario Capture One displays one image per image file. Make sure you understand that each image you see is a displayed variant and why. It is a common misconception that only the second, third, fourth,... image from one image file are called variants, some users fail to grasp that the "first" image is also a variant in Capture One lingo.This is important if you want to understand Capture One documentation where "variant" has the meaning just explained.
0 -
> NFGphoto: There's no second file to run a checksum on
Hmm, I may have misunderstood your first post where you wrote: "I keep getting random duplicate TIFs"
That implies two (or possibly more) TIFs in my mind, and you claimed them to be identical based on metadata. Thus my sha256 suggestion.
0 -
Indeed, you may have misunderstood my post:
> There's only one TIF file in the folder with the NEFs, but two variants.
Rephrasing the whole thing:
The little multiple-variant icon in the top left corner. If I click it, I get two identical variants. All the available metadata within Capture One says that they are identical. I didn't clone it, why does the 2nd variant exist?
0 -
> NFGphoto: All the available metadata within Capture One says that they are identical
Nothing exceptional there, there is one set of metadata per image file. It is a long standing wish that Capture One should have one set of metadata per variant.
0 -
> Nothing exceptional there, there is one set of metadata per image file.
There's only one TIF file. There's only one pair of cof/cop files. I didn't create a variant, this little icon and the second thumbnail file appeared without any action by me.
So, yeah, it's exceptional.0 -
> NFGphoto: ...I didn't create a variant
I can't speculate in "I-did-not-do-anything" :-) You may try to remove the keyboard shortcuts to prevent unintentional activation.
0 -
My friend, I've been using C1 for twelve years. This has never happened before. It's not me and my clumsy meatslab fingers.
1 -
Its a bug. Happens every time when I open image to photoshop. It also says every time on event log that "The created image is not supported by Capture On" (even they work fine in C1 too). Propably only affecting windows version as my mac works fine.
0
Post is closed for comments.
Comments
10 comments