Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

overwrite exported files

Comments

8 comments

  • Doug Peterson
    There is no option for this, and I hope there never will be.

    I never, ever, want the software to overwrite my exported files. I'll be glad to manually delete them (after double checking what I'm doing) if/when such a thing is required.
    1
  • NNN635158767546269381
    Well I do want to hve the choice!

    A window with the list of the concerned files and the following options:
    - Overwrite
    - Rename
    - Use index (-x).

    Would be really welcome!
    0
  • Stefan Segers
    Thanks Nicolas,

    U understand what I mean.

    Sometimes it's much better to overwrite, so getting an option like LR has would be great!
    0
  • H. Cremers
    [quote="Digital Transitions, Doug" wrote:
    There is no option for this, and I hope there never will be.

    I never, ever, want the software to overwrite my exported files. I'll be glad to manually delete them (after double checking what I'm doing) if/when such a thing is required.


    While i see where you're coming from, in my opinion you are forgetting one or more use cases that other users may have. For example, i'm using an external DAM. I don't want my DAM function integrated with my raw converter, not because that's not good, but it (generally) offers more typical DAM functions. Also, i use other raw converters as well and want to bring together the previews from various converters alike.

    So, when i need my CO to write a preview file, the first thing is that i can't specify the file extension. It currently is hard coded to the file type. Second, and on topic, i would need it to overwrite previously existing preview files, because i would need only one preview in my DAM tool of choice.

    So, i concur with having the choice as a user.
    0
  • Andrew Mumford
    Agreed - the ability to easily process & update each export so that the exported variant always represented the latest version when working recursively with hundreds of images for an event would be very useful.

    For me the original file and it's associated develop settings in whichever converter I'm using are what's important - I consider the developed JPG's to be "soft" and easily up dateable without having to version up each new pass.

    Also the ability to view the "status" of the "developed / exported" variant - i.e. whether it's in sync in terms of appearance / adjustments or metadata would also be a very worthwhile workflow enhancement.
    0
  • Mark Connell
    [quote="NNN635158767546269381" wrote:
    Well I do want to hve the choice!

    A window with the list of the concerned files and the following options:
    - Overwrite
    - Rename
    - Use index (-x).

    Would be really welcome!


    I would also really like this capability. Also, as a option in the process recipe it self so I can set it on/off for particular recipies.
    0
  • Permanently deleted user
    I completely agree. I would like to either have a global/recipe configuration to overwrite exported variants, or have a window popup listing the existing files with the same name and asking me what to do. Now I have to first find each file I'm re-processing by name and delete them to avoid having a second set of files that I would then have to rename one by one to the consistent naming that I configured in the recipe.

    I also agree with Andrew902, the next step for me would be for the "Processed" state in C1 to reflect whether the variant has been processed since making the additional adjustments. For me it could be as simple as either removing the "Processed" state from the image once I make any additional adjustment, or change it to a new state like "Processed from older version only".

    I hope someone from P1 actually reads this...
    0
  • SFA
    [quote="ftavares" wrote:
    I completely agree. I would like to either have a global/recipe configuration to overwrite exported variants, or have a window popup listing the existing files with the same name and asking me what to do. Now I have to first find each file I'm re-processing by name and delete them to avoid having a second set of files that I would then have to rename one by one to the consistent naming that I configured in the recipe.

    I also agree with Andrew902, the next step for me would be for the "Processed" state in C1 to reflect whether the variant has been processed since making the additional adjustments. For me it could be as simple as either removing the "Processed" state from the image once I make any additional adjustment, or change it to a new state like "Processed from older version only".

    I hope someone from P1 actually reads this...


    Why just hope?

    Create a Support Case with something like "Enhancement Suggestion:" in the title and then you will know that the idea will be looked at and support for it in the user base can be measured.


    Grant
    0

Post is closed for comments.