Hi Billy,

Same here. Only 2 screensets for my needs, a very clean track view and a console view.

If I am understanding the problem correctly, the screensets are not saving properly? In any case, here is something I have found out the hard way with templates and screensets.

If you "locK" the screensets and then try to change them outside of a saved normal.cwt, it will always revert back to the locked state in the normal.cwt file (even if you unlock and relock). So the steps that work are as followed.

1)Load Normal.cwt
2) first thing is to unlock all screensets
3) make screenset changes
4) Relock the screensets
5) Save new Normal.cwt

This works like a charm and hope it helps.

djjhart@aol.com


Here's something else to consider , You have a template set up as your 3 screen sets , Your working on song you click SS #3 which is your enlarged PRV , your recording midi, Hey guess what You want to record a Z3ta pattern you insert, hey you wanna use True pianos , You insert, Guess what's happening your great SS#3 is all messed up, I wanna get back to just SS#3 , Guess what you cant , you need to reload another project. Now if I was able just to press SS#3 again and it  came up as I had it when I imported it .. Great but it dosen't Your SS#3  has been changed caus you added some Vst's ect.. Where's the usefulness There?  My point is your Project will change as you Compose/arrange. And so will your SS. without a preset your SS will change .

Well you changed by adding to it. Especially another VST soft synth. You need to save the change as another screen set at that point. 

"...You need to save the change as another screen set at that point..."

"...Too bad Screensets don't remember 'muted tracks/solo'd tracks' etc..."

This is so curious, and I'm still so perplexed at what the expectations for Screensets are. 

Screensets are just configurations of the basic Views in Sonar X1.  One View may be minimized or maximized, and things like the Browser may be in view or out of view.  Screensets are just the way components are laid out, as per the way you want to work on a project.

There are two flavors of Screensets:

1)  Basic layouts that work for you, like focus on the Track View, or focus on the Piano Roll View, or Console View, with other components either semi-in view, or totally off screen.  These are the basic starting points for projects, and can be saved a collection in a Template.

2)  The dynamic, changing Screensets which occur as you work on a project.  You've worked on a track in the TV, but want to simultaneously jump easily into the PRV to do more editing, so you've decided during the course of the project, to narrow down the TV and bring the PRV up farther.  It doesn't matter if you have a saved Screenset like this - it's what you decided on at the spur of the moment, and now if you jump to a totally different view, like the Console View, this newly improvised TV screen will still be exactly as you left it when you made the decision to move some things.  There's no reason to save the particular proportions of what you have on the screen, because it may be a fairly unique situation, like with half PRV and half Tempo View.  It doesn't matter--the point is that this on-the-fly Screenset will have been created for you without you putting out any effort.

Thinking that you're supposed to save a Screenset for every synth you might use, or every particular scenario where some tracks are muted and others aren't, only leads to an enormous waste of your time.  That's not how Screensets were designed to be used, and just a bit more time with the program will show you that attempting to collect all these slightly different sets is the way to madness.  All those kind of changes are meant to be done at the spur of the moment, and not saved.

Considering how much confusion there is about Screensets does show that they haven't been sufficiently explained in the manual or Help file.  The very concept seems to be misleading a lot of people.

Randy B.