Unable to set up controller surface in Sonar 8 and X1

Somehow I can't get the controller surface to work in either version.
In 8.3 the WAI-band on the left of the track isn't visible, and oddly enough pushing certain buttons on the righthand side of the VS-100 spawns midi-tones. Tried all sorts of permutations in the setup windows under Options|Controller surface but no go.
In X1 I can't find the setup for Controller surface. There is a WIA band, but the fader doesn't follow my choice of track and its volume setting. Transport buttons do work, but don't light up.
VS-100 updated to 1.50 firmware.

Now I had all this working fine with Sonar 8.3 under XP, but I can't find the right setup in either 8.3 of X1 under Windows 7 (64bits). I realize this maybe a rather vague post as far as diagnostics are concerned, but maybe someone can point me in the right direction.

hello bartveld and mr p.,
in x1, did you:
edit>preferences>midi - control surfaces>in port and out port dropdowns - select "control (vs-100)">apply

wai settings are there as well.

also, i'm not sure if this common to all, but on my system, if i launch x1 without having first turned on the vstudio 100, the vstudio get knocked off-line and i must do what's described above in order to set it up again (annoying).

hope that helps.

I am a newbie with all this, but had my share of setup probs with VS-100 and A-300PRO.
I got all things sorted...but don't ask specifics...all I understand that after starting X1 with admin mode
everything magically went into the right places!

Jyri

if i were you i'd take this one to ryan munnis the cake tech. he'll get you going for sure or at least figure out why it's not working.

bartveld


Thanks for all the input. Yes, in X1 WAI is there, but again: the hardware slider does influence the software, but not vice versa (i.e. changing volume in software doesn't make the hardware slider move). This must be some setting, but which? And also, the transport buttons on the VS-100 don't light up at all (but they do function).

 
 
When you setup the VS-100 as a control surface, did you assign the "output" back to the VS? It sounds to me like the VS can feed to Sonar, but not receive from it.
 
1: Press P to open the preferences
2: Go to MIDI > Devices
3: Make sure "CONTROL VS-100" is checked for both INPUT and OUTPUT
4: Now go to MIDI > Control Surfaces
5: 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 is how you have it set and it still doesn't work - you will have to call Cake tech support.

And the question remains how to make VS-100 work on 8.3 (i have both versions on my system). 

It should work the same as in X1. You can loosely use the steps I mention above, but of course, the Preferences windows are very different in Sonar 8 than they are in X1. Just find all the appropriate windows for settings, and you should be able to set it up.
 
I don't use Sonar 8.3 myself so I am not 100% sure the VS works with it. But I do use 8.5.3, and it definitely works there.
 
Good luck!

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.

double post.

thanks ryan. full x64, havent seen it either.

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.