• SONAR
  • The good old "Loud click / peaking VU meters / DC output / horrible noise" problem... (p.3)
2016/10/20 18:45:12
PeterMc
A bit more information on this "wicked" problem:
 
I can turn off every FX bin in the project (ignoring archived tracks) and the problem persists.
Every time I turn off an FX bin there is a click noise (but no audio) whether it contains an effect or not.
Hitting the "Bypass all audio effects" button, however, restores audio.
 
I am now guessing that there is some weirdness about how plugins connect to the FX bin. I don't think it is a particular plugin because a number of us have problems with different plugins.
 
Curly question: why does this seem to affect only a few of us?
 
How do we make progress on this issue? Is it possible to instrument the FX section of code to try and narrow this down (like adding asserts when an Inf is detected)?
 
Cheers, Peter.
2016/10/20 23:41:32
PeterMc
And now a crash! Maybe this will help nail this bug. While the problem was occurring, I turned on the Prochannel compressor in the Master bus. Blam! The crash reporter did its thing - CWBRN 55858.
 
Can others try this when the problem occurs?
 
Cheers, Peter.
 
2016/10/20 23:42:17
lv455
I´m thinking in the same lines. It seems that some particular plugins are more likely to cause the problems than others but it´s still down to probabilities, ie some days are better than others.
 

I also think that once the problem has occured, removing plugins or disabling channels is not enough to make it go away. Once the problem is there, a Sonar restart at least is necessary to go back to normal conditions.
 
I might add that cycling the FX button previously would give a temporary fix but not in my current project. In other words, disabling all effects does no longer have an effect on the problem.
 
Is there some debugging software that might help finding the problem? Could we make some kind of "crash dump" without the crash to give Cakewalk something to work with?
 
If I get time this weekend, I will go through my previous projects which had this problem (all, I´m afraid) and list the plugins used, as well as the number of instances.
 
 
PeterMc
A bit more information on this "wicked" problem:
 
I can turn off every FX bin in the project (ignoring archived tracks) and the problem persists.
Every time I turn off an FX bin there is a click noise (but no audio) whether it contains an effect or not.
Hitting the "Bypass all audio effects" button, however, restores audio.
 
I am now guessing that there is some weirdness about how plugins connect to the FX bin. I don't think it is a particular plugin because a number of us have problems with different plugins.
 
Curly question: why does this seem to affect only a few of us?
 
How do we make progress on this issue? Is it possible to instrument the FX section of code to try and narrow this down (like adding asserts when an Inf is detected)?

 
2016/10/21 00:09:20
PeterMc
Try turning on the Master bus Prochannel compressor. This might trigger a crash and dump.
 
2016/10/21 00:31:39
lv455
Will do this evening!
 
PeterMc
Try turning on the Master bus Prochannel compressor. This might trigger a crash and dump.
 



2016/10/21 08:16:26
msorrels
Still happens in the 2016.10 early release, which isn't a surprise but I thought I'd mention it.
2016/10/21 13:26:30
lv455
Ok, I opened my current project and got the click thing by adding a melodyne instances. However, none of the tracks or buses inside Sonar had peaking VU meters, only the devices in the RME mixer were peaking. Apart from this, the same old problem. I added some master compressors in the Prochannels of the main buses but nothing happened. Will try again with another project.
2016/10/21 16:39:46
PeterMc
You only get peaking VU meters if you have a plugin that turns infinities into something sane. Otherwise the meters are blank. I usually have Ozone on the master bus with the maximizer activated. I tried putting a limiter on every track but now I can't get the problem to surface. I use SPAN on tracks I suspect. It doesn't make the meters show, but it's really obvious when you look at SPAN's display.
 
2016/10/21 16:57:30
msorrels
That's not the case for me.  There are no audio plugins here, I even stripped the ProChannels on both audio tracks to just the EQ (which can't be deleted).  You can see how the VU meter is pegged but Kontakt is making no audio.  When this happens the MIDI track continues to move/send but no new audio comes out of Kontakt and the two audio tracks (Kontakt and the Master channel) both stay pegged.  This is with the early release of 2016.10
 

2016/10/22 01:03:20
lv455
I do believe used to have maxed out VU meters on a previous projects, I will try to open them again and see if this have changed.
 
PeterMc
You only get peaking VU meters if you have a plugin that turns infinities into something sane. Otherwise the meters are blank. I usually have Ozone on the master bus with the maximizer activated. I tried putting a limiter on every track but now I can't get the problem to surface. I use SPAN on tracks I suspect. It doesn't make the meters show, but it's really obvious when you look at SPAN's display.
 




© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account