I did some sleuthing on my side.
 
I rolled back the Engineering Suite update, forced a re-download and reinstalled it, that made no difference.
 
I rolled back the Sonar update, forced a re-download and reinstalled it, that made no difference.
 
So, I went into preferences/audio/driver settings and unchecked the 64-bit Double Precision Engine (DPE), because that had been a culprit in a number of issues in past months for some people. I hit Play, and then the Adaptive Limiter seemed to work the way it is supposed to. Surprisingly, though, re-checking the DPE did not break it!
 
Further testing revealed this: if the DPE is checked when an existing project that already contains the Adaptive Limiter is opened, or the Adaptive Limiter is added to a project when the DPE is checked, hitting Play will cause the ring modulator and/or extremely loud tone symptoms, and they will not stop until the limiter is bypassed, even though play is stopped. If you subsequently uncheck the DPE and play a few seconds, then recheck the DPE, the symptoms will not occur. Also, if the DPE is not checked when the existing project is opened or when the Adaptive Limiter is added, the symptoms will not occur.
 
This may be a bug that can be fixed.
 
In the meantime, I'll probably just leave the DPE unchecked in general.

That's some good sleuthing, ptheisen. If the workaround is that simple, just leave the 64-bit engine off. Shouldn't be a problem, unless you start noticing some noise down around -384 dB.

That works for me as well by unchecking DPE, and I also found that I could re-check it again and all ok.  It SEEMS to be the first instance of unchecking solves it.  I could then add more instances and it would be ok...even if re-checked again.
 
Going back to MMCSS, it didn't always work unchecking in different sessions. 
 
One last item, and I'll dbl check this too.  I'm putting this on my master buss FX bin, as it's easiest to hear right off the bat.  I'll try single tracks and see what gives. 
 
At any rate, checking and unchecking stuff...seems to be "somewhat" of a cure. 
This was similar behavior to my Boz VST3 plugs too.  But a Sonar update (or one of Boz's updates??) seemed to cure that as it doesn't happen anymore with his stuff.

busses, tracks...it doesn't matter. 
The DPE seems to be more the ticket now too...unchecking it.  I find I can then re-check it AFTER the limiter is already loaded.  But if I add another instance of the limiter, it happens again....so it isn't reliable just unchecking (and rechecking) once.  Uncheck the DPE and all is ok ...and then I can re-check it again each time I add an instance of the limiter.  (or just leave it off)
 
BTW...the meters are going without scrolling thru the timeline....like there is a crazy noise floor happening.  Turn the limiter off...the sound still remains when playing (like a ring modulator), but the meters are just frozen about 2/3rds the way up.

I've had the 64 bit DPE shut off since X1. Some systems just don't like it, no idea why.

All this said, I'm really liking the limiter.  Seems several steps up from the concrete and another league from Boost 11.  This one looks like a definite winner.

Hey Folks,
 
We are trying to come up with a way to reproduce this issue in house so that we can resolve it in an update to the Adaptive Limiter. So far we haven't had any luck recreating the issue on any machines at Cakewalk. I'm wondering if we can get some additional info...
 
What sample rates you are using when this happens?
 
What type of manufacturer of CPUs you are running? AMD? or Intel?
 
What type of processor is it? Quad? Duo? i5? i7? Something else?
 
What OS are you using? Win 8? 8.1? 10?
 
 

Lance,
 
I was one of the ones that reported experiencing the Adaptive Limiter/DPE issue and described the circumstances I was aware of at the time to make it happen for me in post 11. When I saw your post, I tried reproducing it again today and initially I could not. Then I stumbled onto an additional factor that was required to make it happen, at least in my case. The latency on my audio interface had to be set at 64 samples in order to experience the problem. Any other setting, higher or lower, worked fine.
 
I have a Focusrite Saffire Pro 40 running at 44.1khz; Intel i7 4770k; Windows 10 with the Creator update, although the initial occurance was prior to my DAW receiving the Creator update.
 
Hope this helps. Let me know if you need any other info, I'm happy to provide.

My stats in my sig with win 10. 64 samples with Steinberg UR44 interface

Thanks for the additional info guys. If anyone else experiencing this issue could also provide similar info on OS & CPU that would be great. We'd also like to know if others are also running at 64 samples on their audio interface.