So it seems I can never quite get the hang of screensets:
 
I tried to create a screenset that shows the console view with my mastering plugins (assigned to number 2) but everytime I recall it only the plugins show, but not the console.  I have tried unlocking, locking and recreating the screenset but it still won't work!  What am I doing wrong?
 
I have found screensets to be very buggy and unreliable and as a result I don't use them but I thought I would try.  Do they work corectly for you and if so, how are you getting them to work?

Hi there

Not sure why that is not working for you. There are the odd thing or two that screensets don't recall correctly but most of those are older issues rather than screenset related such as the width of the Key pane.

Looks like you have checked the usual suspects. If it is unlocked it should work. I wonder if there is some sort of corruption.

Is it like this in all projects? Is the CV docked in the multidock or floating?

Try starting from a different template and see if that helps.

The answer to the question is that yes the CV size position etc is recalled correctly in screensets here, so there must be a reason it isn't for you.

I don't think you're doing anything wrong. Screensets are buggy and unreliable. For example, when I switch from screenset 1 to 2, it gets corrupted, but when I switch like 1 > 3 > 2, it succeeds. 
I got so used to not using screensets, and now I always press D to show/hide the console and Shift+X to show/hide plugin windows.

Jlien X


I don't think you're doing anything wrong. Screensets are buggy and unreliable. For example, when I switch from screenset 1 to 2, it gets corrupted, but when I switch like 1 > 3 > 2, it succeeds. 
I got so used to not using screensets, and now I always press D to show/hide the console and Shift+X to show/hide plugin windows.

That's not normal behaviour either. I can assure you that they do work, apart from the odd quirk I mentioned earlier. Corruption certainly isn't something I see here and I use them constantly. I'd suggest starting from a completely empty project and see if that helps in case the corruption is in the base template.

Hi FFB ! 

Seeing your enthousiasm regarding screensets over the years (!).. I took a look at it a few times.. 

Honestly, I don't see the point in using it... switching screensets takes way too long ! 
it makes as if it was painful for Sonar to excecute something that seems so simple as move windows around. 

For me it's more efficient to use the multidock with tabbed windows and/or opening/closing windows using shortcuts --- old-school style -- ;)

Maybe there is something I don't get, or maybe after so much time spent working one way I got efficient (or lazy) to enjoy other methods ... 

I was just curious to hear your arguments if you feel like it ! 

Sorry to hijack the thread..;( 

Cheers ! 

V

Well I'm not going to argue about it.....

What I will say though is if screensets aren't switching virtually instantly there is something wrong. Try disabling your floppy device in the device manager (even if you don't have a floppy) that is/was a known issue for slow changing screensets.

My graphics card are nothing special 5450s with 1 GB memory and before that they were even lesser spec'd. Even then screenset changing is almost but not quite instant. Now the change is barely perceptible, certainly should be very little difference between opening the multidock and switching screensets.

The thing screensets can do that the old layouts can't is recall different settings such as zoom level, snap settings (requires an ini file change), hidden tracks, widget layout etc. etc.

Here's one use for them. That's got to be far quicker than resizing the view, hiding tracks, changing zoom, widget settings, and edit filter everytime I want to change an envelope. All done with one keypress and back again (should be) instantly.

If I had to name one thing that has revolutionised the speed at which I can work it's screensets. I've seen it quoted on here by some that the old layouts were just as powerful and I somehow missed that. AFAIK layouts can't remember half of what I listed above and aren't even in the starting line up never mind the race.

YMMV of course

FastBikerBoy

Jlien X


I don't think you're doing anything wrong. Screensets are buggy and unreliable. For example, when I switch from screenset 1 to 2, it gets corrupted, but when I switch like 1 > 3 > 2, it succeeds. 
I got so used to not using screensets, and now I always press D to show/hide the console and Shift+X to show/hide plugin windows.

That's not normal behaviour either. I can assure you that they do work, apart from the odd quirk I mentioned earlier. Corruption certainly isn't something I see here and I use them constantly. I'd suggest starting from a completely empty project and see if that helps in case the corruption is in the base template.

Hi, when I created my regular project template, I was using X1, so I just tested the following on X2a:

1. Create a new project using the Normal project template.
2. Delete the existing two tracks.
3. Hide Inspector, MultiDock, Browser and the Bus pane.
4. Insert ten MIDI tracks.
5. Record the same take at once on those ten tracks (of course, I hear nothing 'cause I haven't loaded any VSTi, but it doesn't matter).
6. On the Screenset module, click all other screensets (2 -10) and remember what they look like. Switch back to Screenset 1.
7. Press Ctrl + Down Arrow key several times to zoom out the tracks vertically until only 4 tracks are visible on the screen.
8. Select "Notes" from the MIDI Filter pull-down menu on one of the tracks while pressing the Ctrl key (this will choose the Notes option on all the tracks, and Inline PRVs appear in the Clips pane).
9. On the Screenset module, click all other screensets again and make sure they look the same as before. Switch back to Screenset 1.
10. On the Screenset module, click the pull-down and select Duplicate Current Screenset To > Track View (for example).
11. Switch back to Screenset1, and then click all other screensets once again. I see one or two of them now show the four tall Inline PRVs like screensets 1 and 2.

This is probably just one example.

Well I'm not going to argue about it.....

of course not ! lol ! given the recent overall tone of the forum ... you did well to specifiy that. ;) 


Actually, this is quite convincing !! thanks for taking the time to "sell" it to me ! 


I checked about my floppy disk controller, and indeed, it was active .. I disabled it in my BIOS, and I can say it improved quite a bit .. I had some screenset changes taking about 5-6 secs, now it's no more than 2 secs. 


Still refreshes a bit slower than using multidock, but with X2, I have this odd behavior that I didn't have in X2 AFAIR... 
Every time I open a piano roll, it resets to default view (it forgets the controller lanes that I took out, Zooms, etc..)
and this is pretty annoying. I think I could get around that with screensets. 


I think I got as fast as I can with the traditionnal layout, but messing around with screensets (seeing that it's faster now), made me think about times where I'm constantly switching between windows (and losing my view settings), 

BTW the link you send in your earlier reply is not working, however, I got to your youtube channel ... I got plenty to learn there.. Thanks for that ! 

Cheers ! 

V

Well I think I will continue to skip screensets as it doesn't matter what project I use, they exhibit the same buggy behaviour.  They are a great idea that doesn't work correctly as far as I can tell.

Jlien X

FastBikerBoy

Jlien X


I don't think you're doing anything wrong. Screensets are buggy and unreliable. For example, when I switch from screenset 1 to 2, it gets corrupted, but when I switch like 1 > 3 > 2, it succeeds. 
I got so used to not using screensets, and now I always press D to show/hide the console and Shift+X to show/hide plugin windows.

That's not normal behaviour either. I can assure you that they do work, apart from the odd quirk I mentioned earlier. Corruption certainly isn't something I see here and I use them constantly. I'd suggest starting from a completely empty project and see if that helps in case the corruption is in the base template.

Hi, when I created my regular project template, I was using X1, so I just tested the following on X2a:

1. Create a new project using the Normal project template.
2. Delete the existing two tracks.
3. Hide Inspector, MultiDock, Browser and the Bus pane.
4. Insert ten MIDI tracks.
5. Record the same take at once on those ten tracks (of course, I hear nothing 'cause I haven't loaded any VSTi, but it doesn't matter).
6. On the Screenset module, click all other screensets (2 -10) and remember what they look like. Switch back to Screenset 1.
7. Press Ctrl + Down Arrow key several times to zoom out the tracks vertically until only 4 tracks are visible on the screen.
8. Select "Notes" from the MIDI Filter pull-down menu on one of the tracks while pressing the Ctrl key (this will choose the Notes option on all the tracks, and Inline PRVs appear in the Clips pane).
9. On the Screenset module, click all other screensets again and make sure they look the same as before. Switch back to Screenset 1.
10. On the Screenset module, click the pull-down and select Duplicate Current Screenset To > Track View (for example).
11. Switch back to Screenset1, and then click all other screensets once again. I see one or two of them now show the four tall Inline PRVs like screensets 1 and 2.

This is probably just one example.

I've just tried those steps in case its a specific bug recipe but don't get  any unusual behaviour. The only screenset to show the inline PRV is the one I duplicate the original one to. Not sure what's happening for you to see something different. AFAIK the default template for X2 doesn't have any tracks to start with either.