Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Welcome to the Rockbox Technical Forums!

+  Rockbox Technical Forums
|-+  Rockbox General
| |-+  Rockbox General Discussion
| | |-+  Does Rockbox clip MP3's to -1...+1 range?
« previous next »
  • Print
Pages: [1]

Author Topic: Does Rockbox clip MP3's to -1...+1 range?  (Read 772 times)

Offline resetter

  • Member
  • *
  • Posts: 6
Does Rockbox clip MP3's to -1...+1 range?
« on: October 10, 2015, 11:01:12 PM »
We know that because of compression artifacts, even though MP3 encoding requires integer input (preferably without any built-in clipping, but the usable range of values is capped at -1...+1 full range regardless, usually as a 16-bit integer), MP3s can contain some peaks that go beyond full range, such as +1.025164, -1.015953, etc.

Does Rockbox clip these values to -1...+1 range or handle them in floating point?
Logged

Offline saratoga

  • Developer
  • Member
  • *
  • Posts: 8974
Re: Does Rockbox clip MP3's to -1...+1 range?
« Reply #1 on: October 11, 2015, 03:39:02 PM »
Rocbox devices generally don't have floating point units, so all decoding and processing is fixed point. Since fixed point wraps around rather than clips we leave enough headroom that no file can exceed full scale.

If you are worried about clipping, I would replaygain.
« Last Edit: October 11, 2015, 03:52:46 PM by saratoga »
Logged

  • Print
Pages: [1]
« previous next »
+  Rockbox Technical Forums
|-+  Rockbox General
| |-+  Rockbox General Discussion
| | |-+  Does Rockbox clip MP3's to -1...+1 range?
 

  • SMF 2.0.17 | SMF © 2019, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.067 seconds with 17 queries.