In the interest of further refining X1 and helping it function even better than it now looks, I hereby present my list of future improvements that I would like to see considered for SONAR X2 (or whatever it will be called). 

• Plugin Manager
  • Better plugin manager - The plugin manager windows should communicate with each other so that its easier to identify which plugins are already available in the currently loaded plugin layout, eg. bolded or italicized
  • Highlighting of new plugins detected after the most recent scan 
  • Protection from VST scans overwriting custom names - I've stopped using the custom naming feature because invariably one day I'll need to do a full rescan and lose all of my custom plugin names. Custom names should also be protected from installing an update of the same plugin.
  • ALL plugins should support custom naming - Ironically, many of the included Cakewalk plugins are the worst offenders in this area and many refuse to save custom names
  • Update button needed in the Plug-in Manager - A new button which saves the current plugin layout, and closes the plugin manager window without opening the File Save dialog every time you make changes
  • Option to use the plugin layout names in Effects bins, instead of the default one assigned to the plugin 
  • Removal of the full rescan of the plugin window each time a single change is made.
• 64-Bit Bridging
  • Make Bitbridge windows function like any other plugin windows -they shouldn't stay on top of or not minimize along with the main application
  • Allow default Bitbridge functionality to include currently hidden ACT controls without requiring special modifier keys when opening
  • Allow full drop-in replacement of Bitbridge with J-Bridge, with a fallback option to use Bitbridge
• Media Browser
  • Return of the ability to deselect individual playing loops when auditioning multiple loops. The removal of this feature (when REX support was added) has seriously crippled the usefulness of media explorer for some people
  • Folders in the Media Browser should open with just a single-click instead of requiring a double-click
  • Fix the random ignoring of the current output bus bug in Media Explorer
  • Ability to exclude changing the currently displayed settings of the Media Browser when using screensets
  • Move the 'Sync to host tempo' and 'Play looped' options to toggle buttons at the top of the Media browser instead of being menu items
• Auto-save
  • Fix the audio glitching that occurs when Auto-saves kick-off while the transport is playing

or

• Provide the ability to postpone Auto-saves while the transport is playing
• Tempo
  • Improve the changing of tempo - Changing tempo shouldn't require pressing [Enter] or clicks outside of the widget to implement. 
  • Mouse wheel support would be nice
  • Make the +/- buttons bigger
  • Access to Tap tempo should be made easier and more obvious
• Console View
  • Option to Auto-expand the currently selected track when Narrow view is being used. Track should then return to narrow mode when deselected
  • Color-coding ala Pro-Tools

Wherever possible, I would like Cakewalk to provide the option to maintain current functionality via preferences where it makes sense. 

JMHO...what do you think? 

-e.B

I'm totally with you for EVERY point about the plugin manager.

I'd add bi-directionality to the Media Browswer, so I can quickly work library items back and forth.

Independent timeline for the Matrix View would be nice.

ACT 2.0! (or something, fer realz this featureset needs some lovin')

Audiosnap 3.0! (they've done a lot of work here, but it's still needs more integration and a more intuitive workflow for beat-mapping functions)

VARISPEED!(my biggest "I want a pony!" desire)

Smoother, more instant screenset transitions

"Replace Synth" command, with some allowance for a newer version of the same synth to be able to read patch selection of the replaced synth.

A "smart select" where selecting the MIDI track of a soft synth will intuit that the audio track is assumed when doing bounces and exports.

Custom control bar modules with a wider access to functions.

Exposing all plugins and audio tracks to inputs would be rad. So we can finally do live recording (bouncing) from bus-to-track and such. I'm a big proponent of SONAR's bussing structure but it's been a while and having some way to do live bounces without going out and back in would be faster workflow.

V-Vocal integration into the Track View. Someone has to say it: the V-Vocal UI is a bear to deal with, and without being able to see multiple tracks or otherwise have visual cues it's a chore to do detailed time-based editing. Everyone else is working it into their core interface, I think it's time to make the jump (this could probably be merged with Audiosnap and/or varispeed updates as well)

like to see a better save system implimented for loops.dragging them into explorer is becoming inconsistant.maybe even a better save system over all for projects as well.how many curuppt files do you hear about where people cant open and having to use safe mode?

VST3...for the love of GOD.

I like to see a 'real time' kinda step sequencer aka drum machine beat/loop programming style.

With the beat running, it's more natural to build up / or erase drums part on real time, especially using an external pad controller.

Not sure if the current X1 can do this already. 

With ref to 
http://forum.cakewalk.com/tm.aspx?m=2302166

I like an option to customize the mixer fader to have a longer travel, to be more usable for touch screen.

I'd rather the bakers worked on making Sonar X1 as rock solid and virtually bug free as previous incarnations before they move forward onto the sunny uplands of enhancements!

How about a plugin manager that can find vst's for older projects when the plugins were in a different folder?

Skyline_UK


I'd rather the bakers worked on making Sonar X1 as rock solid and virtually bug free as previous incarnations before they move forward onto the sunny uplands of enhancements!

+1

Beofre we start making X2 wishes I would appreciate that they continue with X1 so that it fulfills its promise from when it was released.

I get the feeling that is more in keeping with their current position than what's going into X2. Of course as soon as a version is released there's likely already a small planning team working on the next version.