Skip to content

Latest commit

 

History

History
90 lines (61 loc) · 3.66 KB

README.md

File metadata and controls

90 lines (61 loc) · 3.66 KB
Raw

AudioEzDynamics

Classes for controlling dynamic range of audio.

Currently the following usable classes exists:

  • PeakCompressor: Compressor / Expander with Peak Detector.
  • RMSCompressor: Compressor / Expander with RMS Detector.
  • PeakDynamicsLo: Upwards Compressor / Downward Expander with Peak Detector.
  • RMSDynamicsLo: Upwards Compressor / Downward Expander with RMS Detector.
  • PeakDynamicsHi: Compressor / Expander with Peak Detector. Might sound bad. See discussion below.
  • RMSDynamicsHi: Compressor / Expander with RMS Detector. Might sound bad. See discussion below.

Usage

Example of processing a single channel of audio.

#include <dynamics.hpp>
using namespace ezdynamics;

///...

auto c = PeakCompressor();
c.setAttack(100.0);
c.setRelease(300.0);


c.setKnee(0.0);
c.setMakeup(0.0);
c.setRatio(2.0);
c.setThreshold(-25.0);
c.setFs(48000.0);
//c.setRMSTime(10.0); //If using RMSCompressor()
c.reset(); // Reset buffers.
for (int i = 0; i < x.size(); i++) {
	double tmp = c.calc_gain(x[i]);
	y.push_back(tmp*x[i]);
}

Info

Compressors

DynamicsHi

Repos has classes a PeakCompressor() and RMSCompressor() based on the design in Fig. 7c in ref. [1]. Can also be used as an upward expander.

It applies attack and release to the calculated gain in the log (dB) domain.

DynamicsHi

PeakDynamicsHi() and RMSDynamicsHi() are added for completeness. Used for DownwardCompression (aka. regular compression) or Upward Expansion. Based on design outlined in Fig.7a in ref. [1] The same paper outlines some issues with this design:

  • Sudden increases in volume leads to a "lag" in the attack. Since it needs time to ramp up to the threshold.
  • Unnatural sounding release, due to release being applied in linear domain. This applies to compression. if it also applies to upward expansion, I'm not sure.

DynamicsLo

DynamicsLo

PeakDynamicsLo() and RMSDynamicsLo() class. Same as DynamicsHi classes, but used for Downward Expansion or Upwards Compression.

Note that the issues with DynamicsHi, does not show up in the same way here.

  • No lag in the attack. There is,however, a lag in the release, since sound level needs to fall below the threshold before gain starts being applied.
  • Not sure if release applied in the linear domain sounds bad for upward compression or downward expansion. Needs to be investigated. But implementing release in the dB domain seems hard, without complicating the design. The magnitude of the gain (in dB) gets higher the more silent the input signal. And thus the release time can get very short if the soundlevel drops to silence.

Discussion on release lag for DynamicsLo processors

If the lag in the release is undesireable, the LevelDetector can be moved to the end of the sidechain, in the linear domain. This will remove the lag entirely, but might lead to distortion, when the soundlevel is above the threshold. The distortion could for instance be removed by removing the softKnee functionality and introducing a "hold time" as is know from gates.

Another option would be to keep the level detector at the start of the sidechain, but set a max. level above the threshold the soundlevel is "allowed" to go.

Extending the code

New classes / dynamics processors can be created by inheriting from some of the abstract classes in "src/dynamics.hpp" Custom level detectors can also be made by inheriting from some of the abstract classes in "src/level_detectors.hpp"

References

[1] Giannoulis et al. (2012) Digital Dynamic Range Compressor Design—A Tutorial and Analysis