P: Batch is removing parts of names after . in name

[FeedbackCommunityMember]

when running a batch to save as a jpg from tif files, anything with a (.--) is removed....
For example, file ABCD23.5.tif is saved as ABCD23.jpg, so .5 is removed... and other files are skipped or not processed at all.... previous versions has no issue with this... but when running an action while the file is opened, it is saving with a .5, but with thousands of image, i can't be opening them all as opposed to running a batch. Something done different from previous version?
https://feedback.photoshop.com/

[brich4d]

Myself and another coworker as having the same saving issue as part of an action. Removes any text after the first . (period). Saving 8 bit tifs from 16 bit tifs. Action has been working for at least four years with minor changes. No changes in the past two years. I am running Photoshop 2020 on a Mac Pro (Mid 2012) with macOS High Sierra 10.13.6. Co-worker is running Photoshop 2020 on a MacPro (Late 2013) with macOS Mojave.

[J453]

Try using Scripts > Image Processor... as a workaround

That should preserve your file naming.

[FeedbackCommunityMember]

I have a series of 3d renders with sequential names like...

render.0001.exr
render.0002.exr
render.0003.exr  etc..

Previous to the new 2020 update, I could open these files in photoshop and run an action that would tweak various things then save a tif version to a folder on my desktop.  But now when I run the same action (or try to make a new action), the files save as 'render.tif' instead of 'render.0001.tif', so running the action on ten files in a row just repeatedly saves 'render.tif' over itself again and again.

That's a bizarre behavior change and affects my workflow several times a day.  I assume it must be bug because It makes no sense for Photoshop to ever silently change a file name like that.

[Lumigraphics]

There is a known issue with Bridge Batch Rename removing the file extension with a double dot in the filename. I wonder if this is related?

[brich4d]

I don't use Batch in my action. My action knocks down 16bit ProPhoto files to 8bit sRGB. Then saves the file to a different folder. This is where the problem arrises. Somewhere when it goes to a different folder. If I didn't have the file going to a different folder and just saving over the original, the problem doesn't exist. My action is Crop, convert to sRGB, 8bit, Save (not save as.)

[JJMack]

Photoshop 2020 Actions with Save As steps will save incorrect File names when Document names contain "."  where prior versions of Photoshop work correctly. 

Reported is Photoshop Forum
https://community.adobe.com/t5/photoshop/photoshop-21-0-2-batch-action-file-type-change-error-period...

[alanr41133096]

Just updated to photoshop ver 21.0.3 and the problem persists. 
It seems that Adobe does not monitor these forums or take any actions to address the issues raised in them.
So what's the point?
Getting very fed up with Adobe. they have buildings full of well paid engineers, what are they doing?

[J453]

We very much monitor and fix issues reported here. You can see a running list here: https://helpx.adobe.com/photoshop/kb/fixed-issues.html#photoshop-desktop-fixed-issues

The last update was primarily to enable the Hardened Runtime capability to support Apple's notarization requirements for macOS apps and fix the top crashing item for Windows with Select Subject.

[MaeryA_]

So why you don't fix also this bug? I'd like to update PS, but I can't, because I need the saving through Action runs properly...

[J453]

It is being worked on.

[J453]

This should be fixed in the 21.1 update that went out last night.

[The Haven 9]

Does PS take account of Windows 10 maximum file lengths (when folder names are included)? PS Batch processing is truncating my file names but I am using a series of nested folders (more than before when I haven;t had an issue) which could be making the jpg filenames total folder+filename length longer than Windows allows.

[The Haven 9]

Perhaps some one from Adobe could reply to this as they say they monitor these posts?

[PECourtejoie]

Hi, Carol, did you try Image Processor as a possible workaround?

[The Haven 9]

No - but I have just opened PS and found it so I'll give it a try. Thank you.

[J453]

This was fixed in 21.1 or later.