NOT SOLVED -workspaces -I like it but, tired of resizing the console

[Max Arwood]

There's quite a bit going on in this thread, and it's not clear to me what your specific issue is. Can you provide more detail, please?

Basically, workspaces overwrite your console to factory default when you load a song. It does not remember the space settings for the new console design. If I set up the console view the way I want it to be and save the song, when I reopen it my settings are lost because I used a workspace. With workspaces set to none, It loads as expected. The windows and everything else is as it is supposed to be. The console view in earlier versions was not effected by workspaces. The console settings should be added to workspaces or not refreshed by workspaces as it is on older versions.

In order to reproduce the issue, we might also need your exact monitor configuration (eg. left/primary/4K/175%, right/secondary/1080p/100%).

Monitor 1 Acer 2616w 1920x1200 (Default size 100% no stretching)

Monitor 2 TV 1920x1080  (Default size 100% no stretching)

 

My console view 

My console view with my workspace activated

Console not centered or sized .

Yes - it is not centered  size seems to be correct

All expandable sections are closed.

Yes

 

I can think of a few things you might be referring to. For example, are you manually resizing the CV so it covers both monitors, but it doesn't re-appear like that on project load?

No

 

Maybe you're maximizing the CV on your second monitor, but it comes back on the first monitor?

No

 

Perhaps you're referring to stuff inside the CV (eg. width of track and bus panes, wide/narrow strip settings) that aren't restored in the same way?

No - but, there are discussions about this.

 

Something else?

It is related to workspaces there should be a box in workspaces to save console view settings. Then these could be loaded with the other workspace objects.

(In older versions I think the console is refreshed from the saved data in the .cwp  settings not the workspace settings)

 

In order to reproduce the issue, we might also need your exact monitor configuration (eg. left/primary/4K/175%, right/secondary/1080p/100%).

Monitor 1 Acer 2616w 1920x1200 (Default size 100% no stretching)

*Monitor 2 TV 1920x1080  (Default size 100% no stretching)

*Console loaded on monitor 2

 

As Noel mentioned above, I'd also like to rule workspaces in/out. Does the problem occur when workspace is set to 'None'?

The song loads properly when workspace is set to none. It is a workspace error. The new console settings are not saved in workspaces.

Thanks for looking into this.

 

Edited January 6 by Max Arwood
*part added

[Max Arwood]

I have never used screen sets. I set up one today with the console positions I like. Now the saved (Console) workspace is correct only in this workspace. It seem like there is something going on between screensets and workspaces. Now all my screensets have no console view in them at all, except the workspace where I set up my 1st screenset.

I hope this info helps.

 

[User 905133]

7 minutes ago, Max Arwood said:

There's quite a bit going on in this thread, and it's not clear to me what your specific issue is. Can you provide more detail, please?

Basically, workspaces overwrite your console to factory default when you load a song. It does not remember the space settings for the new console design. If I set up the console view the way I want it to be and save the song, when I reopen it my settings are lost because I used a workspace . . . .  [emphasis added]

Thanks for this detail as it is useful for how I use my personal / custom Workspaces.

Previously, I have noticed a distinction between (1) the amount of horizontal space set up for the three section (tracks, buses, and hardware outputs) and (2) the location / selection of the tracks displayed within the borders of each of the defined sections.

I am assuming by space settings you mean (1).  I will double check, but I do know that under some conditions I have to adjust the borders of the three sections that the Workspace set up on a per project basis--depending on the needs of the specific project.  

I basically don't do much with per project screenset tweaks mostly because I don't have a very detailed understanding of the interplay between screensets and workspaces and it's easy for me to just just move the console section borders around on a per project basis as needed.

For my own needs, I will explore this more.

[User 905133]

4 minutes ago, Max Arwood said:

I have never used screen sets. I set up one today with the console positions I like. Now the saved (Console) workspace is correct only in this workspace. It seem like there is something going on between screensets and workspaces. Now all my screensets have no console view in them at all, except the workspace where I set up my 1st screenset.

I hope this info helps.

This came in as I was about to submit my post.  It seems like we may be thinking along the same lines! Thanks for adding this.

[sjoens]

On 1/6/2025 at 8:27 AM, Max Arwood said:

I have never used screen sets.

You use one every time you open Sonar/CbB. 

Screensets are per project - tho they are the same for each project until you change them.  Saving a project retains the current screensets in place for that project.
- Locking a screenset protects it from temporary changes made during a session so those changes won't remain after closing the project.

Workspaces are global - which means the current one will affect any project you open.  I think forgetting or not knowing this is why they cause a lot of confusion.

Edited Saturday at 05:02 AM by sjoens

[Bristol_Jonesey]

3 hours ago, sjoens said:

You use one every time you open Sonar/CbB. 

Screensets are per project - tho they are the same for each project until you change them.  Saving a project retains the current screensets in place for that project.
- Locking a screenset protects it from temporary changes made during a session so those changes won't remain after closing the project.

Workspaces are global - which means the current one will affect any project you open.  I think forgetting or not knowing this is why they cause a lot of confusion.

That's weird. The forum software has notified me that you quoted me in this post, but you haven't. 🤨

[Sock Monkey]

Im in the camp of not actually understanding screen sets so I have never tried them.

I have 2 workspaces. One screen and Two screens. 
they are both kept tidy with the Inspector, Bus pane  and browser closed. 
I then use the keyboard shortcuts to open those views if needed.
The console view I have never managed to control how it opened so I just drag the divider as I work. I guess I should save a screen set but it’s just faster to quickly move stuff around. 
The mile stone for me was memorizing the important keyboard shortcuts to open and close views. 
Im wearing out my D key as I often use only one monitor as I need the second one for looking at other stuff like lyrics. 

[User 905133]

8 hours ago, Bristol_Jonesey said:

That's weird. The forum software has notified me that you quoted me in this post, but you haven't. 🤨

I could be mistaken, but I think a few years ago you explained to me how even though I didn't "use" screensets they were in use by default.  Maybe that was someone else; my memory isn't what it used to be. I'll see if I can find that discussion. 

[Bristol_Jonesey]

5 minutes ago, User 905133 said:

I could be mistaken, but I think a few years ago you explained to me how even though I didn't "use" screensets they were in use by default.  Maybe that was someone else; my memory isn't what it used to be. I'll see if I can find that discussion. 

That's certainly something I would have said, because it's true. By default, you are always using Screenset #1

[HOOK]

At the bottom of this pic....try disabling  "Apply Workspace on Project Load".

 

[sjoens]

15 hours ago, Bristol_Jonesey said:

That's weird. The forum software has notified me that you quoted me in this post, but you haven't. 🤨

Does this help? 

I think originally I did quote you but then I edited my post.

[Bristol_Jonesey]

That could explain it 👍

[sjoens]

16 hours ago, Sock Monkey said:

The console view I have never managed to control how it opened so I just drag the divider as I work. I guess I should save a screen set but it’s just faster to quickly move stuff around. 

Nice thing about screensets is you don't have to save anything.  They remain as you last put them when saving a project.

Screenset 1 is the initial setup for every session.  However, if you save a project when another screenset is open, the project will reopen in that screenset.

I put Console View in the Multidock so it's just a D click away and then put the Multidock over everything else so it's full screen when open.  Every time I open the project it's set up the same way.  I seldom use any other screensets but they can be arranged so one  is all Track View, one is all Console View, one is Staff View, one is Multidock with all the plugins, etc.  Then you just switch views by hitting the screenset number you want to work in.

https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=WindowManagement.08.html

https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=WindowManagement.09.html

CbB still has a bug where it won't always retain Console View narrow strip widths for the Mains.

Workspaces use the current screensets and are useful for other things... I guess.  I don't really use them.

Edited yesterday at 08:34 AM by sjoens

[Max Arwood]

Is there some reason console view settings are not in workspaces? Does anyone think console should be added to workspaces? 

[sjoens]

Could be a reason but I would think everything should be there.