Anderton

John T
As far as I can tell so far (two long working days on Platinum), it's exactly the same as it was in X3. Certainly not restricted to Mackie Mode, so I think you have a setup issue.
 
I'd like support to be better. X1 was worse than 8.5, X2 onwards eventually better than X1, but it's never actually been as good as it was in 8.5 again. Which is fairly shocking I think. But now Roland are out of the picture, and it's been quietly discontinued, I think it's likely all over. I'm just glad they're maintaining compatibility at all at this point.

A fair summary, to be sure. I'm holding on to the Console because the Mackie implementation is solid. I use the 700C with Vegas, Reason, and other programs. However I did replace the audio interface element. It was too unstable compared to other audio interfaces.

Same for me here ... but can we expect a new solution from tascam cakewalk ?

Zo
can we expect a new solution from tascam cakewalk ?

I don't know. Personally, though, I think the touch support takes away some of the incentive for a hardware solution.

I don't understand why they would not keep up support for such an awesome device of their own making. what are some of the other options that are comparable usb surfaces?

keneds
I don't understand why they would not keep up support for such an awesome device of their own making. what are some of the other options that are comparable usb surfaces?

Well again, it's a Roland product but yes, there really aren't a lot of other options, SSL Nucleus is quite expensive. But aside from the original Mackie control and dedicated hardware surfaces for Ableton Live and DJ programs, control surfaces don't really do that well in the marketplace. That tends to scare off manufacturers, because the investment to create hardware gear is substantial.

What is everyone using? Just the mouse? (Been there)

I can confirm: the same behavior on my system. Just like Craig I only use the console so I have the latest specific VS700C driver from the Roland site installed.

You mean you're getting the master fader bug I've described?
 
In any case, I've discovered today that it's somehow intermittent. Has been working fine today.

This is a very important thread to me.  I depend on my VS-700 hardware (I/O and console) and need it to work; otherwise, I would have to stay on my current Sonar version until purchasing a new console.  (I have an unused MOTU 896 mk3 in the rack under the VS-700R I/O, so I am in good shape for an interface.)  The console is a different story and I don't want to mix on the screen.  I really like two-way fader automation—that is, the ability to automate with the physical faders and to see them move in response to automation.  I am also very used to many shortcut buttons on the console (views, save, undo,etc.) and to the rotary encoders which I mainly use for pan.  Note that the "flip" mode on the console is very handy: temporarily make the faders panpots and vice-versa.

I can confirm that it is indeed intermittent, I just created a new project and then opened a project the master fader did not behave well previously, and: no problem. It would be "nice" though if there was some way to replicate it, i.e. to find out what exactly triggers this behavior. 

Yeah, I'm going to keep an eye on this one, I think. I expect it's something fairly trivial. It's even working for me today on projects it didn't work on yesterday.