yea you right i should be patient,  but the controller is still viable and it was working fine until the update so it being discontinued has no relevance. I see people on here all the time talking the same problems they have (i.e.staff view) so if i rubbed someone the wrong way hey i am sorry.  Lance has said on the forum that they had made a mistake and was trying to fix it. just wanted status of the update. just like other want status on other stuff.  so if you see the post just ignore it and i think you would be happier thank you

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
 
 
 
 

thank u so much for the support I will try this today and let you know if it works thanks again

dupe comment
 

DeeringAmps
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.

That's a good point. why don't you really help the guy out by bumping all 4 of his threads on the same issue.
Here they are: 3 of them are within the last week alone. So what you call "criticize" I call "playing fair".
http://forum.cakewalk.com/vstudio-100-problem-since-last-update-m3530971.aspx
http://forum.cakewalk.com/Whats-the-word-cake-on-the-fixes-for-vstudio-100-and-other-controllers-m3540180.aspx
http://forum.cakewalk.com/Controllers-fix-m3541336.aspx
http://forum.cakewalk.com/Progress-Update-from-cakewalk-on-controller-fixes-m3543109.aspx
 

DerringAmps
"If you don't have something nice to say..."
Well I think you catch my meaning.

ya the others  "chastising" and "Criticizing". ... but if you have nothing nice to say...you know..
that's some odd logic.
 
 

Here's my experience. Windows 10 updates have required re-installing drivers, particularly Roland ones, as well as re-authorizing hard drives or computers, especially XLN. I got the V-Studio to work just fine but had to modify the driver. I followed instructions in the hardware forum, which worked.
 
If you have a V-100 driver that is known to work with Windows 10, go to device manager, say you want to update the driver, and point to the file to re-install it. That's what worked for me with the V-Studio.
 
I don't know if Roland would care, but read your EULAs...it's usually expressly forbidden to modify or reverse engineer a company's software. They probably don't care that I made some changes to the driver; I don't know if it gets problematic if an unaffiliated company does it on an official basis. But when lawyers are involved, I always recommend erring on the side of caution.

Thanks Mr. Anderton Roland has supplied new drivers for the vstudio 100 for windows 10 and I have reinstalled after  running into these problems after the cakewalk updates , it seems it is up to cake to find a solution. thanks for the advice

But did you reinstall the way I recommended? I'm not saying it's not a SONAR problem, just saying what worked with the V-Studio. That was the only approach that worked.

no sir it looks like alot to afraid might mess something up. LOL i will wait for cake to fix it 

Ok  great news half of my issues has been solved the arm control is back. For anyone whom may run in to this issue check  under keyboard shortcuts ("type of keys" make sure the enabled box is not checked) Thank God. still on hold for the marker, but cake says fix should be in January.