I have submitted a few support issues recently (August 2016). 
 
One of them, after some urging got "sent to development".  I no longer have the option to "bump" this request as you might a forum post.  I can't comment on it or ask about it.  I have received no feedback at all, and of course, the fix hasn't happened.  As far as I know, it is sitting at the very bottom of a bin of reported tickets that have been there as long as this bug has been around - since at least the x-series product began.
 
The second one is still listed as "This is a new problem report. It has not yet been reviewed by Cakewalk."  I have updated this ticket 4 times, once each month since it was reported.  I have received no feedback, it has not been sent on to development, and as far as I can tell, this ticket has no voice.
 
Both of these tickets were completely described with the issue, the steps to report it, and both have existed through many versions, at least as far back as X1.  These are both things that flat out do not work.  One is extremely simple to reproduce, the other is a little more complicated and the two both are connected to Midi Remote Control.  ACT does not provide the facility I need so I've resorted to this method and it simply doesn't work.  I cannot fathom how this feature is even IN the program for the fact that the first of these two bugs exists.
 
So three questions:
 
1. Is anyone here able to SAVE a project that has a single Midi Remote Control set up and then open the project and still have that Midi Remote Control still in it?  I can't.  I have to re-create this one remote control for a mute button every time I open a project - any project.  It's really annoying and I can't imagine how irritating it would be if you set up several such remote control scenarios.
 
2. Is anyone able to setup a Midi Remote Control on a toggle - like a button - such as a send on/off - and use the midi remote control to actually have an effect?  Here's what I mean: you have the remote control on the send on/off on a track or bus, you press the button on the midi controller, you see the send turn on and off on the screen, but the audio is unaffected.  When you manually click the same on/off with your mouse, both the display and the audio are affected as you would expect.
 
3. Is  there some way that I can get the second ticket at least recognized as being there and is there any way I can get some sort of feedback on these two items? 
 
The "does not save midi remote control" is the one that is still considered a "new ticket" and is ticket #54259.
 
The "midi remote control buttons have no real effect" is the one that has been sent to development and is ticket #54260.
 
Both tickets were submitted on 8/20/2016, so I don't think I'm being pushy in expecting someone to do SOMETHING with either or both of these easy-to-reproduce, version-spanning, obviously-broken things.
 
Looking forward to any assistance!

Hi Blades
 
Sorry I can't help you with your tech issues, but I thought I'd give you a bit of moral support on the ticket issue.
 
I sent a tech support question to Cakewalk a couple of months or so ago, and after waiting a long time and getting no response, then sending them a follow up email asking for a response please, I finally got an email from them. Their email contained an apology for the delay, and a plug about the new "Bakery" forum, but they completely ignored my tech question in the response - not a word in reference to it!
 

Thanks for the input, Dilaco1.
 
Anyone able to reproduce the issues I've reported or want to tell me a way to make them work?
 
Anyone able to get Cakewalk to look into either or both of these issues?

i just gave it a whirl, and i can set it up with remote control and when the send is triggered to off by the set key the output to the bus is not heard, when triggered back on it is heard. also i can save the project, close it, reopen it and the remote key still works. seems fine here.
 
so that would be a 1. yes and 2.yes

Blades
 
Ilike a button - such as a send on/off - and use the midi remote control to actually have an effect? 

oh and you realize that if you select the 'note on/off' option in the remote dialogue, when you press the key it will switch off the send, but when you release the key it will turn it back on, with 'note on/off' you would have to hold the key for as long as you wanted the send to be off. if you select the 'note on' option in the remote dialogue it will act as you desire

Remote control works and persistent for me. I do not use that feature for strip or plug-in controls, for that I have AZ Controller, but for Matrix view there is no alternative.

 
Ok - so I'll reproduce this again and if I can get it to fail as described, I'll post a video of what I'm trying to do.  I have done this over and over and it is consistently a problem for me, so I don't know what is the difference.
 
As for the "way" that I'm doing the trigger: I'm using a midi note, yes.  There is a place where I am able to get this to work, and that is to mute an output.  So to accomplish what my original goal of this was, I set a "remote control" to Note C1 to toggle the mute on a hardware output.  I do the same for the other output, but start it in the opposite state.  So the result is that when I hit the key, it mutes one output and in-mutes the other, so I can use this single button to switch between monitors and headphones (monitors are out2, phones are out1).  The on/off press/release is not causing a problem with the mutes, so I don't know why it would cause a different issue with the sends. Remember, what I SEE is the correct behavior.  What I HEAR is not.
 
The way I was originally trying to do this was to simply set the send on and off on the Master bus to toggle which send is being used - with send1 going to out1 and send 2 going to out2.  The way I'm doing it now is just as functional, but is only a single example.  The Send (as opposed to the mute) is the difference - using the exact method to assign the midi remote control for both and only one of them working.  I took this to the track level from the Bus level to see if it was a bus problem, but I can replicate the issue there as well.
 
And as far as the save is concerned, I've tried the non-working remote setups and the working mute setups and none of them save with the project for me - consistently. 
 
Thanks for taking a look. I'll post back.  Maybe it mysteriously got fixed somewhere along the way or I have a screwed up "base project".  I've used this project as a "start point" for years - so maybe I'll try to create a new project from the base templates provided within the new Sonar instead of the old template I'm using.
 
Another point: this is a two-fold post - part one is about this particular pair of problems and part two is about the non-answers in the support system.  Remember that one of these hasn't been read by Cakewalk and the other has been sent to development. If they sent the issue to development, they must think it's actually a problem.  The other, well - I just haven't heard, so I don't know what they think.
 
Thanks again for your time and input!

I was able to reproduce MOST of this issue.  It seems that some of my problem has gone away and MOST of it remains.
 

• The SAVE issue seems to have been Partially resolved.  The Bus Midi Remote Control at the Bus section allows me to save the midi remote setting and reloads it with the project.  However, since that doesn't actually function properly, I have gone to using the midi remote control for the mute/unmute of the actual audio output.  I assign a midi remote control to THAT and save and when I reload, the midi remote no longer works and has to be re-assigned each time.
• The ability to trigger a bus on/off at a TRACK level seems to be working
• The ability to trigger a bus on/off at the BUS level still seems to be broken.

 
Here is a video screencast showing the problem(s).  I hope that this makes more sense than my text descriptions have been.  I also hope that someone is able to reproduce this and explain what I'm doing wrong.
 
Here's a link to the video example: https://www.screencast.com/t/7jz3xt2Bg0F3

Anyone have a chance to watch this and see if it can be replicated?
 
Anyone from Cakewalk willing to take a look at the tickets I opened and see what the holdup is?

Well?  Anyone?  Thoughts?  Help?
 
You know - it's not this is critical or anything, but it would be nice to get some input from the Cakewalk people.  I appreciate the responses that I DID get on this for other parts that DO work - but what about the parts described here that don't?  Or a way to accomplish the same without these things?