On the first page I said that Lenses load much slower than screensets for me. Is anyone else experiencing this? I shutdown/restart daily, so I don't think it's cache related.

jshep0102
On the first page I said that Lenses load much slower than screensets for me. Is anyone else experiencing this? I shutdown/restart daily, so I don't think it's cache related.

Same here.

I'm definitely in the minority here, but I like my UI to stay the way I have it set up, I'm used to where everything is, and know where to find everything.
When I press a preset Lens, it's like taking a finished jig-saw puzzle and scrambling all the pieces. Especially working on a dual monitor setup, it reverts everything to a single screen, with all the previous full screen sections condensed into little tiny sections.   I tried it once and instantly went back to my default screen setup.

I'm sure people will find lenses useful.  Photoshop has a similar feature to setup your screen for different purposes. But in Photoshop there aren't as many components and windows to deal with, so the changes aren't so jarring.

John
 
So this is incorrect;
 
Using Lenses
To select a Lens
Do one of the following:
Click the Lenses drop-down list in the application bar across the top, then select the desired Lens.

Press the Lens’ assigned keyboard shortcut (if previously assigned in Edit > Preferences > Customization – Keyboard Shortcuts).

Hi John,
 
Yes, the keyboard shortcuts have not been implemented yet. Thanks for pointing out the error in the help. The online documentation has been updated.
 

@Leee - I agree. Maybe it's just that I'm not so ADD.  I have no issue with ALL of the windows and menu items nad such being available to me when I'm doing any particular thing.  I want everything at my disposal during all phases of a project.  I am every bit as likely to need the Piano Roll View during mixing as I am during tracking.  While I may not currently be using the Matrix View for anything, I'd like to learn to incorporate it into my workflow.  The #1 way I can figure on NOT doing that is to create a Lens that takes it out of my options.  I'm likely to never think of that view again.
 
Sure, I might not "see something shiny" or be attracted to a passing squirrel, but I am at least likely to recall that the feature exists at all, where if I were to remove it from my selections entirely, it might as well not exist as a feature.

Like so many features in so many DAWs, Lenses are optional. Any benefit is 100% dependent on how people use the program.

I think I need see a CakeTV video on them. I don't quite understand what differentiates them from Screensets.
 
Truth be told, miss the way it was done in the WAYYYYYY old SAW+. Shift+Fn saved a view, Fn brought it back.

I can see how some may find them useful - particularly those that are using laptops with limited screen real estate.
 
Then again, maybe some months down the road I may wonder how I ever did anything without them.
 
They load almost instantly here on ~small projects.

Lenses are a brand new UI paradigm from Cakewalk that is designed to greatly improve workflow and focus. It is vastly different from screensets which just store view info (screensets are actually a small subset of Lenses). A brief description of the feature:
 
SONAR has evolved into a complex application with hundreds of features. This can cause an information overload for both new as well as experienced users. Exposing every available feature makes SONAR complicated and difficult to use. Additionally an application should not force you to see features you don’t use, some workflows require access to many features, while other workflows benefit from a simpler and more focused UI. Using Lenses the SONAR user interface now allows for easy one click switching to different user workflows by adapting the UI to show or suggest elements that are relevant to that workflow.
 
Most users beginner or advanced, typically use only a small subset of features depending on their workflow or experience level. Lenses solve this problem by hiding features that are not needed for a particular user or task. Feature hiding extends across all aspects of the program.
 
The following elements can be stored and customized as part of a lens:
 

• menu items
• keyboard accelerators
• control bar modules
• controls in tracks and buses
• features
• commands
• views 
• view positioning

 

I think they are a very cool idea. i do wonder how well they support dual monitors? I do think they add a great advantage to laptops. One thing is for sure is, it gives us the user, options. I can't see that as anything but good.