Hate to be a spoilsport, but an issue remains in 8.3. When setting up the control surface, you also have to pick (other than in X1) a controller/surface. VS100 shows up in the list, but when I pick it, it's shown in parentheses. In and out can be set to Control VS-100, but after closing and reopening the setup screen, they have disappeared again. Also, no reaction from the hardware slider and the transport buttons still produce midi sounds.
Might this have something to do with the updated firmware of the VS 100? It´s not a huge issue, I´m happy X1 works properly now, but in some cases it´s useful to refer back to 8.3 with older files.

nice catch coda. i had to look closely at what you described. it very closely resembled what i suggested, but i noticed your instructions were in 'midi-devices' and mine were in 'midi-control surfaces.' thanks. glad you're x1 is working bartveld.

double post.

bartveld,

I am not 100% sure of how 8.3 works. I do have 8.5.3 so I will post those instructions and you can see if they will translate to 8.3.

1: Go to Options > Midi Devices 
2: Make sure "CONTROL VS-100" is checked for both INPUT and OUTPUT
3: Now go to Options > Controllers/Surfaces
4: For the VS-100, your IN should be set to "CONTROL VS-100" and your out must be set to "CONTROL VS-100".

If that doesn't do it, you may need to call Cake Tech support.

Glad to hear it is working in X1 though! Good luck with 8.3

Hi Everyone,

If the VS-100 Control Surface Plug-in (CSP) shows up in parenthesis in the Control Surface menu, like this: (VS-100 - 1 )

...and the MIDI ports will not stay assigned when exiting the menu, then you are most likely using the 32-bit version of the VS-100 CSP with a 64-bit version of SONAR (or vice versa).

Try running the stand-alone installer for the VS-100 Control Surface Plug-in twice, once as a 32-bit installation and then again as a 64-bit installation.

You can find this installer on our site at http://www.cakewalk.com/S...reader.aspx/2007013039

Setup instructions for configuring the VS-100 and SONAR are found starting on page 21 of the VS-100 Getting Started Guide here: http://www.cakewalk.com/S...00_Getting_Started.pdf

Best regards,

Thanks for the advice Ryan. I'm on full 32 bit hear so I've never seen this issue. Great to know for future reference.

thanks ryan. full x64, havent seen it either.

Gentlemen, all problems have been fully resolved, both in 8.3 and X1. I am grateful for your help and commitment and I am impressed with the great work done by the members of this forum. Thank you.

I'm happy that this problem was solved for folks in this thread from five years ago. But the solutions described here did not solve the very similar problem I was having setting up the Nektar Impact LX25 control surface with Cakewalk SONAR X3 running under Windows 10. In my case, the control surface was showing up in parentheses and the MIDI ports were not staying assigned as described by Rynan Munnis in this thread. There is only one installer for the Impact LX25 that handles both 32-bit and 64-bit installations, so that was not the problem. What was particularly vexing was that I could set up the control surface with my laptop but not my desktop, even though they were running the same software. After a couple of weeks of intensive back-and-forth with Nektar tech support, we discovered the problem, and I thought I should share the solution in case someone else encounters it.
 
One requirement for the Nektar Impact to work with Cakewalk SONAR is an appropriate version of Microsoft Visual Studio redistributable. What happened in my case was that the Nektar installation program included a version of VS that used to work, but, unknown to Nektar, Cakewalk SONAR 3 upped their requirement to a later version. Now, VS is often installed with all sorts of other software, and because I use my laptop for many things, it had the required version of VS from the installation of some other program. But I had been purposely keeping programs off of my desktop computer except for music recording and production, so it did not have the required version of VS. The problem was immediately solved by installing the latest version of VS. Naturally, Nektar said that they would revise their installer to include the needed version of VS. But if you have the symptoms described here, this might be the issue.