FastBikerBoy


As I've already said the different snap is not the best example when used on it's own as it is in the video but when combined with other changes such as zoom levels, hidden tracks, etc it really does enhance workflow for me at least. I'll hopefully show what I mean in future videos.

The other stuff makes perfect sense to me and that is exactly what I would expect from Screensets. I'm looking forward to seeing your future videos.

I don't agree with the global idea, even though I thought it would be a good idea at first. I think the ability to save and load them individually to a library would be a much better method.

To be entriely clear, I don't think Global Screensets should replace the per Project  Screensets! They should be an addition to the current system. It might be less confusing to call them Global Screenset Presets.

The reason I don't think going 'global' is a good idea is because of the way they remember everything. Imagine hiding 3 or 4 tracks in one project and then opening another project several days/weeks later and wondering where some of the tracks have gone. There'd be uproar about bugs when in reality it would be the global screenset that had done it.

Not if things are properly implemented. For instance in Cubase the Global Presets only store Window layouts and don't store any project specific windows (like say a plugin). This means that the scenario you describe above would never happen.

Also, the keyboard shortcuts should always refer to the Per Project Screensets. Not the Global Presets. (These Global Screensets could be copied in a separate dialogue accessible from the Screensets Module in the Control Bar).

The other nifty thing about the way it is implemented in Cubase is that there is an option to copy all Global Presets to any new project your create. (And a few more things like that). Cakewalk should really have a look how Steinberg did this Preset system.

I think once the bugs are ironed out, and there are a few that I won't be hiding but pointing out in the videos, they will really come into their own. But they do need some OTB thinking. Plain layouts they are most definitely not, they are far more than that.

And a bit of copying of excellent ideas. No need to reinvent the wheel...

Regarding the num pad key bindings. Yes that's certainly one way of working but it doesn't work for me simply because my number keypad is combined with my touchpad so I have to switch modes, which is a PITA.

Good point. You could assign CTRL-NUM (the regular ones, not the keypad) to this. After all, you  wouldn't need to duplicate Screensets half as often if you had direct access to the Snap-To Settings directly. (And of course you could assign them to anything else. The point is that Snap-To Settings really doesn't belong in Screensets IMO).

UnderTow

Following on from the earlier video, here's a couple of neat tricks that can be combined into screensets to get several changes with one key press.

This one shows how to change zoom levels & snap-to settings at the same time. Also shows how hiding tracks can be useful.

The power of screensets comes when you start to combine several of these together. With a little prior planning it can really speed up a work flow.

This video also exposes an annoying display bug which CW are aware of and will hopefully be fixed. It is intermittent for me and has never happened in a drum track for me before. Of course sod's law states that it will happen in this video.

Again this video is more about giving a few ideas of the possibilities rather than "This is the best way to work"

As always screensets are far better if saved in a template so there is a one time only set up.

Anyway here's the link and I'll update the thread title and include this link in the first post so they are all available from one place.

I hope someone finds it useful...........

Great job FBB. REALLY appreciate the effort.

Thanks; appreciate the work - every little bit helps

Hi. Thanks for all the encouragement...........

@Grem......... yes I do get the quirky PRV behaviour but I've always had this in Sonar so it's not new to X1. I can't seem to pin it down either but I have put in a bug report (or was it a feature request??) that the PRV should remember it's internal layout.

I find the drum pane the worst offender especially the note/name pane which always shrinks down  to a thin strip down the left hand side.

I really like the way screens remember the hidden tracks etc. and hopefully the examples I'm putting up can give people some ideas as to what is possible when combining tricks & techniques. They are there to hopefully get the ideas going rather than as a "this is the best way statement".

Thanks again.