Inspiring

Answered

Bridge is STILL removing the file extension when performing Batch Rename

Forum|Forum|5 years ago
June 16, 2020
3 replies
4774 views

In the past, I could select files, go to Batch Rename, input my renaming criteria, and the changes would be made without affecting the file extension. However, for quite a while now, I have had to manually add a "new file extension" line to my Batch recipe in order for the files not to drop a file extension completely. See attached images to see what happens when I leave off the appropriate extension in the recipe.

Nothing I've tried has worked and I've searched various Adobe forums off and on for ages. I just updated to the new 10.1.0.163 Bridge today (that released alongside Photoshop 21.2.0) AND reset my preferences.

Nothing helps. Any ideas?

Edited to add, this also means the cache has to be rebuilt for all the images.

This topic has been closed for replies.

Correct answer carynorton

I appreciate the effort, and I also hope someone from Adobe sees this.

Before I switched to Sony's Compressed Raw files I was shooting Uncompressed then converting to DNGs, but I saw no difference in quality if I just shot directly to Compressed, so I abandoned that practice and haven't used DNGs since. I actually don't mind the sidecars though I have considered DNG to eliminate this problem.

I've had this problem in the past with DNGs and really ALL file types. I was just doing some testing to try to capture a screen recording to show exactly what's happening and I couldn't get the problem to happen—like when you take your care in to the mechanic, right?

In this testing I found a couple of things. When I coudln't get the problem to present itself, I was simplying renaming "Testing_" with a number sequence after that text, and NO New Extension line. It worked great. On DNGs, CR2s, ARWs. BUT THEN! I realized my normal file system, which is loosely based off the old Magnum negative system, has a lot of periods in it. For example, 2020.30.7R3.0001 (that works out to one line for the "2020.30.7R3." and another line for the Sequence number). So I tested again, and added a couple of extra Periods in my text string. BINGO. Not only did it fail, but it borked Bridge all together. I had to Force Quit it and reopen. I also dragged in the window so you could see the mess it leaves the file names in when it crashes. I tried it again with _ instead of . (underscores instead of periods) and it worked flawlessly. ie testing_testing_test_ [number sequence]. No problem at all. I tried again and replaced ONLY the first _ with a . to read "testing.testing_testing_" and it froze Bridge AGAIN. I guess I'm on underscores in my filenames until Adobe fixes this bug.

I have a video of this happening if it is needed (there's no way to attach the video directly to this reply).

I reported both recent crashes to Adobe via the Crash Reporter with detailed descriptions to recreate.

Chief Mickey

New Participant

This is still happening. Just had it happen today to both Nikon Raw NEFfiles and the JPG files. I had to use the replace extension drop to get the files back into usable. Come on adobe? Renaming is pretty vital for this app?

L

Lumigraphics

Brainiac

Im not seeing this with HEAVY use of Bridge. In fact, I just used Batch Rename on hundreds of files this morning and none lost its extension. What sort of filenames do you have?

carynortonAuthor

Inspiring

I have stopped trying to rename in Bridge since my naming convention includes using a "." (period) as a separator. Using a period vs something like an underscore, as of the last time I tried it, completely borks the file name and truncates the file extension fully, no matter what type of file it is. It worked fine for years and years, and then some under-the-hood-change happened in the last several years (before this orginal post from 2020) and using a . as a separator just absoltely went off the rails. I still use A Better Finder Rename for most of my bulk renames.

carynortonAuthor

Inspiring

Replying again to the original post. This issue was fixed once and only once by resetting things as suggested by gary_sc. This issue is STILL happening.

gary_sc

Community Expert

Hi Cary,

Trust me, I'm digging. I'm also hoping that someone from Adobe sees this.

Meanwhile I did think of one thing to prevent the disconnect of the sidecar files from the original files. Have you ever converted your images into DNGs?

For most people this is a complete option. I do chose to do this because of a number of the advantages, others do not chose to do this because of concern of not being as good as the original raw file. FWIW, I've not found that to be evident in the 14 years I've been doing the converting.

However, for you this might be a way to keep the data of the sidecar file associated with the raw file becuase, amongst other things, the DNG format is a container file and the sidecar data is contained within the DNG format. Think of them like little folders.

I'd also be curious as to whether this format would not lose the file extension.

Let me know, thanks!

carynortonAuthorCorrect answer

Inspiring

I appreciate the effort, and I also hope someone from Adobe sees this.

Before I switched to Sony's Compressed Raw files I was shooting Uncompressed then converting to DNGs, but I saw no difference in quality if I just shot directly to Compressed, so I abandoned that practice and haven't used DNGs since. I actually don't mind the sidecars though I have considered DNG to eliminate this problem.

I've had this problem in the past with DNGs and really ALL file types. I was just doing some testing to try to capture a screen recording to show exactly what's happening and I couldn't get the problem to happen—like when you take your care in to the mechanic, right?

In this testing I found a couple of things. When I coudln't get the problem to present itself, I was simplying renaming "Testing_" with a number sequence after that text, and NO New Extension line. It worked great. On DNGs, CR2s, ARWs. BUT THEN! I realized my normal file system, which is loosely based off the old Magnum negative system, has a lot of periods in it. For example, 2020.30.7R3.0001 (that works out to one line for the "2020.30.7R3." and another line for the Sequence number). So I tested again, and added a couple of extra Periods in my text string. BINGO. Not only did it fail, but it borked Bridge all together. I had to Force Quit it and reopen. I also dragged in the window so you could see the mess it leaves the file names in when it crashes. I tried it again with _ instead of . (underscores instead of periods) and it worked flawlessly. ie testing_testing_test_ [number sequence]. No problem at all. I tried again and replaced ONLY the first _ with a . to read "testing.testing_testing_" and it froze Bridge AGAIN. I guess I'm on underscores in my filenames until Adobe fixes this bug.

I have a video of this happening if it is needed (there's no way to attach the video directly to this reply).

I reported both recent crashes to Adobe via the Crash Reporter with detailed descriptions to recreate.

gary_sc

Community Expert

Hi Carynorton,

I've tested this with both Canon raw images and jpgs and I'm not getting this. Can you go to Bridge's Uservoice and register this? It's apparently a bug with your camera's images.

https://adobebridge.uservoice.com

Also, just so you know, when you change the name Bridge will have to recache the images because the link of name to chashe to image needs to be the same.

carynortonAuthor

Inspiring

I appreciate your reply. I have also tried on Canon raw files and any other file you can imagine. I just tried again with CR2 files, just to test, and the issue happens there, too.

Also, in the past when my image renaming still functioned as it was intended, the cache files reflected the new names and did not re-render. It's only when the filename gets borked in the process and the sync between the file name and the cache files goes out of whack that I've seen any issue.

At any rate, I will gladly register this issue again at Bridge's Uservoice. I registered this same issue at Uservoice back in January and recieved no replies.

carynortonAuthor

Inspiring

That's great news, the fallback solution worked!

I'd be very grateful if you tapped the "Correct Answer" for me. What this does is to help others who have the same problem as it leads them to solutions.

Thanks in advance!

Well, now it's broken again. I've reset the preferences, purged cache, and reset spaces AGAIN and this time it didn't fix the problem. Any suggestions?

I've tried resetting a couple of times and it is still losing the file extension every time.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded