|
| quote: | Originally posted by echosystm
when i was still using FL, i used roughly 3 generators per track, on average. everything else was samples and so forth. so, obviously, FX vastly outweighed generators on cpu load. with fl, i have maxed out a 1.8ghz core2 easily. in cubase, i get nowhere near it. fl also has very bad low latency performance, but that is an entirely separate problem...
fl does not support sidechain compression. the peak limiter method is gain ducking, not sidechain compression.
auto pdc = automatic plugin delay compensation. fl studio doesn't have it. you obviously don't use very complex fx plugins, as this problem would have bitten you on the ass already... (hint: try vintage warmer or a good linear phase eq).
imo, you beg to differ because your projects are still in their infancy. many of us have outgrown fl and these are some of the reasons why. the facts are, FL is lacking some very fundamental things that are just EXPECTED of a daw these days. they may not affect you yet (which they obviously don't), but that doesn't mean they aren't there.
i am entirely aware that many of these things will probably not be fixed for logical reasons, like you say. fruity noobs don't know the difference, so they are probably better off just making more shit house inbuilt plugins to capture new customers (new money). hell, if i was them, i would do it too. but that doesn't mean that more experienced users aren't allowed to be pissed off by it. |
Yes but what i argue is that two of the three points you are making puting down flstudio can be dealt with.
The multicore support is not needed. I believe that you really dont need to go all out and use a high tech fx plugin for everything you need to EQ, compress, reverb, delay, phase, flange, distort or filter. In a 16bit 44.1khz world it is extremely hard to notice whether you are using a good linear phase EQ vs. Fruity Parametic EQ 2. Sure you might have to work a lil harder with the Fruity one but its worth it to save CPU. Same goes for all other FX plugins. Seriously, take a fruity plugin, then get a more "high end" plugin, then give them the same settings or close to the same settings and run a generator with a few notes playing then render each two different mp3s. A to B them I guarantee there wont be much difference, if any, at all. The only difference you will here is when using higher sampling rates. Save the high tech stuff for the master channel and you shouldnt have a problem at all.
As for sidechain compression, sure FLStudio might not have a sidechain compression plugin dedicated to sidechain compression, but if you think about it, in the world of electronic dance music what do we use sidechaining for? Ducking. And this is exactly what the Peak Controller allows you to do. It sounds just like sidechain compression. And if you want to get really technical about it and don't like the idea of level/gain ducking then you can in fact take a Peak Controller, link some parameters to a Fruity Compressor on the desired channel and wala, sidechain compression. Not to mention fully customizable sidechain compression via peak controllers base, volume, and decay rates and the compressors attack/release rates.
I find that the only real valid point you have against FLStudio is Auto PDC, which i think what was writtin in my first paragraph probably could takes care of why FLStudio really wouldnt need that.
|
