Matthew
28th June 2005, 01:07
I wanted to trim some frames from the end of some mp3s, and using BeSplit's fixing/cutting on a couple of 48 khz vbr mp3s, I've noticed it cuts a frame or 2 from the front. mp3trim and mp3splt don't.
When the original mp3, and the fixed or cut mp3, are converted to wave (using BeSweet) and compared, the starting points are off. The BeSplit processed mp3 is missing 48 ms (2 frames) at the start. The converted output of mp3trim and mp3splt match up with the original when compared in a wave editor.
Just using a hex editor it can be seen that BeSplit cuts out a frame or two at the start, wheras the other programs produce binary identical output when compared to the original (apart from the header and the trimming at the back).
Is this a known issue?
When the original mp3, and the fixed or cut mp3, are converted to wave (using BeSweet) and compared, the starting points are off. The BeSplit processed mp3 is missing 48 ms (2 frames) at the start. The converted output of mp3trim and mp3splt match up with the original when compared in a wave editor.
Just using a hex editor it can be seen that BeSplit cuts out a frame or two at the start, wheras the other programs produce binary identical output when compared to the original (apart from the header and the trimming at the back).
Is this a known issue?