Anyone seen this potentially dangerous max output bug?

Page: < 12 Showing page 2 of 2
Author
gcolbert
Max Output Level: -67 dBFS
  • Total Posts : 1176
  • Joined: 2010/11/13 18:34:06
  • Location: Windsor Mill, MD
  • Status: offline
Re: Anyone seen this potentially dangerous max output bug? 2015/06/27 19:34:40 (permalink)
I'm fairly sure I have seen this a couple of times with the PC Concrete limiter.  It probably had to do with settings getting lost, because removing the CL and adding it back in cleared the problem.

Platinum / VS-100 / 12 GB RAM / Win 10 Pro / AMD A8 / MP Touch Monitors
Platinum / on-board audio / 4 GB RAM /Win 10 Pro / HP dm4 Laptop / stuff
THpfft!
#31
lv455
Max Output Level: -89 dBFS
  • Total Posts : 53
  • Joined: 2015/03/30 15:49:32
  • Location: Gothenburg, Sweden
  • Status: offline
Re: Anyone seen this potentially dangerous max output bug? 2016/02/27 01:45:27 (permalink)
I am seeing this issue, together with a loud POP, peaked VU meters and audio engine who will only output DC. Here´s my first thread on the subject:
 
http://forum.cakewalk.com...-m3374594.aspx#3377356

Sonar Platinum, RME Babyface, Dynaudio BM5a + BM9S, Sennheiser HD650, Windows 10 64, HP Z620 Xeon E5-2667v2 32gb, GTX1070, 2x500GB SSD, Readynas 314, Readynas 214

#32
PeterMc
Max Output Level: -80 dBFS
  • Total Posts : 504
  • Joined: 2003/11/12 23:46:34
  • Location: Tasmania
  • Status: offline
Re: Anyone seen this potentially dangerous max output bug? 2016/02/27 06:03:14 (permalink)
That describes the problem I see very well. It continues to happen randomly. I don't have a Babyface - I use a Scarlett 8i6. I suspect the combination of Ozone and Sonar. Every project it happens in has Ozone on the Master Bus. Can be versions 5 through to 7, 32 or 64 bit.
 
Do you use Ozone in the projects where the problem occurs?
 

i5 6500, H170M, Intel HD 530, 16GB, Focusrite Scarlett 8i6, Win 10 Pro (1803) (64 bit), Cakewalk by Bandlab

#33
lv455
Max Output Level: -89 dBFS
  • Total Posts : 53
  • Joined: 2015/03/30 15:49:32
  • Location: Gothenburg, Sweden
  • Status: offline
Re: Anyone seen this potentially dangerous max output bug? 2016/02/27 10:42:18 (permalink)
No, I´ve never used Ozone.I might add that this problem used to be more random but now it´s a little bit more predictable: it almost always starts after an audio export, then it´s downhill from there.
 
Today, I tried to disable most plugins to find out the culprit but I didn´t really get that far. My findings so far:
 
* Disable all FX (using the FX button): worked fine, totally cures the problem.
* Disable known "problem plugins" (channel tools, VC64): No difference, really.
* Disable all Prochannel strips: Does improve things a lot! It´s still there but cycling the audio engine one or two times reverts it back to working state.
 
During my experiments, I realized that by disabling & enabling the FX using the FX button, I always managed to get the audio engine back online when it´s stuck at 9dB. Sonar also seems to be able to run longer without any problems by doing so the problem is not so much of a showstopper now as it used to be.
 
 
 
 
PeterMc
That describes the problem I see very well. It continues to happen randomly. I don't have a Babyface - I use a Scarlett 8i6. I suspect the combination of Ozone and Sonar. Every project it happens in has Ozone on the Master Bus. Can be versions 5 through to 7, 32 or 64 bit.
 
Do you use Ozone in the projects where the problem occurs?
 





Sonar Platinum, RME Babyface, Dynaudio BM5a + BM9S, Sennheiser HD650, Windows 10 64, HP Z620 Xeon E5-2667v2 32gb, GTX1070, 2x500GB SSD, Readynas 314, Readynas 214

#34
PeterMc
Max Output Level: -80 dBFS
  • Total Posts : 504
  • Joined: 2003/11/12 23:46:34
  • Location: Tasmania
  • Status: offline
Re: Anyone seen this potentially dangerous max output bug? 2016/02/27 16:34:02 (permalink)
OK, so it looks like this is not plugin specific. I also find that turning off all FX using the FX button stops the meters maxing out, but hitting the FX button again sometimes restarts the problem.
 
Do you observe the problem when the transport is stopped but audio engine is running? I do.
 
I now suspect some sort of coding feedback loop related to the FX bins.

i5 6500, H170M, Intel HD 530, 16GB, Focusrite Scarlett 8i6, Win 10 Pro (1803) (64 bit), Cakewalk by Bandlab

#35
lv455
Max Output Level: -89 dBFS
  • Total Posts : 53
  • Joined: 2015/03/30 15:49:32
  • Location: Gothenburg, Sweden
  • Status: offline
Re: Anyone seen this potentially dangerous max output bug? 2016/02/28 00:48:03 (permalink)
Yes, I do see the problem even when the project transport is stopped.
 
 
PeterMc
OK, so it looks like this is not plugin specific. I also find that turning off all FX using the FX button stops the meters maxing out, but hitting the FX button again sometimes restarts the problem.
 
Do you observe the problem when the transport is stopped but audio engine is running? I do.
 
I now suspect some sort of coding feedback loop related to the FX bins.





Sonar Platinum, RME Babyface, Dynaudio BM5a + BM9S, Sennheiser HD650, Windows 10 64, HP Z620 Xeon E5-2667v2 32gb, GTX1070, 2x500GB SSD, Readynas 314, Readynas 214

#36
gcolbert
Max Output Level: -67 dBFS
  • Total Posts : 1176
  • Joined: 2010/11/13 18:34:06
  • Location: Windsor Mill, MD
  • Status: offline
Re: Anyone seen this potentially dangerous max output bug? 2016/02/28 17:28:05 (permalink)
Engineering Effects Suite 1.0.0.13 had fixes for this.  Have you upgraded your Channel Tools and VC64?  Seems that there was also a fix to Concrete Limiter at about the same time for this problem
 
Glen

Platinum / VS-100 / 12 GB RAM / Win 10 Pro / AMD A8 / MP Touch Monitors
Platinum / on-board audio / 4 GB RAM /Win 10 Pro / HP dm4 Laptop / stuff
THpfft!
#37
lv455
Max Output Level: -89 dBFS
  • Total Posts : 53
  • Joined: 2015/03/30 15:49:32
  • Location: Gothenburg, Sweden
  • Status: offline
Re: Anyone seen this potentially dangerous max output bug? 2016/02/29 13:34:44 (permalink)
According to Command Center, everything is updated to the latest version. I don´t Channel Tools is the culprit since I removed them and the problem is still there.
 
However, I´m using plenty of effects in a current project and I´m thinking of disabling them one by one while documenting everything. Hopefully, that will give some more information about the problem.
 
gcolbert
Engineering Effects Suite 1.0.0.13 had fixes for this.  Have you upgraded your Channel Tools and VC64?  Seems that there was also a fix to Concrete Limiter at about the same time for this problem
 
Glen





Sonar Platinum, RME Babyface, Dynaudio BM5a + BM9S, Sennheiser HD650, Windows 10 64, HP Z620 Xeon E5-2667v2 32gb, GTX1070, 2x500GB SSD, Readynas 314, Readynas 214

#38
Page: < 12 Showing page 2 of 2
Jump to:
© 2025 APG vNext Commercial Version 5.1