John T


Following on from that: now I've got the PC modules mapped how I like them, I'm currently finding the v700 / x1 combination mind blowingly brilliant. I wish v700 updates didn't lag behind general updates the way they have done over the last year, but in fairness, when they've caught up, they've been very impressive.

Yeah you're right I'm enjoying the whole system A LOT with X1.


I'd like to say that all this is due to Cakewalk devotion to keep offering update. Not sure about Roland help since they NEVER come around this forum, but a real big THANKS to Cakewalk for doing the best they can to continue to give us the best possible experience.


Not shure I'll stay with Roland forever but Cakewalk just cut the quality/support ratio.  

Great information, thanks to all.  Can't wait to get X1 now!

Just curious.  Once you remap using ACT does it fix the problem with values being displayed on the VS-700 display versus the values in the ProChannel display.  For example (from post #3 in this thread)...

- PC4K S-Type Channel Compressor:  Threshold goes from 0 to -30dB on the PC display, and 0dB to 1.0dB on the VS-700C display.  The Ratio goes from 1.00:1 to Inf:1 on the PC display, and from.0:1 to 1.0:1 on the VS-700C.

I know I can answer this myself by just trying it myself but I'm out of the studio for the week and thought maybe someone who has already tried remapping would know the answer.  If it doesn't change the mapping of the values I'm hoping that Seth or someone can explain how to get the displays to sync up.

Thanks,
Don

Regrettably no. This seems to be something that's built in (or not built in) to the individual modules. For example, the PC4k bus compressor displays the correct values on the v700, but the PC2A Leveller doesn't.

Thanks John.  That's what I suspected.

I sincerely appreciate Seth participating in the thread and explaining how to use ACT to remap the VS-700 controls to something more usable.  Unfortunately I really think that it's pretty obvious that the VS-700 integration with X1d wasn't really ready for prime time.  I can easily understand that they had limited resources and had to apply those resources to the areas of the product where they were most needed.  Clearly VS-700 users make up a very small segment of the total X1 user base and the decision was not too difficult .  We are all (VS=700 users and non-users) benefiting from the release of X1d.

Hopefully Cakewalk will continue to work on improving the integration of the VS-700 and X1.  Both are great products.  If the X1 integration isn't any better with the VS-700 than X1 with any one of a number of cheaper controller alternatives I would think it would hurt sales of the VS-700.  It no longer makes the VS-700 the "ideal" control surface for Sonar.  It would still continue to be a VERY good solution for X1 - but no better regarding level of integration than a generic control surface using ACT.

Right now we are in a much better situation than we would be if we didn't have the strength of ACT to compensate for a lot of the VS-700 integration problems.  Unfortunately it  isn't able to overcome the display problems.  A statement from Seth (or someone else from Cakewalk) acknowledging the problems and providing a vague statement that the problems will be worked on over time would be very comforting.  It wouldn't need to provide specifics (dates, specific bugs being fixed, etc).

John (and anyone else) what are your feelings about what we should do as VS-700 users?  Should we report all of the problems individually?  I really think the Cakewalk development team knows the problems exist.  They are certainly easy enough to find.  So in that respect it is kind of a waste of everyone's time to open problem reports and expect Cakewalk engineers to handle each individual problem until they have really had an opportunity to complete the development and testing of the VS-700 integration.  That obviously hasn't happened yet.  I have worked in engineering development for a couple of decades and to take engineers' time to process the problem reports prior to some level of readiness rather than letting them finish their development/test activities isn't always the best use of their time.  Clearly at some point it is a very worthwhile and necessary process.  I don't think the VS-700 integration is currently ready for Beta (or even Alpha) testing.

Seth - what would you recommend?  Report each and every VS-700 issue - or wait until there is a patch or release that attempts to "complete" the VS-700 integration.

Thanks!
Don

I've been reporting issues with it, yeah. I think "the squeaky wheel gets the grease", so the more reports the better, probably. I am a little disappointed with v700 integration in two ways. Firstly, the way it lags behind updates to the main program is a bit frustrating (eg: we got modular PC in expanded, but the V700 didn't handle it til X1d). And secondly the integration feels a bit like box ticking in places, like with this incorrectly named parameters thing. The promise of tight integration with Sonar was true of 8.5, but for my money, it's never quite caught up in X1.

Thank you very much Seth. I've tried your instructions on Sonar X3e, and it worked like a charm, however, when I try to map for example the 4 options in Pro Channel EQ which are: Hybrid, Pure, E-type and G-type to 4 buttons, it won't do that. It lets me go through the process, then I have the option to click ok. But they don't work as I mapped them. Any ideas? Thanks in advance!