mp3DirectCut 2.02 has been realeased on 9-March-2006



Download at: mpesch3.de

...I would have put it to 'News Submissions', but maybe the 'information is not important/potentially interesting for a mentionable part of HA members'

As it is directly mp3-related I put it here instead of the General-Audio-forum.

Enjoy another fine release - thx to Martin Pesch

edit: link added - thank you Ganymed

For those who are interested: you can get the new version here.

Has version 2.02 been withdrawn? All I found was 2.01 from June 2005.

http://fileforum.betanews.com/detail/mp3DirectCut/1010041409/1

I see a link to 2.02. Must be a proxy/caching issue your end.

This feature will break ID3v2 tags with TLEN frames, because mp3DirectCut will replace the whole frame by 0's. This prevents any sane ID3v2 parser to parse frames beyond this frame.

Why not simply remove the whole frame?

Edit: also reported the problem on the mp3DirectCut forum.

You are correct. I use Google Web accelerator and Faster Fox. When I diasbled those two and cleared the Firefox cache, there it was... exactly as discribed.

Greatly Embarassed,
Woody

v2.04 is out now.

v2.05 is out now http://www.mpesch3.de/

I thought MP3 can't be cut without re-compression. EncSpot reports different information between the original and the file, edited by mp3DirectCut. And if it's possible why isn't this technique used by software like Audition and Sound Forge?

There are certain limitations, but it's possible.

If it were, then this software wouldn't be necessary . Except that it's free, of course!

Could you elaborate a little bit?


Well, if this method is better, then why don't programers use it in professional audio editing software?

I'm no expert, but simply cutting MPEG files with a hex editor should work, more or less.


Professional audio engineers don't want to use MP3 sources in their professional audio editing...

I know a few old school audio experts (who are used to lossy analogue dubbing between pieces of equipment) and are abusing MP3 input in Sound Forge 6, by open and saving over the compressed format. I believe there is no place for lossy data output in professional apps.

I agree with that. Yesterday I cut a fragment of a song compressed using LAME and the fragment itself, according to Encspot, was compressed using Go-go.

So, what is wrong, Encspot or the claim made by Mp3DirectCut that there's no recompression? I'd really love to know.

I think it's probably encspot getting confused because cut files might not have the LAME header. I bet LAME-encoded MP3s cut with pcutmp3 (for example) show up as LAME-encoded files. I also bet MP3 files stripped of LAME headers show up as go-go.

edit: if by gogo you mean "gogo no coda" then it *is* LAME, more or less....

True but this still doesn't explain why professional audio editing software does recompress MP3 files if there is a better way.

Because lossless cutting only works frame-based (and it [afaik] still destroys the first frame of cut parts because of the bitreservoir) and audio editing software works sample-based, and for any other operation than cutting (and roughly changing the loudness) you would need to recompress the file anyway.

search for pcutmp3