Bug in Peak/RMS limiter
Thread Summary
The user inquired about the Peak/RMS limiter in ADAU1702, noting that the Peak Hold functionality seems missing. The RMSTC field, labeled in ms, might be a typo and should control the peak hold, while the RMSTC in dB/s controls the RMS time constant. To focus on peak limiting, the RMSTC (dB/s) should be set as low as possible. The final answer suggests posting a new question for further clarification.AI Generated Content
The Peak/RMS limiter in ADAU1702 is supposed to have a Peak Hold, according to the documentation, but it does not:
Does the RMSTC field do the same thing as a peak hold? It can be changed between ms and dB/s, so I'm not sure what dB/s means for a hold.
Also, is there a way to see what the peak limiter component is doing? If I turn the 3 RMS values to maximum, it should essentially disable the RMS component and leave only the peak component working, right? But if I do this it just behaves like an RMS limiter with the values maxed out.
Audio Signal Processors
bug_report
adau1702
SigmaDSP Audio Processors
limiter
I am going through the forum now and looking for old and possibly "forgotten" threads. Sorry that this one never was answered.
The cell you are referring to is the combination Peak/RMS dynamics processor. It looks like there were some iterations in the algorithm and perhaps the documentation refers to an outdated build.
I will check with the software team to see what the RMSTC field actually controls. The (ms) label is dubious. Perhaps RMSTC is a typo and it really should read "PeakHold".
Then, on the third control, you see RMSTC again but with the proper units (dB/s). I'm guessing this is the real RMS time constant, used to track the signal level with the RMS approximation.
I think in order to get rid of the RMS portion of the algorithm and focus on the peak, you need to turn down the RMSTC (dB/s) control as low as possible. That means the algorithm will be extremely slow to track incoming transients, and therefore the transients will have to be handled by the peak compressor code.
Hi Brett, I'm interested in the abilities of this Combo dynamic processor, but the Peak portion seems to have little effect in my decompression block. Can you confirm that the top field really is a typo for "PeakHold" and that the functionality remains intact?
This question has been assumed as answered either offline via email or with a multi-part answer. This question has now been closed out. If you have an inquiry related to this topic please post a new question in the applicable product forum.
Thank you,
EZ Admin
Please log in to reply.