P: Does not remember original file number when exporting an AI Denoise Image

[Holten]

When exporting an image with the option "Custom name - original file number", LrC fails to do so if the image is denoised using the new AI functionality. Instead you get the "Custom name - Sequence" instead.

OS: Windows 10,
LrC build no: 202304101834-a085245c

Steps to reproduce: Denoise an image using the new AI-function (button above the denoise sliders), export using "Custom name - original file number".
Result: The images get sequence number in the file name instead of image number. (The "Enhanced" addition to the name seems to confuse the export function. Should be fairly easy to parse or link back to the original file.)
Expected result: The exported images should have the original file number.  

[Rikk Flohr: Photography]

I was also able to replicate this on Mac. I have logged a bug with the Classic team. Thank you for the report. 

[Holten]

A similar problem occurs when having edited an image in Photoshop using the function "Edit in - PhotoshopXX" (right clicking on the image). 

[Evgeny27224797q07m]

Basic steps to reproduce the problem:

Hi, when I use the new Denoise feature on some photo, it creates 1 additional image with a name pattern like (what is fine):

ORIGINAL_NAME-enhanced-NR.dng

Then I do some things, editing, etc, and want to export this photo with a custom name pattern like:

{Date (YYMMDD)»}-{original number suffix»}

Expected result:

The correct date and number from the original file should be taken.

Actual result:

It doesn't work, export a photo with just a date, without the sequence. What in general is wrong, as the real original file which was a source for the denoised version work well with the same export options.

Additional information:

Lightroom Classic version: 12.3 [ 202304101834-a085245c ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.19044
Application architecture: x64
System architecture: x64
Logical processor count: 20
Processor speed: 2,8GHz
SqLite Version: 3.36.0
CPU Utilisation: 0,0%
Built-in memory: 32673,9 MB
Dedicated GPU memory used by Lightroom: 4070,4MB / 12010,0MB (33%)
Real memory available to Lightroom: 32673,9 MB
Real memory used by Lightroom: 4036,8 MB (12,3%)
Virtual memory used by Lightroom: 9122,5 MB
GDI objects count: 940
USER objects count: 2995
Process handles count: 6480
Memory cache size: 0,0MB
Internal Camera Raw version: 15.3 [ 1451 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 1198MB / 16336MB (7%)
Camera Raw real memory: 1272MB / 32673MB (3%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Standard Preview Size: 2560 pixels
Displays: 1) 2560x1440
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:
DirectX: NVIDIA GeForce RTX 4070 Ti (31.0.15.3161)
Init State: GPU for Export supported by default
User Preference: Auto

[jillymc926]

Issue:  When using Custom Name - Original File Number  to export files after denoise all files are saved with 'Custom Name-.jpg'  

Adobe Lightroom Version: 12.3

OS: Windows 11

Step 1.  Set export file renaming to Custom Name - Original File Number

Step 2.  Denoise an image

Step 3.  Denoised file created (Filename_number_Enhanced_NR.dng)

Step 4. Export denoised file

Step 5.  File saved as 'Custom Filename-.jpg'  (not Custom Filename_original file number.jpg)

All files saved with that same name.  Subsequent files overwrite earlier file.

Workaround has been to manually assign a unique name in the 'Custom File Name' for each photo denoised.    As an example, on the last image, I renamed the Custom Name 'buds-blue bird', otherwise the file would have the name 'buds-.jpg.

[KR Seals]

I just ran the scenario you describe. That's what I get, too.

I have seen that behavior for many versions of LrC as I recall. The only time the correct file number gets added to the exported .jpg is when a number of files are exported in the same operation. All the exported files after the first one get the correct file number added.

Win 10 pro, I7-8700K, 64GB, RTX370TI

[John R Ellis]

Moderators, @Rikk Flohr: Photography, please merge with the existing bug:

https://community.adobe.com/t5/lightroom-classic-bugs/p-does-not-remember-original-file-number-when-...

Also, merge this one:

https://community.adobe.com/t5/lightroom-classic-discussions/ai-denoise-has-killed-the-export-macro-... 

[KrishnaMaithreya]

@Evgeny27224797q07m @jillymc926 

This is an existing behaviour in export workflow.
Only when source file name ends with an integer, would the original file number work during file renaming.
For Denoised images, file name generally ends with '-Enhanced-NR'. Due to this, original file number doesn't work for file renaming during export.

[Holten]

Yes... the renaming is the problem. So don't rename them (or move the
number to the end of the file name). It is disrupting present
functionality. It perhaps seems like a small thing to you, but concider
the extra effort / workflow because of this:

I will now have to sit and rename files for extended periods of time,
comparing images and adding numbers by hand, especially being tired after 3
hours of editing. And if any of them needs to be re-exported, the old
versions (with correct naming) need to be first deleted and the new images
(with the faulty naming) needs to be renamed manually. LRc should have done
all that automatically if the images had only been exported correctly
(without name change, or with the file numbering moved to the end of the
file name, or detect your very standardized renaming in order to remove it
before exporting). It does not seem like rocket science. But I don't know
the state of the codebase you are working with...

The original numbering in the file name is crutial to identify the image
when someone, three years after the fact, asks for that image in full
resolution or just not compressed to pieces.

Sincerely
Olav Holten

[jillymc926]

The problem is that all files are named the same.... 'custom-.jpg' without
the numeric part of the 'enhanced xxx' file.

--
'Work like you don't need the money.
Love like you've never been hurt.
Dance like nobody's watching.'

[John R Ellis]

While waiting for Adobe to fix this (or change this if they deem the current behavior "as designed"), here's an inconvenient workaround:

1. Prior to exporting, select all the photos and use the Write Data Field command of the Bag-o-Goodies plugin to construct and store the desired filenames for the photos in an unused metadata field, e.g. IPTC Subject Code.

2. In the Export settings' File Naming, rename the files using just IPTC Subject Code.

Depending on your workflow, this might be faster than renaming manually.

[jillymc926]

Thank you!

--
'Work like you don't need the money.
Love like you've never been hurt.
Dance like nobody's watching.'

[RomasBudras]

Another workaround - 2 step rename process, by using Preserved Filename field which still contains original number suffix (but there's no direct way to extract the suffix and use in renaming rules).

1. Rename the file to "Preserved Filename".
2. Repeat your original rename rule (probably modified to avoid conflicts with source file).
This may not be a solution for all situations however.

[RegnadKcin]

The Denoise function saves a DNG file, but appends "-Enhanced-NR" to the filename. For instance, a file saved by my camera is named "IMGP2112.DNG"; the Denoised version of it is "IMGP2112-Enhanced-NR.dng".

Using the Export... function to save a .jpg version, I use a custom File Naming preset of "{DATE (YYYYMMDD)»} {Filename number suffix»} {Custom Text}". Here's how this renders to a filename in the Export folder:

1. IMGP2112.DNG: 20230825 2112 Custom Text.jpg
2. IMGP2112-Enhanced-NR.dng: 20230825  Custom Text.jpg

The exported filename from the Denoised image does not include the Filename number suffix. What I expect to see for the exported Denoised file, #2 above, is

20230825 2112 Custom Text.jpg

If I want the filename number suffix to be included in the exported file's name I have to manually add it.

This seems to indicate a parsing error on the part of the Custom Setting file renaming function when the original file's Filename number suffix is followed by text. Since the Denoise-related text is added by Lightroom it should be a simple fix to determine whether this sequence of letters is present in the filename and, if so, ignore it to determine what the number suffix is.

By the way I'm using Windows Lightroom Classic Build [202308091523-68a7abd6] on a PC with Windows 10, version 22H2, OS Build 19045.3324.

[John R Ellis]

Moderators, @Rikk Flohr: Photography, please merge with the existing bug:

https://community.adobe.com/t5/lightroom-classic-bugs/p-does-not-remember-original-file-number-when-...

[John R Ellis]

See here for a two-step workaround that might be faster than manual renaming:

https://www.lightroomqueen.com/community/threads/noise-filter-renaming-issue.47839/post-1317136

[johnb60867848]

Its been almost a year since this but was reported - but still no resolution in sight.  I rename all my files using custom settings YYMMDD-custom text-(file name suffix. 240312-Tokyo street-7812.NEF for example.  After denoise, the file becomes 240312-Tokyo street7812-Enhanced-NR.DNG. The built in rename function provide no way or repeating the original custom settings rename, so I am left with 2 options:

Configure custom rename to rename the files using the preserved filename (DSG_7812), Then reconfigure custom rename to use (date)-custom text-extension and rename the files again. Alternatively, I rename the files outside of lightroom using a batch renamer app (e.g. renamer) and reimport to lightroom.

Either method is tedious, error prone and unneccesary.

This should be an easy-fix for Adobe:

1. They already have the option  edit/preferences/file handling/keywords/automatically add keywords to enhanced images. Add another option to turn on/off "Add additional description to filename" (the only risk with this is if the orginal file is also .DNG)

2. To prevent file name conflicts they could provide an option to save denoised files in a subfolder of the original folder

3. Add more functions to the library/rename function e.g.

i.  in custom settings/image name - have an option: Preserved filename number suffix.

My custom rename would become {Date (YYMMDD)>>}-{Custom Text}-{preserved number suffix>>}

ii Provide the ability to save custom rename settings so they can be reselected from the drop down list

iii Improve the rename function to make it on par with windows based file rename apps by allowing insert / delete / move / replace etc. based on rules

Denoise is great, but I hesitate to use it because of the additional steps required to maintain consistent file naming

I hope they address this issue soon

[Nathan S Hamilton]

Did a google search for this problem and see it has been going on for a while now with still no fix...any idea of when this will be resolved Adobe?

[Holten]

Please upvote the bug (press the icon on the top left) to get their attention. Othervise nothing will happen.

[SStrackside]

This JUST started for me - discovered using the new "lens blur" affect was causing the issue - turn it off - refresh the masks and boom - now it will save the files renamed in sequece - kinda liked the blur effects but not if it compromises the abiloity to export thousands of photos renamed to accomidate website uploading sequences & storage.... 

[Holten]

Upvote this bug report to increase the probability of them to actually do
anything about this bug! This causes me extra effort for every client. Very
annoying. Just as you, I really don't want to use the new good featured due
to this problem.

[Rey Noel]

So was this ever addressed because I just also made a report about this issue. 

[John R Ellis]

"So was this ever addressed"

Not yet. You can see the current status as "Bug: Acknowledged" at the bottom of the top post.  When Adobe fixes it, they'll change it to "Bug: Fixed" and post to this thread, so you'll get notified (as long as you keep following the thread).

Note that Adobe rarely indicates ahead of time when/if a bug will be fixed.

[Rey Noel]

understood, i will follow the thread also.

[Rikk Flohr: Photography]

Note: This has been reviewed and moved to Feature Requests. 

[Rey Noel]

They fixed it!! at least it is working for me, test it out let me know if its working for yall.