PLEASE, is there any way to have global screensets?

The moment I realized how the screensets are designed and implemented in X1 (not global and cannot be reused in other projects unless you import from an open project, and cannot be used with custom global key-binding for all projects), my enthusiasm for X1 fell thorough the floor and into the abyss. I cannot fathom how a development team could make that kind of mistake. Did NO ONE during the entire development cycle of X1 noticed this as a glaring problem, and no beta users noticed this either? How is this even possible?

In past versions of Sonar, I have custom layouts that I switch between on the fly that are absolutely crucial to my work (using dual displays). I jump around between them with the custom key-bindings of SHIFT+A (track + synth rack view), SHIFT+D (track + console view), SHIFT+S (track + pianoroll view), SHIFT+E (full console view), SHIFT+W (full pianoroll view). I absolutely must have this in order to work smoothly like I'm used to. The fact X1 has taken away that ability is absolutely mind-boggling. I don't mind that Cakewalk likes the idea of unique screensets for each project, but AT LEAST allow us to KEEP the global layouts if we so choose, or allow us to toggle between using project-based screensets of global screensets.

And just how is the project-based screensets better? Most people using Sonar are NOT doing a huge variety of different types of productions. People are either musicians doing tracking, mixing, mastering, or composers working with video, or FX guys doing sound design, and so on. Very, very few people do all of them, and even if they do, 10 global screensets are more than enough to cover just about anyone's needs, ESPECIALLY when many things can be tabbed. So, why then, would anyone need to have 10 unique screensets PER PROJECT, as if they are constantly doing radically different tasks every time they use Sonar? Who does Cakewalk think their target audience is? And to think we lost our global layouts views switchable with custom key-binding over this. Garrrhhh... Like I said, why not have the cake and eat it too--why does it have to be either, or? Why not give us the option to choose what we want? For an upgrade that makes a huge fuss about customizability and ergonomics, this is an embarrassment. ( I know I sound agitated, and I apologize, but this really got to me.)

Please Cakewalk. I beg you. Fix this.

That's a pretty simple workaround, but seeing how I have a bunch of work-in-progress projects that I want to continue in X1, I'd then have to copy those screensets from the template for all of them. I don't mind having to do that, but I still want to see this fixed, as it's one of the worst flubs I've ever witnessed any software development.

I haven't done anything with screensets yet.

Would it be possible to save a normal template with a set of 10 screensets that you would use as a global arrangement and if necessary just edit any that needed changing for that particular project?
Would that get around the problem you see?

Not only could I save and import my screen "Layouts" in Sonar & Cakewalk Pro Audio (since PA 5, I know) but I even had my favorite Layout assigned to a Key Binding and I even had a quick CAL program that would set up the file for live use including the "Layout" and save it.

I HIGHLY doubt that Cubase, Nuendo & Logic put in such a great feature without the ability to save/import their "screensets".

I'm sure it will be fixed in the X1b and I appreciate what Cakewalk is doing with the GUI... I do wish they would have baked it a little longer and bypassed all the negativity though.

i like screensets, but only working in new projects that i have just begun in X1 after the screensets have been saved doesn't account for all the projects i am currently working on.  that's gotta get fixed, easily

"I absolutely must have this in order to work smoothly like I'm used to..."

I get your frustration but X1 is definitely NOT about working like YOU used to.

For better or worse it's been totally re-thought and re-designed and that's going to alienate a bunch of customers but not all. And believe it or not there are many users who really like the changes and haven't found the lack of global Screen Sets to be that big a deal.

Like FBB suggests they did include a way to integrate the new Screen Sets into old projects. Could be more elegant I think but it's there.

I'd only suggest to dive in and really use the program and see if it really is as awful as missing global screen sets at first appears.

Cool, I didn't realize that... Thanks!

yorolpal


Screensets should, at the very very very least, have a "global" option.  Go ahead and call those "layouts" again... who cares...just bring them back.  For those of you who do find screensets useful, rock on.  But to many of us they seem about as useful as tits on a boar hog.

I think they do serve some purpose, indeed.  Just not in every situation or in trouble situations like I mentioned about Safe mode.
 
Seems to me there is some consensus that having BOTH options would be the best solution.
 
 

Right, it should be an option.  For someone like me who always uses (for all practical purposes) the same general settings and views for ALL of my projects a global option is the only way to go.  I'm such a dullard... I can't imagine having multiple screensets that are proprietary to each individual project...as long as my mix settings are saved with the session, I'm good to go:-)

Yorolpal, you can still have all your screensets the same for all projects. Get a project set up how you want it with all the screensets sorted out and then save it as a template.

All the screensets are recalled when you start a new project from that template.

For existing projects see my post #10 above. Not ideal I agree but it only takes a couple of seconds per project and only needs to be done once.

FastBikerBoy


Yorolpal, you can still have all your screensets the same for all projects. Get a project set up how you want it with all the screensets sorted out and then save it as a template.

All the screensets are recalled when you start a new project from that template.

For existing projects see my post #10 above. Not ideal I agree but it only takes a couple of seconds per project and only needs to be done once.

Right FBB.  I've already done that as regards my "Normal" template.  But I'm currently working on my latest CD project (over 20 songs I hope to cull down to about 12) which were done in 8.5.3 and they, of course will not have the screensets, unless I import them.  Which I might.  All my future X1 projects (if I decide to stay with X1) will have my three pitiful little screen sets.

yorolpal




...I'm currently working on my latest CD project (over 20 songs I hope to cull down to about 12) which were done in 8.5.3 and they, of course will not have the screensets, unless I import them.  Which I might...

Yorolpal, have you experimented with drag-n-dropping your 8.5 projects into X1 from the browser?  Maybe that'll get what you need.

Randy B.

There definitely should be an option to save and load Screensets to separate "Screenset" files

+10000000000000. If they ever get that they'll be almost perfect (once the known bugs are fixed)

There definitely should be an option to save and load Screensets to separate "Screenset" files +10000000000000. If they ever get that they'll be almost perfect (once the known bugs are fixed)

This is one feature I would greatly appreciate. I wanted this as soon I got X1. But FFB knows this already. LOL

So now it's well over a year later, and still nothing's been done about global screenset option? Instead, Cakewalk spends its time developing audio effects, rather than work on workflow key issues that are far more vital to the user experience? Why the hell would we want more and more audio effects when there are plenty of options on the market already, of cheap yet high quality effects suite that we can easily afford? We can buy third-party effects but we can't buy a better workflow--unless we abandon the software altogether.

If that's not a company with its head stuck in its own ass, then I don't know what is. How effing hard could it possible be to implement a global screenset option? Looks like Cakewalk is just being stubborn, thinking they know better than the users what the users themselves want. If they indeed do have such clairvoyant ability like that of Steve Jobs/Apple, then Cakewalk wouldn't be what it is now. 

The most useful features I have continually begged for for since years ago are still nowhere to be found--ones that I feel do have the clairvoyant quality of Jobs/Apple, where even though the user base might not have thought of it, will become extremely popular once implemented (for example, the Photoshop-like "grabber tool" that allows complete freedom in navigating the workspace, with 360 degrees of movement, in any situation where we currently are forced to use the damn scroll bars to move around).

The best software development teams understand that flexibility and customizability is key to a good product, especially when it comes to any kind of complex software where the workflow will make or break the experience. 

I swear, if I ran Cakewalk as its head of development, I'd completely change the way Cakewalk is run.