Concrete Limiter Question - Anyone Experience this Issue?

First of all, I use the Concrete Limiter a lot on tracks, for a variety of reasons. So it gets a lot of exercise around here.
 
Every now and then, it will freeze in the fully limited position, which means it doesn't let audio through. Bypassing it, bypassing the ProChannel, or replacing it with a new instance doesn't reset the limiting back to normal. I need to insert a new instance, match the settings, and remove the old instance.
 
I've been trying to send the Bakers a project where this happens, but it's really elusive. It seems as soon as you close the project and open it again, the problem corrects itself...most of the time. Sometimes I'll open a project, the CL will be at full limiting, and I'll think "aha! Something I can send!" So I save it, open it, and...works perfectly.
 
So my question is - has anyone else experienced this? If not, I guess it's system-specific and I'll quit bugging the Bakers about it. But if others are encountering this issue, I'll keep trying to find a way to reproduce it. And if you have experienced this, please give your system specs so I can see if there's any commonality. Thanks!
 
 

I have never experienced this either, and not seen this particular issue posted before. It is definitely worth letting the bakers know about; but "saving, opening, and works perfectly" seems system specific, but no clue as to "what."

Yes , I have had that happen to me only one time in a project and it drove me nut's ..
I had no idea what was going on , I shut off all the pro channels and re engaged them . the bass track w the concrete limiter wouldn't re engage the concrete limiter…the blue button was on …nothing was coming through and the C L showed no acticvity  
I wound up closing the project down w out saving and loosing a few edits I was happy with …
usually I always do a manual save every couple of effective edits…
this time I bit the bullet and cut my losses …to this day I still don't know what happened ….
when I reopened the project the concrete limiter on my bass track was working again ...
it only happened that one time , all though I didn't mention it at the time it was contributing factor as to why I started that I can't trust my DAW thread ...
 
oh , edited for system specs...
Asus Lap top , intel I3 ,  OS Win 8 64 bit , 6 gigs of ram , 2i4 usb sound card,  X3 e Pro 64 bit install . 
 
Kenny 

So far this seems to be one of those "UFO bugs"...if you've seen it, you believe it exists but you have no proof. It's really rare, and the fact that most others haven't experienced it doesn't add any clues...
 
 

The behaviour you describe Craig happens to me continually!! It drives me nuts! I have to delete the instance of Concrete Limiter from the Pro Channel and add it again. Sometimes that doesn't even work. Just last week I opened 10 different projects (one at a time) with that plug in used multiple times and had to go through every track of each project deleting every instance. I've basically given up on using it. I have tried rescanning my plug ins, uninstalling Pro Channel completely and reinstalling it again multiple times (as administrator). This has been my single most greatest frustration with X3E.   

Craig, I see this quite a lot. I've already bugged it up as best I can but as you've said it seems to sort itself out as soon as the project is closed.
 
Worse still it appears almost random and there doesn't seem to be steps that replicate it. But it definitely happens, as you know.
 
It usually catches me by surprise and causes some initial head scratching when I'm greeted with either missing instruments/vocals or total silence if it's my master buss. I don't always remember it happens and usually scratch around my mixer/sonar checking routing etc. 
 
It's also inconsistent in that one CL on a track may be working perfectly while another one doesn't. Very strange that's for sure.
 
//

I get this all the time!
I set up a template for a track such as bass guitar that loads cl in it's pc.
If I reload the saved pc preset, the cl goes silent. My only recourse is to load a new instance of cl, match the settings and remove the original instance of cl.
Running Sonar X3e x64 on win7x64.

I had a problem the other day whereby a track was making no sound but the track meter was showing activity. Turning off the ProChannel made the sound come back. I eventually narrowed it down to the console emulator at the end of the chain. Removing it did the trick.

I don't encounter this any more.

I've had this happen something like two or three times since the Concrete Limiter first came out. So very rarely. No idea of the cause.

CakeAlexS
Wasn't there two versions of CL? (i.e. it got updated).
Or am I thinking of another Pro Channel module?

I think you are thinking of the LA2A/CA2A

I had an issue when I forgot to remove the old one

Craig, as experienced as you are, can you explain why you have many instances of CL on many tracks. Can't you just render them to alleviate the CPU load?
Just asking.
dan

I've had this happen two or three times, no more than that. Deleting that instance of the CL and inserting a new one got things working again for me.

I had problems with this in the past, but cannot be sure if I have experienced it since X3/ CL update (Sleep deprivation from young family can distort temporal reality ). 
 
I will keep an eye out fo it.
 
I am still experiencing some weird graphic problems with the Ca-2a.  Hope that's not too O.T. for this thread.

gustabo
Craig,
This may be reproducible, insert cl on a track and save a pc preset.
Load that same preset that you just saved on the same track and the cl may mute...
Happens to me.

Nice catch, gustabo.  Just followed your steps and got 100% reproducible.