there are still some bugs with this setup, when I tried it with pan just to confirm, it took about 4 attempts to get them all moving simultaneously, but the faders were no problem bottoming out and returning all to unity with the dbl click.  this was on a new project for testing. I know very old projects have many issues, but I will test on somewhat old projects and see.

Okay...if I save the project that didn't work as expected as a bundle file, and then re-opened, everything worked as described in post #10. So I assume there's something inhibiting proper operation that the bundle file strips off. Or, maybe the project being built on an old template is the issue.

Update: I found a project where the "it doesn't return to 0 on double-click" failed every time, and sent it to Cakewalk for analysis. It's really weird, because everything works as expected in all the other projects I've tried. Hopefully having this rogue project will provide the requisite clues to figure out what's going on.

You bring up a reoccurring point Craig. I don't think I've ever started a new project since using SPlat. I have dozens of older ones I keep working on and keep having weird issues with. It would make sense if there was something within the cwp file that invokes older behavior patterns. But it doesn't make sense that cwp files would have the power to do that.
 
Even so, I have saved many older projects in SPlat after editing them. After so many save-as'es the issues seem to increase as if they're carrying behavior over from every version of Sonar they were saved in, and that behavior is conflicting with itself.
 
Maybe I should look into restarting older projects afresh in SPlat and see what happens.

Anderton

bitflipper
I'd like to see CTL-double-click reset all faders to 0 dB.

Simplest way I know to do this is:
 

1. Select all tracks
2. Ctrl+click/drag any fader to bring all down to -inf
3. Ctrl+double-click any fader to set all faders to 0

Thanks Craig
 
It worked very well for me.   I knew I liked you for some reason...

soens
You bring up a reoccurring point Craig. I don't think I've ever started a new project since using SPlat. I have dozens of older ones I keep working on and keep having weird issues with. It would make sense if there was something within the cwp file that invokes older behavior patterns. But it doesn't make sense that cwp files would have the power to do that.
 
Even so, I have saved many older projects in SPlat after editing them. After so many save-as'es the issues seem to increase as if they're carrying behavior over from every version of Sonar they were saved in, and that behavior is conflicting with itself.
 
Maybe I should look into restarting older projects afresh in SPlat and see what happens.

Why don't you try Craig's tip above - save an errant project as a bundle, then re-open it in Splat?
You have absolutely nothing to lose.

soens
You bring up a reoccurring point Craig. I don't think I've ever started a new project since using SPlat. I have dozens of older ones I keep working on and keep having weird issues with. It would make sense if there was something within the cwp file that invokes older behavior patterns. But it doesn't make sense that cwp files would have the power to do that.
Even so, I have saved many older projects in SPlat after editing them. After so many save-as'es the issues seem to increase as if they're carrying behavior over from every version of Sonar they were saved in, and that behavior is conflicting with itself.
 Maybe I should look into restarting older projects afresh in SPlat and see what happens.

I have found similar, and using custom templates that were created with previous versions of SONAR can lead to some unexpected gremlins.
 
I recreate my templates every year or so, that way I'm working from a reasonably fresh code. Just reduces "odd behavior". Plus, with the advances in SONAR, I've found I rely more on track templates that are universal..which enables my project templates to be simpler...easy to "refresh".
 

soens
You bring up a reoccurring point Craig. I don't think I've ever started a new project since using SPlat. I have dozens of older ones I keep working on and keep having weird issues with. It would make sense if there was something within the cwp file that invokes older behavior patterns. But it doesn't make sense that cwp files would have the power to do that.
Even so, I have saved many older projects in SPlat after editing them. After so many save-as'es the issues seem to increase as if they're carrying behavior over from every version of Sonar they were saved in, and that behavior is conflicting with itself.
 Maybe I should look into restarting older projects afresh in SPlat and see what happens.

I have found similar, and using custom templates that were created with previous versions of SONAR can lead to some unexpected gremlins.
 
I recreate my templates every year or so, that way I'm working from a reasonably fresh code. Just reduces "odd behavior". Plus, with the advances in SONAR, I've found I rely more on track templates that are universal..which enables my project templates to be simpler...easy to "refresh".
 

Created a new BASIC project in 2017.08 with 2 audio, 3 midi and 1 instrument track. However, the ctrl functions still do not behave 100% as Craig described. So project age doesn't seem to be at fault. Maybe geographical region magnetic variances are affecting it. I AM closer to the North Pole, after all.
 
FWIW I don't use this feature and so it really doesn't matter to me how it's supposed to work tho I'm not alone as bitflipper, others, and the CakeTV video have noted.

control A = [track]- [property]-volume..
 
work good here on SONAR 5
 
martin