this post was submitted on 31 Oct 2025
21 points (100.0% liked)

Android

20544 readers
222 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

🔗Universal Link: !android@lemdro.id

💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.

Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below

Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More

founded 2 years ago
MODERATORS
ijeff@lemdro.id
ladfrombrad@lemdro.id
Paradox@lemdro.id
multimoon@lemdro.id
mikestevens@lemdro.id
Devgard@lemmy.world
limerod@reddthat.com
Netrunner@lemdro.id
21
How Android handles Hi-Res audio: An audiophile's guide to the best sound (www.androidauthority.com)
submitted 4 days ago by baatliwala@lemmy.world to c/android@lemdro.id
7 comments fedilink hide all child comments
top 7 comments
sorted by: hot top controversial new old
[–] semisimian@startrek.website -2 points 4 days ago (3 children)

"considering that 16-bit, 48kHz exceeds the threshold of human hearing even for “golden ears,”

Um, no it doesn't. 16-Bit dynamic range is 96 decibels, 24-bit is 144 decibels. 96 cuts off quite a bit of an average person's hearing range. A/B a 16 and 24 bit recording and you can hear it easily over even modest headphones.

[–] randomblock1@lemmy.world 9 points 4 days ago (1 children)

https://www.researchgate.net/publication/304572591_A_Meta-Analysis_of_High_Resolution_Audio_Perceptual_Evaluation

"Results showed a small but statistically significant ability of test subjects to discriminate high resolution content, and this effect increased dramatically when test subjects received extensive training."

Basically, people can just barely detect high res audio but it's not much better than a coin flip. If you have lots of experience you're more accurate but not by a whole lot.

Anyway 48kHz sampling can produce up to 24kHz and the human limit is like 20kHz. Most songs don't have 96db of dynamic range, and 120db is hearing damage, so the idea that the average person can easily hear the difference is not true.

[–] semisimian@startrek.website 1 points 4 days ago

That's why I didn't mention the sample rate. You aren't going to get really anything back increasing to 96 khz. But I promise you increasing the bit depth leads to a noticeable change in the perception of the recording. You're not going to get anything from modern pop since it's compressed to hell and back, but find a good recording of an album you've listened to a lot and find some decent, wired headphones and try an A/B of a 16 and 24 bit mix. You'll see what I mean.

[–] fubbernuckin@lemmy.world 2 points 3 days ago (1 children)
[–] semisimian@startrek.website 1 points 30 minutes ago

Thank you, that was an interesting breakdown. I really appreciate his methodology. I'm going to deep dive into anything he has posted. Though he doesn't come to the same conclusion I do, the takeaway is:

  1. Yes, there is noticeable sound loss when converting a 24 bit sample to 16 bit.

  2. You can really screw with a 24 bit sample and still have a listenable file, presumably because of the bit depth.

  3. Recording and mastering in 24 bit benefits classical music reproduction, and I would argue, any acoustic music reproduction. So, anything with a vocal, drum kit, acoustic guitar, etc.

Since the video is about dither specifically, he does conclude that mastering to 16 bit gives the technician a sturdier product when played back on the myriad of modern equipment we have. It's arguable, sure, but since this an audiophile sub...

Really though, thanks for posting the video. Deep dive in 3, 2....

[–] heatofignition@lemmy.world 3 points 4 days ago (1 children)

Decibels?

[–] Spider89@lemmy.world 2 points 4 days ago

Yup I think So.

It's the Dynamic Range. The difference between the quiet and loudest parts of the sound (measured in decibels).

You can see the dynamic range of your audio by putting it in Audacity/Tenacity and seeing it's quiet parts and loud parts.

(I'm not well versed in audio. If I made a mistake, I'll fix it.)