Obviously you can't overwrite a file that you're still reading from. That's just not possible.
The current operation is the only one I'm aware of.
Thanks for the reply. However, overwriting source files during a batch process is a common feature in audio/video software. It's possible in Audition, for instance, as well as in third-party programs such as Sound Forge, Wavelab and Samplitude.
Presumably in these cases the software writes to a temporary file, either in RAM or on the hard drive, before deleting the original and replacing it with the new one.
I'm surprised to hear that AME can't do this for conversions that stay within the same file format (such as the bit depth of a wave file).
Presumably in these cases the software writes to a temporary file, either in RAM or on the hard drive
Correct. NLEs are typically non-destructive, however, and don't do that. All they do is read the source media, they don't alter it in any way. (And that's a good thing.)
Thanks for the response. I understand what you mean about NLEs, but the batch processing features I'm describing aren't non-linear, and can be used "destructively" if needed. (FWIW, Sound Forge and Wavelab aren't NLEs.)
Anyway, that aside, is there a way to stop AME from renaming outputted files with a numerical suffix, without having to specify the name for each file?
No. besides its bad practice to overwrite files.
If you want the same file name delete the previous file first.
Sorry but I don't understand what you mean by "If you want the same file name delete the previous file first" - if I am not overwriting the previous file (if by previous file you mean the source file), then how would I do what you describe?
Apologies if I'm misunderstanding something obvious.
I think Ann meant for subsequent exports. Like a version 2 or something. She wasn't thinking about overwriting the original source.
The short answer here is, what you want can't be done with AME.
Ok, thanks Jim.