2014/02/14 03:30:15
reza
Thanks Ryan
Is there any news?
2014/02/17 01:49:34
reza
Ryan , is there any news? did it happend for you too? please inform us if you got any news. i am still trying to find a way to solve the issue, but no success yet.
2014/02/20 20:40:52
reza
Gabriel, do have any news ? I think no one wants to fix this issue.....
2014/02/20 22:04:44
Ryan Munnis [Cakewalk]
Hi Reza,
 
Unfortunately I'm a bit at the mercy of other people at the moment. Here's what I found in my testing:
  • Not specific to SONAR X3 (it happens with SONAR X2a)
  • Not specific to the VS-700 Version 2.0.2 update (it happens with version 2.0.1)
  • Not specific to Windows 8.1 (happens on 8.0 also)
  • Does not happen in other hosts (tested Logic Pro 9 on OS X)
  • Cannot replicate with other control surfaces such as Mackie Control
Ultimately my su****ion is that this might be specific to the VS-700 Control Surface Plug-in, however I can't confirm since I'm not sure what message the VS-700C itself needs to listen to. The only people who can really confirm this for me are Roland Japan who would have access to the MIDI implementation for the VS-700C itself. 
 
What I ultimately discovered is that the only difference on a successful launch of SONAR (where the master fader works) and an unsuccessful launch (where the fader does not work), is that some events are sent in a different order sequentially. So all messages are still sent, just at a different time occasionally.
 
In any case, I've passed along this information to one of our developers and product managers for the time being. I still would be making an assumption if I were to say it was software or hardware related. I just don't know yet. In any case, I do care about the issue but unfortunately I cannot promise a quick turn-around for this hardware since it has been discontinued by Roland and they are no longer offering direct support for it. 
 
In the meantime, the best suggestion I can make is what I made a few posts up, which is that if it happens I would suggest CTRL + Clicking on the Reset MIDI and Audio button on the Transport Module in the Control Bar. This is very quick to do and will easily resolve the issue.
2014/02/22 04:22:44
reza
Thanks Ryan,
I found out If I add another vs700c in control surface (in sonar) and keep them both, my master fader on vs700c will work with no problem, and it just be a bit lazy because it probably receive the command 2 times. but as I said I tried it and worked.
let me know please if it is helpful to figure the problem out.
regards
2014/03/14 04:50:51
reza
Ryan do you know if there is any bug fixed regards the master fader in new update x3e?
thanks
2014/03/14 05:02:12
Splat
I don't think X3E will fix it but it's out very soon so you can try it out shortly. There will be release notes with it as well.
2014/03/19 01:50:42
reza
you are right Alex it didn't fix the issue and i think they completely forgot this issue and no one wouldn't  take care it. I hope some one from roland or cakewalk take the responsibility and fix it.
 
2014/03/19 02:39:06
Splat
It really is a Roland issue I suspect and Cake have had their hands full with X3E I suspect. Maybe Ryan could give you an update now we know it won't work with X3E.
2014/03/19 11:12:35
Ryan Munnis [Cakewalk]
Unfortunately it didn't make it into X3e.
 
It's not that we forgot about the issue, it just wasn't a top priority. The fix list in SONAR X3e is significant and the areas we focused on were very important areas of the program that have to do with core functionality. With that being the case, some lower priority issues were put on the back-burner to focus on higher priority ones.
 
I'll be honest in that there are a few reasons for this issue being a lower priority:
  1. There is an extremely simple way to correct this. CTRL + Click on the Reset MIDI and Audio button on the Transport Module in the Control Bar. It takes a only a second and will get you back up and running if this happens.
  2. The product is discontinued by Roland. With limited resources it's hard to justify focusing on discontinued products over core functionality (such as the fix list in X3e) and future products. A lot of time and careful focus was put into the areas we updated with X3e.
  3. Considering point #2, we do still care about the VS-700 and have open-sourced our Control Surface Plug-in SDK. One of the included projects in the SDK being the VS-700. More info from Noel here: http://forum.cakewalk.com/FindPost/2993349 . As indicated by Noel's post, it seems like we're still maintaining a level of involvement but wanted to be able to put into people's hands the ability to work on projects such as this. This has been requested by the community for a while and was an effort that we really wanted to help bring to our customers so that development for the VS-700 can still live on and not end at where Cakewalk's resources allow.
I hope this helps to explain why it didn't make it into X3e. Sorry guys.
© 2024 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account