Progress Update from cakewalk on controller fixes

You are asking for fixes for a controller that discontinued support like 3 years ago ? 
Imagine if everyone flooded this forum with multiple threads (about the same subject) about their personal needs. Then it would be impossible to help those who needed it.
This post (and the same one you posted last week on the same subject) wont get you a fix any faster and will more often than not rub others the wrong way. bump your old thread or be patient.
 
PS- for what its worth, I used to own a V studio controller. I got rid of it when they dropped support for it.
I bought a Mackie MCU which works amazing and they can be had for cheap money. there are 3 used at GC right now for under 300 bucks.

Thornton,
Rather than "chastise" you for numerous threads on the same subject, or suggest you "give up" on your
current controller (more on that later); I'll offer some advise.
A) Roll back and wait for Cake to "fix" things; you're not "alone" in this.
If there's nothing in the latest updates you "need" or rely on...
B) Now lets see if we can "fix" it ourselves.
I have 2 controllers; the Tascam FW1884 (orphaned years ago) and the Frontier Tranzport (also an orphan).
Both lost some functionality in the latest updates (2016.11 and .12)
Most notably the "Marker" key.
You have to open the ACT module and click on Controller/Surface Properties

It's  ^ there.
Now, hopefully, you can locate Project | Insert Marker in the drop down menu

I tried this in 2016.11 on the StudioCat for the FW1884 and could not find Project | Insert Marker.
I may have "missed" it. I'm not re-installing to find out.
When I rolled back to 2016.9 the Tranzport worked fine, dropping a marker each time it was "keyed".
The FW however did NOT. When I opened the Properties dialog I had to re-bind the Marker key to
Project | Insert Marker.
Did I change something, inadvertently, in 2016.11? I don't know; it works now.
Best of luck!
<begin rant>
Discontinued Support
It is unconscionable, given the "flagship" status that the whole VStudio series enjoyed, to think
that discontinuing VS support is OK.
Roland has indeed "left the building", BUT it is NOT unreasonable for users to expect Cakewalk to continue
insuring "basic" functionality remains.
Obviously something very basic is "amiss" if all the commonly used controllers are "broken".
Cake chose to "ignore" the EQ sections when it introduced the ProChannel.
I can "twist" my EQ knobs, and things happen; just not the "right" things.
Why not leave the "basic" commands the same in the new PCEQ section? (but I diverge).
The bottom line is Cake changed or missed something in the latest updates.
FIX IT!
<end rant>
One last thing, every time you criticize the OP, or any post, you bring that thread back to the top of the heap.
You might want to think about that.
"If you don't have something nice to say..."
Well I think you catch my meaning.
T