pbognar


@twigman - every one has their own way of working.  But some would say that typically, speedy power users use keyboard short cuts more that mouse clicks.

An example would be <ctl> A to select all, <ctl> X or <ctl> C to cut or copy, and <ctl> V to paste - way faster than using the mouse to got to the Edit menu to select these functions.  And once you've mastered these, you gain incredible speed and efficiency through the repetitive motion.

Twigman


IMO keystrokes are so pre-Windows - Windows was invented for mouse it's a GUI rather than being reliant on keystrokes like DOS Apps were.

UnderTow

Brandon Ryan [Cakewalk
]

I hit C, make the change, and hit C agian to get it out of the way.

I agree that this is quick enough and makes the CB concept in itself a good improvement top Sonar.

FWIW: The module concept of the CB needs to be taken to the next level IMO.

Just to make sure it doesn't get missed, let me repeat my previous suggestion:

It would be great if the Control Bar had three modes. The Current mode as it exists in X1a, a Compact mode and a Button Mode.
The Compact Mode is similar to the current mode but everything is smaller and tighter. The Button Mode is just one (SMALL!) button height high with all the relevant and necessary buttons and maybe the most relevant text modules like Loop Points (side by side to save height) and of course the usual ability to select which modules are shown. And, as I have already suggested elsewhere, the ability to undock any module.

If this kind of approach is implemented I think it is really important that the buttons in the Button Mode are small for two reasons: It makes the overall height small and it allows more items horizontally. (Assuming the buttons are as large as they are tall of course). The least important of the three modes I suggest would be the compact mode. The combination of the Button Mode and the currently existing mode with quick showing/hiding through the C shortcut should cover most workflows.

I do think the current mode with it's largish size should be kept not least to add the functionality I proposed in my long suggestions list. I'll repost them here to keep them together with the above Control Bar suggestions:

Control Bar:
============
- All Control Bar Modules should be detachable.
- Modules don't need Module names. (Waste of Space).
- Enable/Disable menu should reflect order of modules in the Control Bar.

- Snap To Grid Module has room for a Snap_To/Snap_By toggle button. (Long clicking on the enable/disable button is too slow).
- When you have musical time selected, the other selector (Samples/Seconds/Frames) should show the actual value equivalent automatically calculated based on tempo. So if the tempo is 120 BPM and you have the Snap_To_Grid set to a 1/4 Note and you left the second selector on Seconds, it will show: 0.500 Secs. Wouldn't that be nifty? :-)

- Loop Module: The Format of each value should be easily selectable by right clicking. (When working to film, you might want to loop based on specific SMTP times rather than musical times for instance).
- Loop Module should show Loop Length underneath the start and end times. (There should be room once you remove the word "Loop").

- Selection Module should be called Selection Module in Enable/Disable Menu (Not Select).
- Selection Module should show Selection length. Format (Musical/Absolute/Samples/etc) should be easily changeable by clicking or right clicking.

- Event Inspector should also display info on Audio Clips. (Start Time, Length etc) Now as it is, it is wasting space when you select an Audio Clip. It should also have buttons to toggle the Lock state of clips, Toggle Groove-Clip-Looping, V-Vocal Enable, Mute/Unmute... Make use of all that space! (It would have some redundancy with the info in the Inspector but that doesn't mean it is not useful, Especially if one has the Inspector closed).

- Event Inspector should have a little icon that opens the clip Colour changer. (Yes it has to be that easily accessible).The ability to quickly change a MIDI/Audio CLip's colour makes for more organised and easier arrangement.

Well I could go on and on with ideas and suggestions but I risk being told that it is easier to come up with ideas than implementing them.

UnderTow

UnderTow


but stop characterising shortcuts as old fashioned. They are not.

pbognar




I like the new UI, but if it could be size scaled to the display you are working with, that would be great.  I want to be able to work on an industry standard laptop AND a kick ass wide screen monitor.

As far as icons, perhaps the option to create a custom, personalized floating icon set would satisfy some - similar to the effort going on in another thread.

GAMBLE

I couldn't disagree more. 8.5 was massively cluttered with buttons and widgets everywhere. 

 




I can not for the life of me figure out why you would say something like that knowing it was customizable. 

Is that the point you guys are at now?  Really?  Is this what is has come down to?

himalaya

pbognar




I like the new UI, but if it could be size scaled to the display you are working with, that would be great.  I want to be able to work on an industry standard laptop AND a kick ass wide screen monitor.

Agree and it's what some here have been saying (in relation to scalability).

As far as icons, perhaps the option to create a custom, personalized floating icon set would satisfy some - similar to the effort going on in another thread.

I think Samplitude deals with the issue of too many/not anough icons/buttons with the most elegant and easy to use method: there are several memory locations, each able to hold a different toolset. Click  'Editing' and the toolbar gets filled in with buttons primed for editing. Click 'User', you get what you have chosen as your default User defined set. Click 'Mastering'....you get the picture, etc, etc. And this makes sense, as each task, recording, editing, mastering, etc. may need a different toolset. An easy, fast and elegant solution.

Brandon Ryan [Cakewalk
]

You shouldn't need to think, "ok now I'm going to edit" and then have the interface change it's buttons and tools for that process only to revert back when it's time to record.

Twigman

Brandon Ryan [Cakewalk
]

You shouldn't need to think, "ok now I'm going to edit" and then have the interface change it's buttons and tools for that process only to revert back when it's time to record.

I agree which makes X1 all the more puzzling to me.
In previous versions of Sonar all those tools were available right there - the right click contextual menus gave choices right where the cursor is - the icons were all available in the toolbar....

In X1 you have to tell it Now I'm going to edit this envelope in the Edit Filter - before you could just grab an envelope node....
To me X1 feels far more 'Now let's tell Sonar what we want to do next' rather than just doing it.
Which makes your post surprising as X1 feels like a step towards the method and processes you are criticising!

John

that involves using the keyboard........:rolleyes:

I think you again misunderstand. Using the keyboard is only one way. The middle mouse button will engage the HUD which allows you to click on the tool you want. You need to read the manual.

You shouldn't need to think, "ok now I'm going to edit"

UnderTow

John


How many DAWs have an editable buss track? That was first incorporated in Sonar.

An editable bus track? What do you mean?

Please don't mention ones that came out after Sonar. They took the idea from it.

I am pretty sure there are developers out there that are hardly aware of Sonar and have probably never opened it. (Especially in Europe).

UnderTow

Twigman

Brandon Ryan [Cakewalk
]

a quick shift-click

that involves using the keyboard........:rolleyes: