← Back to PluginProof Services

FL Studio Exploratory Testing Case Study

By Aaron Shippey | Feb 23, 2026

← Back to PluginProof Services

FL Studio Exploratory Testing Case Study

By Aaron Shippey

Section 1: Introduction

This case study documents my first experience with FL Studio, approached from the perspective of a plugin QA tester. My goal was to understand FL Studio’s core workflow well enough to test plugins effectively in this environment.

Rather than following tutorials initially, I explored FL Studio on my own. I documented what felt intuitive, where friction appeared, and how FL Studio’s workflow philosophy differs from track-based DAWs.

This case study focuses on four core areas:

Section 2: First Impressions

One feature I really appreciate in FL Studio is the hint panel in the top-left corner, just below the Escape and Maximize icons. Whatever element your mouse hovers over, the panel displays a short description of that tool or control.

Hint Panel

It’s like having an integrated reference while exploring the DAW.

Another feature that stood out immediately was how customizable the FL Studio interface is. Like in a physical studio, where your mixing console isn’t glued to a certain place, FL Studio allows you to resize, reposition, and organize nearly every panel.

Hint Panel

After getting a feel for the general workflow, I wanted to find and open a plugin. As a new user, locating the plugin type I wanted felt clear and intuitive.

Hint Panel

After clicking on the browser icon, I found the plugin folder was organized clearly. I immediately knew how to find what I was looking for. The plugin database includes ‘Effects’ and ‘Generator’ folders.

Hint Panel

Section 3: Playlist & MIDI Recording Friction

After several days of exploring FL Studio, I still haven’t successfully recorded MIDI from my keyboard. This has been my biggest friction point so far.

What I tried:

Hint Panel

Result:

No MIDI was recorded or played back.

I repeated this process multiple times:

Still no success capturing MIDI input.

What works:

What doesn’t:

Recording MIDI in real-time like in Logic or REAPER (arm → record → play → capture).

This could be:

This suggests a potential UX friction point.

Section 4: Channel Rack

When I first explored the Channel Rack, I didn’t realize it functions differently from tracks in other DAWs.

While it lets you manage and sequence channels, they must be routed to the Mixer to:

Hint Panel

This is where I manage all of my channels.

Adding a new channel is straightforward:

Below the channel list is FL Studio’s step sequencer, one of its most recognizable features.

It allows for:

No need for real-time performance to build rhythm.

Hint Panel

Section 5: The Mixer

Hint Panel

In the mixer console, I noticed the track latency button, which I haven’t used before. I’m currently experimenting to understand how it impacts timing and workflow.

When I first encountered the “Enable FX” button, I wasn’t sure how it worked. I later realized that it only functions once a plugin is loaded into the slot.

Loading FX was initially confusing:

After further exploration:

Section 6: Technical Issues Encountered

Format-Specific Crash: Surge XT (VST3)

Issue: FL Studio crashes consistently when applying filters in the VST3 version of Surge XT.

Error: EAccessViolation

Observation:

Conclusion:

This suggests a VST3 bridge compatibility issue in FL Studio (trial version on Apple Silicon), rather than a problem with Surge XT itself.

Section 7: Final Thoughts

Exploring FL Studio showed me that a DAW workflow doesn’t need to be fixed — there are many valid approaches to creating music.

One feature I would like to see:

Aside from that, I enjoyed getting familiar with the fundamentals of FL Studio and understanding how its workflow differs from more traditional DAWs.

If you’re an audio plugin company looking for plugin QA, I can help.
Reach out at aaron@pluginproof.com