overwrite on export?
Is there any way to coerce/trick C1 20 into overwriting a JPG on export?
Last time I checked the answer was NO.
-
The answer is still no. Some users would like to be able to do that, though I am not one of them. If you want to add your voice to that, make a feature request.
Ian
0 -
As I feared.
After half a lifetime in the software industry I've come to view the "feature request" as only a little less futile than a letter to the President. :-)
3 -
Jim, after retiring from the software industry, I second your opinion. Too funny. When I was a ON1 PhotoRaw user, they had a way for people to vote up a feature request and when it hit a point, they would implement it. But I found that they just pretty much had their own ideas about what new and great features they would add (especially ON1) and how many existing things they would break when they did. The wacom tablet interface was broken for almost a year. Of course, not for everyone, just for me and a few others.
0 -
All of that, plus the fact that they know what people are saying in their forum - or at least they can, if they're interested.
1 -
I'm with you Jim. C1 is about the only program I have ever come across that does not allow an overwrite on export. Not touching the raw file I can understand, not allowing, even by a preferences switch with current practice the default, is just bloody mindedness. Unfortunately, like the chance of C1 ever writing a real "external plugin manager", I am afraid until the person whose fetish this is leaves C1, users can whistle.
If you look at LR irrational choices like this tend to be down to one powerful person on the team. The original lead engineer created LR as "anything but PS" which is why even the crop tool works the opposite way to PS and every other image editor :-)
I think we need to keep asking for these reasonable user requests and no one person lasts forever :-)
2 -
Could there be way to use some sort of shell script/command line/OS hook to do a quick file rename/delete at the time of export?
1 -
Bumping this thread, as an act of absolute futility, but also because I was just thinking yesterday of what an ungodly amount of pointless hoop-jumping this issue causes me.
I used to be a software developer; there has to be some way to solve this from the 'outside'. And I'm sitting here right now trying to think of one. But without a public plugin API, it could be really tough.
I totally agree with IanS above, this is just someone's religious conviction: "We never overwrite no matter what."
1 -
Agree completely on the desire to over write jpg's on export. The current method is highly sub-optimal.
1 -
I agree, this is just flogging a dead horse. Religious conviction rules.
And I also agree that it just causes so much irritation if, like me, it's how you work!
Software developers don't appreciate the effect that a tiny, easily addressable, issue like this has on a product's overall feel of quality. It just makes you think that the company doesn't care about their users.
1 -
For me it's no longer a little thing, and it actually has me thinking about moving to other software.
1 -
I've NEVER gotten the impression that Capture One cares about their CUSTOMERS, nee users. CUSTOMERS, those who provide a source of income for them......
Just the tone of the messages sent back from support requests tells you all you have to know.
0 -
I used to be a developer and worked for several software companies.
As a software product ages, it's more challenging to make a profit from upgrades. Eventually only critical bugs get fixed, and every proposed change or addition is subjected to a brutal analysis: how much will it cost to "implement" this new "feature", and how many upgrade sales might it generate?
This sort of makes sense, but it rules out small changes or additions like the one we're talking about. Developers might feel strongly about what they see as a useful improvement but aren't going to argue with marketing about it. And they can't just slip it in; everything new has to be disclosed to the testers.
The end result is that things like this never get 'fixed' because no one can prove they're worth it.
1 -
Hi Jim.
Like you I would really like the ability to set C1 to overwrite previous jpeg exports which I use in Final Cut Pro. It is so tedious to have to delete the original file and rename the new one so that the changes are sucked into FCPX. :-(
1 -
Sigh.
1 -
I also really want to overwrite feature. I asked this multiple times on forums/support etc since Capture One 8!
Every version over C1 is getting the software to work smarter and faster. But exporting and NOT overwriting will take extra time, specially when your working with photo album design.
So instead of adding so much cool new stuff please give us the option to overwrite files during export.
1 -
As a software developer myself, I would be very surprised if it takes more than a few hours to implement, test and document (unless the code is a mess and/or the devs are not that familiar with the code!).
2 -
Bumping this thread just to say that I'm moving on, and looking into Exposure X6, mainly because of this single, simple restriction in C1 and all the annoyance and wasted time it causes me.
For various reasons I often want to revisit my editing of raw files and create new JPGs. And I'm just burned out on having to find and delete, or renaming, all those filename...1.jpg, filename....2.jpg files. Especially since another bug - on export - often creates a jpg full of junk, which I have to manually delete.
I've enjoyed using C1 for years, but this problem has become like a rock in my shoe that I simply have to get rid of, somehow.
1 -
Hi Jim
I understand your frustration, this is for me as well the ONE thing that is a huge irritant. It didn't help that there was a survey about a week ago from them about exporting, and this question was not even asked!
Sometimes companies have blind spots and this is one of theirs. It would help just to get some feedback to explain exactly why they don't want to put this simple feature in.
It makes no sense at all. Standard practice just about everywhere is to simply ask whether to overwrite or not. Absent a good reason, one is left thinking that they are just being plain stubborn about it.
Having vented like you, and earlier in this thread as well, I wouldn't leave C1 just for this reason. Besides this, it's a great product. Feature updates are slow, and I would have hoped for some more innovation over the last few years. But that is another matter, and again, no reason for me personally to leave.
So I hope you decide to stay!
1 -
Bumping this!
I finally took time to try Exposure X6. After working with a raw photo for 15 minutes I am very impressed! It's too soon of course to fairly compare it to C1. BUT I can tell you that it completely addresses the issues with exports. It has reasonable functionality for editing IPTC keywords, description, title and copyright AND it embeds this data in an exported JPG. This alone is a huge advantage for me. And, if you export again, a nice dialog pops up asking if you want to overwrite the existing file, or create a new one with an incremented name - just like every other sensible program in the world. Except C1.
1 -
Hello CaptureOne Team, Hello community participant,
Please add an option to overwrite export target files.
My Workflow is like this:
I am working on all Pictures from an event and at the end I am exporting them.
When work is done I usually find images I like to adjust and exporting them again and simply overwriting the old exported image.
This Option should be avilable in Process Recipe Files very simple.
Please help to improve workflow handling in CatureOne solution.
thanks Josef.0 -
The Feature has been implemented as version 14.3.1
0 -
Yes, but that's version 21, which would cost me $200.
0 -
The process recipes allow to select an executable ("open with"), maybe you can write a small app which deletes the previous jpg (the one without the increment in its name) and renames the file which was just exported?
0
Post is closed for comments.
Comments
23 comments