Report Bugs
Help us with the issues you are facing by taking one of the following actions:
- VOTE: Help us rank the most relevant bug -by doing this you will also get status updates
- COMMENT: Join the conversation and help us identify the problem
- SUBMIT: If you can’t find the issue you are experiencing, report a new one
When filing a new bug, please provide:
- Version of Adobe Bridge
- Steps to reproduce the issues
- Operating System
- Expected result
- Actual result
- Optional- Upload your File or Video
Want to be the first to see the next release of Bridge? Join the Bridge Prerelease Program
For any issues with the Prerelease builds, please use the Bridge Prerelease Forum
Thank you for your time, we really appreciate your feedback.
57 results found
-
1 vote
-
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…
1 vote -
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.
6 votes -
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 voteHi,
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
-
Bridge 2022. Error en Batch rename
Version 12 error. I have reinstalled version 11 and it does not appear. Attached Chat
11 votesThis issue is fixed in Bridge 12.0.1, now batch rename files in pairs RAW + JPG
-
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 -
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 -
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 -
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…
1 vote -
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 -
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 -
Batch rename does not work. The only option I have is Text and sequence Number
Bei Stapelumbenennung wird mir nur die Option Text und Sequence Number angeboten. Die weiteren bekannten Optionen stehen nicht zur Verfügung
1 vote -
The drop down menus in batch remain no longer work in ver. 12.0.1. A reinstall of version 12.0 seem to work properly.
Window 10, 64 bit OS.
1 vote -
Batch Renaming Pairs (Not working like it used to in Version 12.0)
In previous versions of Bridge version 11 (or older) if you have RAW+JPEG pairs, you can select only the RAW files and do a batch rename and Bridge will automatically rename the JPEG pair. Apparently, in version 12.0 this feature was either removed or is not working correctly. Just spent some time with an Adobe Rep and we just tried this in both Ver 11 and Ver 12 - This clearly works as it should in Ver 11, but in Ver 12 selecting the RAW file and doing a batch rename only renames the RAW file and will not rename…
1 vote -
Batch rename ask for new version of photoshop
When I try a Batch operation from bridge as batch rename and image processor, I got a message telling me to install the latest version of Photoshop.
I have latest version of both Bridge 11.1.0.175 and Photoshop 23.0.0.release.
So what
1 vote -
Bridge Batch Rename Bug
The batch rename function is failing to rename any files that have been previewed in Bridge.
So when trying to batch rename all the files in a given folder, the first one tends to fail as it's auto started a preview, and now Windows 10 is considering that file to be in use / protected from having changes made to it.
Infact, I can't manually rename the file in Windows either, until I shut bridge down to releasse it from that protection, allowing for changes to be made to the file.
It's a real annoyance as I'm doing batch renames…4 votes -
Batch rename skips pictures
Starting with the update before the current one, batch rename will randomly skip files in the batch.
On the previous update it was dropping the last photo in the batch. I originally thought that I was just being careless making my selections.
In the latest version, (Rev. 11.0.1.109) it will drop several out of a batch. They will not be sequential. Just several random shots.4 votes -
Extension Name Mash-Up
When mixed media files extension names are changed to the wrong media/format. I have MPV, DNG, NEF, JPG, HEIC, WAV files in one folder. I sort them chronologically. then I build a name protocol of three line elements to from YYYYMMDD-AA-BBB-XXXX. In the past, it left the extension name alone. Now many will hfe their extension switch to one of the other formats present in the folder.
.NEF BECOMES .MOV, .MOV BECOMES .NEF, DNG BECOMES MOV, .MOV BECOMES .WAV.IT IS VERY TIME CONSUMING TO FIX THESE ERRORS. (CHECKING METADATA AND LIKELY FILE SIZE TO MANUALLY RENAME THE EXTENSION NAME.
…
1 vote -
リネームの機能に不具合
(1)NEFなど、rawファイルを含むデータに、バッチでリネームをかけるとその後不具合が発生。
(2)その作業以降の「バッチで名前を変更」作業において、ファイルの種類にかかわらず、拡張子が(1)の作業時のrawファイルのものに強制的に変更されてしまい、さらに正しいリネーム作業が出来なくなってしまう。至急バグの修正をしてほしい。バカ高いサブスク料払ってるんだから、こんな初歩機能で、不具合を出さないでほしい。
1 vote -
rename
Rename adds extra numbers and text. It seems to be a portion of the previous file name. v
Also looses the suffix, so when you batch rename and drop into Bridge, Bridge does not recognise the file type.
UPDATE: I've spoken to the photographer and apparently the images were retrieved from a corrupt card, another batch from someone else seem fine.
1 vote
- Don't see your idea?