Two support "ticket" questions

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!

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?

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

 
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!

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?

Seriously?  No one?  Not one Cakewalk person that can help or who has any input here?  No one else who can verify that this really is a problem?  I know it's a pretty specific combo of things that fail here, but I'm really surprised I have so little feedback.

Hey telecharge - yeah - I think I HAVE put that to the test, both through the normal expected support channels (i.e. opening a ticket) and through the forum here begging for someone to at least acknowledge the ticket.  Same business day?  I'd like same business year at this point!
 
As the owner of tech support company (which I know I've mentioned here many times), I'd be horrified if one of my clients had to go to a public forum to complain that ticket was not being answered AT ALL.  Embarrassing!  I'd have an HR meeting that day with that employee.  Here - I get neither a response to the ticket(s) nor to the public plea for help.
 
Not sure what else to do to get a simple "yep or nope" at this point.
 
Thanks for your support, though. :)

Telecharge / all,
 
I have submitted an email to support to follow up on both of these issues today - Saturday at 1:20pm.  I will report back about this 24/7 commitment and "same day responses".  I don't necessarily expact a Saturday solution or even a response, but I think that (unlike my ticket submissions) I should get a response at some point anyway - vs the wait since last September.

Chuckebaby,
 
I am a Platinum lifer!
 
I don't think there is a hardware issue at play here.  I could easily set the bus sends the same way using a reverb or something and have the same "doesn't turn on and off" and as for the save issue, I tried to set it to my other sound card's outputs as well (actually two other types of hardware, a soundblaster and a Line6 Toneport)) and the save still doesn't work.  So, both cases have been tested out with alternate options and worked (or not) the same way.

Just as a follow-up on this issue:  Seth got development's eyes on this.  He sent my demo video on how to repro the issue to them, they saw what the problems were, and in the 6/17 version, BOTH of these have been addressed and fixed.
 
I hope that someone other than me was wanting to use these features.
 
Yea! Finally!  
 
Of course, I only needed one of them fixed for my purposes, and it could have been either one, but both is good for a few reasons:
 
1. I can CHOOSE either method depending on my reasons.
2. I know that I 'm not losing my mind.  These really were bugs and not something I was doing wrong or expecting to work in a way not intended.
 
Thanks to Seth for getting these pushed into development and noticed.