VS 700C communication problem

I have a problem with my v700Console that is herassing me for quite a while now...
 
My set up is : Vs700 console + Rack + sonar x2 producers edition, i have intel core i5 2500k cpu running @3.70Ghz with 16Gb Ram memeory, its a 64 bit system with windows 10 home.
 
Before i went to windows 10 the system worked very good for years, but this problem allready excisted since windows 7, it came out of the blue without changing anything, everything still works fine, except, my faders wont transfer their input to the software, they follow everything that happens on screen, but when i want to make adjustments to the mix, nothing happens.
Called for hours and hours with our Roland representitive here in Belgium who has a lot of knowledge and patience, trying to figure out what was wrong, installed all the software over and over again, went thru lists in a method of trial and error to find the problem, they even gave me a second VS700 set because they tought my console was broken, but nothing helps... They said they contacted the head office, but that didn't bring any news either...
 
For one reason or another i can't get the sonar soft to pick up the faders signal...
 
We installed mid ox, the signal of the faders is coming into the pc but the software doesn't catch it...
 
this is a very big problem that i come around now by moving the faders on screen with my mouse but this is taking me more tiime then it should...
 
anybody ever experienced this ? or anybody that nows a solution, i would be glad to send the helper a very good bottle of champagne for the right solution ;)

Hi Bertl,
 
the problem allready occured in win 7, i'm just looking for answers for so long...  ;)
 
A) checked that, everything is as it should be.
 
B) on my system is only the vs700 system with an edirol keyboard(usb) and the adobe creative suite, but nothing else soft or hardware. I use the system to produce radio tv and web commercials.
 
i have nothing midi connected to the system, just the vs700 and the edirol keyboard thru usb, so no midi loop.
 
In the beginning this problem popped up,  only transport functions worked all the other buttons did nothing... after several reinstalls with roland on the phone, i managed to get almost everything working again except for the faders...
 
Now last night i was talking to a friend of mine that worked a week on my system when i was sick, and out of the blue he told me that when he worked on it he tried to get the control surface to work with audition, in wich he partially succeeded... he followed a thread on a forum, but i can't find it and he doesn't remember what he actually changed, the only thing he did remember was that he had to assign every knob to a shortcode in adobe audition... at last after several months i know the cause of this... but i want to find a solution...
 
i was always thinking that doing a a complete clean reinstall would solve these issues, but it didn't
 
where do i start solving this issue ?
 
 
 
 

I can propose to check that Sonar Control Surface DLL is really receiving something from the console, then check this "something" is what original Roland DLL expects. That can localize the origin of your problem.
 
Since Roland DLL does not show what (and either) it receives MIDI messages, you can do the following:
1) install my DLL (see link in my signature)
2) add it to the control surfaces list in Sonar, attach it to the same Input as you use for Roland DLL (but do not remove original DLL from the list!)
3) open Property page for AZ Controller (From Utilities menu)
4) move some fader, look at "Last MIDI event" section.
5) Do you see something is changing there? If yes:
5.a) just touch the fader (without moving it), write down the message you see (if there is a change)
5.b) move it, write the message
5.c) release fader, write the message (if there is a change)
 
Write here your observation from (5).
 
Note: after the test, please remove AZ Controller from the Control Surfaces list to avoid "side effects" during your normal work.

cladavid
@azslow 3: i used midi ox before to do that, but will try your suggestion tomorrow when i am in the studio. Thx !

Important is not the tool to use but either Touch/Move detection is correct within VS hardware/firmware.