Copy link to clipboard
Copied
Hi, I'm using the latest version of Audition and this bug has finally got on my nerves enough to actually post about it.
In some cases when using batch process and using a custom favorite chain (with specific first-party and third-party VST3 plugins), the audio file comes out damaged, like some parts of other audio files in the batch list get pasted into the opened audio file, in random spots. This is not a common thing to happen and happens very rarely but it is too big of a bug to ignore, as I have to then constantly check if all files were processed successfully without glitches and is really a time waster when you get to more than 50 files. Please fix this as this problem has been present since I started using Audition CC (CC2021, or maybe even older), so it's been going on for too long!
It's a rare thing to happen but still worthy of posting.
Currently using Audition CC v24.6 (Build 24.6.0.69) on Apple M2 Max, macOS Sonoma 14.6.1
Copy link to clipboard
Copied
This has been mentioned before. One of the issues with batch processing, and indeed any processing that happens in waveform view, is that it involves the use of temp files. Quite often, if the temp file location is in the 'default' location, it's sharing that space - and that can cause accesss issues. What many people have found is that if you relocate your Audition temp file location to a non-shared space with good access, the apparent problems magically disappear. It's not guaranteed, but you have to try this first. So what do you really need for a good temp file? The ideal is for it to be on a drive of its own, and a fast one at that. So if you get yourself an external USB SSD, you should be good to go. The advantage of these drives is that they are quick, so access speed is good. The other thing you could try, especially when processing is complex, is to limit the number of concurrent file processes allowed. Processing might take slightly longer, but it will inevitably be less error-prone. You can access the setting in Edit>Preferences>Data - third item. Mine on this laptop is set to 2 - no problems.
The chances are that this isn't a bug - it's about optimising settings.
Copy link to clipboard
Copied
Hey Stege, thanks for your input. I'll try your suggestions as they are very specific! I hope that this will solve it for now, thank you!
Copy link to clipboard
Copied
I've been having the exact same problem, except more prevalent, happens to 1-10% of files when batch processing. This has been a problem for the last few years and just assumed it was a problem they would fix eventually, but even on the most recent version of Audition it is happened, if not more now, than before. For reference, looks like below:
I have now changed the concurrent file processes to 2, but wanted to ask about the advice on setting audition temp files to a "non-shared space", where do I find the temp files, and are you suggesting I need to purchase a whole other external SSD just for adobe audition temp files?
Copy link to clipboard
Copied
Edit>Preferences>Audition Audio Disk Cache is where you can alter the path to them. And yes I really am suggesting that you get an external SSD and dedicate it to the task of handling temp files. I've got the DAW I use set up like this, and have no problems at all with glitching. Maybe I've just been lucky, but I suspect not...
One thing to note about using an external SSD is that it should be connected directly to your machine, and not go via any sort of USB hub. It's fine to have slow drives, mice, etc going via a hub, but not anything that is potentially in a hurry.
Copy link to clipboard
Copied
Thanks Steve! Yeah it's a bit wild as I use other software like pro tools and logic with no issues, only adobe that does this specifically with batch processing (fine for everything else I use it for). I also don't think it was a problem with older versions. I'm not particularly up for the idea of buying a dedicated hard drive just for that haha! But it is an annoyance having to check over 100s of files for glitches like this whenever I use batch processing, the software itself should not do this in my opinion, it's essentially destroying audio files. I keep lots of back ups but not everyone will. Hopefully just changing the concurrent file processes might help for now (fingers crossed)!
Copy link to clipboard
Copied
Hi Steve, Just tried the external SSD USB 3.2 and it is a no-go. Glitches are still showing up. We are processing audio files for books and it is a problem. We can't reduce the max concurrent processes due to our timelines. Did you happen to find a sweet spot with batch jobs? What is the max number of audio files that you are processing at once and/or what is the max audio length? I did contact Adobe support and they have a bug number, DVAAU-4205679, but no ETA on the fix. If anyone has any suggestions in the meantime, it would be really appreciated!
Copy link to clipboard
Copied
Steve sorry, had a typo "g" there in your name, my apologies. One more question, do I change only the "Audition Audio Disk Cache" or do I also change the "Shared Media Cache Files" and "Shared Media Cache Database" locations to external SSD?
Copy link to clipboard
Copied
It's only the Audition Audio Disk Cache that is affected by this directly - the other two caches are related to Multitrack behaviour.
Copy link to clipboard
Copied
Good to know, Steve. I've been bitten by this too.
Copy link to clipboard
Copied
Well, it's definitely a bug either way. I tried your settings and it worked....at least that's what I thought. It just made the problem not pop up as often but today it still happened to me! I'm thinking of switching to Reaper now as I've had other problems with audition that are unbearable...
Copy link to clipboard
Copied
I have the exact same problem. Really bad and frustrating. I've lost hours of work because of this already, initially thinking it was a problem I caused. Turns out it's a software issue.
Copy link to clipboard
Copied
I am having this issue too.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now