Razorwit
Hi CakeAlexS
Good thought, but still doing it after full reset and rescan. In fact, sometimes it pops and the meter seems to "stick"....
 
 
When it does that the meter is pegged but no sound is coming out. If I bypass the plug the meter drops to -inf. Re-enable it, loud pop and the meter sticks like that. I only see that now and again but it sure is weird.

This sounds like the behavior associated with Pentagon's Valleys Simulation. The picture shows an instrument track, could it be a Pentagon track?

scook
This sounds like the behavior associated with Pentagon's Valleys Simulation. The picture shows an instrument track, could it be a Pentagon track?

Hi scook - Nah, it's a TruePianos track in that pic, but it does it on anything I put it on. Even a project with only one audio track. That particular meter behavior only happens once in a while, but the pop is consistent. 
 
Dean

Razorwit
Hi CakeAlexS
Good thought, but still doing it after full reset and rescan. In fact, sometimes it pops and the meter seems to "stick" :

 
When it does that the meter is pegged but no sound is coming out. If I bypass the plug the meter drops to -inf. Re-enable it, loud pop and the meter sticks like that. I only see that now and again but it sure is weird.
 
Funny thing is that it's only happening with this one plugin. Everything else seems to work just fine....Waves, UAD, FabFilter...all of it.
 
Dean

This is exactly what I have been experiencing.  The same sound, the same stuck meters (even the red plus nine db level showing).  For me it was only happening in when I had lots of instances of glisseq running in the project.  I guess channel tools might have been more of my issue than the eq - ill experiment with this a bit.
 
This issue was bugging me so much that i re-installed everything (windows 8, sonar, pluggins etc - just to be sure it wasn't my user error). Everything works fine up until the sonar 3xc patch is run - then all the problems start.

Has a solution been found for this issue? I'm running into similar issues.
 
Often when I insert one of the pre made FX chain modules, I get a load pop, at which point Sonar no longer produces any audio on any tracks. However the strange thing is I'm not getting any of the pegged meters, or even any indication of the pop on any of the meters. When I disable the FX chain module, another load pop is heard and the audio in all tracks return.
 
Here are typical repro steps:
 

1. In an audio track (I'll call it the vocal track), drag/drop the FX Chain > Vocals > BG Vocals 1 PX2 FX chain module.
   Result: Hear a loud pop.
2. Start playback.
   Result: No audio from any tracks.
3. Mute the FX chain module.
   Result: Loud pop and all tracks start playing back, including the vocal track.
4. Unmute the FX chain module again.
   Result: Loud pop and all audio in all tracks go away.
5. Double-click the FX chain module to open it.
6. Mute the VX-64 module.
   Result: No change.
7. Mute the Tempo Delay module.
   Result: Load pop and all audio returns, including the vocal track audio.
8. Unmute the VX-64 module.
   Result: Load pop and all audio goes away.
9. Double-click the VX-64 module to open it.
10. Mute the Tube Equalizer section.
    Result: Load pop and all audio returns.

 
Some more observations:

1. If I re-create the exact same FX chain module from scratch using the same plugins and same settings for each, I cannot reproduce the problem.
2. I tried with both 32-bit and 64-bit engine selected, same results.
3. Sometimes the problem is not reproducible at all, and none of the FX plugins exhibit the problem. It seems to be random.
4. None of the meters in any track, buss or main shows the loud pop. My speakers and ears however are very much experiencing it.
5. This sounds like max DC clipping, however the meters not showing this is a bit strange.
6. I'm not hallucinating.

 
EDIT: I found that repeatedly dragging/deleting the same FX chain module into the FX bin will randomly result in an instance that reproduces the issue. Once it doesn't reproduce the issue, it seems to stay in a good state. So keep doing it if you are trying to repro the issue.

CakeAlexS
I tried 1 to 4 and could not reproduce...
My BG Vocals 1 PX2.fxc file is 198,801 bytes.
 
Thanks

Mine is the same size. Other info:
 
MD5: 797BF6561A884756694AAA99CD01F753
Modified Date: 9/6/2013
 
Somehow I have a feeling it has to be something else. Did you try to add/remove the FX chain multiple times? It seems to randomly go into that state for me.

That sound very similar to the old patch browsing within Dim Pro issue (I think it was Dim Pro). You are happily browsing through the sounds then every dozen or so a horrendous sound emanates from the monitors/phones and Sonar craps the bed. I haven't had that happen since X1 (mind you I haven't done that type of repetitive patch loading with DP for a while either) and I haven't seen it brought up for a while but it does sound similar and it's making me wonder whether it's a RAM overload issue or something.
 
Mind you it's not a single pop. It's like a weird horrific swelling of noise THEN a loud "KAPRRRRAAAPP!"
 
Scared the pizzle out of me the first time it happened... hurt my ears too.
 
Edit... oh and Sonar would crash or at least white screen. The manifestation of tracks disappearing and what not sounds like a build up to a crash. X1 used to crash pretty danged hard on me, X2 would just freeze. X3 has only crashed once and it was because I was being an numbskull (pressing ctrl + z a million times instead of using the history).
 
Put a limiter on your Master bus (but remember it's there and turn it off while you are mixing) while your doing stuff you think might result in this. It'll protect your gear and ears... supposedly. Not sure if that kind of thing would bypass the master. It's just what someone recommended to me when I originally reported this.

CakeAlexS
Hmmm here is an idea (for laughs)... rename your AUD.INI + update your sound interface drivers and firmware..
 
Cheers...

Was that for me? I ain't touching my firmware right now. Everything is working relatively well at the moment. Everything will get updated to current versions when I wipe the rig and reinstall everything.

Beepster

CakeAlexS
Hmmm here is an idea (for laughs)... rename your AUD.INI + update your sound interface drivers and firmware..
 
Cheers...

Was that for me? I ain't touching my firmware right now. Everything is working relatively well at the moment. Everything will get updated to current versions when I wipe the rig and reinstall everything.

Nope Silk - sorry...

CakeAlexS
 because I didn't understand why and where Sonar and all the other crap on there was sending sh*t.
 
LOL :)

Well to be fair I was kind of TRYING to do the right thing by sending my audio to the E drive and my project files to the C drive. That... apparently... is wrong... and I didn't realize that every time I did a Save As that the audio would default back to my C drive (even though I pointed the audio path to the E drive when I started the project).
 
So yeah... I got stuff all over the bloody place and right now I'm just sending stuff to my C drive because it works and I'm not really writing a ton of new audio files anyway.
 
So that'll be the next big clusterfuffle I'll be bugging everyone about. Setting up the rig and the paths. I've got a good plan but support and the forum will have to suffer through another round of derpy beepisms as I sort that out. For now though I'm just cleaning and reorganizing my apartment.
 
Smells like Pinesol in here.
 
wheeeeee!

Renaming AUD.INI didn't help. I also switched between all driver modes and it didn't make a difference either.
 
I'm not 100% sure that FX chain module gets into that bad state only when initially dropped, but once it is dropped successfully that it would then continue to work properly. I think that is the case, and if so I can live with it. Since it is very obvious when in this bad state I can just keep retrying until I get a good instance.
 
BTW I once got the meters to peg into the red (the FX Chain module, its track, its buss and the main meters), but usually the meters don't show anything.
 
Not too serious but annoying.

It has nothing to do with Audio drivers. I have seen this behavior on various systems, always related to the Channel Tools, insomuch that deleting it fixes it. Deleting all instances, saving, opening and then reinstantiating Channel Tools ALWAYS fixes it.

CakeAlexS

eikelbijter
It has nothing to do with Audio drivers. I have seen this behavior on various systems, always related to the Channel Tools, insomuch that deleting it fixes it. Deleting all instances, saving, opening and then reinstantiating Channel Tools ALWAYS fixes it.

Sadly this is the sort of typical confusion that normally happens when we post two different issues on the same thread. I was responding to SilkTone,  FX Chain > Vocals > BG Vocals 1 PX2 FX chain module does not contain Channel Tools. Unless I've missed something in which case somebody better relieve me of my confusion.... Cheers...

Well, a search showed this thread as the closest related issue. It could very well be that this is something to do with FX Chain modules (the container itself) since when you add any FX plugin (including Channel Tools) to a ProChannel module, an FX Chain module is automatically created. I'm very sure it has something to do with the FX Chain module container because I've never seen this behavior in a track's FX bin. I guess I can play around with FX bins and FX Chain modules and see if any pattern emerges.
 
Also I'm trying to figure out if the initial issue had any resolution so I can see if the same fix/workaround resolves it for me.

SilkTone
 
 
Well, a search showed this thread as the closest related issue. It could very well be that this is something to do with FX Chain modules (the container itself) since when you add any FX plugin (including Channel Tools) to a ProChannel module, an FX Chain module is automatically created. I'm very sure it has something to do with the FX Chain module container because I've never seen this behavior in a track's FX bin. I guess I can play around with FX bins and FX Chain modules and see if any pattern emerges.
 
Also I'm trying to figure out if the initial issue had any resolution so I can see if the same fix/workaround resolves it for me.

Hi SilkTone,
I never did get a fix for the problem I was having. That said, I also never called support, so I haven't really tried all that hard.
 
Dean

Uh, not sure Alex. My solution so far has been to just replace instances of channel tools with Waves S1 and move along. I haven't really tried deleting and whatnot.

Dean