And export as MP3 is now free and just works like wav.
 

I don't only do midi only projects.  I also do mixed midi and audio and just audio.  With my midi only files I can get by using Sonar X3 until Cakewalk gets around to fixing the problem with Sonar Platinum.  I will however, miss all the power of Sonar Platinum on integrated midi and audio projects.  Just the fact that you mentioned that you will look into the problem is motivation enough for me to be patient.
 
I believe the easiest way to reproduce the problem is to produce some midi only tracks file in X3 adjusting the reverb and chorus knobs with different values for each track. Then save it as a midi file.  Then, open it up with X3 and you will notice for each track the reverb and chorus settings are recalled also. Close the file then open it up in Platinum. You will notice that the reverb and chorus dials register zero (0) for each track selected.  Look in the track view and the reverb and chorus settings are displayed as inline controllers with the values set.
Thanks again for just showing interest in looking into this.

I am unable to delete aux/patch points from the send submenu.  Whenever I delete the sends, they still appear as assignable patches in sends menu, altjough the track itself (aux) is deleted.

One problem still persists: as I mentioned in this post, I prefer to always work with the Multiple Lanes view as Default.
I have always worked with the Multiple Lanes view as default, which gives me an important overview mainly for VST instruments that use multiple simultaneous CCs.
Now, even though I check this option in the PRV, every time I close PRV, this option goes back off. And then I'm forced to manually repeat this step all the time.
The correct thing would be for Sonar to somehow memorize whether or not I want to open the Multiple Lanes PRV as default.

Good catch rogeriodec,
 
I've bugged it up for a 17.05 fix.  Thanks!
 
~Bob

Are you the new Midi guy we have heard about Bob. Your short posts have been very reassuring. Can you look at the font colours for the next release too. In Mercury and Tungsten it's hard to read the active CC selector, but I noticed in Tungsten the Transform button is drawing from two Font colour pools, so maybe assign this CC selector to the same two
 
I think the Active CC Selector should come from the 'Global Menu/View Menu text' pool

Ahh, looks like the Theme  weren't updating and was stuck on the colour.
 
I just noticed in the guide that had an orange tab, so must be Tungsten, but my Tungsten was showing dark grey
 

 
ReSterted Sonar, and now it shows blue for Merury, even when I change to Tungsten and my own themes.

Ok, so I don't need to close Sonar, just the current file/project to get the changes to stick. Anyone know what sets this colour. Having to experiment on my own theme, close the project and re-open to see if it changed is turning into a right b******e.
 
Here's Tungeten showing Mercury's selector.

Are there any plans for tempo track enhancements? For example, the ability to increase/decrease all selected tempo points proportionaly.

"TAB-to-Note now auditions the note"
 
I couldn't get this work but then I found you have to touch a note first. Is that intended?