C1 14.3 Exporter severely flawed when exporting variants and other serious bugs and flaws
Seriously! Please fix!
- I work a lot with C1 image variants for cropping. With the new export dialogue, when it is set to "overwrite", variants can not be exported as each variant is replaced by the next one and you end up with one image representing the last variant. This is a severe flaw and has cost me a lot of trouble the past two weeks since I did not notice and now I have to go back and see with clients what they actually received. It's a bug that is worse than the broken image one some years ago (the one where some, but not all images would have lines of broken pixels, usually a single line of pixels not visible in many previews). The really bad thing is: to change be behavior from "overwrite" to "suffix" I now have to enter each and every receipe and change it there. The overwrite function should be a "set and forget" feature, unfortunately, it is now a feature that completely ruins my workflow. I have about 50 export recipes and changing them leads to a complete mess and mistakes. This system is unworkable for studios with more than 1 person, as it will flaw image deliveries since people are unaware of the settings. Please make the behavior for "overwrite vs suffix" global!!! Adobe Lightroom does variant in export right for years now!
- Same for the whole export destination: I used to set a global destination and then set subfolders to this destination conveniently in the C1 export tab. The problem is: each recipe now has its own destination. I have to check each one every time! The only global destination I can set is the default one, but I also have to change that in each an every recipe. A nightmare. I reverted to setting them ALL to default. However, usually I need to export subgroups of images to different folders. Now I have to direct the destination for each group by changing the default destination. That is loads of clicks. To make it worse, you've included one of these warning popups that warn be about changing the default destination EACH and EVERY time. Seriously - that is a workflow nightmare.
- As mentioned before in other posts: we live in times with 32 inch screens. Making a workflow such that you need to click in the top left corner to chose your recipe and then click in the bottom right corner to export is just not an option, I'm sorry. I get a tennis arm from that. Pleas fix what was beautifully working.
- Also: who needs dedicated export window! That is what I loved about C1 and hated about Adobe LR. Also: tabs are good! Still in 2021! Why not tabs?
- Consequently: the exporter pop up window also means I have even less room to see all my recipes. This is bad, I have many. The list is absolutely tiny, especially on a 32 inch 4k screen.
- And by the way: where is the export queue? I was using it all the time. I now have only an export bar that has next to no info on what is going on.
In a nutshell: with the new exporter you made one step ahead and about 3 steps back. Please make sure that this software does not need a PhD to run. Right now I cannot tell my assistent to export sth without going into intricate descriptions about the logic behind the C1 exporter. As of now, C1 can easily ruin a job by someone delivering the wrong set of images without even knowing. I cannot afford to check each and every export to make sure that no error occurred.
Also: try to get less clicks instead of more! Please, I'm serious! This is a thing that always annoyed me with Capture One. Lots of things require lots fo clicks, if you have to work days in a row for a project each and every click is relevant.
I still think C1 is the best Raw Converter on the market. And that is why I was so disappointed after the last update.
Thank you!!
-
Hi, would you be able to submit this as a support ticket? I think this is best handed over the the development team.
Regards
0 -
Thanks, good input. Will do!
0 -
+1
Written very well and I 100% agree.
0 -
I believe C1 are aware of the issues, but reporting them directly will help. I am sure this is a priority for them.
0 -
Yes, they are:
https://learn.captureone.com/blog-posts/we-hear-you/
I hope they will solve all the issues very soon.
0 -
Excellent - I did not see that!
I appreciate that one will be able to integrate Export Tools in the main UI as Tabs. They did not comment on the variant overwrite problem however. Anyhow, I submitted a support request based on my text above.
Also: they seem to now go via Tokens to handle subfolder management upon export. I do not like that. Too complicated.
0 -
With the new export dialogue, when it is set to "overwrite", variants can not be exported as each variant is replaced by the next one end you end up with one image representing the last variant. This is a severe flaw and has cost me a lot of trouble the past two weeks since I did not notice and now I have to go back and see with clients what they actually received.
Severe flaw? What do you expect when you set that option to "overwrite" and not to "skip" or "add suffix"? The flaw probably is in your thinking and maybe not checking the output.
Also, I'm not sure because I use rather simple export concepts, but you could set the export files name to, say, your job or collection name by using tokens. So, if you had a photo in two different collections, you'd get tow differently named export files.
The more I read about many people complaining to have lost the "old way" of 2 tab exporting which were divided into even more tabs (and opposite of a transparent process imo), the more I see the new way of export not necessarily better, but some parts of it are simpler. Meaning "more easy to understand for me".
0 -
Conrad,
Option: Overwrite: I think you could use the token "Variant position" for the output file name to distinguish different variants of an image.
Joachim,
Seriously? What has the new overwrite option, which requires additional changes by the user to work for variant exporting and which was not immediately recognized by the user, to do with your preference of the "simpler" modal dialog?
0 -
BeO, the new overwrite function has not necessarily something to do with (in my eyes) simpler export functions. It just takes away the hassle to delete the old suffix versions and gives me the option to decide what to do with duplicates. However, seeing new export functions and not looking into them, not reading "what's new" notes, not consuming the webinar with David - I'm not blaming anybody in this forum, but some questions and remarks tell me "somebody was just jumping into a new version, believing and expecting everything will just work as before."
Come on, we all experienced situations when Apple took away some apps, some commands, some "established workflows", and we needed to adapt. People were complaining about loosing their way of workflow but did C1 ever promise "set up your workflow once and it will remain stable for eternity"?
When the software I'm working with to earn my money comes out with an new version, I first read the release notes, read in the new manual how things will change and if I have some questions, I get in touch with the excellent support of the company. If everything appears to look good, I give my OK to our IT guys to run the update procedure. After that update I carefully check our recipes, job options, settings and routines, if they work the way they used to. I always prefer "prepare" against "repair". That update costs us about 10× of a C1 update and it would be difficult to "just exchange it to the older version". I'm sorry to say so, but a couple of posters might call themselves professionals, but act in a different way. It's like "No backup, no pity" – when I need an app professionally, I sure can complain after a bad update, but that will not help my clients. It's like going to a shooting without spare batteries, broken lenses... Sorry, I sound like a bloody teacher, but I simply understand the reasons of being careless the it comes to C1 updates. I sort of work with this unstable app and I'm glad not depending on it. I don't want to defend C1, some bugs and quirks will retire only after a long life full of working as pita.
Last thing: As far as I can see, C1 is already aware of the troubles their decision caused. One can work with the older version (at least the ones who did a backup of their catalogs before updating) and maybe a fix is on it's way.
0 -
It‘s simple: assume you have 1 image and you generate 1 additional variant. You wish to keep export function as “overwrite”. When you export both images, the variant will overwrite the original and you end up with one image (the variant). I’m sorry, but no software I know does that, it’s a flaw in the logic. Lightroom handled this well since day one, no tokens needed. This is so damn basic I don’t know what to say.
@BeO: I agree, it seems to be possible to discriminate variants with a naming token. But you need to know this and you need to permanently have this token active. More things to go wrong and more thinks to remember. Not elegant.
0 -
I don't generally disagree with the procedure you describe, however even if you prepare with a considerable amount of work you still might find out that C1 has removed something which you relied on, and there is no alternative or not a good one or not described and a bad update path. Then you would complain. Rightfully, imo.
And the level of well thought through changes and an easy "update path" you could expect from a professional software company is higher than the level of well-prepared update testing on the users side.
You are in a luxurious situation,
(1) you like the modal window exporter stuff and(2)
I sort of work with this unstable app and I'm glad not depending on it.
cheers
BeO0 -
Conrad, what does LR do wrt. naming in this case?
0 -
BeO, it appends a sequence just like C1 does in suffix mode. So if you have a file A plus a virtual copy it exports the as A and A-1. If you realize you want to change sth and reexport it will ask you wether you’d like to overwrite, you end up with two files.
In Capture One in overwrite mode, when you have a file named A and 1 variant, you get 1 file exported named A, but it represents the last variant, not the original. Same happens if you re-export.
Funny thing: if you have 1 file with x number of variants, it exports them all (so 1+x) but overwrites x times. That’s nonsense in my opinion.
0 -
Hi Conrad,
Yes, if you use the token "-Variant position" you have almost (but not quite) the same.
0 -
I agree, the latest version is a big step back. The loss of the Output and Batch Queue tabs is a huge backward step for me too. It seems in the march towards making the product appealing to Lightroom users Capture One has forgotten what its traditional professional user base need.
0
Post ist für Kommentare geschlossen.
Kommentare
15 Kommentare