Yes. It’s an exaggeration. This does not happen. I won’t say anything beyond that, as arguing about this is a waste of time.
You act as if I don’t have multiple DAWs installed on my computer and cannot simply … check it myself.
FL Studio does not have 60% less CPU usage running the same plug-ins with the same virtual instruments, audio tracks, etc. as Cubase.
To even pretend to believe that is serious next-level gaslighting hilarity.
What had my com at 65-75% CPU in FL Studio barely registers a blip of CPU in Cubase 13 - it’s a huge difference.
That’s definitely an exaggeration, and absolutely not my experience and I’ve been using Cubase (and other DAWs) for years. The difference is not big, and Cubase is not the only DAW that has look-ahead or PreGen (Digital Performer PreGen, Samplitude Pro X’s Hybrid Engine, etc.).
Also, I think CPU use has a lot more to do with the Plug-ins, Samplers, Virtual Instruments, etc. you are using in your session than what DAW you are using.
If you have a session full of Ozone and RX, then your CPU usage and latency are going to be sky high and switching to Cubase or DP or Samplitude Pro X or a whatever DAW will not alleviate that issue.
There is no universe where 65-75% CPU use in FL Studio becomes “barely a blip” simply by recreating the same project with the same MIDI, Samples, and plug-in/virtual instrument/sampler instances in Cubase.
This is simply not a thing. It’s not true. I can barely even call this an exaggeration. It’s literal pipe dream. A fantasy.
Melodyne is better. So is the Pitch Correction in Digital Performer. The algorithms are better.
I think anyone who uses pitch correction really should capitalize on the massive discounts and take an upgrade off of Melodyne Essentials up to the Editor SKU, and maybe even to Studio if they can afford it and Polyphonic Correction is something that would be useful to them.