• SONAR
  • Concrete Limiter Question - Anyone Experience this Issue? (p.6)
2014/09/29 22:35:23
Anderton
Okay...I tried all the recipes given here and could get them to screw up sometimes, but not every time...frustrating. However, I think y’all got me started down the right path, because I came up with a variation on your themes. I’ve now done this like ten times in a row, including closing and re-opening Sonar and even re-booting the computer a few times, and this seemed to work every time. Can anyone verify?
 
1. Open a new project with the normal template.
2. Create a new audio track. Insert a CL into its ProChannel. FWIW only the PC master and CL buttons are enabled.
3. Create another audio track. Insert a CL into its ProChannel.  FWIW only the PC master and CL buttons are enabled.
4. Drag some audio into both tracks from the browser and hit playback so the CLs get signal.
5. Select the first audio track and save the PC preset.
6. With the first audio track still selected, load any PC preset other than the one you saved. Play some audio.
7. Now load the PC preset you saved in (5)
8. The PC opens in its full limiting/muted state. Or at least it has for me...
2014/09/30 15:04:30
Dan Cate [Cakewalk]
Hi Folks,
 
We're currently looking into this issue with the Concrete limiter. With your help we've been able to reproduce this issue in house and are investigating a solution. At the moment it looks like we may need to update the Concrete Limiter ProChannel module. 
 
In the meantime, we find that the CCL can still be used successfully by simply adding it directly to the ProChannel strip. Many users report having no issues with the CCL using this method. To reduce or eliminate your exposure to the issue I recommend not using ProChannel presets or using Project or Track Templates that include the Concrete Limiter. I also recommend that if you do run into the issue with current projects please save, quit Sonar, and reopen the project rather than replacing the Concrete Limiter module. Re-opening projects in most cases will correct problem. In our tests, adding or replacing the module can actually expose the issue more regularly. Freezing tracks that are persistent with this issue is also recommended.
 
Thank you Craig and everyone who participated in this thread and bringing this to our attention! If you have any questions or concerns, please let me know.
2014/09/30 15:10:32
Anderton
Wow Dan, that's great news. This is exactly why using Sonar feels more like a partnership than the usual company/user relationship. I suspect this will become even more of a partnership with the forum restructuring that includes all the new feedback options.
 
Also thanks for the tip on the right way to do a workaround while you continue your investigations.
2014/09/30 16:42:20
gustabo
Glad you could reproduce it Dan and I'm glad that I finally got around to filing a bug report last week...
 
2014/09/30 18:52:35
mettelus
Thank you for the post Dan! It also sheds some light on why I have never seen the issue as I have always inserted it and never saved presets/templates including it. Just goes to show that workflow can make a difference in troubleshooting.
2014/09/30 19:15:39
Splat
Excellent thanks..
2014/09/30 21:35:28
Pastacrow
woohoo! Light at the end of the tunnel!
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account