1. Click on the clip you wish to change the name of. 2. Shift+I opens the clip properties tab in Inspector (even if the inspector is closed). 3. Click on the name field in the inspector and change the name.
 
 Easy as 1,2,3. No CAL would be any simpler.

The fastest way to rename ALL of your clips is to set a key binding to "copy track names to clip names" (I used Cntrl-/).
 
Then you can select all (Cntrl+A) then your new key binding (Cntrl-/) will rename all of your clips to match their corresponding tracks. Of course this works only on selected tracks so you can change just one or as many as you choose. 
 
Tracks can easily be renamed directly in Track View or Console view.
 

Really, how hard would it be to program such a feature request: "right click" on a clip, and have an option to simply rename the clip ? It's the most intuitive way that any new Sonar users would be looking for  . . . doesn't most software have a right click and select options function, it should be fairly straightforward to implement, why so much resistance here in this thread ?
 
It seems there are many ways demonstrated here to rename clips, surely Cakewalk would recognize "right click" on a clip as being the most intuitive way to do this . . . much as they re-programmed the "Add Track" feature to be more intuitive for new users to add new tracks to their projects ?

noynekker
Really, how hard would it be to program such a feature request: "right click" on a clip, and have an option to simply rename the clip ? It's the most intuitive way that any new Sonar users would be looking for  . . . doesn't most software have a right click and select options function, it should be fairly straightforward to implement, why so much resistance here in this thread ?
 
It seems there are many ways demonstrated here to rename clips, surely Cakewalk would recognize "right click" on a clip as being the most intuitive way to do this . . . much as they re-programmed the "Add Track" feature to be more intuitive for new users to add new tracks to their projects ?

That's part of the problem, really. Context menus (right-click) are a standard paradigm and X1 tried to move away from them to context menu bars. That's fine, but elsewhere in Sonar we have context menus all over the place. So, if consistency leads to intuitiveness and shortens the learning curve, then Sonar is doing it wrong.
 
Please note, this is not a complaint, just an observation as to why some users would be confused on how to do things and maybe why folks like Tripecac are so squeaky.
 
Regards,
Dan

But what functions should be on a right click menu...too many and the menu is unusable, too few and some people won't be happy.  Presumably, the most commonly (or expected!) commands would be so available, and rename clip probably isn't up there...

With full knowledge that we're discussing a specific case here, it seems to me that the most reasonable approach is to have fully customizable menus and toolbars; to the point of being able to create complete toolbars that can be instantiated via hotkeys and/or context.
 
I'm pretty sure there is already an FR or two for this.

KPerry
But what functions should be on a right click menu...too many and the menu is unusable, too few and some people won't be happy.  Presumably, the most commonly (or expected!) commands would be so available, and rename clip probably isn't up there...

If you can do something with something (a clip in this case), it should be available as a context menu item. Yes, that means we would all have different menus, but I don't see the big deal with that.
 
Regards,
Dan
 
 

One of the most aggravating things about X1 ---> is that touch implementation does not (yet) include a right-click equivalent. A conspiracy theorist would suggest that cake eliminated the right click context menu to accommodate touch - then left touch implementation partly finished when touch didn't turn out to be the big market feature they hoped it would be.
But I would support (and have in the FR forum) a feature request to bring back context sensitive menus (hopefully touch capable).
As has been pointed out several times to the OP, if he were to promote feature requests (instead of beating horses like the clip renaming comparison between 8.5 and SPlat into the ground), he would get a lot more support and actually have a shot at effecting some change.

Even if it were possible, in what universe is selecting a clip, running a cal scrip, typing in a new clip name then applying the cal any kind of improvement over changing the selected clip (or clips) name in the inspector clip properties box?

 
CAL can potentially save a couple clicks and keypresses, since you can bind hotkeys to CAL scripts.  So, *if* CAL could rename clips, the steps to rename a clip would be this:
 
1) select the clip (1 click)
2) hit F2 (or another key) to open the Rename Clip CAL script (1 keypress)
3) type the new name for the clip (N keypresses)
4) hit ENTER (1 keypress)
 
That's 1 click + N+2 keypresses, which is better than using the inspector.
 
The reason these extra clicks and keypresses matter to me is I am doing most of my editing in real time (during playback).
 

Context menus (right-click) are a standard paradigm and X1 tried to move away from them to context menu bars. That's fine, but elsewhere in Sonar we have context menus all over the place. So, if consistency leads to intuitiveness and shortens the learning curve, then Sonar is doing it wrong.

 
I think there is another factor at work: unlike some people on this forum, I am a software developer, and am using Windows *all day*.  Windows applications have standard UI behaviours, such as right click opening properties, F5 saving, F2 renaming, etc.  When a program deviates from this, I remap the keypresses to the "correct" (standard) Windows behaviour, so that I can work most efficiently.  If a program has a unintuitive UI *and* an inability to be customised, then I tend not to use it.  Sonar 8.5.3 was more consistent with the Windows UI "out of the box" *and* it was easier to customise.  X1 seemed to deliberately separate itself from the Windows UI paradigm.  That might be fine for "casual" Windows users, but not for me!
 
This makes me wonder: will Cakewalk modify the UI further to be more in line with the Mac UI?  Things could get even worse for us... or, if Cakewalk relents and adds back customisability, things will get much better.
 

it seems to me that the most reasonable approach is to have fully customizable menus and toolbars; to the point of being able to create complete toolbars that can be instantiated via hotkeys and/or context.

 
Yeah.  This is what I've been whining/squeaking/spamming about since X1: bring back the UI customisability that we had in 8.5.3.
 

As has been pointed out several times to the OP, if he were to promote feature requests (instead of beating horses like the clip renaming comparison between 8.5 and SPlat into the ground), he would get a lot more support and actually have a shot at effecting some change.

 
There is a fine line between promotion and spamming.  And I'm not into marketing.  Or even socialising!  If my sloppy, annoying, repetitive whining inspires other, more tactful and eloquent people to present the same general idea to Cakewalk and the community in a "pleasing" manner, and through that enough support is drummed up to inspire Cakewalk to make a change... then great!

KPerry
But what functions should be on a right click menu...too many and the menu is unusable, too few and some people won't be happy.  Presumably, the most commonly (or expected!) commands would be so available, and rename clip probably isn't up there...

yeah, but if the "customise right-click menu" still existed, it's a win-win ;-)