46 results found

1. Batch Rename Freezes Does Not Work

   Batch Rename Freezes and program will not respond. This happened today with Version 13.0.4 so I checked for updates and found Version 14.0.0 was available so downloaded it but had same issue. A few days ago I started getting a popup about Adobe Acrobat: Acrobat quit unexpectedly. Click 'Learn more' for possible fixes. However, Acrobat did not quit unexpectedly, I had just closed an Acrobat Document. This has been going on for about a week. Wondering if there is any relation to this and Batch Rename not working. I have used Batch Rename previously in Version 13.0.4 before with no issues.

   Batch Rename Freezes and program will not respond. This happened today with Version 13.0.4 so I checked for updates and found Version 14.0.0 was available so downloaded it but had same issue. A few days ago I started getting a popup about Adobe Acrobat: Acrobat quit unexpectedly. Click 'Learn more' for possible fixes. However, Acrobat did not quit unexpectedly, I had just closed an Acrobat Document. This has been going on for about a week. Wondering if there is any relation to this and Batch Rename not working. I have used Batch Rename previously in Version 13.0.4 before with no… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  BATCH RENAME  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Batch Name doesn't work since 2022

   The Batch Rename function does not work on Bridge 2024, also didn't work on 2023.

   I keep going back to Bridge 2022 when it did work. (kinda)

   Sometimes Br '22 gets stuck if I'm renaming hundreds or thousands of files. I have to rename them in parts so I can rename all the files.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  BATCH RENAME  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Batch renumbering is unreliable

   Bridge, newest version 13.0.4.755, Windows 10 Pro.

   "Batch rename" produces unreliable results.

   A simple renumbering of frames

   from name.0000.png name.0003 .0006 .0009 etc.

   to name.0001.png name.0002 .0003 etc.

   Batch rename decides to shuffle the renumbered frames and reordering the sequence.

   Weirdly batch rename with the exact same settings, worked on my colleagues pc, same Bridge version.

   Cheers, Mikkel

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  BATCH RENAME  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. ファイルリネーム時の旧名ファイルと新名ファイルのキャッシュ書き込みについて。

   Mac os12.6.8　macbookpro2017

   ファイルのリネーム時。旧名ファイルと新名ファイルが同時に生成され大量のデータ処理時にパソコンのフリーズやメモリに多大な負荷が発生している。

   以前は旧名ファイルは表示されなくスムーズに処理されていたが。5000枚の写真データのリネームが、一瞬にして10000枚のデータ処理が必要になる今の状況は狂っている。

   以前の状態に戻してほしい。

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  BATCH RENAME  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Bridge 2023. Bug when batch renaming files with metadata

   Metadata values aren't anymore correctly extracted from picture files (NEF or JPG).
   Only ^F<value>^F<value> added.
   It was perfectly working in Bridge 9, 10,11,12.

   •  

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  BATCH RENAME  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   BUG- FIX RELEASED  ·  AdminSwati (Admin, Adobe Creative Cloud Bridge) responded

   Hi,

   
   

   The mentioned issue is fixed in the latest patch release #13.0.1.583, Please install and confirm if that fixes the issue.

   You can refer the issues fixed in the patch @ https://helpx.adobe.com/bridge/kb/fixed-issues.html

   
   

   Thanks,

   Bridge Team

6. image duplication when batch renaming

   Doing a batch rename duplicates all of my images. Bravo Adobe, maybe try beta testing this bloatware before releasing it to the public... it is far and away the buggiest software on my computer.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  BATCH RENAME  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Barch rename causes crash

   Adobe Bridge 13.02.636 prompts for an error report and then shuts down whenever Batch Rename is invoked.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  BATCH RENAME  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Batch Rename Doesn't Work

   Bug
   Bridge v12.0.1.246 operating on Windows 10 Pro

   None of the options for Batch Rename are operational: There are no presets to choose from and New Filename options are not functional--stuck on Current Filename / Name / Original Case; next choice is Text--no choice. You can remove Current Filename and begin with Text--still no choice. Completely dysfunctional.

   26 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   BUG- FIX RELEASED  ·  11 comments  ·  BATCH RENAME  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. change lot name

   when doing the batch rename doesn't work as the original file format is lost. And then the file cannot be opened since no format is recognized

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  BATCH RENAME  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. When choosing "Batch rename" and choosing "yyyymmdd" it writes 2022 instad of 2023
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  BATCH RENAME  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Bridge doesn't start number sequences with the correct number

    When batch renaming files, Bridge used to automatically advance the sequence number to the next number after the current sequence, which let you select the next group of images and they would automatically get the next numbers in the sequence. Say, files A to F are renamed to imgxxx, I would get img001 to img006. When I'd go to rename the next files, G to M, , the Batch Rename would automatically apply 007 as the next starting number, so the first renamed file would be img007.

    This worked until around 2017 or 2018.

    Now it picks some random number that's of no use to me.

    See the included images. In the first image, I have the files highlighted that I want to rename. In the second image, I have to enter 31931 to get the correct sequence number to match the original file number (1931). I'm renaming both JPG and CR2 files, so the count should increase by 6, so when I select the next batch of images, I should see it fill in 131937, which would be the next number since the last renamed file is numbered 0311836. The third image shows the results highlighted.

    The 4th image shows what Bridge thinks the next number should be. 31943? Where di that come from? In the 5th image I had to enter the correct number, 031937. Image 6 shows the next batch, which starts at 1945. Batch Rename should automatically pick 031945, like it would for over a decade before, but nope, image 7 shows it picked 31953.

    Fix this so it works like it used to. I had to avoid newer versions of Bridge because this was a hassle. And now I can't even go back to the older versions because someone at Adobe decided it would be useful (it wasn't) to delete my older versions that worked right.

    The way it worked for years before 2017 or 2018 (I can't even provide the version it changed because it's been deleted) is the proper way it should work. This gets old real fast when working with hundreds of images. I tend to rename them in batches of about 50-100 since Batch Rename has frequently skipped images or mixed up their orders in larger batches in the past.

    Oh, and get a better bug report system. Five short lines of text might have been fine in the early 80s.

    When batch renaming files, Bridge used to automatically advance the sequence number to the next number after the current sequence, which let you select the next group of images and they would automatically get the next numbers in the sequence. Say, files A to F are renamed to imgxxx, I would get img001 to img006. When I'd go to rename the next files, G to M, , the Batch Rename would automatically apply 007 as the next starting number, so the first renamed file would be img007.

    This worked until around 2017 or 2018.

    Now it… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  BATCH RENAME  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Metadata not available for batch rename

    I am unable to use Metadata entries for batch rename using Bridge v13.0.
    Additionally it seems to be not possible to save templates containing a condition with metadata entries.

    Rolling back to Bridge v12.0.3 and everything works fine.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  BATCH RENAME  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    BUG- FIX RELEASED  ·  AdminSwati (Admin, Adobe Creative Cloud Bridge) responded

    Hi,

    
    

    The mentioned issue is fixed in the latest patch release #13.0.1.583, Please install and confirm if that fixes the issue.

    You can refer the issues fixed in the patch @ https://helpx.adobe.com/bridge/kb/fixed-issues.html

    
    

    Thanks,

    Bridge Team

13. Batch Rename Milliseconds 000 After Editing Files in ACR

    When trying to batch rename files that have ACR settings in a .XMP sidecar file, the batch rename always puts "000" for the Milliseconds field instead of reading the original timestamp. When I delete or rename the .XMP files to not match and then do the batch rename, it works, but then I'd loose the metadata.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  BATCH RENAME  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Bridge 2022. Error en Batch rename

    Version 12 error. I have reinstalled version 11 and it does not appear. Attached Chat

    • 

    11 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    6 comments  ·  BATCH RENAME  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    BUG- FIX RELEASED  ·  AdminSwati (Admin, Adobe Creative Cloud Bridge) responded

    This issue is fixed in Bridge 12.0.1, now batch rename files in pairs RAW + JPG

15. Adobe Bride 2022 batch rename

    Batch rename is just grayed out. I can't click it. I've given permissions, I've done the reset/purge game. Just simply grayed out. Any ideas?

    Or otherwise, any other programs that people use to do this same feature? I'm not married to Bridge and I'm sure some other thing would be less buggy than the hell that is Adobe.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  BATCH RENAME  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Batch Rename is deleting files

    This just started today. When I select files and do a batch-rename, they disappear. It will not undo. I shut down and restarted my computer, and I un-installed and re-installed Bridge, but the problem persists.

    Mac Powerbook running 12.5, Bridge 12.0.2.252

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  BATCH RENAME  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Photo Downloader Order Reversed

    Photo downloader USED TO show files in the order shot. That is, oldest first, then next, etc. So when renaming and numbering you'd get them numerical as oldest as lowest number, newest as higher number.

    Not anymore. Now it shows newest first, so when you rename/renumber you get newest as the lowest number, oldest as the highest number. Please go back to the old way.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  BATCH RENAME  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Batch rename works incorrectly if there is a dot '.' in the new filename

    Heads Up: To avoid this error don't define new filenames that contain a dot.

    In Bridge Batch Rename, if I choose to use a new filename that has a dot in it (e.g. name1.name2_unique-identifier) then the RAW files lose their extension and the JPEG files are named differently, see typical results below:

    For the JPG's: name1.JPG, name1(1).JPG, name1(2).JPG etc.
    For the ARW's: name1.name2_unique-identifier etc. i.e. NO ARW extension.

    This destroys the association between out of camera RAW and JPG.

    REMEDY: With a bit of care the batch rename can be used again (once for the RAW and once for the JPG) to alter the naming, restore the .ARW to (just) the RAW files and restore the association by using the EXIF info. But it's fiddly.

    Heads Up: To avoid this error don't define new filenames that contain a dot.

    In Bridge Batch Rename, if I choose to use a new filename that has a dot in it (e.g. name1.name2_unique-identifier) then the RAW files lose their extension and the JPEG files are named differently, see typical results below:

    For the JPG's: name1.JPG, name1(1).JPG, name1(2).JPG etc.
    For the ARW's: name1.name2_unique-identifier etc. i.e. NO ARW extension.

    This destroys the association between out of camera RAW and JPG.

    REMEDY: With a bit of care the batch rename can be used again (once for the RAW and once for the… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  BATCH RENAME  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Adobe Bridge 2022 Batch Rename. BUG

    Unable to RESET Batch Rename DEFAULT Preset.
    Batch Rename window shows "DEFAULT (modified)."
    I am unable to RESET to original DEFAULT.
    Cannot apply Number Suffix to photos in Bridge.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  BATCH RENAME  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Batch Rename Doesn't Work (ver 12.0.1.246)

    None of the options for Batch Rename are operational: There are no presets to choose from and New Filename options are not functional--stuck on Current Filename / Name / Original Case; next choice is Text--no choice. You can remove Current Filename and begin with Text--still no choice. Completely dysfunctional.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  BATCH RENAME  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close