wav file cleaner

[hummingbird]

I've got the excellent jpg cleaner from Rainbow S/W which strips out
all the junk that image apps like Adobe imbed to consume HDD space.

Does anyone know of a similar utility which does the same for
music wav files?

TIA

 

[John Jay Smith]

Here ya go:
http://audacity.sourceforge.net/

audacity has cleaning filter
after loading your sound in the app,
select all the sound wave and go to >
EFFECT > NOISE REMOVAL

if you want to save as mp3 you will need the lame dll file that you can find
here:
http://audacity.sourceforge.net/help/faq?s=install&i=lame-mp3


-ken www.computerboom.com

 

[hummingbird]

Here ya go:
http://audacity.sourceforge.net/

audacity has cleaning filter
after loading your sound in the app,
select all the sound wave and go to >
EFFECT > NOISE REMOVAL

Thanks but audacity is for audio noise removal and I already have s/w
for that (I won't name it in case JC gives me a mauling!)

What I'm after is a util like 'jpgCleaner' but to clean WAV files of
unnecessary bytes of clutter like Adobe Photoshop or whatever inserts
into jpg files. Many data files contain clutter inserted by the
program which created them but isn't actually a necessary part of
the file - it just takes up valuable disk space. This surplus data can
be seen if viewing a data file in binary format.

eg: jpgCleaner describes itself thus:
"JPG Cleaner is simple but powerful utility for cleaning JPG files
from anything that is not picture data. Commonly used programs such
as Adobe Photoshop are writing additional information into JPG file
that isn't needed for correctly displaying the picture."

 

[John Jay Smith]

A wave file is a pure data stream of information, there is no "clutter"
equivalent to what you have in jpg images.

The standard for cd audio sound quality is 44.1 khz sampling and 16 bit.

The only thing you can do is compress it with a lossy eg MP3, or lossless
compressor.
Lossy compressors like MP3 use algorithms to try to remove data that the
human ear
cannot hear, thus making it smaller. This can be a sort of clutter removal,
but you already know this I presume.

A lossless compressor gives a bigger file but no data is sacrificed, rather
it performs a compression similar to what ZIP does but the
file is playable, decompressed in real time.

Kenny

 

[hummingbird]

A wave file is a pure data stream of information, there is no "clutter"
equivalent to what you have in jpg images.

There can be. Any file can contain data tagged onto it by a program
but which is not actually a part of the data in the file - like jpegs
which have Adobe Photoshop or whatever splattered inside.

I have a lot of WAV files which started life as MP3s, which I've then
normalised and cleaned through CoolEdit but still retain some data
tagged onto the end of the WAV file, typically the software prog used
for the original ripping or original MP3 encoding. IIRC there are one
or two MAC programs which do this.

The standard for cd audio sound quality is 44.1 khz sampling and 16 bit.
Indeed.

The only thing you can do is compress it with a lossy eg MP3, or lossless
compressor.
Lossy compressors like MP3 use algorithms to try to remove data that the
human ear
cannot hear, thus making it smaller. This can be a sort of clutter removal,
but you already know this I presume.

Indeed. I use Lame for encoding into VBR MP3s.

A lossless compressor gives a bigger file but no data is sacrificed, rather
it performs a compression similar to what ZIP does but the
file is playable, decompressed in real time.

Quite so.

 

[John Jay Smith]

Hi, what kind of data is this? ID tags? the space needed for these is
miniscule...
I posted an id tag editor yesterday. is this what you mean?

 

[hummingbird]

A wave file is a pure data stream of information, there is no "clutter"
equivalent to what you have in jpg images.

Some more info about the clutter which I want to remove:

From CoolEdit2000 Help:

"Windows PCM (.WAV)
Microsoft Windows format. Windows WAV files support both mono
and stereo files at a variety of resolutions and sample rates. This
file type follows the RIFF (Resource Information File Format)
specification, and allows for extra user information (see Info*) to be
embedded and saved with the wave file. The standard Windows PCM
waveform contains PCM coded data, which is pure, uncompressed pulse
code modulation formatted data."

*Info:
"You can embed extra user information in Windows .wav files using the
RIFF LIST INFO and DISP type 1 formats. Store summary information
such as who played what, who was the engineer, etc. Provided that
other audio editors support this information, this information remains
with your audio file throughout its lifetime. Be sure to enter the
appropriate information here!"

 

[hummingbird]

Hi, what kind of data is this? ID tags? the space needed for these is
miniscule...
I posted an id tag editor yesterday. is this what you mean?

It's very small amounts of data for sure, but the data which gets
carried across to the WAV file is probably the original MP3tag but
this can contain unwanted info (like where the original MP3 came
from or even a website name etc). I see this as a possible security
exposure if I d/l the MP3 from usenet.
I want my WAVS to be 100% clean - just like my jpegs.

[My other post below cotains some quotes from CoolEdit200 Help
which explains what the data is in Windows .WAV files.]

BUT I've just been playing about and think I've found a solution:
If I load an MP3 into CoolEdit and then save it as a raw .PCM file,
that strips out the unwanted data. If I then re-save that file as a
Windows .WAV file - hey presto! - no unwanted data and it encodes
back into MP3 using Lame just fine.

My tests show that this circuitous route produces a .WAV file which
is smaller by about 200 hundred bytes than if I'd gone straight from
MP3 to Windows .WAV without the .PCM step in between.

 

[John Jay Smith]

I was going to look into it later...

I was thinking of that solution.. glad you found it.

--
"What concerns me is not the way things are, but rather the way people think
things are."
- Epictetus 55-135

Hi, what kind of data is this? ID tags? the space needed for these is
miniscule...
I posted an id tag editor yesterday. is this what you mean?

It's very small amounts of data for sure, but the data which gets
carried across to the WAV file is probably the original MP3tag but
this can contain unwanted info (like where the original MP3 came
from or even a website name etc). I see this as a possible security
exposure if I d/l the MP3 from usenet.
I want my WAVS to be 100% clean - just like my jpegs.

[My other post below cotains some quotes from CoolEdit200 Help
which explains what the data is in Windows .WAV files.]

BUT I've just been playing about and think I've found a solution:
If I load an MP3 into CoolEdit and then save it as a raw .PCM file,
that strips out the unwanted data. If I then re-save that file as a
Windows .WAV file - hey presto! - no unwanted data and it encodes
back into MP3 using Lame just fine.

My tests show that this circuitous route produces a .WAV file which
is smaller by about 200 hundred bytes than if I'd gone straight from
MP3 to Windows .WAV without the .PCM step in between.

 

[hummingbird]

I was going to look into it later...

I was thinking of that solution.. glad you found it.

Thanks for your help John.