2 more...
 
1. folders in console would be awesome, especially if they match the folders from the track view.  you can see this in reaper for example.
 
2. not having bus/master tracks in a separately divided panel in the track/console views.  we should be able to position a bus where ever we like.  i dont like having my buses so far away from the tracks im using them as a group on.  to then be able to collapse the tracks under the bus saves so much space and makes mixing much much easier.  after using this in reaper and studio one, this is probably my biggest pain point in sonar from a workflow perspective.

#1 a Big One issue / bug for me...
It was acknowledged by previous Sonar bug team as a "bug" about 5 month ago but was never repaired.
When I do vocal take lanes, new material is placed in random "empty spots" comping.
That is ok...
BUT it would also record new material to MUTED take lanes if they have empty space.
If the take lane is MUTED by user, It should stay MUTED. Sometimes I would have 50+ audio items in tracks and when new audio is recorded to muted take lane it drives me mad to locate it, and delete other items within take lanes except the new recording. 
If new bug team is proactive and responsible, please look into it. If you need, I will gladly share correspondence with previous bug team.
 
Hopeful and passionate user.
Thank you!
 

You have been given quite a list. I just want to thank you for caring and asking. That’s the biggest change you’ve already given us!

Another one... I never liked take lanes. Waaay back (mebbe PA9 or SONAR 1XL) when I was looping and doing multi takes, I could set it to *make* a new track and store take there. 5 takes would equal 5 tracks and each but most recent would be muted. This was (for me) *much* easier to work with than lanes. If there is a way to set this behavior in SPlat, I haven't found it. If it's there, please tell me, peeps. Otherwise, consider this a feature request. 

1.  Hassle-free compatibility with the major-player MIDI keyboards and control surfaces from the last ten years or so.  Studio One and Ableton work with my Akai MPK61 (v1) out of the box, but Sonar requires major ACT headaches to get the basics going.  This is offputting to new (and even seasoned) users.  It's needless hassle. Dump ACT.
 
2.  Improve Matrix view so users can record audio or softsynth midi into cells.
 
3.  Make the full version Cakewalk softsynths part of the flagship DAW package.  I already own all of them but Rapture Pro, but this would be a good gesture for others.
 
4.  Modernize, expand and improve upon the ProChannel.
 
5.  Put resources into Support and revitalize Cakewalk's reputation for support.  I never needed it myself, but the user reports and assigned resources were highly embarrassing at the end of Gibson's ownership.
 
6. PLEASE make dedicated iOs/Android control surface apps.
 
 

Phoen1xPJ
Another one... I never liked take lanes. Waaay back (mebbe PA9 or SONAR 1XL) when I was looping and doing multi takes, I could set it to *make* a new track and store take there. 5 takes would equal 5 tracks and each but most recent would be muted. This was (for me) *much* easier to work with than lanes. If there is a way to set this behavior in SPlat, I haven't found it. If it's there, please tell me, peeps. Otherwise, consider this a feature request. 

Take Lanes are non negotiable for me.  They are absolutely brilliant if you actually use them how they were intended.  Maybe make it an option to turn on or off if people don't want to use them.  

Hi Meng & thanks
 
1. Metronome bug fix: At times it doesn't work (silent) unless you toggle the FX button.
 
Mike

Thank you!!!
1- Fix the bugs (Freeze is broken, surround is broken, ect.) 3d party plugin relationships.
2 - The automation is very clunky need a complete overhaul. ( Maybe also have a checkmark for the items needed and ability to remove the pain in the ass lanes with too much clicking. In Sonar 8.5 there were many removed features I'd like back.
3-Use of icons, please bring back the icons.
4- audio snap is very cumbersome could be simpler and more effective.
5- Improve workflow is so important to me. Anyplace you can remove clicking and speed up wk flow. So many 3 or 4 clicks to do something that should take 1 click.
 
Very excited to see the progress!!

.

Hi. Long-time Cakewalk/Sonar User here...

1) Bugs!!! They all must go... It is a matter of integrity and should be any companies top priority, especially for software that has been around as long as Sonar has... and which has been under constant development (aka: Rolling Updates) since Sonar X1.

2) MIDI - Back in the day when Memory, Processing, and Storage were expensive, much was done to improve the way MIDI functioned to produce AUDIO. Now that the aforementioned is relatively cheap, it seems much of the development in the past 15 or so years has gone towards improving Audio, which is not a bad thing but I’m afraid MIDI development has been neglected. There are keyboards being manufactured now without MIDI ports, which is a shame since MIDI, from it’s conception, was supposed to be about standardization and compatibility. FINE, add a USB jack but leave the MIDI Jacks, so we have compatibility with our vintage gear! Now with MPE and IOS integration...how quickly we forget.

3) Specifically, LOGIC, or at least in the old days, before Apple, their used to be an “Environment” page where there were all these different objects you could drag and connect with your mouse...It gave you a very visual oversight as to what was going on ROUTING wise (Again, mainly for MIDI) but you could easily route a multi channel instrument and split it to various destinations and be able to actually have a good idea what is happening when you open a project you completed 6 months ago... I don’t have a MAC so I’m not sure how they are doing it today but I believe SONAR, or whatever the name is going to be, would greatly benefit...much as the Skylight Interface helped to visualize a Recording Environment, in a system where anything can be virtually routed to almost anywhere, this sort of virtual patch bay/wiring diagram I believe is a necessity. Frankly, I’m surprised nobody has thought to include this GUI. The Track/Arrangement view is not the ideal place for it and frankly, with the Patch Points and Auxillary connections, it actually clutters that screen, though the idea of adding the connection points is needed, you should be able to just drag a line from one object to another and then back again...

4) Get rid of the dead weight... Personally, the .cal scripts never did nothing for me and though the rest of the platform has been developed consistently, .cal and the instrument configurations have not been updated for several major releases. I appreciate application integration if it helps with performance, otherwise, it’s just one more place for something to go wrong and crash the whole Program...

5) Control Surfaces - This needs to be on the leading edge, with all the new generation controllers that are now available (E.G. Roli Seaboard). It would be great if someone would produce a mapping system that actually worked...or one that could be easily assembled by again dragging objects (faders, knobs, switches, buttons, etc) and assignigning them to hardware counterparts. That way you don’t have to wait for a template to be made for every one of a gazillion devices one may want to control. I’m sure that would probably require a collaborative effort but I see it as being very do-able and essential.

I could be living in a Virtual World, but that’s the way I see it...in Detail....