i'm looking for a little app (console is fine) that will quickly remove all silent samples from the beginning/end of a wave file. kinda like the thing in eac that does the same, but that only works when extracting. need it for live recordings and such that i download but can't extract, or when extracting 'ranges' which eac handles differently.

also is this a good idea, to do this, or a very bad idea. i'd like some opinions.



p.s. - kinda looking for something like a gap killer with similar results, but isn't post-process.

Try WavTrim... it should do just what you need.

- M.

WavTrim says it only removes digital silence, so it wouldn't work with live recordings.

No; when you launch the "Options" menu there is a tab called "Analog trim." By default this is off, but you can enable it if desired and set the threshold (dB) under which WavTrim will remove near-silent passages.

- M.

alright, i played with it a little ... it's pretty good.

two things, though. in the options, on the "trim start" tab, there's a check box for compacting file headers ... is that for riff headers? or keeping that checked would cause it to not add any extra stuff to my file right? and that's a good thing, right?

the second is on the "trim end" tab. theres a check box for truncating files. it says it saves disk space, but at what cost? is this lossy compression, or what?

thanks for any feedback ...

If "Compact the file headers" is left UN-CHECKED, WavTrim will simply modify the start-position of the audio in the header itself, and leave the WAV data untouched. If it is CHECKED, WavTrim will physically remove the unwanted audio from the file, and write a canonical WAV header. This is a slightly slower process, since removing data from the beginning of the file means that the entire file must be re-written.

"Truncate the files" also physically removes silence, from the end of the file. This process is quite fast, since the file itself does not need to be re-written.

Both processes are simply for specifying the removal of data you have already discarded, and do not use any sort of "compression." They are safe to use.

The default settings provide for fastest performance, but checking "Compact the file headers" should not produce a significant slowdown, and does result in files that are more compatible with some post-processes, since they are truly canonical.

- M.

ok, thanx for the explanation ...