Batch or command-line editor prog? noise gate needed

[prom3theus]

[looks like there is a plugin for besweet, which i really don't use, so maybe I can get that plugin working correctly and doing what i want with that. I would still have to edit in an outside program for some things, but at least it might allow batch noise gate, resample, and other stuff]

I am looking for a cheap program I can use to edit wav files, doesn't need to edit anything else, which can do a preset of functions on a file. For instance, I might want to noise gate, apply some filter, then normalize the audio. Also, the ability to apply to all files in the editor window is a plus, if you can't get command-line. I don't think sound forge (I'm using an old version now) has the ability to simply 'apply to all' or any preset creation where I can create a set of filters to apply, like in photoshop where you can create a batch set of commands to apply at once.

I encode a lot of audiobooks to mp3 for my drive and for just listening to in my portable mp3-cd player. I apply the same exact filters to every file. I'd love a batch program where i can say
'editor file.wav -resample antialias 22050 -noisegate 30.0 -normalize .95'

or something, and I can add this to my cgi script which uses besplit to cut them into 5-minute tracks and renames them so the part number is first, not last.

Thanks for any advice.

[prom3theus]

The normalize plugin for besweet is not very flexible. In the Readme it lists about 4 preset decibal threshold levels, all of which are fairly low (highest is about -60 and I want about -35).

Looking into audacity with fishbones vst plugin now.

[prom3theus]

DirectX can't do normalize. The excuse is lame also, as I think it would be pretty easy to do it in one stream pass if you know what you are doing, but I've never handled uncompressed multimedia programming before. Seems like no different than any other non-inter-compressed data. Ie. if you can easily break it into small quanta, you can use recursion to get a lookahead in single-pass, and make changes in the recursive ascent based on what you read in the descent, just in the reverse order. If the data is not inter-frame compressed, then you should just be able to work frame by frame regardless of which direction, one would think.