QUOTE(mixminus1 @ Oct 14 2006, 20:45)

Have you ever actually used mp3directcut?
Yes. I did a project to make a music mod for a game in which I used mp3directcut as the primary tool. ~100 mp3s merged to 30, 3.5 hours total music. It took a hell of a lot of experimenting and trail and error. And other miscellaneous smaller things, cutting silence from songs, a couple of fade ins / outs, and such to try to fix small annoyances on mp3s I got from places other than cds I own.
QUOTE
I've used it on dozens of MP3s encoded (and tagged) with LAME 3.96.1 at V2 and V5 and I've never had a single problem with mp3directcut or any of the files it creates.
I've had:
problems with tags (id3v1 is fine, id3v2 is unsupported)*
problems with files encoded with non-lame
problems with joining files from different encoders
problems with VBR files (more failures than successes here)
total failures to open or properly work with some files
*I recommended removing all tags above for simplicity and safety.
QUOTE
Of course, you lose the LAME header on the split files (AFAIK, SebastianG's
pcutmp3 is the only splitter that can keep gapless information), and every once in awhile you'll end up with an odd total time being reported when the file is played ("Fix MP3 header" in foobar2000 always cures that).
Fix header cures it
most of the time, but not always. I had several results that display incorrect times and even stop playing prematurely in foobar, despite fixing headers and rebuilding streams and everything else until I was blue in the face. Fortunately other players like the basic mp3 dshow codec don't have the problem.
QUOTE
Really, I've never seen anything like the problems you're describing...
Maybe you're the one who hasn't used it enough?

Or you always use it on files you encoded, and haven't encountered the weirdness of other encoders?

Or you're just really lucky, or I'm really unlucky?

I dunno.