this post was submitted on 09 Feb 2025
519 points (97.6% liked)
Technology
62009 readers
4219 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A lot of people cant tell the difference between MP3 @320Kbps and a fully lossless FLAC.
All people. 320kbps mp3 is completely audibly transparent under all normal listening conditions. It's a low-tier audiophile meme to claim otherwise but they will never pass a double-blind test.
MP3 has some disadvantages over more modern formats, regardless the used bitrate. It's been a long while since I was very interested in audio formats, so I may not be up to date on some newer developments but unless anything major changed, MP3 can't do truly gapless playback between tracks (used in live albums), for example.
Aren't there unofficial extensions to mp3 for gappless playback? IIRC you can tag tracks as gappless and many audio players will make them so.
Yes and no.
IIRC an MP3 track is divided in fixed-length frames and unless the actual audio matches perfectly with the end of a frame, it's not possible and that's why cross-fading plugins for audio players were invented. The padding data is there either way but can be documented in the metadata section of a file.
Last I checked (and that was years ago, so I may be wrong) this approach was never perfect and prone to breaking. It's an inherent flaw with the format where some form of workaround exists.
That said, for most use cases this is irrelevant.
Audio playback is such a low-demand process, surely a player (e.g.VLC) can spare a thread to line up playback of track 2, a few seconds before track 1 ends? It knows the exact length of the track, why can't track 2 be initiated when the audio level in track 1 drops to zero (or minus infinity dB) in the last frame?
Workarounds in a specific player don't negate the fact that the format has limitations.