More Batch Renaming Issues

*) An "undo" function is necessary. Let's say, "very necessary," as I just learned.
*) Using letters as sequences doesn't give you the option to start at a particular letter. This is necessary if you want to pick up sequencing from a series that left off at some other letter. Nor is it clear wheat it'll do when it hits 'z' and needs to continue. It should offer the option of double-letter naming.

Mea Culpa--
I just NOW saw the [rather obvious] FEATURE REQUESTS link on the Bridge page. I apologize for mis-posting this thread.
(Is there a way to "move" it?)

Similar Messages

  • Bridge Batch Rename Issues!!!

    I'm having problems using "batch rename" in Bridge. I run two machines at work, on one the "rename in same folder" option is ALWAYS non-selectable. On my other machine I can select the option to save in same folder but when I "select all" and then batch rename Bridge automatically deselects some of the images and only renames those that are left selected. Needless to say this is pointless and I end up in Photo Mechanic.
    My co-worker and I both have this issue, both run two computers. We're running OS 10.4.1 and CS3.
    Anyone have a similar issue or even better a fix?!
    Thanks,
    -Matthew

    You are better off with this .. http://www.versiontracker.com/dyn/moreinfo/macosx/14404
    Called R-name - its a small freeware application that I use all the time, quicker and less problematic than using Bridge. Been using it for years with no problems at all, works with drag and drop too.

  • Batch Rename Issues - CS5 - Win7

    Bridge (4.0.2.1) will not Batch Rename in sequential order.  Have tried several times on different folders and get the same results each time.
    For example:
    Folder with 280 images.  I request a Batch Rename in Same Folder, numbered sequentially starting with 001+JobName+Original File Name.jpg.
    What I get is:  sequential 001 to 051, then 096, 098, 100, 102 - 106, then 052 -107, then doubles -  2x 108, 2x 109, 2x 110, 2x 111, 2x 112, 2x 113, 2x 114, 2x 115, 2x 116, 2x 117, 2x 118, 2x 119, 2x 120, then 121-258.
    I've never experienced anything like this, ANY HELP APPRECIATED!!  I do not want to name over 1000 total files by hand!

    Is this really an Adobe Reader problem?

  • Issue with Adobe Bridge batch rename crashing

    Hi, I have been trying to rename photo files in Adobe Bridge CC using the batch rename tool. I have just started using CC apps. All the updates are done. It crashes after doing just a few files. Started with 40 files at a time, crashed. Empty folder cache. Tried with 20 files, worked for a few times then crashed again. Tried 10 files and it crashed immediately. I found directions online (unfortunately it was for CS5, but I assume it's similar to CC). Any ideas on what to do differently? I really need to get these photos renamed and to a client tomorrow. Thanks in advance for any help.
    Cheryl

    Video card is updated, though I've been getting an error message on it.
    I'm not sure what this should have to do with your batch rename problem. Your specs seem more then sufficient and batch renaming does only save the files you already have cached.
    First check if you have enough free space left on your disk (at least 10 - 15 % free space is needed for good operation of your system and apps) and also try to reset preferences for Bridge by holding down contrl key while restarting Bridge. Check reset preferences from the pop up window and try again.

  • Batch Renaming Event Clips Issue

    Hello,
    I have been trying to batch rename my event clips.  I know how to do it with the option and then the gear, and choosing all of the options I want in the title. 
    The problem is, when it renames a bunch of clips it throws them all out of order.   I can't figure out why this is happening. For instance, if I'm renaming files
    1 through 10.  It won't rename them with the first clip #1 and second #2, and so on.   It takes the 9th clip and names it #1, and takes the 4th one and names it #2, and messes them all up in that sort of way. 
    Naturally, I want the first thing I recorded to be named #1, and the clip right after that to be #2, and so on.
    Would anyone have any experience with this, or know how to fix this problem?
    Thanks so much,
    K-

    This problem is a known bug to apple.  No fix yet.  But you should give them feedback about this to  move it up the chain of issues to fix.  It's been broken since 10.0.3.  I find it very frustrating.

  • Batch Rename - allow 6 digits (or more)

    Batch rename of files allows a sequence number that is limited to 5 digits. Even though the selector control allows you to specify six digits, the sequence number box does not allow the entry of the 6th digit. For example, I have the following:
    New file name:
    text: tf
    sequence number: 40389
    allow: Six Digits
    If I attempt to enter the sixth digit, I get a "beep" and the entry is not allowed. The Preview at the bottom indicates:
    Current file name: tf0001.cr2
    New filename: tf0403980.cr2
    It might also be useful to allow seven digits on the sequence number.
    The motivation for this is to allow perpetual sequence numbers. I have named all of my digital images with the series tf######. At present, I have over 400,000 images in my system. This provides a unique image identification without restoring to additional information such as "date + subject". In this way, all images on my web pages are identified by this simple number and a customer can simply provide a file number as an image reference - no matter when the image was taken or for which event.

    You are probably stuck with writing a script as this is an unusual format.  Check with Bridge scripting to see if one is already available.

  • Molt: batch renaming utility

    Hi all,
    Recently I was looking for a batch renaming utility, and while I did find a few, none of them would really fill all the checkboxes of my requirements list. Either because they didn’t provide the "rules" I was looking for, or because they would rename files after each rule has been applied, or because they couldn’t be used from scripts (that way I wanted), or whatever the reason. So I made myself one: molt.
    You use it by specifying a set of rules to use, which will all be processed to determine the new name. molt will make sure those new names are "free," as in not already in use; and handles "avoidable conflicts" - when a file's new name is taken by another file to be renamed (performing two-steps renaming with a temporary name if needed).
    Usage: molt [OPTION]... RULE... [FILE]...
    Options :
    -D, --exclude-directories Ignore directories from specified files
    -F, --exclude-files Ignore files from specified files
    -S, --exclude-symlinks Ignore symlinks from specified files
    -i, --from-stdin Get list of files from stdin
    -P, --process-fullname Send the full path/name to the rules
    (Imply --output-fullname)
    -p, --allow-path Allow (relative/absolute) paths in new filenames
    (Imply --output-fullname)
    -m, --make-parents Create parents if needed
    -O, --output-fullname Output full path/names
    -B, --output-both-names Output the old then the new filename for each file
    -N, --output-new-names Output the new filename for each file
    -R, --only-rules Only apply the rules and output results,
    without any conflict detection
    (Imply --dry-run)
    -n, --dry-run Do not rename anything
    -C, --continue-on-error Process as much as possible, even on errors
    or when conflicts are detected
    -d, --debug Enable debug mode - Specify twice for verbose
    output
    -h, --help Show this help screen and exit - Specify twice for
    verbose output
    -V, --version Show version information and exit
    Rules :
    Rules are the part of molt that process filenames. Rules will be applied
    in the order specified, you can use the same rule as may times as you want.
    Some rules require a parameter, what it can be depend of the rule. Usually,
    it will be a string where you can specify multiple parameter using slash ( / )
    as separator.
    --upper Convert to uppercase
    --lower Convert to lowercase
    --vars Resolve variables
    --tpl PARAM Apply specified template (resolve variables)
    --sr PARAM Search & replace a string
    PARAM = search[/replacement[/option]]
    If no replacement is specified, the string will be removed.
    Search is case-sensitive, unless option i was specified.
    --camel Convert to Camel Case
    --list Use list of new names from stdin
    --regex PARAM Search & replace using regular expression
    PARAM = pattern[/replacement[/option]]
    If no replacement is specified, the string will be removed.
    Search is case-sensitive, unless option i was specified.
    Variables :
    You can use variables in the new filenames. The syntax is to put the
    variable's name in between dollar signs, e.g: $FOOBAR$
    You can also (if supported) specify one (or more) parameters, using colon
    as separator, e.g: $FOOBAR:PARAM1:PARAM2$
    Variables are not automatically resolved, you need to use the rule --vars
    in order to have them resolved, which gives you the ability to determine
    when resolving happens, and continue processing with more rules afterwards.
    Note that rule --tpl also resolves variables.
    NB[:PARAM...] Counter, incremented for each file using it
    You can specify up to 3 parameters:
    - the minimum number number of digits (padding with 0's)
    - the starting value of the counter
    - the increment (can be negative)
    E.g: $NB:3:42:-2$ will resolve as 042, 040, 038, etc
    _[:PARAM...] Magic variable: specify "variable" as parameter
    The first parameter is the name of the "variable" to resolve.
    Resolving is done running the corresponding command line, using output
    as value (removing trailing newline (\n) if present)
    Links:
    - Slightly more verbose description
    - Source code
    - PKGBUILD in the AUR
    Hopefully someone may find it useful.
    Cheers,
    -jacky

    Yes, this works. However, this was already part of my workflow.... and not where the trouble lies.
    After exporting jpeg images from Aperture, they carry the same name of the original RAW files, from which they came. (So, IMG_8342.jpg would have started it's life as IMG_8342.CR2.) But we dont' send them out like that. We sequentially name them 0001_image.jpg, 0002_image.jpg, etc... So after renaming, how do you find the original file again, right?
    BEFORE the renaming phase, I would run the "Store Original Names in Spotlight Comments" action. That way, I could look at the comments for a derivative .jpg—whose name has now changed—and determine the name of the ORIGINAL file.
    After renaming, the derivative file might end up being named 0361_image.jpg, but it's Spotlight comments would say, for example, Original Name:<<IMG_8485.jpg>>. Then I would know that this particular file started off as IMG_8485.CR2.
    As such, I could quickly/easily backtrack, knowing that the original RAW file was named IMG_8485.CR2
    The issue is that once you've gone thru the effort to ADD these spotlight comments, if you THEN go through a re-naming step, this erases all those Spotlight Comments. That was my problem... Getting the Spotlight Comments in place was never the issue. KEEPING them there was the problem.

  • Batch Rename Order Getting Mixed Up

    When batch renaming a large amount (usually over 100) of RAW NEF photos, in the format of YEAR_Month_DAY_TIME_#### (where #### is a 4 digit sequence number) EX/ 2014_10-25-122506_0001, the files get renamed and when sorted by file name are in order, however the 4 digit sequence number gets mixed up somewhere along the way.
    It usually happens after the mid hundreds.
    Example, I had apx 900 images in one folder I batched renamed, and the sequence number progressed properly from _0001 to _0191, but then the next image went straight to _0232.
    Any one else experience this issue or have any ideas as to a solution?  Very frustrating issue.
    Thanks!

    Thanks, Tulse... i'm glad that it's an issue that can be reproduced by others. I'm amazed that it hasn't come up (perhaps it has) in the time since Keynote was released. I'm even more amazed that what seems like such a significant bug hasn't been addressed yet. I just hope a new version of Keynote is coming soon that will address things like this.
    The reason i'm doing so many build ins and build outs is because i want the content of the slides to transition independently of the background. This is something i would love to see in the next version of Keynote.
    For example, i'm using a looping video clip as the background, with our company logo superimposed over it. I'd like for the foreground text and other graphical elements to transition from slide to slide, but leave the background constantly looping. So instead of an empty black "stage", i can have 3D effects applied at the slide level without disturbing my own background.
    Anyway... i tried using the blank slide as an intermediary and did not have the success that you did. Build orders still ended up different from those on the master slide.
    I wonder if the builds need to be created in the order in which i want them to appear... it seems like new slides may be ignoring the order in which the builds have been dragged around in the Build Order inspector on the Master, and instead, executing them in the order in which they were created.

  • Batch Renaming loses Spotlight Comments, Os X to blame?

    I posted this over at the Adobe forum for Bridge, however, I'm going to post it here too because part of me feels like this issue I'm experiencing is tied to a recent Os update: from Leopard to Snow Leopard.
    I'm a photo editor for a wedding photographer and have been implementing some of my own personal workflows into his pipeline. I tend NOT to rename camera-generated files, at all, unless there's an important reason to do so. Sorting an entire wedding by "Date" works perfectly for building the proper timeline for a shoot. So camera-generated file names are perfectly okay for our needs.
    When an edit is complete I'll generate JPEGs from Aperture. The resulting files will continue to carry the original RAW files names, unless there is a duplicate file name, then Aperture will add a number: "(1)" to the file, if necessary. Typically, after export, I run an Automator action that stores the file name in the Spotlight Comments. Because prior to shipping and archiving, I AM going to rename the final JPEGs sequentially: 0001_wedding, 0002_wedding, etc.
    The beauty was that with the original name stored in the Spotlight comments for the JPEG, I would easily look at 0148_wedding.jpg, see that it's spotlight comments said, "Original Name: IMG_3471" and obviously know exactly what RAW image this new JPEG started as. Worked perfectly.
    So process was: Export, Store Original Name in Spotlight Comments of JPEGs, Batch Rename (sequentially) based on date modified in Bridge CS4.
    Well now everthing's changed. We had a system drive go down. We were running 10.5.8. When the system came back from the shop, with a new drive installed, it was/is running Snow Leopard. 10.6.3? I think. Snow Leopard, no doubt.
    And now my prior workflow has been wrecked because the act of renaming, in Bridge CS4, erases all those handy Spotlight comments. However, part of me is wondering though if this issue is rooted more deeply, at the OS level? Because R-Name (Batch renaming utility) is now eradicating Spotlight comments as is an Automator action built for the same purposes. This all used to work perfectly. And the one major change that has occurred was this "upgrade" from Leopard to Snow Leopard.
    So, question is: is there something I can alter in Bridge Preferences to maintain my Spotlight Comments, when batch renaming? Is this all tied to the Snow Leopard? Is there ANY renaming utility that's not going to fall victim to whatever the hang up here is?? How can I batch rename and not destroy my lovely Spotlight Comments in the process?
    Thanks for your time!!

    Yes, this works. However, this was already part of my workflow.... and not where the trouble lies.
    After exporting jpeg images from Aperture, they carry the same name of the original RAW files, from which they came. (So, IMG_8342.jpg would have started it's life as IMG_8342.CR2.) But we dont' send them out like that. We sequentially name them 0001_image.jpg, 0002_image.jpg, etc... So after renaming, how do you find the original file again, right?
    BEFORE the renaming phase, I would run the "Store Original Names in Spotlight Comments" action. That way, I could look at the comments for a derivative .jpg—whose name has now changed—and determine the name of the ORIGINAL file.
    After renaming, the derivative file might end up being named 0361_image.jpg, but it's Spotlight comments would say, for example, Original Name:<<IMG_8485.jpg>>. Then I would know that this particular file started off as IMG_8485.CR2.
    As such, I could quickly/easily backtrack, knowing that the original RAW file was named IMG_8485.CR2
    The issue is that once you've gone thru the effort to ADD these spotlight comments, if you THEN go through a re-naming step, this erases all those Spotlight Comments. That was my problem... Getting the Spotlight Comments in place was never the issue. KEEPING them there was the problem.

  • Bridge Renaming issue Dialogue box color

    Attached is the screen grab for the issue i have. In Bridge (Creative Cloud CS6 when I go to doa batch rename my dialogue box is black. How do I fix this?
    Andrea Stork
    <Removed by Moderator>

    Graphics  ATI Radeon HD 2600 XT 256 MB
    Almost certainly this is the trouble maker.
    The minimum amount of VRAM for the Cloud CS6 is 512 MB, (1 GB recommended)
    And 4 GB of RAM is also not that much for a MacPro (I have 16 GB RAM installed and upgraded my Graphic Card with the ATI Radeon 5770 with 1 GB VRAM from the Apple Store)
    If you check the preferences for PS under performance you will see that you can only use a few GB RAM for PS (system and other open applications also consume a bit of RAM) and the use of a graphic processor (needed for Open CL with nice features as flick panning, Birds eye zoom, scrubby zoom etc) is not able to select on your computer.
    So basically investing a bit in a lot of RAM (fairly cheap nowadays) and a new Graphic card (a bit higher investment) will not only most likely solve this bridge problem but will let you also benefit with more over all performance of your whole system. But of course, the decision is up to you, because sadly enough you are also the one thats need to pay for it...
    The upside is that both replacement of RAM and Graphic card is very easy for a Mac Pro and you certainly are able to do this yourself after reading some short instructions

  • Batch rename files preserving the original file name in metadata

    How can I batch rename files while preserving the original file name in metadata? (Don't want the old file name as part of the new file name)
    (Adobe CS Bridge can do this with some success, but I don't want to be dependant on this software. Results are inconsistent.)

    With a simple terminal script. More details needed, though.

  • Batch rename is not working

    I attempted to batch rename files in Adobe Bridge CC. Nothing happens. I force quit as Bridge will not quit on command (which is strange as Photoshop will). When I reopen Bridge the files have been renamed "AdobeBatchRenameTemp(than the file name I asked it to write)".
    Any ideas what is wrong with Bridge? Thanks

    Hi
    Are you using Mac Or windows  please mentioned some of the  system specification as well as it will be helpful
    if you are using mac . please go to a location ~/library/cache/adobe      "there will a folder by the name of Bridge CC please move it to desktop and then restart the bridge. this should take care of the cache issue.
    if you are using windows , please go this location C:\Users\user name\AppData\Roaming\Adobe\Bridge CC   and move the cache folder to the desktop
    and restart the Adobe Bridge CC

  • Batch rename does not remove original filename

    Bridge CS4 ver 3.0.0.464
    Not sure what I am doing wrong but when I try to batch rename my files for some reason I cannot remove the origanal filename,
    I have checked the preferences and searched for a solution and have come up with nothing.
    Any help would be great. Thank you.

    This has fixed the issue, however it is not really an ideal solution as it deletes all custom preferences, was there not a way to to reset just the renaming preferences?
    Thank you anyway, I forgot about cntrl bridge!

  • Batch renaming and relinking in InDesign CS4

    Is there a plug-in available for InDesign that will batch rename and relink placed images?
    In Quark, I used Badia Link Renamer which worked perfectly but it's not available for InDesign. (Was told they hope to have it incorporated into BigPicture for CS5.)
    Is there something similar currently available for InDesign?
    Essentially I need it to rename and relink files with random names to structured names such as:
    001_Cust_000123456789_art_r1.tif
    (I love that Bridge does batch renaming but then I have to manually update links in InDesign which is extremely time-consuming. I've also manually renamed/relinked files individually with Adobe Dialogue but it doesn't seem to be part of CS4.)
    Any help or suggestions would be greatly appreciated! Been looking for something for months.
    Thanks!

    Here is my last version of the script, it deals with multiple instances of the same file.
    Kasyan
    var myDoc = app.activeDocument;
    var myAllLinks = myDoc.allGraphics;
    var myMultipleLinks = new Array();
    var myLinksCounter = 1;
    var myPrepend = prompt("Example: thebook_08765", "Job description", "Please enter job description");
    if (!myPrepend) exit();
    var response = confirm("Warning: You are about to rename all images linked to the foremost Indesign Document - proceed? Keep in mind - it is not reversible!", false, "Rename Links Script");
    if ( response == true )
         WriteToFile("\r--------------------- Script started -- " + GetDate() + " ---------------------\n\n");
         for ( k = 0; k < myAllLinks.length; k++ )
              var myLinkName = myAllLinks[k].itemLink.name;
         crearLabels();
         var myPages = myDoc.pages;
         // Pages
         for ( p = 0; p < myPages.length; p++ )
              var myPageNumber = pad000(myPages[p].name);
              var myLinks = myPages[p].allGraphics;
              var myASCII = 97;
              for ( k = myLinks.length - 1; k >= 0; k-- )
                   var myLink = myLinks[k].itemLink;
                   if (myLink.extractLabel("relinked") != "yes") {
                        var myOldLinkName = myLink.name;
                        var myLinkUsage = LinkUsage( myLink );
                        var myExtension = myOldLinkName.substr(myOldLinkName.lastIndexOf( "." ));
                        if (LinkUsage(myLink) == 1)
                             var myNewLinkName = myPrepend + myPageNumber + String.fromCharCode( myASCII ) + myExtension;
                             var myOldImageHDfile = new File( myLink.filePath );
                             var myRenameResult = myOldImageHDfile.rename( myNewLinkName );
                             if (myRenameResult)     {
                                  myLink.insertLabel("relinked", "yes");
                                  myLink.relink( myOldImageHDfile );
                                  try {
                                       myLink = myLink.update();
                                  catch(err) {}
                                  myASCII++;
                                  WriteToFile(((myLinksCounter < 10) ? (" " + myLinksCounter) : myLinksCounter) + " - " + myOldImageHDfile.name + " --> " + myNewLinkName + "\n");
                                  myLinksCounter++;
                             else {
                                  if (new File(myOldImageHDfile.parent + "/" + myNewLinkName + myExtension).exists) {
                                       WriteToFile("CAN'T RENAME LINK -- " + myOldImageHDfile.name + " to " + myNewLinkName + " because the file already exists\n");
                                  else {
                                       WriteToFile("CAN'T RENAME LINK -- " + myOldImageHDfile.name + "\n");
                        else {
                             if (!IsObjInArray(myLink, myMultipleLinks)) {
                                  myMultipleLinks.push(myLink);
         var myMasterSpreads = myDoc.masterSpreads;
         // Master spreads
         for ( m = 0; m < myMasterSpreads.length; m++ )
              var myMastSpr = myMasterSpreads[m];
              var myPageNumber = myMastSpr.name;
              var myPrefix = myMastSpr.namePrefix;
              var myLinks = myMastSpr.allGraphics;
              var myASCII = 97;
              for ( n = myLinks.length - 1; n >= 0; n-- )
                   var myLink = myLinks[n].itemLink;
                   if (myLink.extractLabel("relinked") != "yes") {
                        var myOldLinkName = myLink.name;
                        var myExtension = myOldLinkName.substr(myOldLinkName.lastIndexOf( "." ));
                        if (LinkUsage(myLink) == 1)
                             var myLinkLetter = (myLinks.length == 1) ? "" : String.fromCharCode( myASCII );
                             var myNewLinkName = myPrepend + '_master_' + myPrefix + myLinkLetter + myExtension;
                             var myOldImageHDfile = new File( myLink.filePath );
                             var myRenameResult = myOldImageHDfile.rename( myNewLinkName );
                             if (myRenameResult) {
                                  myLink.insertLabel("relinked", "yes");
                                  myLink.relink( myOldImageHDfile );
                                  try {
                                       myLink.update();
                                  catch(err) {}
                                  myASCII++;
                                  WriteToFile(((myLinksCounter < 10) ? (" " + myLinksCounter) : myLinksCounter) + " - " + myOldImageHDfile.name + " --> " + myNewLinkName + "\n");
                                  myLinksCounter++;
                             else     {
                                  if (new File(myOldImageHDfile.parent + "/" + myNewLinkName + myExtension).exists) {
                                       WriteToFile("CAN'T RENAME LINK -- " + myOldImageHDfile.name + " to " + myNewLinkName + " because the file already exists\n");
                                  else {
                                       WriteToFile("CAN'T RENAME LINK -- " + myOldImageHDfile.name + "\n");
                        else
                             if (!IsObjInArray(myLink, myMultipleLinks)) {
                                  myMultipleLinks.push(myLink);
         // Multiple images
         if (myMultipleLinks.length > 0) {
              for ( a = myMultipleLinks.length - 1; a >= 0; a-- )
                   processMultiUsedLinks(myMultipleLinks[a]);
         WriteToFile("\r--------------------- Script finished -- " + GetDate() + " ---------------------\r\r");
         if (myLinksCounter == 0) {
              alert("No links have been renamed", "Rename Links Script");
         if (myLinksCounter == 1) {
              alert("One link has been renamed", "Rename Links Script");
         else if (myLinksCounter > 1) {
              alert(myLinksCounter  + " links have been renamed", "Rename Links Script");
    //--------------------------------------------- Functions ------------------------------------------------
    // Check how many times the link was placed
    function LinkUsage(myLink) {
         var myLinksNumber = 0;
              for (var c =  0; c < myDoc.links.length; c++) {
              if (myLink.filePath == myDoc.links[c].filePath) {
                   myLinksNumber += 1;
         return myLinksNumber;
    // Relink the links placed more than once
    function processMultiUsedLinks(myLink) {
         var myExtension = myLink.name.substr(myLink.name.lastIndexOf( "." ));
         var myMultiUsedLink = new Array();
         var myAllLinks = myDoc.links;
         for (var d = 0; d < myAllLinks.length; d++)  {
              if (myAllLinks[d].filePath == myLink.filePath) {
                   myMultiUsedLink.push(myAllLinks[d]);
         try {
              myLink.show();
         catch(err) {}
         var myNewLinkName = prompt ("Enter a name for this image", GetFileNameOnly(myLink.name), "This image is placed " + myMultiUsedLink .length + " times");
         if (myNewLinkName) {
              if ( myNewLinkName + myExtension != myLink.name ) {
                   var myOldImageHDfile = new File( myLink.filePath );
                   var myRenameResult = myOldImageHDfile.rename( myNewLinkName + myExtension );
                   if (myRenameResult) {
                        myLink.insertLabel("relinked", "yes");
                        myLink.relink( myOldImageHDfile );
                        try {
                             myLink = myLink.update();
                        catch(err) {}
                        WriteToFile(((myLinksCounter < 10) ? (" " + myLinksCounter) : myLinksCounter) + " - " + myOldImageHDfile.name + " --> " + myNewLinkName + "\n");
                        myLinksCounter++;
                        for (f = myMultiUsedLink.length-1; f >= 0 ; f--)
                             var myCurrLink = myMultiUsedLink[f];
                             if ( myNewLinkName + myExtension != myCurrLink.name ) {
                                  myCurrLink.insertLabel("relinked", "yes");
                                  myCurrLink.relink( myOldImageHDfile );
                                  try {
                                       myCurrLink = myLink.update();
                                  catch(err) {}
                   else     {
                        if (new File(myOldImageHDfile.parent + "/" + myNewLinkName + myExtension).exists) {
                             WriteToFile("CAN'T RENAME LINK -- " + myOldImageHDfile.name + " to " + myNewLinkName + myExtension + " because the file already exists\n");
                        else {
                             WriteToFile("CAN'T RENAME LINK -- " + myOldImageHDfile.name + "\n");
         UpdateAllOutdatedLinks();
    // Clear labels in case this script has been already run on the current document
    function crearLabels() {
         for (var f =  0; f < myDoc.links.length; f++) {
              if (myDoc.links[f].extractLabel("relinked") != "") {
                   myDoc.links[f].insertLabel("relinked", "");
    function UpdateAllOutdatedLinks() {
         for(var myCounter = myDoc.links.length-1; myCounter >= 0; myCounter--){
              var myLink = myDoc.links[myCounter];
              if (myLink.status == LinkStatus.linkOutOfDate){
                   myLink.update();
    function pad000(myNumber) {
         if (myNumber >= 1 && myNumber <= 9) {
              x =  "0" + "0" + myNumber;
         } else if (myNumber >= 10 && myNumber <= 99) {
              x = "0" + myNumber;
         } else if (myNumber >= 100 && myNumber <= 999) {
              x = myNumber;
         return x;
    function GetFileNameOnly(myFileName) {
         var myString = "";
         var myResult = myFileName.lastIndexOf(".");
         if (myResult == -1) {
              myString = myFileName;
         else {
              myString = myFileName.substr(0, myResult);
         return myString;
    function IsObjInArray(myObj, myArray) {
         for (x in myArray) {
              if (myObj.filePath == myArray[x].filePath) {
                   return true;
         return false;
    function WriteToFile(myText) {
         myFile = new File("~/Desktop/Rename Links Script.txt");
         if ( myFile.exists ) {
              myFile.open("e");
              myFile.seek(0, 2);
         else {
              myFile.open("w");
         myFile.write(myText);
         myFile.close();
    function GetDate() {
         var myDate = new Date();
         if ((myDate.getYear() - 100) < 10) {
              var myYear = "0" + new String((myDate.getYear() - 100));
         } else {
              var myYear = new String ((myDate.getYear() - 100));
         var myDateString = (myDate.getMonth() + 1) + "/" + myDate.getDate() + "/" + myYear + " " + myDate.getHours() + ":" + myDate.getMinutes() + ":" + myDate.getSeconds();
         return myDateString;

  • Batch Rename with additional "."s, drops the file extension. Request for "Keep File Extension" option...

    I NEVER name files with extra "." s in the name. I realize that all OS's (even Windows) will recognize it, but I haven't gotten out the old mindset of 8.3 filenaming... Although I do use longer names. So... I was surprised to see that when I was renaming files as per a clients naming preference to add a period within the name, the file extension is removed.
    For example: 
    original file -  2014_10_31_1643.CR2   when batch renaming to "2014.31" + sequence, drops the "CR2" extension.
    but.... if I change it to "2014_31" + sequence, the ".CR2" remains
    Since adding multiple "." is a legitimate naming convention, shouldn't the file extension remain?  Or, possibly this could be made more flexible by adding a check box "Keep file extension"
    just a thought.

    Refer to this stackexchange article:
    http://apple.stackexchange.com/questions/47319/how-can-i-make-os-x-recognize-new -file-extensions
    The finder will only select the filename only for "known" file types.

Maybe you are looking for