Batch Rename Error In Bridge

[nicholasp94971515]

I'm having a problem in Bridge where every time I try to batch rename I get a ^SEQN^ error in the images I tried to batch rename.

I've attached two screenshots of the issue.

If anyone has any idea how to fix this that would be great.

[Lumigraphics]

How many photos are you renaming?

[nicholasp94971515]

Only about 4 or 5 in separate folders. It's been working fine for years and
now all of a sudden has stopped.

[Lumigraphics]

Where did that "SEQN" come from?

[nicholasp94971515]

It's come from the Sequence field on the batch rename. It should obviously be sequentional numbers but instead it's been replaced with the SEQN. 

I have already reset workspace, cleared cache but still it appears. 

[Lumigraphics]

This isn't enoiugh information. What are you STARTING with? Your screenshot shows a photo that already has the SEQN in it.

[nicholasp94971515]

You can see in the other image that the Sequence Number (in this case) is
1704 in the batch rename but once you click ok it appears as SEQN in the
image file

[nicholasp94971515]

 

[Lumigraphics]

Look at the bottom of the image. SEQN is the starting filename.

[nicholasp94971515]

1. The preview filename at the bottom of the Bath Rename replaces the SEQN with the correct filename but once you click 'OK' it still keeps the current filename

[Mary25254818gqwp]

I am having this same issue -- can OP or anyone else help resolve?

[Mary25254818gqwp]

After some A/B testing I can see that the issue is only occuring when there are multiple "Sequence Number" components in the rename schema.

[gregreser]

Sadly, I can confirm @nicholasp94971515 original results.

I can also, sadly, confirm @Mary25254818gqwp conclusion that it is caused by repeating "Sequence Number" commands.

Interestingly, if I change one of the "Sequence Number" to "Sequence Letter", I don't get ^SEQN^ so this is a batch rename bug. Now, to find a workaround...

[gregreser]

@nicholasp94971515 are the first and second sequences always synchronized, e.g., 04 and 1704?

[Tanu Goel]

Hi nicholasp94971515,

Thank you for reporting the issue to us. This issue is added to our engineering pipeline. Team is investigating the same.

There is a workaround for this issue: Its working fine if copy /move to another folder while batch rename instead of batch rename in same folder.

Regards,
Bridge Team

[weba63719669]

Hi Tanu Goel/Bridge Team,

Thanks for adding it to the pipeline. This bug has meant I have not been able to update Bridge, Photoshop or Camera Raw because I use the batch rename too often to have it bug out and you cant have an old copy of bridge but have it work with an up-to-date copy of camera raw and Photoshop. Sadly the workaround you mentioned would waste too much time for the way I use it. 

Since it has been a bug for the last 3 years do you have any idea when it might be fixed? I would love to use the new features in all your programs.

Thanks,

Jon

[yetimade]

Me: Hey Adobe, I've found a bug with bridge

Adobe: Noted. That'll be $50 a month please.

Me: Hey Adobe, is it fixed?

Adobe:

Me: ???

Adobe: *2 years later* That will be $50 a month please.

[rayadutta]

This is still not fixed, please do something