In addition to screensets 1, 2 and 3 I had set up before (they're all locked), I created a new layout and saved it to screenset 4.
Since I realized I never use 2 and 3, I decided to copy 4 to 2 or 3.
So I did that, even to both 2 AND 3, and locked them. But the old screensets 2 & 3 that I thought are now forever gone keep coming back like a zombie.
Saving the project didn't help.

I think I hate screensets more than anything else in Sonar. 

(Note that I'm usinig the Essential version)

When you say coming back do you mean in the same project or when you create a new one?

Screensets are saved per project so to change all future projects screensets you need to save the template. Changing a screenset only affects that one project not all others.

Some have already said they'd like to see some sort of global set up. I can live with that but I personally like the per project set up as I have different ones for different needs. I hope they don't remove that.

Personally I'd like to see a whole screenset management/library system to make saving and loading much easier.

Hi, it's the same project. It's quite a heavy project so I hope I won't have to migrate all the data to a new project. I haven't checked if this behavior is common to other projects, but just wondered if this is a known issue.

FastBikerBoy


Some have already said they'd like to see some sort of global set up. I can live with that but I personally like the per project set up as I have different ones for different needs. I hope they don't remove that. 

Maybe 5 global screensets and 5 per-project screensets would be good for all users?  

Karl, I had you run a similar test before, but that one involved a bit of recording and displaying the Inline PRV, which were unnecessary. So I run the following test this time.


1. Create a new project using the Blank Project template. If the Bus pane is visible, press Shift+B and hide it (Strangely, when I tested this the first time, I think the Bus pane was not visible...)

2. Insert 10 MIDI tracks.

3. Lock the current screenset (=Screenset1).

4. Duplicate Screenset1 to Screenset2, and before doing anything, check the Screenset pull-down list and make sure Screenset1&2 show exactly the same name, and they are both locked.

5. Click the [1] and [2] buttons on the module alternately and check if the two screensets appear exactly the same. (In my case, Screenset2 looks different at this point. The Bus pane is displayed in Screenset2).

6. Check the Screenset pull-down list again. (In my case, Screenset2, which was locked, is now unlocked. So I manually lock it.)

7. Go back to Screenset1 and minimize the height of all the tracks, then duplicate the current screenset to Screenset3. 

8. Make sure Screenset 1-3 are all locked. And check if the three screensets appear exactly the same. (In my case Screenset3 shows Browser on the left, although I never opened it, and Screenset3 is unlocked. So I manually lock it. And the track height is back to normal...)

9. Unlock Screenset2 and copy Screenset3 to Screenset2.

10. Click the [1]-[3] buttons on the module and check if the three screensets appear exactly the same. (Now, in my case, the Track Control drop-down in the three screensets show different options. One of them shows "Custom," while the other two show "All")

(I run this test 4 times, and each time the result is slightly different.)


Complete disaster. I think I'll contact Cakewalk.

As much as I admit to hate defeat I think calling Tech support is a good idea. It might even be an issue with Essentials. One other thing that might be worth trying is a completely fresh template.

Navigate to you template folder (Path in preferences---->File--->Folder locations) and rename "Normal" as "Normal Bak" or delete it if you aren't going to need it
Open Sonar and close any open projects.
Press Ctrl+N - that will open a bare bones project that you can now customise and "save as" your normal template.

Try from that template and see what happens. If your "Normal" template is corrupt you will get problems no matter how many times you try it.

HTH

So I deleted the "Normal" template (I can always recover it from the original file location), restarted Sonar, opened the bare bones project as instructed, and without changing anything, I save it as a template.
Then I created a new project using that new template, and ran the above test again....only to see the same result. 


I think this is a bug in Essential. I'll contact tech support. Thanks anyway.