Hello, thank you imagine line for personally addressing these issues!
I tried the "plugin behaving badly" thing, surprisingly I had to enable it on ALL THE PLUGINS in the mixer, and each time I did, the CPU would go down more and more lil by lil. I ended up at 80% CPU and was able to play the project with midi notes on all guitars and it was hitting "90 to 95%" much better then the 150% usuage I think it was doing before..
I had to go into each plugin, and check the Use fixed size buffers then "Process Maximum Buffer" also the other option there.
It's weird though, the plugins are Izotope, waves, reputable plugins. literally each time I did this with each plugin it would go lower by 1 to 3%.
In cubase I still get much more out of CPU usage, but I am using their "ASIO Guard" checkbox, I'm not sure what that does.
I am going to get a 300$ audio interface soon to see If I get better CPU usage, I'm also thinking of trying the mac version.
I just want to get the same performance completely that other daws get in FL, then I can use it's mixer in a stanard way
BTW, the automatic PDC delay update was great, that has been a problem forever with Bias for me here. Can't wait for the other updates, i'll update the first post, cause I don't want to slander your company or anything like that.
@jtrak
Thanks, I will try that out. I think the ASIO Guard may be giving me the extra performance, just like the new Presonus Studios "hybrid engine"
FL Studio poor CPU / Audio performance compared to Presonus Studio / Cubase. How to optimize?
Audio Plugin Hosts and other audio software applications discussion
Moderator: KVR Moderators (Main)
FL Studio poor CPU / Audio performance compared to Presonus Studio / Cubase. How to optimize?
2017-08-06T14:31:01+00:00
Edit// Nov. 5th
The issue is almost "mostly resolved"
I had to go into each mixer plugin and hit "Use fixed size buffers" then "process maximum buffer"
This made the CPU usuage slowly drop for each plugin, which eventaully made the project below playable at 90% CPU usage. I still think there may be something to get more CPU out of FL Studio, and I'm not sure if Cubase "ASIO Guard" is giving me more CPU to run my project with, but as it is I still get more stability and CPU out of Cubase with the same project, I'd say about 25% more or such. But FL Studio is still the "best" daw for me. I just can't get my ideas out in Cubase lol
Edit// Here's a video comparing cubase and FL
https://youtu.be/fWG-sMiBzXo
I posted the problem on page 2, It's same problem but with updated example
https://www.kvraudio.com/forum/viewtopic.php?f=7&t=489076&start=15#p6905840
Here's link to the video problem. Presonus Studio is more optimized than Cubase and gets even better performance, my trial ran out, so you can disregard current issue below, I understand some daws are more optimized than eachother, but FL seems to be way behind. like about 50% behind cubase in performance. Would upgrading my CPU help? Upgrading to WIN 10? Upgrading my i7 4790 from 2014, 300$ CPU is actually not an option right now lol
Hello, I've been using FL Studio since version 9, I really like using it. It's the fastest for composing my ideas. I seem to be able to just "flow" with it and create really fast midi music.
The problem I've been having, since I started using more advanced plugins, such as "Soundtoys, Slate Digital, Fabfilter, Amplitube, Bias" etc, MY CPU in DAW idling at 50 to 80, then when playing back it spikes from 50 to 99 or such, and my audio crackles / clicks and daw freeze/unfreeze. I think I fixed the "Spikes" by removing the bridged plugins. but my CPU used is still too high.
I have I7 4790, 16GB ram, Windows 8. FL Studio 12.5.
Settings I have in FL Studio
ASIO4All / FL Studio ASIO, all multithreaded options on, tried all options on and off from audio panel
in plugin wrappers, I have tried "Fixed buffer size, process maximum inputs, etc"
Recently fed up, from a simple project I had, I decided to try Cubase / Presonus Studio.
I rebuilt my project exactly, in Presonus I have 19% CPU being used while it plays back, in Cubase I have 25%, and it seems like they have tons of room for more plugins.
While in FL Studio I have 55 to 80% CPU usuage while playing back.
I decided to getting rid of all bridge plugins in FL Studio, this brought it down to sit around 50% CPU Used, but I also didn't have 9 of the plugins I needed for my project, BUT! It did stop "spiking to 99%" I think, the bridges in FL Studio cause spikes.
Now, I decided to create new projects in Prosonus Studio, and FL Studio
10 instances of AmpleSound Guitars each, with 16th midi notes power chords, transposed up n down etc routed to 10 mixer tracks, 10 Fabfilter Pro L, 5 Amplitube 3, 5 Bias FX, 5 Neutrun compressor plugins, all summed up to one mixer bus, then that sent to a reverb.
Presonus Studio CPU usage was around 19%, wow! I decided to copy a few more onto more channels, it only went up a couple percent.
FL Studio's was in the 55% and spiking up a bit when playing, only a bit. I tried adding more it went higher.
All plugins were native not bridged.
Also, when FL Studo uses 50% CPU in the program, my ACTUAL CPU used is only 20%, but none the less when FL reaches 99% my project just sucks.
With Prosonus Studio, when it uses 19%, my actual CPU used is 19%.
So, from my conclusion, FL Studio is NOT optimized for modern processors / Plugins. I don't know how code works, but it's mixer is mostly not optimized, I have no trouble with of plugin inserts, just when you start using the mixer, CPU goes up fast.
Now, I'm wondering if there's anything I might be missing here, or am I pretty on target with this here? Maybe I'm missing an optimization button that would make FL Studio work like the other daws? I love using it for composing, and if the mixer was optimized would love to set it up like a traditional bus/send mixer and used that as well, but as it is now, most of my projects I have created in FL Studio do not get completed, cause I end up using too MUCH CPU and it becomes a hassle disabling plugins here and there.
I think FL Studio needs Optimization now, it does not use multithreaded enough yet, the code is still using the power of normal core processors, instead of taking advantag of all the power of new processors and plugins. I wish the develoeprs would focus on optimization, and updating the mixer, cause it's amazing for composing, it just sucks for modern FX / Mixing.
HREQ
https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=376505
Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”
Jump to
- The Main Forums
- ↳ KVR Developer Challenge 2026
- ↳ KVR Studio Manager
- ↳ Getting Started (AKA What is the best...?)
- ↳ Instruments
- ↳ Effects
- ↳ Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)
- ↳ Guitars
- ↳ Mobile Apps and Hardware
- ↳ Soundware
- ↳ Samplers, Sampling & Sample Libraries
- ↳ Hardware (Instruments and Effects)
- ↳ Modular Synthesis
- ↳ Sound Design
- ↳ Production Techniques
- ↳ Music Theory
- ↳ Computer Setup and System Configuration
- ↳ DSP and Plugin Development
- ↳ DIY: Build it and they will come
- ↳ Music Cafe
- ↳ Machine Learning and AI for Music Creation
- ↳ Sell & Buy (+Special Offers, Deals & Promos)
- ↳ KVR Experts
- ↳ Everything Else (Music related)
- ↳ Off Topic
- ↳ Off Topic Classics
- Official Company Forums
- ↳ 2getheraudio
- ↳ accSone
- ↳ Acon Digital
- ↳ AcousticsampleS
- ↳ AcousModules
- ↳ Agitated State
- ↳ AIR Music Technology
- ↳ AMG
- ↳ Ample Sound
- ↳ Antares Audio Technologies
- ↳ Apisonic Labs
- ↳ APU Software
- ↳ apulSoft
- ↳ AriesCode
- ↳ Arts Acoustic
- ↳ Arturia
- ↳ Audjoo
- ↳ AudioSpillage
- ↳ Audiority
- ↳ Best Service
- ↳ Big Tick
- ↳ Bitwig
- ↳ Controller Scripting
- ↳ Blue Cat Audio
- ↳ Cherry Audio
- ↳ CWITEC
- ↳ Embertone
- ↳ energyXT
- ↳ Eventide
- ↳ Expert Sleepers
- ↳ forward audio
- ↳ Future Audio Workshop
- ↳ FXpansion
- ↳ g200kg
- ↳ Harrison Mixbus
- ↳ HG Fortune
- ↳ Homegrown Sounds
- ↳ HoRNet Plugins
- ↳ Ilya Efimov Production
- ↳ Image Line
- ↳ Impact Soundworks
- ↳ Indiginus
- ↳ Insert Piz Here
- ↳ Ju-X
- ↳ Kirk Hunter Studios
- ↳ Kirnu
- ↳ Kong Audio
- ↳ Krotos
- ↳ Kuassa
- ↳ KV331 Audio
- ↳ LennarDigital
- ↳ Les Productions Zvon
- ↳ Liqube Audio
- ↳ Loomer
- ↳ LVC-Audio
- ↳ Maizesoft
- ↳ Manytone Music
- ↳ Media Overkill (MOK)
- ↳ MeldaProduction
- ↳ Mellowmuse
- ↳ MIDIMood
- ↳ moForte
- ↳ Mozaic Beats
- ↳ mucoder
- ↳ MusicDevelopments
- ↳ Tips & Tricks
- ↳ MusicLab
- ↳ MuTools
- ↳ New Sonic Arts
- ↳ NUSofting
- ↳ Oli Larkin Plugins
- ↳ Orange Tree Samples
- ↳ patchpool
- ↳ Photosounder
- ↳ PlugInGuru
- ↳ Polyverse Music
- ↳ Precisionsound
- ↳ Premier Sound Factory
- ↳ Psychic Modulation
- ↳ Realitone
- ↳ Resonance-Sound
- ↳ Reveal Sound
- ↳ Roger Linn Design
- ↳ rs-met
- ↳ S3A: Spatial Audio
- ↳ SaschArt
- ↳ Smart Electronix
- ↳ sonible
- ↳ SonicBirth
- ↳ Sonic Reality / eSoundz.com
- ↳ Soundiron
- ↳ SPC Plugins
- ↳ Sugar Bytes
- ↳ TAL Software
- ↳ Tokyo Dawn Labs
- ↳ Tracktion
- ↳ Tweakbench
- ↳ u-he
- ↳ u-he Linux support
- ↳ United Plugins
- ↳ VAZ Synths
- ↳ Virharmonic
- ↳ xoxos
- ↳ XSRDO - SynthCraft
- ↳ ZynAddSubFX
- Site Stuff
- ↳ Site Stuff
- Archived Forums
- ↳ AlgoMusic
- ↳ easytoolz
- ↳ Elevayta
- ↳ Hollow Sun
- ↳ LinPlug
- ↳ Muse Research and Development
- ↳ Shuriken
- ↳ SoHa Sound Design
- ↳ Soniccouture
- ↳ Topten Software
- ↳ Valhalla DSP
- ↳ CK Modules & VST
- ↳ Sennheiser AMBEO
- ↳ Muon Software
- ↳ Westgatesounds.net
- ↳ Squaredheads
- ↳ Sonigen
- ↳ CFA-Sound
- ↳ Back In Time Records
- ↳ Livelab.dk
- ↳ Skytopia
- ↳ audioD3CK
- ↳ Inspire Audio
- ↳ Krakli
- ↳ Drumdrops
- ↳ Futucraft
- ↳ OverTone DSP
- ↳ RaXnTraX
- ↳ solar3d-software
- ↳ Signaldust
- ↳ Soundemote
- ↳ ReleaseLab (Powered by Artist Expansion)
- ↳ Wolfgang Palm
- ↳ UJAM
- KVR Forum index
- All times are UTC
- Delete cookies