Glitch in exporting with Batch Process to Mp3

[PT Educa28645906mg5q]

I Tried to export multiple wav files in batch process.  One of the files is (bica_6b.wav).
Unfortunatelly the result file (bica_6b.mp3) has some glitch, that I think it was some fragments from another snippet (from the next file; bica_6d.wav)

This occurs several time with differents projects and on random files.

1. Version of the app is 25.0.0.47 Build

2. Platform and OS version is Windows 10 Pro 22H2 OS Build 19045.5487

3. Basic steps to reproduce the problem:

Drag multiple wav file to batch process, activate or tick the export option and run with no favorite or effects applies. I attach the screenshot of my Export Settings.
4. I expected the result audio should be without any change or glitch, but the actual result has some glitch that suspectedly is cuts or fragments from the other file.

[SteveG_AudioMasters_]

Usually when these things happen, the root can be traced back to Audition's temp file setup. There are a few things to note; firstly that ideally, the temp file location that you use shouldn't be shared with any other temp function (I have mine set up on a fast SSD of its own). You can set the location of this in Edit>Preferences>Media and Disk Cache. Don't worry about the secondary temp - we've yet to find out what it does! The other thing you might need to change is in the Data tab. Where it says 'Maximum number of concurrent file processes', keep that number low. I have it set to 3 and it works fine. The larger that number, the greater the chances of temp file cross-corruption are.

[PT Educa28645906mg5q]

Hi Steve thanks for replying,
I've checked both and as I remember I never change them so they are still in the default setting.

If I delete the files in the temp folder will it help? 
Or do I need to move the temp folder to another location? Maybe to other directory in the same disk since I don't have other disk for this.

Should I lower the Maximum number of concurrent file processes' to less then 3?

[SteveG_AudioMasters_]

Yes you could try reducing the number of processes. If you reduce it to one, and the same thing happens, then we'd have to look somewhere else! But if it works better, then this may indicate some sort of an access issue with the temp directory.