Glyn Barnes

occide
Please add support for Instruments with multiple Midi channels and multiple audio outputs. This has been requested for more than a decade. It causes so many problems having to split audio and midi for multi-out instruments.

I not sure what you mean. I use Kontakt a lot and often have several MIDI inputs and audio outputs.

Also, SONAR can have multiple MIDI channels in a single track to which various instrument inputs can point. I'm also not sure what the problem is.

Oh...and great job with the update. Thanks for making it happen so fast.

Piotr
Virtual Controller introduces a bug as CAPS is not working anymore.
 
Thanks for unblocking R to be able to record but why are keys not used in virtual keyboard blocked at all? :(
Still blocked I, B etc...
 
It is not big deal but kind of workflow imperfection.

These now have their own separate shortcuts. Shift+0 for the Computer Keyboard and Shift+Alt+0 for the Piano Keyboard. Using Caps Lock to switch would become problematic if you were also naming tracks or work with other apps open because the keys may be unintentionally be typing all caps. That is why we made the switch to dedicated view shortcuts and deprecated the Caps Lock behavior.
 
As for I and B we discussed unblocking these as well but found that in some situations we would accidentally press these views when performing on the keyboard. We'll consider this again for a future update. Thanks for the comments.
 

Let it be known my comping issues with 2017.06 were resolved with the update. 
 
@Lance Riley, you people are awesome. 

Lance Riley [Cakewalk]

Improved Project Handling

Artist, Professional, and Platinum

Never wonder again where your files went when you’re in the heat of creativity. As soon as you decide to save a new project, SONAR will create a folder automatically with the appropriate name, and place the project audio and Mix Scenes in it—there’s no need to create a folder beforehand. And, if you later “Save As” or “Save As Copy” in the same location as the current project, SONAR will know this is the original location and not create additional folders—but if you save to a different location, SONAR will intelligently place the project and associated files in a new folder. Now you can spend more time making music—and less time thinking about where to store it.

All right, didn’t read this post through and wondered what’s the problem...

My way of working includes saving multiple versions of projects in case something breaks or I just want to go back to an earlier version: something like SongName_version1.cwp, SongName_version2.cwp and so on. More than occasionally, I have an existing folder with files from some other software where I want to save these multiple versions. Now 2017.06 wants to save the SongName_version1.cwp file to a subfolder named SongName/SongName_version1 and doesn’t let me change the folder name or use the upper level folder. Of course, I can cut/paste the files to the upper level folder or rename this new folder, but it’s a slightly annoying extra step to do.
 
So my question is: Is there a way to turn this Improved Project Handling feature off?

Mwah

Lance Riley [Cakewalk]

Improved Project Handling

Artist, Professional, and Platinum

Never wonder again where your files went when you’re in the heat of creativity. As soon as you decide to save a new project, SONAR will create a folder automatically with the appropriate name, and place the project audio and Mix Scenes in it—there’s no need to create a folder beforehand. And, if you later “Save As” or “Save As Copy” in the same location as the current project, SONAR will know this is the original location and not create additional folders—but if you save to a different location, SONAR will intelligently place the project and associated files in a new folder. Now you can spend more time making music—and less time thinking about where to store it.

All right, didn’t read this post through and wondered what’s the problem...

My way of working includes saving multiple versions of projects in case something breaks or I just want to go back to an earlier version: something like SongName_version1.cwp, SongName_version2.cwp and so on. More than occasionally, I have an existing folder with files from some other software where I want to save these multiple versions. Now 2017.06 wants to save the SongName_version1.cwp file to a subfolder named SongName/SongName_version1 and doesn’t let me change the folder name or use the upper level folder. Of course, I can cut/paste the files to the upper level folder or rename this new folder, but it’s a slightly annoying extra step to do.
 
So my question is: Is there a way to turn this Improved Project Handling feature off?

I haven't upgraded to 2017.06 since there weren't any features I needed and people including Craig A. were having problems updating.
I use a similar naming convention i.e. SongName_ProjectStartDate_RevisionLetter_Mix# and put it into organized folders with the name of the song. I hope I can still do this. I certainly don't want Sonar to start saving my projects in my C drive that is SSD and used only for the operating system.
 
Have you tried "SAVE AS" and put the project files in a folder you have created for it?
 
Walt

WallyG
I haven't upgraded to 2017.06 since there weren't any features I needed and people including Craig A. were having problems updating.

Just to follow up...it seemed like it was a temporary issue, I updated on two other computers with no problems. 
 
I love AT&T internet - it teaches me the meaning of patience. 

WallyG
Have you tried "SAVE AS" and put the project files in a folder you have created for it?
Walt

Yes, it’s ”save as” that wants to create the new folder with a predetermined name (if you’re not happy with the folder the previous version of the project file resided).

Mwah

WallyG
Have you tried "SAVE AS" and put the project files in a folder you have created for it?
Walt

Yes, it’s ”save as” that wants to create the new folder with a predetermined name (if you’re not happy with the folder the previous version of the project file resided).

I'm a little confus-id (as my good Italian friends would say). If I'm working on a project and want to "save as" with a new revision letter, and I am "happy with the folder the previous version of the project file resided", will it store it there or force you to put it in a folder that Sonar selected?
 
What if I started a new project and set up a folder where I want it, does Sonar say you can't save it there, you have to put here with this name? That wouldn't make sense.
 
Walt 

Save As .. might be defective in 2017.6. I tried to save a copy under another name in the same directory as the primary project, and SONAR put it into a sub-directory with the name of the new project name I'd entered.
 
Edit:
Darn, I can't reproduce it. It might have been my fault. I'll pay close attention next time.