kb420 wrote: thread has been around for a month. I've been revisiting it when I see new posts, but I'm still curious as to what needs FL Studio wasn't meeting. I'm not a FL user, but I would still like to know, if that isn't too much trouble.
Yeah no worries...
FL Studio doesn't have integrated workflow features for the management and mitigation of CPU intensive plugin configurations.
Cubase has a Freeze function with options to manage how much of the signal path to render as audio and unload the plugins. FL Studio does have rendering to audio however it's not an integrated resource management function, it's a discrete, labour intensive manual process. It's ok for a couple of tracks here and there but not practical to manually manage in larger projects.
Cubase has Direct Offline Processing which integrates the rendering in place any number of processes and plugin chains, non-destructively. These are stored with the project and can be undone at any later date.
I can do a similar thing in FL Studio however again it's a manual process I'd have to manage myself, keeping track of all the discrete signal paths through the mixer and it's gets messy very quickly as the project scales.
Backing up a project in Cubase puts everything in a self-contained folder that can be run from a different location. FL Studio can "back up" a project however the process of creating self-contained backups is a manual process which becomes complicated when you're working with different versions of rendered audio between the project versions.
In Cubase I can save discrete templates and settings, export and import virtually anything about the project and the way it's set up. For example I have a way that I process my drums and bass section through submixes, EQ, compression.
In Cubase I can export that configuration and import it into any other project at any time, or just keep it as a backup, a starting point. If I update the configuration I can import that into existing projects.
In FL Studio I can save one mixer or instrument configuration at a time, so it's technically possible to manually reconstruct a configuration but not practical.
The dealbreaker for me was FL Studio wasn't able to make efficient use of the system resources that I have. In Cubase I'll typically see all cores at 60 - 80% and the project is playing fine in 96/24 with 256 sample latency. In FL Studio it's struggling to play a smaller project with 2048 latency in 44.1/16 and barely using 30% of CPU. So I don't know what it's doing but I spent a long time wasted searching for answers.