LLyons

sharke

LLyons
Sharke - I know this doesn't help but for the life of me, and I don't want to trivialize it, I have not stumbled on a waves setting not being saved.  My projects regularly have 20 to 30 waves tools on them, and I am editing roughly 3 hours every day,  so I believe that I SHOULD be seeing this behavior.   It could be many things, I know - but I DO NOT USE MIDI - I wonder if that might hold a clue.  
 

Well Sonar is definitely sending these plugins a message telling them to reset themselves. What form that message takes, I don't know. There could be multiple sources for these erroneous messages. I've seen these resets happen when the project loads as well as in the middle of a session. I've seen it happen when starting or stopping the transport and I've also seen Waves EQ's have bands adjusted (gain and Hz values) through doing something as simple as turning the ProChannel on/off, as demonstrated here:
 

 
The problem is always with EQ's. I've seen it in the Waves Q10, the Waves V-EQ, Fabfilter Pro-Q 2 and also the Quadcurve. Someone else on the beta team said they had seen it happen with the Quadcurve when moving the playhead back and forward across the timeline. 
 
There must be something peculiar to EQ's which differentiate them from other plugins, otherwise I'd be seeing the same thing in other kinds of plugins. I think it must be that EQ parameters in VST's share the same internal ID's or something like that, and Sonar is firing off messages to these ID's somehow. Sonar definitely has a serious problem with MIDI leakage and I've seen all kinds of weird things happen, like hitting mute or solo on an audio track firing off a MIDI message to a synth on a completely unrelated track. Imagine hearing a drum machine trigger a kick drum every time you hit the mute button on a vocal, for instance. I've heard lots of talk of MIDI crosstalk in Sonar, as discussed here. 
 
I think in general, Sonar has the potential to throw around MIDI and CC messages to places they're not supposed to be. But I'm not even sure if this is the full story - as I've mentioned before, Noel once said that an earlier problem with plugins losing their settings was due to a bug in the ARA implementation. It's hard as a layman to understand exactly how all these issues tie together or whether they're all totally separate, but one thing's for sure - they exist, and many people have experienced them. Maybe this is one of those areas in which Sonar really needs a good taking apart and putting back together again.....

 
I believed you before you posted the image.  I just tested inserting Q10 and LP EQ in the effects bin and in the pro channel.  Played with them hoping I could replicate using what I was seeing, and I could not.  I tried saving and exiting the program, no avail.  Theres something else in the equation that I am missing, but I did try.  
 
Well, I hope you fair better in the days ahead with your new DAW.  I purchased another and am enjoying the learning curve.  They have different pluses and minuses so to speak, and I will keep both. 
 
Take care,
 
LL

I think the "magic recipe" to recreate this is to turn the ProChannel off, make a change to a band in the EQ, and then turn the ProChannel back on. When you turn it back on, the band that you adjusted with the ProChannel turned off will move. I just tried it again and it works (well when I say "works," I really mean "doesn't work" lol)

This would indicate some sort of caching of the plug-ins last enabled state by pro-channel, and that being restored to it upon reenable. What you really want it to do is sensibly function as a bypass, using whatever state the plug-in is in.
 
You could get into some coding trouble if you were a little too clever and made a blanket presumption that bypassed plug-ins might get unloaded and blindly added code to restore them. I don't have a machine handy, if this if true, it'll always restore to the last time a modification was made when pro-channel was already enabled.

1.  Sound goes out when using certain synths (KLC, Zeta) - You have to toggle a (any) synth in the synth rack to get the sound back, and it only lasts for a few minutes, then goes out again - the only 'resolution' is to freeze track and delete synth - which kills workflow
 
2.  Dragging loops into Sonar is hit and miss.  if it hits, life is good, if it misses, dragging loops of any size and/or format will cause Sonar to Crash
 
3.  There is still that 'bug' in the Plugin Manager, which malfunctions whenever you try to select more than one VST/VSTi/Dx/DXI/MFX plugin to move around in the creation box.
 
 

Session Drummer issue:  If I try to adjust any fader or knob in SD, it instantly goes to max or all the way to the right, and will not go back.  Now I can't adjust ANYTHING without the same result, even outside of SD.  I uninstalled and reinstalled everything.  Before using SD for the first time again, I could adjust any volume, pan, etc with no issues.  Load SD and the same thing happened again.  Using Sonar Artist demo.  

While I remember, the "Clean Audio Folder" needs looking at. Needs a total overhaul IMO. Often become unresponsive and can crash the whole program.  

Let's not forget the horror show that is ACT

One issue that still annoys me after some years with Sonar Platinum (compared to the much older Sonar 7) : In Sonar 7 I could see by how many bars/beats I had dragged a clip but Sonar Platinum only shows me to which position I drag it. For example if I wanted to copy a clip and use it again after 48 bars I just had to drag-copy it until the little number in the time line showed 49:1:000, regardless of the original position. In Sonar Platinum I have to calculate manually at which bar number I have to drop it. I have to admit that I'm not good at doing calculations in my head but I also can't understand why the programmers killed such a useful little feature...

siliconscientist
One issue that still annoys me after some years with Sonar Platinum (compared to the much older Sonar 7) : In Sonar 7 I could see by how many bars/beats I had dragged a clip but Sonar Platinum only shows me to which position I drag it. For example if I wanted to copy a clip and use it again after 48 bars I just had to drag-copy it until the little number in the time line showed 49:1:000, regardless of the original position. In Sonar Platinum I have to calculate manually at which bar number I have to drop it. I have to admit that I'm not good at doing calculations in my head but I also can't understand why the programmers killed such a useful little feature...

Have you tried using Aim Asst ?
Press the "X" key.

chuckebaby
Have you tried using Aim Asst ?
Press the "X" key.

Yes, that's exactly the function I was writing about...

In Sonar Platinum the number marked with a "B" just shows the absolute value of the new clip position while in Sonar 7 it showed the relative value, i.e. the distance from its original position. This makes much more sense in a drag/drop situation, at least to me... 

You guys are going to scare away the new buyers :-)