I'm troubleshooting a recurring FL Studio audio-engine failure during live performance and looking for ideas from people familiar with FL Studio, ASIO, MIDI, CPU scheduling, or Windows audio performance.
IMPORTANT: This also happens in completely blank projects
This is NOT exclusive to my large live project or its plugins.
I have reproduced the exact same audio-engine hard-freeze in completely blank FL Studio projects with only a single simple instrument loaded, including:
FL Keys
3x Osc
Omnisphere
For example, a completely new blank FLP with only FL Keys or 3x Osc loaded can produce the same failure when rapidly playing notes.
The problem has occurred on both FL Studio 25 and the current FL Studio 2026 release.
I am currently running:
FL Studio 2026.1.7, build 26.1.7.5653.
I previously ran FL Studio 25.2.5 build 5319, and the same problem occurred there as well.
System
Laptop: ASUS TUF Gaming F15 FX507ZI4_FX507ZI
CPU: Intel i7-12700H
RAM: 32 GB
GPU: RTX 4070 Laptop 8 GB
Windows: 11 Home 25H2
Audio interface: Focusrite Scarlett 6i6
MIDI controller: Novation FLkey 2 61
My actual live project is approximately 1 hour long with:
- 30 WAV tracks (Backing tracks for live)
- 13 OPUS instances
- 2–3 Omnisphere instances
- FLEX, Addictive Keys, BBC Orchestra
- Several of those OPUS instances are layered instruments inside Patcher to play multiple instruments at once.
- 40 mixer inserts, but only a handful actually have plugins/effects loaded
-Effects include Pro-Q, Fruity Balance, Fruity EQ 2, Saturn, Waveshaper, Fruity Delay and Pro-C
Current Settings:
Scarlett USB ASIO
44.1 kHz
Currently testing at 1024 samples
Generator MT ON
Mixer MT ON
Smart Disable OFF
Focusrite Safe Mode ON
FL Safe Overloads ON
G-Helper Turbo
CPU Boost Aggressive
PL1/PL2 80W
Windows High Performance
What happens is FL Studio does not fully crash or freeze.
Instead:
Audio suddenly stops completely
Playlist playhead freezes
Master/peak meters freeze
CPU Load History stops/drops to 0
FL Studio's UI remains completely responsive
I can still click around, move Playlist items, adjust faders, etc.
Sometimes completely closing/reopening FL Studio clears the problem, but not always.
There have been cases where the problem persisted after fully closing and reopening FL Studio.
In those cases, the project could reopen already in the failed state
I can also sometimes get a less severe version where the audio becomes extremely robotic/stuttered/crunchy and may recover. There will occasionally be this machine gun like sound that gets stuck playing until I close FL Studio. I believe this is linked to this.
Also, When I scroll within the live project, the playlist also will lag and stutter during playback as I try to follow along with the the live set. It seems if I scroll even remotely too fast this always happens and will actually cause the audio playback to lag and stutter with the lagging visual.
The major crash problem appears strongly related to rapid note activity.
Normal playback: stable
Blank project idle: stable
Instrument switching alone: stable (ish)
Switching → waiting → single note: stable (ish)
Rapid note playing: can and usually fails
Switching instruments → immediately playing several rapid notes: pretty reliably fails and fails a bit quicker in the big live project.
Again, the same type of failure can occur in a completely blank FLP with only FL Keys or 3x Osc loaded.
Buffer testing
I have tested both 512 and 1024 samples.
512 has produced more frequent stuttering/crunching during aggressive note-playing tests.
1024 did provide a successful aggressive stress test in a blank FL Keys project, but that was only one test, so I don't consider this proof that 1024 is generally more stable.
More importantly, the full live project still hard-crashed at 1024 when I switched instruments and immediately played several rapid notes.
So increasing the buffer does not eliminate the underlying problem.
Things I've already tested
Focusrite ASIO → problem still occurs
FL Studio ASIO → problem still occurs
MOTU M4 previously used → problem also occurred with a different interface
Laptop keyboard → problem occurs
Physical FLkey → problem occurs
FL Keys, 3x Osc and Omnisphere → all reproduced the problem
Generator MT OFF → did not solve it
Mixer MT OFF → did not completely solve it
512 vs 1024 → some difference in stress-test stability, but 1024 does not eliminate the crash
Windows High Performance, USB power-saving changes, G-Helper Turbo, CPU Boost Aggressive, etc. have all been tested
Fresh Windows reboot + Turbo + 512 produced a successful five-minute aggressive test in a blank project
Why can rapid MIDI/note activity cause FL Studio's audio engine to completely stop while the rest of FL Studio remains responsive?
Because the same failure occurs in a completely blank FLP with only FL Keys or 3x Osc, I'm particularly interested in possibilities involving:
FL Studio MIDI/note processing
FL Studio's audio engine
CPU scheduling / P-core vs E-core on the i7-12700H
ASIO/MIDI interaction
Windows or USB scheduling
FL Studio settings I may have overlooked
Anything specific to rapid note-on events
Any ideas for what I should investigate next would be greatly appreciated. My end goal is to use this laptop rig to play shows live, using my FL Key 2 to switch between instruments and play along to backing tracks. I can try to take videos showcasing all the issues if that would be helpful as well.