еще одно письмо по поводу vcc2
Hi folks. So the response to the Sneak "Peak" (did anyone get the pun?) at VCC 2.0 was overwhelmingly positive and it's brought a great sense of motivation to us as we prepare it for beta (and NAMM).
So there have been a few questions about VCC 2.0 that I want to address. Let's start.
Q: Will the VCC 2.0 be back compatible with old projects?
A: No, it will not. As I've said in many emails, the original VCC code was just pretty hopeless. It was written with complexities that made it hard to fix bugs, hard to add new consoles, and hard on the CPU. There was absolutely nothing we could do to save the backwards compatibility if you wanted new consoles (with more coming in the future), better features, cleaner, code, and less CPU. But fear not, your current VCC 1.x will not be affected. If you have old projects with those plugins in them, they will work as they do now.
Q: Will VCC 2.0 modules be standalone or modules for VMR?
A: Let me first start this by saying that the new VCC 2.0 workflow will be the EXACT SAME WORKFLOW as you have now if you choose it to be. But yes, the modules will work in the FREE Virtual Mix Rack. Now don't jump to conclusions, let me explain.
If you load VCC 2.0 in VMR and save it as default, you essentially have the SAME workflow as now. You go into your plugin list, you choose VMR, it loads instantly with VCC 2.0 on your screen, and you proceed in EXACTLY THE SAME WAY as you do now. No extra steps or problems, no monsters jumping out of the screen, all is the same, and you'll have some sweet analog console tone again! If your plan is to just use VCC (since you are under absolutely positively NO obligation to get any other VMR modules), then just pretend that it is now listed as 'VMR' in your plugin menu. That's it.
Now, if you DO have VMR modules, this is gonna be a huge advantage for you. For me, I have several preset "dream channels" saved that I can easily pull up on tracks. For instance, the new Brit 4k E to the FG-S EQ to the FG-401 Compressor followed by some polish from Revival Sonic Enhancer is my go to channel for close drum mics. Heavy guitars are now US-A Discrete to FG-N EQ to FG-S EQ to FG-401. The cool thing about having VCC on your monitor with the entire signal chain is that you can really adjust its settings and gain staging in a much more intuitive way with the rest of your channel processing. You can experiment with pushing the output harder into the EQ to get more input saturation from the transformer, etc.
But again, you don't want to get VMR modules, no problem. Save VCC as your default module so it always pops up when initiated, and you're all good.
So why did we do this? Do we secretly want to get you to buy new VMR modules? Well, of course we want you get VMR modules, because they're awesome and we love them. But no that's not the reason we did this. We made the VCC modules for the VMR platform because if we didn't, you WOULD NOT be using VCC 2.0 for another few months. I'll explain.
Pretend you just built a house. The house is all done, but it's empty. Let's imagine that this empty house is the VMR framework. So now let's imagine that the furniture that goes in the house is DSP code, like VCC modules. To make VCC 2.0 for VMR, we simply put the furniture in the house and spend a bit of time placing it just right. But to make VCC 2.0 standalone… we have to build another entire house! Yes we'd have to create another framework, put all our new framework code into it, put all our graphic and CPU optimization into it, put our grouping network into it, and then test it for a month or two to ensure it all works well, then get the VCC code in, test more, etc. It would have been a major delay. Whereas the VMR framework has already gone through this vigorous testing for almost a year and has proven to be extremely stable.
So I really hope that this explains the VCC 2.0 situation, and you find comfort in knowing that if you want nearly the exact same workflow as you have now, you can have it. And I hope you understand that these decisions were made so that we can provide this update to you faster, which was very important to us.
I look forward to seeing many of you at NAMM booth 6921 next week, and I once again thank for your support, patience, and understanding. I am grateful to have you in the Slate Digital family and promise to keep delivering great tools to help you make music.
Cheers,
Steven Slate