Is there any software that will do this to a mp3?

I know eac does, but I don't want to use that to rip cd's and what then do I do with mp3's that I already have on my hard drive?

Thanks,

~ Danny

Mmmm... with foobar, I use the "Edit MP3 Gapless Playback information" to fix that inconvenience. (it was named "fix vbr mp3 header in 0.8")

(hey. i didn't say it was easy to do!)

I do this all the time with mp3directcut

If the silent parts contain absolute silence and not noise, then you can as well use a hex editor to cut the empty frames. I find it hard to make an exact selection in Mp3DirectCut.

Is there any way to do it in bulk fast, without manualy dooing each track?

and is there a CD ripper out there that isn't eac and will do it (with lame)?
I will use eac if that is the only thing that will do it.

Just then, what with the tracks that I already have?

Mp3trim (mptrim) with Batch Conversion. It is payware and may delete too many frames in certain cases. I think it disregards any bit reservoir when deleting leading silence (but I might be wrong). Doesn't allow for a safe 'keep x silent frames' (add 0.1 s simply adds crafted empty frames).

Thanks for your help, the silance isn't that annying to pay to get rid of it.

Thanks

This sounds like something that mp3packer should do, but it doesn't look like it does.

I wonder whether it may be worth posting to Omion's thread and asking the question...

Edit: When I say "should" I mean that it would make a sensible optional switch.

Edit 2: Hmm.. changelog has the entries "Also tweaked the silent-frame detection." and "Remove all data from frames which have been determined to be silent.". Sounds helpful.

Remain on the legal track. Thats fine.


Sounds like the frames still remain there, only without any data – i.e. 32 kBit/s.

Ha, I should make myself clear, they are legal tracks
I admit, I use bittorrent sometimes but not near as oftern as I buy cds. [/offtopic]

I think he just meant that he wasn't willing to pay for Mp3trim (he wants a free solution to the problem).

Yeah, what I was more getting at is that there may be some routines already in mp3pack that Omion could easily repurpose to provide a switch that removed leading and trailing silence.

On second thoughts, I'm not sure if this is relevant to mp3pack, as mp3pack's main goal is to decrease filesize without changing actual audio data. It's a thought though (if it was added as an optional switch, and most of the code was already there).

I'm planning to test mp3pack's -z switch to see what that does, as I'm a little confused at the moment.

It's not automatic but MP3 Doctor is able to make a fairly precise selection. Payware though...

Mp3 doctor looks intresting, If it wasn't for the fact it was payware I would give it a shot!

I was writing between the lines that it is possible to acquire certain files...

Mp3Packer is already a very useful tool. It would be nice if it could trim silence (with an option to keep some), because I am doing a lot of manual trimming.

I just came across this thread, and I finally figured out why you wanted mp3packer to output null bytes when silence is encountered (from the mp3packer thread)

To answer your implied question, this would be difficult to add to mp3packer, for two different reasons:

1. Removing the ending silent frames would need quite a bit of retooling. mp3packer goes from the first frame to the last, and in order to check if the frame should be thrown out, it needs to know if all the frames from the current one to the final one are silent, which would require a potentially large variable-length list and a bunch of nasty (to code) delays. It's possible, but I don't want to do it without also being able to remove silence from the beginning, which is impossible because:
2. Removing silent frames from the beginning frames actually may result in an un-repackable file. The problem is that a silent frame may be used for storing data from any following frames, and removing them may cause too much data to be stored in later frames. It's kind of odd, but it wouldn't work all the time.

Even throwing out a frame which has no data in it is slightly dangerous, as the frame's data could be entirely contained in another frame. Frames which look silent may actually be quite loud!