Neyrinck have announced that there is an update of their V-Control Pro software which brings support for Avid’s legacy Pro Control and Control 24 control surfaces to more DAWs.
Back in July 2018 we were able to bring you the news that Neyrinck V-Control Pro software brought support back for the Avid Pro Control and Control 24 control surfaces to Pro Tools 12 and later.
With the release of V-Control Pro 2.3 you can now use Avid’s Pro Control and Control 24 control surfaces to control Apple’s Logic Pro X, as well as Steinberg’s Cubase and Nuendo. Paul describes it “making another impossible thing possible”.
Paul had hoped to get this done sooner but he found it was a lot more difficult than he anticipated. He had to “re-architect V-Control Pro so it could best use these wonderful surfaces for incredible control”.
It’s not clear from Neyrinck’s announcement what protocol they are using to communicate with Logic Pro X, Cubase and Nuendo, but we know that when Neyrinck released the version of V-Control Pro that brought support for Pro Control and Control 24 surfaces to current versions of Pro Tools, he achieved it using HUI because Pro Tools only supports the HUI protocol for third-party surfaces, so we asked Paul what protocol he used for Logic Pro, Cubase and Nuendo…
We implemented custom control surface plugins in Logic and the Steinberg apps in order to get very extensive control.
He went on to tell us that this has given much better control than what they can achieve with Pro Tools because they are restricted to using HUI, but that these custom control surface plugins were why it took so much longer than expected to get support done for Logic Pro X, Cubase and Nuendo.
The update is free for all V-Control Pro 2 licenses owners, with either perpetual or annual licenses.
How To Buy V-Control Pro From Neyrinck
If aren’t already a V-Control Pro user then there are 2 ways you can buy the V-Control Pro Bundle by getting a perpetual license or an annual license.
V-Control Pro Bundle Annual License
$49.99 per year
V-Control Pro Bundle Perpetual License
Sale price $199, regular price $249
What Is In The V-Control Pro Bundle
V-Control Pro Software – Connects your favorite DAWs and Video edit applications to controller apps on mobile tablets, smartphones, browsers, and MIDI hardware controllers
V-Console App – 8 or 16 fader controller with multiple skins for most DAW/Video Editors, and V-Window for controlling plug-ins
V-Panner App – Surround Panning and Dolby Atmos plug-in control screens
V-PlugIn App – Directly control the Neyrinck Spill plug-in for Pro Tools on iPhones and iPads
Enables Digidesign Control 24 and Digidesign Pro Control to work with Pro Tools 11, Pro Tools 12 and Pro Tools 2018
All features enabled with the perpetual or annual licenses
Computer or iLok activation
Digidesign Control|24 and ProControl control Pro Tools (11, 12, 2018, 2019), Logic Pro X, Cubase, Nuendo (Mac OS 10.10 / Windows 7 and later supported)
Works on smartphones, tablets and laptops
Future Plans For V-Control Could Include Being Able To Control Interfaces
Now that they have added in the other DAWs that they planned for V-Control Pro, Neyrinck are now turning their attention to investigating the possibility for V-Control Pro to be able to remote control I/O interfaces. Paul explains…
“Many nice I/O interfaces force you to use a software panel to adjust input gains and to adjust the internal monitor mix. Well, what if you could use your control surface instead? Or what if you could adjust the input channel settings from the Pro Tools Mix Window? I would be most grateful if you could take a small survey and help us get some perspective”.
The questions in the survey are…
Do you currently remotely control your I/O interface with a control surface or within a DAW?
Would you like to control your I/O interface with a control surface?
Pro Tools lets you remotely control and save the Avid PRE input settings (gain, pad, highpass, mic/line) in the Mix Window. Would you like to do the same with a 3rd party I/O interface?
Can you please help me understand why and how you need better control of your I/O interface? Any and all details are helpful.