trashing any file moves compare varient to trash!
Firstly thanks for listening to users re the copying over of a rating of the last shot image when shooting tethered- why it was reimplemented in the first place i dont know. I have noticed a major issue with 5.1.1 - when you move an image to the trash and have a compare varient set both are moved to the trash, even though the compare varient is not selected. How stupid is that? When i trash an image i always look to check how many i have selected; if it says one image selected i presume i am only moving 1 image to the trash. I have raised the issue of unselected compare varients rating being changed when edit primary only is off in a support case but this has not changed either. That you might accidently move an important capture into the session trash is beyond belief. the work around requires deslecting the compare varient, trashing the file, reselecting the compare varient (a bit of a pain when the compare varient is 200 captures back). Sort it out.
0
-
What else would you expect?
From the user guide:An important feature of Capture One 5 is the ability to create Variants. Each of these variants is a duplication of the settings file, not the RAW image data. Multiple variants can be created which provides a multiple variations of your file, in adjustments and any other setting.. Since they are only a few kilobytes each they take up very little space on the hard drive.
And:A variant is actually a copy of the settings used to create an image preview; it is not a duplicate of the original file. This means that it is possible to create multiple image variants without using any significant disk space.
If you delete the original file, what purpose would the variants left behind (to use your thinking) serve? They'd be settings files that related to nothing whatsoever.0 -
You've completely misunderstood me keith. The compare variant option is used when you want to compare an older image to what you are currently shooting, the compare varient stays alongside your current image when shooting tethered. Its not a varient in the proper sense. Did you actually try this for yourself before you posted? It moves the raw, not a set of settings. 0 -
Hmm, a bit confusing perhaps but the difference in terms here is subtle.
The Compare Variant and Image Variant can certainly be cause for confusion.
The Compare Variant is simply a selected image with staying power. As such, it is in fact selected. So deleting the selected images would include that Compare Variant.
The Image Variant is a settings variation of a RAW file and deleting one of these variants is different than deleting a RAW file. Deleting a file is just that, deleting a file. If you are physically moving the RAW to the trash then it stands to reason all the settings would go with it, the Variants are "Settings" so they go to.
If you have 3 variants of a single RAW and don't want one, just select it and hit "Delete". This will edit the settings of the RAW to delete the variant you don't want and remove it from the thumbnail view.0 -
Drew, I am clear on the difference between compare varients and image varients unlike the inital responder - I use C1 on a daily basis so I have a fairly good understanding of the software.
"The Compare Variant is simply a selected image with staying power. As such, it is in fact selected. So deleting the selected images would include that Compare Variant."
Drew - above the browser tab you will see that information of the number of captures and number of selected captures in the current folder e.g. "1 of 30 images selected". This figure ("selected") does not take into account the compare varient. I would assume if the software is informing me i have 1image selected i have one image selected. You explanation of the term directly contradicts the softwares, and strikes me as more than a little laxidasical when it comes to peoples files ending up in the session trash. When you are in primary view it would be fairly easy to fail to realise that you have a compare varient selected (by pressing enter) and trash that file.
Also the fact that the compare varient is sucessitible to any tagging makes it impossible to edit multiple images in comparison to the compare varient without changing the rating you have already given to the compare varient.
Is it really so difficult to understand why this is frustrating?0 -
Also drew i'd point out that the compare varient does not move when dragging other selected files to another folder (e.g. the move to folder). So it is not behaving consistently i.e. always as if it is selected. It moves to the trash if you press apple+delete - but not if you drag a bunch of captures to the trash. In fact when you drag a capture over to the trash inthe library tab you get a little red circle appearing with the number of files you are dragging, presumably as phase acknowleges its important you know how many files you are moving ! 0 -
Sometimes one can learn a lot when you least expect it. When I take out the anger of the OP, reward the OP and other posters gratefully and gracefully for their admission, I conclude:
- the Variants term is used in two slightly different concept (Compare versus Image Variant)
- the Compare Variant is not counted for in the 'x of y selected' indicator
- the Compare Variant though is sometimes treated as selected for actions like trash, move to folder, rating and tagging; but not for processing (with Edit All Selected in ON position) to just name a few.
To my humble opinion it is best to consider the Edit All Selected in the OFF position when working with the Compare Variant to prevent disappointing results.
I will open a support case with Phase One to draw their attention to some inconsistency here.
And to the OP: thanks for posting, please come back, but threat your fellow users with a bit more respect for their free effort. After all, this is a user-to-user forum, helping each other because we are in the same boat. You can always open a case to direct your concerns to Phase One directly to get their reply. Thanks again.0 -
[quote="xmmx" wrote:
Drew, I am clear on the difference between compare varients and image varients unlike the inital responder - I use C1 on a daily basis so I have a fairly good understanding of the software.
Perhaps my description wasn't directly for your benefit but the benefit of others that may be confused by your post. 😉
I'll take a look into Paul's comprehensive findings today and let you know what I find and if future changes are possible.0 -
[quote="xmmx" wrote:
Drew, I am clear on the difference between compare varients and image varients unlike the inital responder
Yes, I misunderstood your problem (although of course I understand the difference between the variants) - but rest assured I won't be looking to help you again any time soon, because your attitude stinks.0 -
"What else would you expect?"
Keith, I actually found your tone deeply abrupt and patronising ( more so as you didn't appear to know what you were talking about - and I actually felt you presumed i didn't).
"although of course I understand the difference between the variants" You posted "Each of these variants is a duplication of the settings file, not the RAW image data" Not the case with the compare varient. Sorry you feel agreived by my response, but your advice was simply inaccurate. Its not that I dont appreciate being helped, but the fact that you begun by adressing me in such a derogatory patronising way. As for pointing out that you were wrong to Drew my point was that the majority of his initial post seemed to be geared towards you rather than me, when I was the one requesting attention.
Paul, Drew - I appreciate your input, sorry for any offence. Generally speaking I think if you understand the presure you can be under on a high profile shoot you can understand how aggravating it can be when software malfunctions/behaves in a counter intuitive/unexpected way. Loosing a crucial file can break someones career and i didn't feel this was taken seriously. I've raised issues about tagging the compare varient prior to 5.1.1 and nothing has been done about it.0 -
[quote="xmmx" wrote:
I've raised issues about tagging the compare varient prior to 5.1.1 and nothing has been done about it.
To be clear, the two support cases that were submitted by you listed the items that were fixed or pending a solution. As such, something has been done and is still being done on your behalf. Thank you for raising those cases.
In addition, the current issue was reported in a previous case but apparently never completely understood by the supporter, for that I apologize. If you would like to follow up with that case you are welcome to do so. In the meantime I will report the findings to the proper department.
Also, it is worth mentioning that we all can sympathize with a stressful or frustrating work situation. Despite that however, you still get more bees with honey... 😉0
Post is closed for comments.
Comments
10 comments