Hi Edouard,Edouard Arturia wrote: ↑Mon Jan 17, 2022 11:04 am I'm Edouard, V Collection & Pigments product manager .
A bit surprised by the poll, not much room for love, but I guess it's fine like this.
At least I can expect to find some relevant criticism maybe? So I jumped in to check if some useful information could be gathered to continue improving our instruments and utilities.
Thanks to those who wrote constructive remarks, I'm taking good notes.
I agree with the general sentiment that the Arturia VST's on the whole are very bloated. I'll be specific about why in the hopes that it will help drive some improvement.
You've got way too many images for most VSTi's. Why does every single key on a keyboard need it's own image? Then multiple that across all the different sizes! It can't be efficient to have to load all those resources. And for what gain? Why not just create a 200% set of graphics and scale those down? It would at least save some hard drive space. System drives are frequently SSD's and not as big as a sample library drive. I appreciated that the SQ-80 had a synth tab that ditched the Skeuomorphic GUI, but that was really the only page necessary IMO. Or if you're going to keep the fancy graphics to attract new users, at least be more efficient about the HD space requirements and figure out a better way to do that.
Let's also talk about plugin scanning. After an Arturia round of updates, I have to let Reaper start up, scan the plugins, then walk away because it will take so long. Reaper will inevitably warn me that Analog Lab V got hung up and ask me if I want to terminate, but I have to just let it wait, it will eventually work. Happens with a few others. What is going on with that? Why does this only happen with Arturia plugins?
On a similar note, Arturia plugins also have WAY TOO MANY VST automation parameters. You ever open the automation list? It's insane! Why does a Dimension D chorus plugin require over 2,100 VST automation parameters? All the Arturia FX plugins have about this many, no matter how small the plugin. We don't need literally thousands of MPE and MIDI helper parameters exposed to the DAW. That's crazy. Arturia is the only developer that does this.
And the result of all of this, is that when I load up an Arturia plugin, I'm frequently waiting 20 seconds for the GUI to open and the plugin to be operational. As an end-user, it creates a Pavlovian response: "don't do load those plugins." So I'll frequently start with NI's Phasis over the Arturia Bi-Phase because well, even though the latter may sound better, if I need to work quick, I avoid Arturia plugins because they're slow.
I really hope Arturia begins to operate more lean and focuses on performance by creating more efficient plugins. And I don't mean CPU use! If increasing the CPU use made things sound better, I'd be all for it. When I mean efficient I mean fast to open, fast to scan, no unnecessary automation parameters, no wasted hard drive space with graphic resources I'll never use, etc.