I know this is an old question, but I have the best answer for you. David’s answer is true that simply concatenating files will leave ID3 tags scattered inside (although this usually doesn’t affect playback, so you can do “copy / b” or on UNIX “cat a.mp3 b.mp3> together.mp3” in the extreme case).
However, mp3wrap is not quite the right tool to simply combine multiple MP3 files into one "clean" file. Instead of using ID3, it actually inserts its own custom data format among MP3 frames (the “wrap” part), which causes playback problems, especially on iTunes and iPod. Although the file will play perfectly if you simply allow them to run from start to finish (because players will skip this bytes other than MPEG), the file duration and bitrate will be reported incorrectly, which will lead to an interruption in the search. In addition, mp3wrap will destroy all your ID3 metadata, including artwork, and will not be able to update the VBR header with the correct file length.
mp3cat itself will create a good file with merged data (better than mp3wrap, for example), but it also splits ID3 tags and could not update the VBR header with the correct merged file length.
Here's a good explanation of these problems and the method (in fact) for combining MP3 files and getting a "clean" end result with the original intact metadata - this command line works on Mac / Linux / BSD, etc. She uses:
- mp3cat to merge MPEG data frames only into a continuous file, then
- id3cp to copy all metadata to the merged file and finally
- VBRFix to update the VBR header.
For the Windows GUI tool, check out Merge MP3 - it takes care of everything. (VBRFix also comes in a GUI form, but it does not complete the connection.)
joelhardi Mar 19 2018-11-21T00: 00Z
source share