Arturia FX Collection- SonicLAB Review

[@NightShift-kx9pb]

Nice run-through; much more valuable than the obviously-sponsored stuff on some other channels. Thanks for making and posting this.

[@danwhite7629]

The Intensity reverb is actually really fun to dive into and get creative. Once you start tweaking it;s quite intuitive to make interesting effects. Defo not suited to more standard reverb sounds but we all have plugins that can do those.

[@rlins8688]

Thanks. Great sound ,simple to use and not very expensive for this quality!!! Made in France😎👍.

[@Pulse2AM]

I got the plate free as a Studio 1 user, it's awesome I must say.

[@PendelSteven]

18:04 To be fair, it's called _Rev INTENSITY Not _Rev SUBTILITY

[@brunovalente2077]

The Intensity reverb has a piece of tape under the feedback button written "use it wisely", really cool GUI this plugins

[@ModernDevotion]

“Why is the reverb called INTENSITY lacking in tame presets??” 😂

[@PendelSteven]

I hope you like my comment :)

[@annother3350]

Nick? You've changed?!

[@seanchristophersynthesizer6999]

I do not recall him having that much hair. LOL

[@martinneal5240]

Thanks for this. Does the FX pack open as a suite with drag and drop in other Daws as well ...it obviously does in yours. I thought they would have opened individually from the Daw's Vst list.

[@st0rmchild]

SPRING-636 is modeled after the Grampian 636.

[@tomkarlson86]

to much talking. I thought i watch a demo and not a guy talking about how beautiful the GUI's are ... etc.

[@TwstedTV]

Every time he says the word "really" everyone take a vodka shot......lol

[@MrMikomi]

Nearly 7 minutes until we hear something .... please, less talking more doing in future reviews.

[@jacoboshaughnessy8316]

Arturia needs to sort their sh*t out with compatibility and software instrument and Logic pro X . Massive crashes to the extent that i have had to remove their software from all of my current projects. All care no responsibility from this company in terms of customer service. Will keep texting until they fix it :)

[@iaamusic1121]

Jacob O'Shaughnessy well, I have v collection 7 and it works flawlessly with logic 10.5.1.

[@Screaming-Trees]

@@iaamusic1121 Yeah but it's 2020 and these problems go back to 2008 or before even actually. Reports of crashes etc etc. I myself got the shits with them and decided to ban them until they learn how to write quality code that doesn't crash intermittently. It is well acknowledged that they have quality control issues. If you look at the release notes for the latest updates they've published to the V Collection it says in no uncertain terms that the updates include fixes for Logic 10.5 crashes. They wouldn't have done that if the bug reports weren't reproducible. There is absolutely no excuse for plugins crashing in 2020. Especially not on the Apple platform consider the tightly controlled hardware pool provides a very predictable environments to work in. And that goes doubly so for a company that's been around since 2003 or so. Last year I tried to demo their new stuff. They're basically all over the forums shouting form the rooftops that their new plugins are a revolution in both sound and quality. I installed the DX7 and the CZ and launched Pro Tools only to be greeted with a startup dialog that says neither the DX7 nor CZ plugins can run in Pro Tools and do I want to move them to an incompatible folder. How the f*** did that ever get past quality control? And Avid isn't like other DAW vendors. There is a rigorous certification process. Before the demo could even take place there were terminal problems. How does such a monumental fuck up get past the QA teams over there? It's fucking mind blowing that this happens. I can almost see it on the Logic platform. QA was never really their focus. But Avid puts a lot of emphasis on QA. If you look at some of the smaller developers who haven't been around as long, U-he for example, they don't have these elementary issues. In my use I've never experienced a terminal crash from one of their plugins. Ever! And that goes back to 2012 basically so that's 8 years of use now. Obviously then tight QA is possible. What is one to infer from Arturia's continuing elementary problems in 2020 then? Arturia just don't seem to give a shit? Is that the conclusion to draw? Or they don't know what the fuck they're doing? What? What's one to infer from this kind of elementary bullshit problems from a company that's been around longer than pretty much any other in this business? It's great that your setup is working but that's neither here nor there. Everybody's setup should be working every time. Elementary problems such as this shouldn't exist period. Plenty of developers don't exhibit them. For me the conclusion is Arturia, after 20 years or so, is a company that just doesn't know how to build software. They have great ideas and some of their plugins even sound good but the implementation is lackluster. For that reason they've burnt their bridges with me and there is no going back.

[@morlidor]

@@Screaming-Trees Computers are complicated so many things that can go wrong, Combinations of different software and different hardware and of course different settimgs can mess things up. Also a lot of people are not aware that different processors can affect the stability of computers even though they run the same OS! Not saying Arturias stuff is flawless but for me it very seldom doesnt crash.

[@Screaming-Trees]

@@morlidor In the PC world that argument is mostly true. The hardware pool is unrestricted and can be quite large. If I were Arturia I'd probably do what Avid do; publish a certified list of compatible hardware combinations that they've put through exhaustive testing. In the Apple world this argument is mostly false. The hardware pool is restricted and much smaller. That's the whole design philosophy (you lose in the total amount of choice/variety but you gain in other areas like predictability etc). My use case is not controversial at all. My hardware is old. Avid has certified it with every new version of Pro Tools they've released. It's also commercial grade hardware (Xeon processors, registered ecc memory etc etc). That should be impossible to crash more or less. And to a greater extent that's true. It's really difficult to fault the hardware to the extent that it's not unusual to get several years of uptime in one sitting (without rebooting the computer). But the other point here is that other developers have managed to figure out how to build software that works more or less flawlessly on a variety of disparate hardware configurations. Arturia, even in 2019/2020, can't get it's software to run flawlessly on a commercial grade/server grade hardware from Apple circa 2010/2012 with additional hardware capabilities (ecc ram etc) and tight tolerances. My computer should have been a slam dunk for those guys even back in 2010. So what kind of conclusion is one to infer from that? For me the only obvious conclusion is they don't know how. They have good ideas but they don't know how to implement those ideas in a robust way. Which is both a shame and a non-starter. For me anyway.

[@morlidor]

@@Screaming-Trees OK thre we have it your hardware is OLD! Almost ten years old, and probably not the best to run moden software on yet you complain about Arturia. And as I stated earlier there actually is a difference between running different OSX software on different processors and other pieces of hardware between macs.Which is not that strange as there are many variables such ad different cache size, different bus speeds, disk types, memory used etc. I guess most mac softwaredevelopers mostly try their software on fairly current models. Some things which can make software crash is damaged memory, bad disks or bad powersupplies. I am not saying Arturias software is perfect but its far from being as bad as you make it out to be.

[@MrOuija-rr8kq]

Nice. I also refuse to pronounce GUI as “Gooey”

[@ogasi1798]

AWFUL - ZERO AUDIO UNLESS YOU WISH TO HEAR HIM WAFFLE ON

[@shadividiomixsing]

Asruuyt7iiuu.

[@vroteg]

@whiteseastudio will not agree with you about UI 😂