Build 22.214.171.124 bug: Export setting lost in Save as batch
Repeatable error: I save 21 files as a batch, either to change format or to run a favorite. I know I want to do further processing, so I make sure "Close files upon completion" is unchecked, but I check the option to remove the files from the Batch Process panel (well, it merely says "panel," but in past versions it has always meant to remove the files from he Batch Process panel, not the Files panel). So far today, since updating Audition, all the files are closed at the end of the batch process, even though I did not ask Audition to close them. This makes me have to reopen the files, a waste of my time. And then Audition crashed!!! After restarting Audition I had to redo some work I'd already done to prepare for the second batch process that is also preparatory for the next step in my workflow. (Now I'm gnashing my teeth.)
3rd time: This time the filenames stayed in the Files window as I'd intended. But I wanted to add a couple files to the window, nd the Open dialog box does not show any files having been copied into the destination folder. This despite the directory (macOS Catalina) showing all of the files present and correctly named. The only way I could open the two file I wanted to add was to quit Audition and then reopen it. Now I see that the 3rd batch process concluded with Audition arbitrarily changing the bit depth of the files. I did not order any change to the file formatting as part of the Export Settings.
This begins to truly disturb me. I love how fast Audition is on my new laptop compared to the old one I recently drowned, but yipes. These failures in file management make me feel wary about the potential for technical failures that might cause me to have to redo work if my files are rejected after I complete my steps. A painful thought. I guess I'm going to have to make more backups than usual to make sure I can return to states that are viable until the new Audition 13 settles down.
Please correct this promptly. I suspect it's an easy fix on your end because it's a new error in the latest build. Unless, yipes, the crashing!