Shane Wiswell

Just sharing... I am using the VS-700C with two (2) VS-700Rs and two (2) Echo Audio Layla's hooked in through the light pipe using Windows 10 (latest build). 99.?% of the700C control surface and the 700R's features/functionality are working flawlessly (for the most part) for me. Some of this issues I experience have been: I sometimes receive .cwp projects that will crash my main system and I know it has something to do with audio driver and the 700R with the error that is referenced. I have a mobile rig that uses the Roland VS-100 which will open these projects without crashing (same Win ver, CakeWalk ver, Audio driver ver.). Seems to be something about where the .cwp was sourced and the VS-700R - perhaps? I usually will have the client resend it in a ProTools session and work it on my ProTools rig. 50% of the time I open a project (new or saved) and the master fader strip on the 700C console doesn't engage. To remedy this I close and relaunch Cakewalk (sometimes 3 or 4 times) and this gets the master fader to engage with the Cakewalk software. Checking this has become part of my work flow before starting any session - A minor annoyance. There is an issue from the CakeWalk DAW interface engaging the Word Clock when slaving one of the 700Rs to the other which doesn't work. You have to actually do this from the external Roland VS-700 IO Editor application. This is probably a non-issue with most people, you have to have 2 of the 700Rs. I have saved profiles for my 700Rs on the IO Editor and launching this app and calling up those profiles prior to starting CakeWalk is just part of the workflow I have discovered/created. A minor annoyance. The Fantom Synth editing can be a bit buggy, but for me I just use presets so its never been an issue for my workflow. Each of my 700Rs has as ARX card (Drums & Horns) and works without issues - just load them (Fantom or ARX) up as a virtual instrument. What has changed over time with the DAW versions is the mappings of the VS-700C Channel Strip Control knobs. What I did was create a custom template and using ACT, mapped the knobs to the various controls i.e. map the physical knobs to the software knobs on the ProChannel EQ section. This resolves that issue. JohnT - I tried to crash mine with what you wrote 'going back and forth between "EQ" and "Send" on the channel strip control panel' but I can't get it to crash on my system. Everything else works as advertised! All the Inputs, all the outputs, MIDI, surround, SPDIF, T-Bar, all the buttons, all the knobs do exactly what they are supposed to do. I use close to 100% of the capabilities this system provides and have been very happy with it. I hope y'all find some of this interesting/helpful. None of these items have been a deal breaker for me to stop using this rig.