Re: Marc Lopez of Yamaha Commercial Audio Q&A
Hi Marc,
thank you for doing this here. Here is my question.
Some years ago Yamaha acquired Steinberg and I thought, this would lead to a new dimension of VST-Plugin/ASIO insert integration into the new Yamaha live desks. But nothing really happened.
I'm still puzzled, that Yamaha does not make use of that untapped potential. By now this claim is taken by Waves and all the "waves solutions" are "Waves only":-(
So a lot of nice plugins, that would be very useful in a live enviroment (f.e. Drumagog, Trigger, FabFilter and so on) can't be used in Waves Multirack and such. I thought, Yamaha & Steinberg could pull off a new standard of VST Plugin integration, that would allow the user to use any VST plug (even Wave) they like. Why is that?
Hi Christian,
I'm really glad the moderators asked me to join for this Q&A.
Regarding your question, I have a few different answers, and hopefully one of them addresses your question:
Many options for VST Host software exist (Cubase and Nuendo to name a few that I would recommend
~
~:smile
, so why not use one to get external inserts? Latency through the interface and software could be optimized to be very low (depending on the interface and computer of course). Connection would be done using the corresponding MY-card flavor. This is not too far from the Waves Soundgrid concept. Yes, in this case we aren't providing a finished plug-and-play solution, and it is up to the user/sound company to assemble and test a viable solution, but it is something that is reasonably attainable.
If you are asking about implanting VST
inside the console, we have consciously chosen not to do so. VST is an open standard, and as an open platform, anyone can create a VST plugin. You can find many types of VST plugins on the web (including student/hobbiest experiments and non-commercial). There is no governing body that verifies the stability or implementation of VST plugins, and as a result, some VST plugins can produce errors resulting in noise or even crashing the VST engine, or just have unsuitable latency for live use. Reliability and stability are fundamental principles for Yamaha digital consoles, and so far we have opted to suggest the external VST route.
if you are suggesting that we create a different standard or VST "offshoot" for live plugins, you'd have to consider the business model for plugins. In order for a software company to produce yet another version of their plugin technology, they would expect to sell a relatively high volume of units to recoup at least their engineering efforts. Digital consoles do not sell in the same volumes as DAW/Performance software, so we believe this would not be an attractive business proposal for plugin designers. VST is a high-volume format with a multitude of host software platforms.