I am rather relieved that I have never had the issues below that were reported by others in this thread:

• Plugins losing settings
• Sidechain crashes
• Midi editing crashes
• Non-working automation
• Huge delays on MIDI arpeggiator

I feel with you, I would go totally nuts if I had those issues! I am using the last released Sonar 2017.10.
 
Hm, stretching audio clips is CTRL + SHIFT + drag nowadays, although that took me some time to get used to as well...

CarriageHouse
Question are your waves plugins cracked or not current version?

I used to have this problem until I went legit with Waves and afterwards plugins losing their settings stopped happening to me.

None of my plugins are cracked and they're always up to date.

Audio dropout! When switching around in the asio panel for a different buffer size, I usually get the audio dropout. 

sharke
With regard aux tracks, could it be possible that you don't have input monitoring enabled on them? You need to have that enabled to hear them. Got me a few times. An example of poor design rather than a bug though - it's really counterintuitive and almost certain to cause confusion among people who, quite reasonably, presume that an aux track should be heard straight out of the box without having to enable anything. 

Agree, but input monitoring is not my the issue here. I know I have a few projects with issues, will try and make a video at some point to illustrate the problems :-)
 

CarriageHouse
Question are your waves plugins cracked or not current version?

All legal and current here :-)

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.  
 

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.....

tried using VST 2 instead ?

That could be it, but at this point I'm in the process of transferring all of my active projects to a DAW that can hold onto plugin settings (regardless of VST2 or VST3), so I guess it doesn't matter one way or the other. Might be something for the new Sonar team to look into though, perhaps there are still some bugs related to VST3 compatibility. 

I raised the question a few month ago, but was met with sword and shield replies saying:

"Yes, that is what we wanted"  I will try to rephrase my concern, maybe a kind soul will understand what I mean and hopefully backs my request to a new tech team of Sonar.
 
Sonar with one of the last updates enabled a feature where new recordings utilize  "EMPTY SPACES" of take lanes, placing recorded content randomly,  not to create additional take lanes.
The logic is fine with me. I get it!!  BUT it also records takes  to muted takes. Muted takes means... that I do NOT want to hear them. Why in the world it would record there?
To me this is a MATH 101 mistake. It just does not make any logical sense  to deliberately record stuff on muted lane. I doubt that in real life situation anybody here would record anything on muted lane.
 
This is probably my biggest nemesis in Sonar, since I am mostly using it to record live vocals... And I would appreciate if this bug was fixed or possibly an option to tick to "NOT to place new recorded content on muted take lanes"  
 
 If it maters to somebody besides me, I wrote to Sonar tech support when it was still part of  Gibson.  A few weeks later I received a reply. They admitted a bug, but it was never corrected. My sincere hope that 
Bandlab will take this in consideration and improve this bug.
 
Maybe there is a feature that I am unaware of, if so, kindly point me to it.... to avoid automatic recorded content to be placed on previously muted lane.
 
I know work arounds.. to create a new track...for example, but that diminishes whole idea of take lanes.
 
Thank you.

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