If you're super concerned about accuracy, then you'll want to use the Java command-line app pcutmp3, which is so far the only tool I know of which works around these issues. It's robust and free, and it has a nice graphical view of the volume level of each frame (you might need to play with the scale a bit), which although is not a true view of the decoded waveform, is usually good enough for the purpose of spotting ideal places to cut. But as long as the split points are in the middle of silence and you're not terribly concerned about losing a fractional second of that silence, then I second the recommendation for mp3DirectCut, a Windows app. This is due to complications related to various features and side-effects of MP3 encoding and decoding (the bit reservoir, encoder delay, padding, and decoder delay).

However there's a penalty: a split-second of audio around the split points often becomes unplayable, sometimes resulting in a skip or click if the audio there isn't silent. General-purpose audio editors decode MP3s and then re-encode upon saving, so avoid those.ĭedicated MP3 splitters usually slice on frame boundaries, thus the audio is not being decoded and re-encoded, which is good.

Ocenaudio cutting mp3