I don't get it, the cw preset system always works for me, I type in the name that I want to save it as (usually ProjectName-TrackName) and hit the save icon twice, once to save it and the second time to overwrite it to make sure it was saved. Simply typing in the name and hitting enter does not save it.

 

sharke
 
Sonar - still junk 

 
I am only a semi professional (hobbyist).. But I wouldn't use anything that was junk.
 
- No more fixes
- No more support
- No more development
 
Im using Studio one now. With that said, I miss Sonar. It does things that Studio one does not.
I had no problem dealing with its quirks in exchange for a great platform to create music.
But if I were losing presets and other issues, id be gone yesterday.

chuckebaby

sharke
 
Sonar - still junk 

 
I am only a semi professional (hobbyist).. But I wouldn't use anything that was junk.
 
- No more fixes
- No more support
- No more development
 
Im using Studio one now. With that said, I miss Sonar. It does things that Studio one does not.
I had no problem dealing with its quirks in exchange for a great platform to create music.
But if I were losing presets and other issues, id be gone yesterday.

Like I've explained multiple times in different threads Chuck, I have a number of large, unfinished projects that are way too complicated in terms of track count, Fx chains, routing and automation to be transferred to another DAW. It would take me months. So until I get these finished (which is taking longer because of how poorly Sonar behaves with projects like this) then I am forced to struggle through, with all of the associated frustrations.

One odd thing I've noticed about these Sonar menu presets is that when I load the project, all of my selected presets have a star next to them indicating that they've been changed, even though they didn't have the star when I closed the project. Makes me wonder if this is a clue as to what Sonar's doing to bork my settings. 

That can happen with things like auto-running LFOs in the plug-in changing parameter values (and hence the opened version is immediately out of sync). Not saying that's what is happening here, but it does happen (and is a PITA sometimes).

KPerry
That can happen with things like auto-running LFOs in the plug-in changing parameter values (and hence the opened version is immediately out of sync). Not saying that's what is happening here, but it does happen (and is a PITA sometimes).

 
Interesting, I never thought of that. However in my case it's all EQ's, so I don't think any active LFO's 

Unlikely :-)

What's really annoying about it is when it dirties a project and you wonder if you've actually made a change or not...

That's the worry I have when I open projects now. And I have a kind of OCD urge to go through all my EQ's and click save again just to get rid of the asterisks. 

Another weird little clue just occured. I'm starting to think there may be more than one cause of Sonar messing with plugin settings. 
 
What happened was that I had a synth part running on loop in quite a large project. I then inserted an instance of Pro-Q onto the track, as the transport was running, and activated a high pass filter at 200Hz. Inserting plugins during a looped playback sometimes causes MIDI to go out of sync in large projects for me, and it did this time. So I stopped playback with the spacebar, and immediately hit space again to restart from the start of the loop. At the exact same time I did this, the high pass filter in Pro-Q jumped down to 30Hz in front of my eyes, without me touching it. I did the same actions again with the same results. I'll try and capture it in a screencast. I tried reproducing this in a fresh project but of course it didn't happen - so there must be some combination of conditions, which aren't present in a fresh project, which causes this nonsense to happen. 
 
I remain quite sure that certain actions cause Sonar to send errant automation data to plugins, and stopping or starting the transport seems to be one of them. Someone else reported that they saw the Quadcurve settings being messed with as they clicked the cursor back and forth to different locations in the clips pane. And finally there's this which I've posted before - evidence of Waves Q10 settings being messed with when turning the ProChannel on:
 

 

OK so here's a screencast of the Pro-Q filter being moved when I stop the transport. Inserting the plugin during playback makes the MIDI go out of sync, this seems to be a crucial ingredient. Might want to right click and "view in new tab" if it's too small.