- Status Closed
- Percent Complete
- Task Type Patches
- Category Music playback
- Assigned To No-one
- Operating System All players
- Severity Low
- Priority Very Low
- Reported Version Version 3.3
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#10612 - Dynamic Range Compressor
This patch replaces the limiter, which was, well, limited. A new sub-menu opens in the place of the limiter preamp which contains the following settings: threshold, ratio, makeup gain, knee, attack time, release time, and auto peak.
Threshold ranges from Off to -30db in 3db steps. It controls the level at which the compressor starts to work. Ratio is in 5 steps: 2:1, 4:1, 10:1, 20:1, and 60:1. This controls how much the signal is compressed above the threshold. At 2:1, the signal is mildly compressed. At 60:1 it is essentially a limiter, and the signal is reduced in gain to such an extent that its not allowed to rise above the threshold. Makeup gain ranges from 0 to 20. It applies this gain to the signal after compression to “make up” for volume loss. Knee has two setting: hard knee and soft knee. Hard knee engages full compression exactly at the threshold. Soft knee engages compression gradually from -3db to +3db of the threshold. Attack time ranges from 2.0 to 6.5 ms. It looks ahead this amount to compress the signal slightly before it’s required. Release time ranges from 20ms to 200ms. It slowly reduces the amount of compression after it’s required. Attack and release work together to reduce distortion and volume “pumping”. Auto peak, when enabled, overrides the makeup gain setting and raises it to its maximum to just avoid clipping.
This version removes reference to IRAM settings for everything except a single buffer that gets a lot of use, so there’s a big RAM hit. This is due to running out of IRAM on some targets when I included everything. I would appreciate testing on different targets, especially Coldfire targets like the h100/120, to see if this results in an unacceptable performance hit. If the performance is acceptable, I will probably do something like the timestretch feature does and only allocate the buffers if this feature is specifically enabled, which would fix the RAM hit.
Currently, the compressor is triggered with peak sensing only. Incorporating an RMS sensing feature is possible but I suspect that performance would suffer enormously.
Feedback, feature suggestions, and testing (with test_codec) would be greatly appreciated.
2009-10-03 01:59
Reason for closing: Accepted
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
Committed in r22832 / r22834
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
This is a stripped down version that removes the attack buffer and has a few performance tweaks. IRAM is back in for those few variables that are left. The attack setting is gone. The release slope is now a function solely of the release time, vs. release time and compression amount. Some code changes for performance actually hurt very slightly on my e200 but should help lower performing targets more.
This version has all the attack buffer material completely removed. I also simplified the menu. The attack menu item is completely gone. The auto peak setting is gone, replaced by an “auto” setting in the gain menu. The ratio setting are different: 2:1, 4:1, 6:1, 10:1 and Limit. Limit is an infinite ratio, meaning a hard limit at the threshold.
This version is probably 99% complete.