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!
 
 

Anderton
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 also use Concrete Limiter on several tracks on many projects and have never had any issues with CL. FWIW...
Walt
 

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."

I have not seen this with concrete limiter however I did have a similar experience opening an older project that had a specific fx chain in the PC. This chain had 2 instances of the Sonitus eq and one of Span. 
 
There was no sound reaching the speakers but the levels in the meter on X3 were pegged. I think my rme card clipped the output which saved my speakers. 
 
Once I narrowed the problem down I was able to delete the fx chain and add another. Since it was a saved fx chain I did not have to tweak anything.
 
I my case I chalked it up to the project being created in x2. I have not had a repeat of this so far. (Knocks on wood)
 
Have you double checked that you do not have more than one copy of the Concrete Limiter's dll on your system?

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 

I have no problem with CL.

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...
 
 

I have had the CL give me the problems you describe. Next time it happens i will save an alternate version of the project and send it to the bakers.  I usually do the same thing,  create a new track or bus and copy all settings.
 
my specs are below 

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.   

I've encountered this problem once before just after the Concrete Limiter was first released.
At that time I got into the habit of deleting everything in the picture cache folder before opening a project, which to this day seems to have solved a number of small annoyances.  Having said that, if closing and reopening the project solves the problem, I suspect cleaning the picture cache folder has little to do with this issue.
 
But, you never know