Thanks for taking the time to do this, add James Collins.

Add me to the List..

I have always wanted the ability to create one short midi clip and then freeze or export it without creating a bunch of new tracks.

mrfitz

bitflipper

Ability to 'Rename' a project and its containing folder simultaneously

+1. And update the recent-files list in the registry.

Why in the world hasn't this been done yet? PLEASE! As my projects evolve I almost always want to rename.

Add me to the list. Although I would think the bakers have the roadmap to 9.0 pretty well set, which will take us to Oct 2010. So with their development cycle I wouldn't anticipate seeing any of this stuff until 2011 (unless it's already in the plan for 9.0). That's a pretty big ship to be turning mid-stream.

Mike Fitzgerald

+1 here too  RENAME RENAME RENAME

hugojacquet >> - Track inspector giving more info (especially on midi tracks). The empty space could easily contain more elements that are now in the track header only. Make at least in and outputs selectable in the track inspector!!

+1 

Good initiative. Well done fellas.
 
I'd like all aspects of 'management' (items 2, 4 and 5 on your list) to be controlable from a work-surface rather than mouse/screen/keybd. This should just require a significant extenion of ACT.
 
Regards & thanks,
 
SJ

timidi


My suggestion would be to have floating windows that are alt/tab abled

For the record for those that might not know this, you can switch between windows within an application by using CTRL-TAB. (ALT-TAB switches between applications). This applies to most if not all Windows applications. Not just Sonar.

where you could select say tracks 1-20 as a view and then have 21- 35 as a view etc.

I believe having nested folders would already aid project navigation and organisation significantly. Maybe not enough for your needs... I don't know.

like you're looking at track 70 and you hit f to bring the whole project into focus (whatever will fit) it defaults to the top track?? huh? I was looking at 70.

I think this is a significant point. I would like the devs at Cakewalk to consider this type of case when adding/enhancing features. Not just think "Hitting the key should bring the whole project into view. Now it does. Mission accomplished" but rather think something like "OK, what was the user likely to have been doing? What do they want to achieve? How will they be using this feature? What will they have been focusing on and what are they likely to want to be focusing on after the command is applied? Is this really the most complete and efficient implementation of the Zoom Out command?" and when in doubt, make different behaviours user configurable.

The same goes for modal windows. The example often cited is the Snap to Grid window. For me an ideal workflow would be something like: You press a keyboard shortcut, the window opens. The Snap To Grid value is already selected. I can either directly type in the time division I want or press the up down arrows on my keyboard to use any of the standard values, hitting TAB once would bring me to the "Move To" / "Move By" selector. Then press the same keyboard shortcut to close the window. Then I can return to doing whatever I was doing before. This would save a lot of time over the course of an entire project.

It is all about how people are most likely to use a feature and how to make it as efficient and quick as possible. Just implementing a feature is only half the job IMO. Going the extra 10% makes the feature 2 to 4 times more efficient and powerful.

For obvious reasons, we could not go into such detail for every feature we included in the list. It would make the list at least a dozen pages long. (Often it takes many more words to explain something that becomes perfectly evident once implemented).I (and I believe we) would like to urge Cakewalk to think of speed, efficiency and flexibility when considering any and all of the features we presented and of course for all and any features they come up with themselves. The name of the game is workflow.

UnderTow

UnderTow

... I would like the devs at Cakewalk to consider this type of case when adding/enhancing features ... think something like "OK, what was the user likely to have been doing? What do they want to achieve? How will they be using this feature? What will they have been focusing on and what are they likely to want to be focusing on after the command is applied? Is this really the most complete and efficient implementation of the ... command?" and when in doubt, make different behaviours user configurable....

... It is all about how people are most likely to use a feature and how to make it as efficient and quick as possible. Just implementing a feature is only half the job IMO. Going the extra 10% makes the feature 2 to 4 times more efficient and powerful.

... The name of the game is workflow.

Well said, sir!

UnderTow >> The same goes for modal windows. The example often cited is the Snap to Grid window. For me an ideal workflow would be something like: You press a keyboard shortcut, the window opens. The Snap To Grid value is already selected. I can either directly type in the time division I want or press the up down arrows on my keyboard to use any of the standard values, hitting TAB once would bring me to the "Move To" / "Move By" selector. Then press the same keyboard shortcut to close the window. Then I can return to doing whatever I was doing before. This would save a lot of time over the course of an entire project.

And to have the current Snap-To attributes visible ALL the time somewhere, both for Clips and PRV ... not the whole window, but just the main attributes set, like Absolute or Musical Time, Values, Move By or Move To, Strength and Snap-to-Zero setting, would be very helpful.

Can't believe I missed this thread.

Excellent idea, add me as well please.


Colin Jones (THE CJ!), or just Bristol_Jonesey.

Bristol_Jonesey

Excellent idea, add me as well please.

Colin Jones (THE CJ!), or just Bristol_Jonesey.

Done, thank you, sir!

UnderTow

The same goes for modal windows. The example often cited is the Snap to Grid window. For me an ideal workflow would be something like: You press a keyboard shortcut, the window opens. The Snap To Grid value is already selected. I can either directly type in the time division I want or press the up down arrows on my keyboard to use any of the standard values, hitting TAB once would bring me to the "Move To" / "Move By" selector. Then press the same keyboard shortcut to close the window. Then I can return to doing whatever I was doing before. This would save a lot of time over the course of an entire project.

It is all about how people are most likely to use a feature and how to make it as efficient and quick as possible. Just implementing a feature is only half the job IMO. Going the extra 10% makes the feature 2 to 4 times more efficient and powerful.

For obvious reasons, we could not go into such detail for every feature we included in the list. It would make the list at least a dozen pages long. (Often it takes many more words to explain something that becomes perfectly evident once implemented).I (and I believe we) would like to urge Cakewalk to think of speed, efficiency and flexibility when considering any and all of the features we presented and of course for all and any features they come up with themselves. The name of the game is workflow.

UnderTow

good points. Speaking of snap to grid, is it just me or did the bakers take away the ability to close the snap to grid window with 'enter' or 'esc' ? Now, you have to mouse the little 'X'.

eratu ... you missed me out (wah)

please add kevin rossiter (kevvvvv) to the list

"I fully support this effort, sign my name to that letter, man!"

eratu

rainmaker1011


It is a great list. I fully support this effort!

Thank you for the support! Just to be certain: Does "I fully support this effort!" mean, "I fully support this effort, please carry on and may The Force Be With You!" -- or -- does it mean, "I fully support this effort, sign my name to that letter, man!" ;)

Best, James

:) of course it means: I fully support this effort, sign my name to that letter, man!

Amazed


Tim,

good points. Speaking of snap to grid, is it just me or did the bakers take away the ability to close the snap to grid window with 'enter' or 'esc' ? Now, you have to mouse the little 'X'.

IMO it doesnt make sense to use esc to close a modal window. How would the program know that the esc is meant for the snap to grid dialog and not something else you are busy with? It's quite possible that the window wouldn't have focus at some points. It was mentioned earlier that the same keystroke to invoke the dialog could close it? That could work? Also modal dialogs should have a close button on them for mouse interaction because I don't like the little X either. Big buttons are easy and quick to acquire. Bit OT here. sorry.

On the subject of Snap to Grid, I recently upgraded from Sonar 4 to 8.51, and it seems a very useful feature has been changed in the snap properties.  In version 4 I could set my Snap to Grid value to be a musical interval, (Whole, Half, etc.) and also have Snap to Zero crossings selected.  If I turned off Snap to Grid, Snap to Zero crossings would remain in effect, which was VERY useful for audio clip editing.  Now I have to futz with the Snap properties dialog every time I want to edit audio, and also when I'm done editing.  I would very much like there to be an option for it to work the way it did before.

Also, I believe the term for the Snap to Grid properties dialog is modeless, not modal.  A modal dialog is one which takes over input from the app until dismissed.  (Sorry, I get a bit anal about terms.)

Please add me the list of letter signees.

Terry Lawhon

Count me in.... Andy Wiest(AndyW).