![]() ![]() To me, as a programmer, this is trivial stuff, and I'm sure that once the development team gets the information it will be fixed within minutes. All Lighroom would have to do is to pick files where the destination file does not exist first, then the result of the operation would be correctly named files. It will perform the rename operation on one file at a time, at any order. Lightroom has got full control over all the files that are involved in the rename operation. Here, the result of the operation will be files named "xxx-1", despite the fact that after the operation, no file is named "xxx".Ĭletus, I do not agree that it's the fault of the operating system. If, say, slide 14 is missing I mark the subsequent photos (starting with the one incorrectly numbered 14) and re-run the rename command starting with number 15. The next step is to locate the missing slides. Currently, I scan old slides from boxes - the boxes are fairly complete, but sometimes an odd slide is missing.Īfter I have scanned a box I run a plain rename command that includes a sequence number, this initial rename is done on all slides starting with number 1. I run into this problem basically every day. *This naming scheme is quite common amongst those who show clients all their keepers and the gapless sequential numbering means the client won't see breaks in the sequence and ask to see substandard images. You avoid it by renaming twice - once with a random renaming scheme, and then with the correct one. You'll see the 5th image onwards has a "-1" in the name. Now delete one image - the 4th - and try renaming them again. To prove LR has a problem (which I've moaned about) set up a folder of 10 images and name them using a YYMMDD_ naming scheme *. But it really needs to consider whether there will be a collision based on what the filenames are going to be at the conclusion of the renaming process and if necessary do the renaming in two passes. The problem is that at the start of the batch renaming process, LR checks the existing file names in the folder and generates new names with "-1" to avoid naming collisions. The cause and workaround are very much as andersl explained. LR certainly can add the "-1", and I wouldn't be at all surprised to see it add the "-2", though I've not seen it myself. Perhaps you are always writing to the same folder each time and each time your template begins with "00001-YYMMDD" If you run this process twice or more on the same date, you will generate a file names "0001-111004" each time and subsequent files will append the "-1", "-2" to the file names.Īre you doing this on import? If the problem is with your naming template, could you post a screen shot of your "Filename Template Editor" dialog and explain what your desired output name needs to be?Īctually. So either your custom template is constructed to make duplicates or the file already exists in the folder whenever you generate the file name using the template in LR. To obey this rule, the OS either does not copy the second occurance or the OS adds extra characters to make a unique name. One of the cardinal rules for file systems is that no two files can reside in the same folder and have the same name. LR does not add the "-1", "-2" to the file names. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |