Re:Show HN: MP3 File Editor for Bulk Processing
by out_of_protocol on Sunday May 04, 2025 @11:40AM
(#43887358)
Isn't it a bit too late for mp3-specific tooling? There's way too many better audio formats like .aac or .opus. I see no reason to encode stuff into .mp3 for many many years already. Maybe podcasts?
Re:Show HN: MP3 File Editor for Bulk Processing
by JodieBenitez on Sunday May 04, 2025 @12:17PM
(#43887593)
> I see no reason to encode stuff into .mp3
for me it comes down to:
1/ everything can play mp3s
2/ audio quality at 320kbps is good enough for me
3/ disk space is just not an issue anymore so I don't need more efficient codecs
Re:Show HN: MP3 File Editor for Bulk Processing
by kennyadam on Sunday May 04, 2025 @12:09PM
(#43887536)
Plenty of people still use mp3 files. It’s not representative of the average person, although the average person isn’t going to be using this tool, but the large(est?) music tracker still accepts uploads in flac and mp3 format, scene releases are in flac or mp3. For a broader example, when people want to rip music from YouTube, they google stuff like “youtube to mp3” and if you google “download youtube music” top results names like “convert youtube to mp3” and the results not including “mp3” in the title offer downloads in mp3 format. It may not be technically the best format, but my parents know what an mp3 is, they have no idea what aac is.
Re:Show HN: MP3 File Editor for Bulk Processing
by pxoe on Sunday May 04, 2025 @02:51PM
(#43888615)
In a context of "converting youtube into mp3", "technically not the best format" is an understatement for what most likely is "conversion" of 128 kbps aac or opus into "320 kbps" mp3s (or whatever random bitrate). The least one could do is just listen to the aac/m4a or opus files without converting them yet another time.
Re:Show HN: MP3 File Editor for Bulk Processing
by leptons on Sunday May 04, 2025 @12:24PM
(#43887628)
Most people know what an "mp3" is. Not many people know what an "aac" or "opus" is. Mp3 just works practically everywhere, but aac and opus - not so much.
Re:Show HN: MP3 File Editor for Bulk Processing
by TheDong on Sunday May 04, 2025 @12:01PM
(#43887493)
It appears you're including libmp3lame, and linking against it, but I don't see any copy of their LGPL license included (and it's not output in 'strings', so it seems like there's probably not a menu item. I don't run windows, so I can't really check that part).
To avoid violating libmp3lame's copyright, you need to include their notice somewhere in your application.
Re:Show HN: MP3 File Editor for Bulk Processing
by precompute on Sunday May 04, 2025 @12:33PM
(#43887692)
Cool. I would certainly use this on windows if I ever need to wrangle mp3s.
On linux, puddletag provides a decent GUI for modifying audio file metadata. For bulk editing / transcoding, parallel with ffmpeg and (fd)find works very well.
Re:Show HN: MP3 File Editor for Bulk Processing
by Dwedit on Sunday May 04, 2025 @01:19PM
(#43888010)
Mp3tag is a really good program for this task, how does this one compare?
I once used MP3Tag to fix some MP3s where the artist got screwed up because the track name contained a slash, and these files had already been put into separate directories by artist. Since you could match album even recursively in directories, it was easy enough to move all the files back to their proper place.
Re:Show HN: MP3 File Editor for Bulk Processing
by cutandjoin on Sunday May 04, 2025 @01:49PM
(#43888196)
Thanks for all the comments.
This is a tool for editing MP3 files at the frame level.
It’s similar to mp3DirectCut and mp3splt in some ways, but today’s hardware enables more advanced editing of lossy audio.
Any feedback is appreciated.
Re:Show HN: MP3 File Editor for Bulk Processing
by flysand7 on Sunday May 04, 2025 @04:20PM
(#43889274)
In a change log simply stating "bug fixes" is not enough, because as a user, it's not clear whether or not any of those bugs that you have fixed has affected me. This might be my personal opinion though, I'm not sure, but when some software releases an update that says "fixed the issue where X goes wrong because of Y" and that specific thing has been annoying me for a few months, it kinda makes me happy in that moment, because I know I can expect the next update to suck a little less. Might be something to consider, but at least writing down the scope of the bug would be already better.
for me it comes down to:
To avoid violating libmp3lame's copyright, you need to include their notice somewhere in your application.
On linux, puddletag provides a decent GUI for modifying audio file metadata. For bulk editing / transcoding, parallel with ffmpeg and (fd)find works very well.
I once used MP3Tag to fix some MP3s where the artist got screwed up because the track name contained a slash, and these files had already been put into separate directories by artist. Since you could match album even recursively in directories, it was easy enough to move all the files back to their proper place.