A "Duplicate pattern" button in the Step Sequencer. Better yet, a "Duplicate" shortcut everywhere, a la Ableton Live CTRL + D.

Better Step Sequencer integration with the Matrix View, like editing and auditioning a pattern while the Matrix is running.

Integration between the Step Sequencer patterns and Drum Maps. Save drum maps with patterns. Better yet, save the track template with them, too, and make it possible to audition it directly from the browser, a la Ableton Live Clips. This is one of my favourite Live features. I can save a midi pattern with all the track routing and patch changes to an external hardware synth like a .alc file and audition it from the browser without loading the actual track. If you don't know what I am talking about, think of it like a previewable track template with data.

Thought I'd revisit this suggestion I made some time back. Lots of VSTs operate with keyswitches and CC, whether it's selecting velocity layers, articulations or even different playing techniques. It'd be incredible for workflow if we could customize visuals on the piano roll for this per track (and obviously save them as track templates) so that keyswitches and CC thresholds, etc are easier to parse at-a-glance rather than flipping through VST user manual PDFs every couple of hours. Here's a mockup example for Prominy's V-METAL guitar library.
 

 
Similarly, CC lanes and even the velocity row could show specific thresholds for the VST in question.
 
Ideally, if piano roll themes were per-track (defaults to global if no per-track data) and included BG color selection, text color selection, and label text per MIDI pitch, that'd accomplish something very close. Ditto on CC lanes, although that'd have to also then add number of divisions, where the boundaries are on each, etc.

See your original post in the forum

Narrow strip versus Wide console strip:  Can we please have the buttons on the same rows?  In the console view, a narrow track will have REC and INPUT MONITOR and MUTE shown.  In the wide strip, it adds phase/interleave, and other stuff.  But, the two rows are not on the same "line".  Can we have the two rows swapped so that those functions are on the same "line" for narrow or wide strip?  
 
It makes for a cleaner look, and easier to drag mute across tracks.
 
Dave

I know you guys are working hard at bringing Cakewalk back from the dead, and as a long-time user I am grateful. but when are you bringing out the cakewalk plug-in and instruments that are still waiting in the wings? Specifically CA-2A and Rapture Pro

Want these:
1. Add scale and root notes to step sequencer. I was using korg sq1 for sequences. Cakewalk sequencer is good for drums, but making it iseful for synths is not that easy and fast.
2. Add lock merge and lock transient guides more simple.
I was using Reaper, where timestretching for multitrack source is very easy. I group tracks and then I add stretchmarkers to one or two tracks. And other tracks just locked to main. That is fast and easy enough instead of activating audiosnap, then changing threshold, then select tracks and then merge. After that i need to select few tracks to make timestretching.
3. Fix export option "what you hear". Because when you have midi and soft synths on separate tracks, there's no sound on exported wav. It's not what I hear.
4. Clip gain. It's a timekiller to adjust clip gain without preview. I would like to touch my clip sonewhere and boost or cut gain.

for export i'd suggest additional setup of exact export time, so now i can highlight it with mouse and selected area will be rendered, but in some cases it's better to do just with changing some number values
And well a new major feature that needs a lot of pro hardcoding 
- enable few cards for play
i got 3 sound cards inside, 1 for music, 1 for games and one with mobo, they are all capable for 192khz/24bit
the problem i got - i described in my previous suggestion post, i need play sound and play midi.
right now we can solve it with freeze track and switching latencies + asio\wasapi
and if i could use 1 card for 1 real time instrument and routing other devices, then other cards i could use for rendering audio in realtime, but for different instruments.
So i could send those instruments for new buses and switch those buses to render with different cards and main bus will aggregate it all with main card.
the hardest part here is about different latencies and different hardware driver modes and well if you remember one of my other req posts, using cuda or opencl for some reasons (fx bin, fx bus, console routes, prochannel) would be good too.
yes, maybe i'm too freak, but no other soft can do this (cub?) so this can be a pro feature for live show.
you'd better ask more musicians about that, to check if it is really needed and enable it as a paid or pro-feature,
but you'll need a lot of supported hardware and tests.

*BUG*
I have a recorded video for better understanding. Video here
 
When you take two clips on the same track and move them together (and create a crossfade, if so desired) I try to drag one of the clips to make sure it is in sync with the metronome and when I move the clip, the part that is crossfaded now has a "cut", or "gap" in it after being moved.  Sonar 4,5,7, or 8 that I've used in the past has NEVER done this, so why now?  When I would drag one of those clips, it would just slide accordingly with the crossfade (if applicable).  I could not find any option in the preferences menu to change this from happening.
 
80% of the time this works how it SHOULD and does and this bug does not show it's ugly face.  I have to assume this is a bug in the software since I have ALWAYS edited in Sonar the exact same way since Sonar 4 and this editing bug happens MOST of, but not all the time.

It would be nice if Sonar got the Randomness of something like Dr T's Keyboard Control synthesizer Level 2. (KCS Lvl 2 This system is so far ahead of its time and to my knowledge nothing even comes close to it.  Biab seems to be the only company left with it.  

Hello,
 
Thanks for opening this forum to suggestions.
Wish list:
1. Better, tighter midi engine (explanation below)
2. Better compatibility with Melodyne.
 
Before Gibson shut down Cakewalk there were two issues I found plaguing Cakewalk through a few versions which started when they changed the midi clock;
The MIDI records a slight bit ahead of where it was actually played.
So, if I strike my key right ON the beat, the midi mark would show up just before the beat after the recording was complete. 
I found that switching from 48 to 44.1 corrected this a bit.
 
Switching from 48 to 44.1 also helped correct a lot of what was wrong with Cakewalk's interaction with Melodyne. 
 
In 48, Melodyne crashed almost all of the time and preview functions did not work.
In 44.1, the crashing was reduced by 75% (it still crashed but a lot less time) and preview worked.
 
Thanks!