# Sigma 300 (ADAU145x) Slew Volume Rates

Slew volume controls can filter noisy control inputs and minimize clicks.  Often the desired slew rate can be found by experiment.  However, in some applications it would help to know the actual slew rate a given setting yields.  For example, the ADAU1701's slew rates are described at https://ez.analog.com/message/156092#156092

The -1452's slew volume controls are different (and more versatile) than those of older SogmaDSPs,  There's separate rise and fall settings, each with several curves to choose from.  The "RC" curve setting shown here provides slewing similar to that of the older slew volume blocks, thus the slew rates can be measured the same way (see the post cited above).  Although this RC curve is exponential in nature (it follows the RC characteristic that includes the term e^(-t/RC), the -1452 slew block also offers a separate exponential choice. Testing the -1452's RC slewing this way results in the table below.  Slew times are given as a time constant as well as the dB/s rate often specified for SigmaDSP dynamics processors.

The Sigma 300's Exponential slewing operates in ways both similar to, and different from, the RC slewing.  The post at Sigma 300 (ADAU145x) Exponential Slewing describes the differences.

Linear slew settings yield these 10 -- 90 % rise and fall times.  If you prefer 0 -- 100 % times, multiply these times by 1.25..

Parents
• Next chapter: constant dB

As expected this basically multiplies the value by some constant each frame until it reaches the endpoint, specifically by 1+δ when rising or 1-δ when falling. (Note that this implies it falls a bit faster than it rises for any given parameter value.) The values of δ for slope parameter values 0...63 are easiest to express in binary:

` 0  0.00011 1  0.000101 2  0.0001001 3  0.0001 4  0.000011 5  0.0000101 6  0.00001001 7  0.00001..60  0.0000000000000000001161  0.00000000000000000010162  0.000000000000000000100163  0.0000000000000000001`

Based on limited testing it appears the exact update is:

x = x + max( floor( δ * x ), 1 )  when rising

x = x - floor( δ * x ) - 1  when falling (this is wrong, see later post)

until the target value is reached of course.

• Next chapter: constant dB

As expected this basically multiplies the value by some constant each frame until it reaches the endpoint, specifically by 1+δ when rising or 1-δ when falling. (Note that this implies it falls a bit faster than it rises for any given parameter value.) The values of δ for slope parameter values 0...63 are easiest to express in binary:

` 0  0.00011 1  0.000101 2  0.0001001 3  0.0001 4  0.000011 5  0.0000101 6  0.00001001 7  0.00001..60  0.0000000000000000001161  0.00000000000000000010162  0.000000000000000000100163  0.0000000000000000001`

Based on limited testing it appears the exact update is:

x = x + max( floor( δ * x ), 1 )  when rising

x = x - floor( δ * x ) - 1  when falling (this is wrong, see later post)

until the target value is reached of course.

Children
No Data