Skip to main content
S
SCPhotoVideo
Participating Frequently
December 3, 2021
Answered

Batch Export Custom Name - Original FIle Number not working

  • December 3, 2021
  • 3 replies
  • 1522 views

I see various versions of this question going back to 2012 without a workaround or answer. If I want to Multi-Batch export an image from LRC using a Custom Name - Original File Number renaming:

 

My raw image (Canon) 3WXXXX.CR3 to FullSize-3WXXXX.JPG and WebSize-3WXXXX.JPG (two different presets)

The export will strip the Original File Number from the name making impossible to export unique filenames.

 

Am I missing something? Is there some weird import setting I need to tick?

 

LRC version 11.0.1

OS X Big Sur 11.6.1

This topic has been closed for replies.
Correct answer richardplondon

The example cited shows "3W" and then the XXXX (which I presume denotes the incrementing number assigned by the camera, that you are looking for). If LrC's extraction method turns out to be (as I suspect) looking for the first group of number characters present - then all filenames having this 3W prefix could return the result "3" as their presumed file numbering. That would not happen with the default IMG prefix (which becomes _MG when the camera's set to Adobe RGB). So if my (sheer) guess is right, this might be an unwanted side consequence from customising file naming in the camera menu.

3 replies

S
SCPhotoVideoAuthor
Participating Frequently
December 11, 2021

3Wxxxx(number sequence) is the default naming sequence with canon R5 raw files. I've never tried to change it.

Sean McCormack
Community Expert
Sean McCormackCommunity Expert
Community Expert
December 3, 2021

My solution is to use the Filename Number Suffix as part of the filenaming. 

Sean McCormack. Author of 'Essential Development 3'. Magazine Writer. Former Official Fuji X-Photographer.
S
SCPhotoVideoAuthor
Participating Frequently
December 11, 2021

Could you it explain that a bit more? Do you mean on the camera. Nothing I've tried with custom file name have worked so far.

my workaround is to use separate subdirectories for different versions of the images. They don't get custom banes this way but at least they get put in separate "piles".

R
Community Expert
richardplondonCommunity Expert
Community Expert
December 12, 2021

Retaining the whole filename as-is will always give you unique file naming regardless of naming settings in the camera - assuming the camera is set to continually increment its counter, and not reinitialise that e.g. for each fresh memory card (or whatever).

 

For example: "Fullsize-3WXXXX.JPG" and "Websize-3WXXXX.JPG" -

or, for that matter, "Fullsize-IMGXXXX.JPG"

R
Community Expert
richardplondonCommunity ExpertCorrect answer
Community Expert
December 3, 2021

The example cited shows "3W" and then the XXXX (which I presume denotes the incrementing number assigned by the camera, that you are looking for). If LrC's extraction method turns out to be (as I suspect) looking for the first group of number characters present - then all filenames having this 3W prefix could return the result "3" as their presumed file numbering. That would not happen with the default IMG prefix (which becomes _MG when the camera's set to Adobe RGB). So if my (sheer) guess is right, this might be an unwanted side consequence from customising file naming in the camera menu.

    S
    SCPhotoVideoAuthor
    Participating Frequently
    December 11, 2021

    The Canon R5 defaults to a Preset Code, in my case 3W0A instead of IMG, but I see the IMG option in the menu setting now so I will try that. Thanks.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices