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. ⚠️

Rename RAW and associated JPG output

Comments

16 comments

  • Ian Wilson
    Moderator
    Top Commenter
    No suggestions from anyone?

    Ian
    0
  • SFA
    Nothing I could think of Ian since the output file may not have the same date (for example).

    I'm tempted to suggest just re-processing them and so get the revised name in the output. However it's just possibole that in some situations you may not get exactly the same result - depends how old your older files are and what version of C1 (or something else?) you were using at the time and whether the original C1 "engine" is still available for output processing in release you are using.

    Put the new versions in a new folder upon output. Then, if so preferred, delete the old folder and rename the new one on successful completion of the revise output.

    Does this help at all?


    Grant
    0
  • Ian Wilson
    Moderator
    Top Commenter
    Grant

    Yes it does help a bit. I had thought of renaming the raws and then reprocessing. The catch is that as you have suggested these are older pictures, edited with older version of C1, so the results may not be the same as before. I suppose that I could go back to the original engine. In many cases, reprocessing with a new engine (and better editing skills than I had a few years ago) would in fact produce a better result, but the doesn't help with cataloguing old stuff. For smaller collections, I suppose I could rename the raws automatically then locate and rename the output JPGs by hand to match, but I don't relish that for larger collections.

    I think I now have a naming convention that should stand the test of time, and it goes to show that changing it is likely to produce difficulties like this, and that settling on a good convention earlier on would have been wise!

    Thanks.

    Ian

    PS - how did the file name extension to one of the examples I gave in my original post become *censored word*? I am at a loss to think what I may have typed that fell foul of any profanity filter!
    0
  • bml
    I didn't test it, but maybe NameChanger is helpful.
    0
  • Ian Wilson
    Moderator
    Top Commenter
    Maybe. But if I change the names outside Capture One, what will happen to .COS files associated with the RAW files and will it mess up finding the files in Capture One?

    Ian
    0
  • Eric Nepean
    I've gone throught the same process, except that I did it in Aperture as part of the Aperture to Capture One Migration.

    One of the things I did was to copy the orignal Filename and Date into one of the IPTC metadata fields, so that I could always go back if I really messed up.

    If you felt like trying Applescript you could for write an Applescriot to save the name root (without JPG or RAW) in some IPTC Metedata field of the JPEG. Execute this on all the variants in your collection.
    Then do a batch rename of all the JPEGs.
    Now write a second applescript to open the JPEG, read the name root out of the IPTC Metedata, find the RAW and rename it. Execute this on all JPEG variants in your collection.

    Otherwise, BettterFileRenamer is a really good file renaming utility.
    0
  • Ian Wilson
    Moderator
    Top Commenter
    Thanks, Eric.

    Ian
    0
  • SFA
    [quote="Ian3" wrote:
    Grant

    Yes it does help a bit. I had thought of renaming the raws and then reprocessing. The catch is that as you have suggested these are older pictures, edited with older version of C1, so the results may not be the same as before. I suppose that I could go back to the original engine.


    <snip>

    PS - how did the file name extension to one of the examples I gave in my original post become *censored word*? I am at a loss to think what I may have typed that fell foul of any profanity filter!


    For the first part - if using sessions and the original engine is not too old you don't have to convert to the new engine for the image - just the cosessiondb file which will be done automatically of course as you know.

    So in theory you can still process the older images with the older engine ...

    I have done so, (with Windows) and all seems well. Whether there are any downstream issues with newer functionality - output sharpening comes to mind - I can't say - I don't remember paying any specific attention to that.

    For your final question - no idea. What was the text?


    Grant
    0
  • Ian Wilson
    Moderator
    Top Commenter
    [quote="SFA" wrote:

    For your final question - no idea. What was the text?

    I can't remember now. It can only have been intended to be something like ORF, CR2, NEF, ARW, JPG or TIF I'd have thought.

    Ian
    0
  • SFA
    [quote="Ian3" wrote:
    [quote="SFA" wrote:

    For your final question - no idea. What was the text?

    I can't remember now. It can only have been intended to be something like ORF, CR2, NEF, ARW, JPG or TIF I'd have thought.

    Ian


    Hmm.

    Strange.

    Inadvertent misplaced punctuation perhaps? (Still can't think what though ....)
    0
  • Permanently deleted user
    I know this probably won't help since they are already in CaptureOne but Finder can rename batch files like you want in a pretty advanced manner.
    0
  • Permanently deleted user
    I just tried it and it seemed to work just fine. Just right click on the images you have selected on the right side and choose Batch Rename. This will rename the raw files, keeping all of your changes you made too in C1. Then you can export variants with all the changes you could want.
    0
  • Ian Wilson
    Moderator
    Top Commenter
    In the batch rename tool, I found that when you click on the ... menu, there is an option that says Pair RAWs and JPGs. Experimenting with that on the All Images album of a small session, I get a pop-up that tells me that this only works if the images are sorted by name, and I had then sorted by date. So I resorted by name, but it didn't seem to achieve the result I had expected. I'd thought that where a RAW and a JPG had the same old name (apart from the file extension) I'd end up with them having the same new name (apart from the file extension). But what I got was 13-04-07 0001.jpg then the raw of the same image called 13-04-07 0002.NEF.

    Am I doing something wrong or does this not work the way I thought?

    Ian
    0
  • Ian Wilson
    Moderator
    Top Commenter
    OK - answered my own question.

    Selecting all the images in the All Images session album and applying batch rename (with the Pair RAWs and JPGs option) didn't achieve the desired result.

    But then I tried moving the JPGs from the Output folder to the Selects folder first, so that they are all in the same physical folder. And then the batch rename with the Pair RAWs and JPGs did work as I had hoped, so I get both 13-04-07 0001.JPG and 13-04-07 0001.NEF. It is then easy enough to resort the folder by file extension, select all the JPGs and move them back to the Output folder.

    Ian
    0
  • SFA
    [quote="Ian3" wrote:
    OK - answered my own question.

    Selecting all the images in the All Images session album and applying batch rename (with the Pair RAWs and JPGs option) didn't achieve the desired result.

    But then I tried moving the JPGs from the Output folder to the Selects folder first, so that they are all in the same physical folder. And then the batch rename with the Pair RAWs and JPGs did work as I had hoped, so I get both 13-04-07 0001.JPG and 13-04-07 0001.NEF. It is then easy enough to resort the folder by file extension, select all the JPGs and move them back to the Output folder.

    Ian



    Totally unacceptable lateral thinking Ian.


    Well done!

    Not something I would have dared to suggest publicly in this forum as a possible approach ....


    😉


    Grant
    0
  • Ian Wilson
    Moderator
    Top Commenter
    Thanks. It obviously makes a difference whether they are in the same real folder or just a virtual one.

    Ian
    0

Post is closed for comments.