Beat Generator
Drum patterns, fills, swing, ghost hits. Style-aware — trap hats behave like trap hats.
Multi-agent music production · FL Studio native
One prompt.
A populated FLP.
FLCC orchestrates a fleet of agents — beat generator, MIDI/WAV asset builder, local plugin scanner, vocal-chain architect, reference-track matcher, FL Studio bridge, setup wizard, and an FLP runner — turning a single creative prompt into a runnable FL Studio project.
Interactive demo
Type a vibe. Watch the room change.
FLCC reads your prompt, picks a mood, and reconfigures the agents accordingly. The page below is the same engine — try it.
How it works
From prompt to populated project in four orchestrated steps.
-
01
Prompt
Tell FLCC what you hear. Genre, BPM, key, references, mood, or pure adjectives. The orchestrator parses intent and dispatches agents.
-
02
Agents work in parallel
Beat, MIDI, vocal chain, plugin patching, and reference matching agents collaborate over a shared scratch project, swapping artifacts.
-
03
Compile FLP
The FLP compiler arranges patterns, routes mixer buses, drops samples, wires plugin presets, and writes a real FL Studio project file.
-
04
Open & flip
The FLP runner hands the project to FL Studio via the desktop bridge. You land in your DAW with everything already loaded.
The fleet
Eight agents. One conductor.
Each agent owns a narrow craft and reports to the orchestrator. You can run them solo or let the conductor coordinate.
MIDI / WAV Asset Builder
Chord progressions, basslines, melodic hooks. Outputs both editable MIDI and bounced WAV stems.
Local Plugin Scanner
Indexes your VST/VST3/AU/FL Native plugins and presets. Patches are chosen from what you actually own.
Vocal Chain Architect
EQ, comp, de-ess, saturation, reverb sends. Genre-tuned chains using your installed plugins.
Reference Track Matcher
Drop a track. FLCC analyzes tempo, key, instrumentation, and loudness target — then matches arrangement intent.
FL Studio Bridge
Talks to FL Studio over a local desktop service. Loads projects, prints stems, automates the boring bits.
Setup Wizard
One-time guided install. Detects FL Studio, plugin folders, sample libraries — confirms everything before first run.
FLP Runner
Compiles the project, validates references, and hands it to FL Studio. You open a finished session, not an empty timeline.
Desktop bridge & setup wizard
The command center lives on your machine.
FLCC ships as a local desktop package. The bridge owns the FL Studio handshake; the wizard makes sure your plugin paths, sample folders, and DAW version are wired correctly before the first prompt.
- Detects FL Studio install location and version
- Scans VST2 / VST3 / AU / FL Native plugin folders
- Indexes preset libraries and sample packs you point it at
- Local-only — your prompts, plugins, and projects stay on your machine unless you opt in to cloud assist
- No unsigned binary required — see security-block-safe setup
Security-block-safe setup
No scary “unknown publisher” dialog. No unsigned installer to dodge.
FLCC ships without a binary you have to right-click “Run anyway” on. Antivirus stays calm, SmartScreen stays quiet, your IT policy stays happy.
- MVP runs as a plain Python / Node script bundle — nothing to code-sign during alpha
- Create a desktop launcher by copying one snippet into a .bat or .command file
- Everything lives in a folder you chose — delete the folder, FLCC is gone
- A signed Windows installer and notarized macOS app are on the roadmap for v1
If your workplace blocks unsigned executables, you can still run FLCC today — the launcher is just text you paste.
Plugin intelligence
Patches built from plugins you actually own.
FLCC doesn't fantasize about gear. It reads your scanner index and assembles vocal chains, bass tones, and sound design out of installed plugins and your own presets — falling back to FL stock instruments when needed so nothing is missing on open.
- VST2 / VST3 / AU / FL Native aware
- Preset-level matching when metadata is available
- Graceful fallback to stock plugins, never a broken FLP
Vocal chains
Chains tuned for the genre and the voice.
The vocal architect picks a chain based on prompt mood, then adapts gain staging and de-essing for your installed compressor and EQ. Open the mixer and the inserts are already loaded, ordered, and bypass-toggled where useful.
HPEQCompDe-essSatVerb·SendDelay·Send
Reference matching
Drop a track. Inherit its blueprint.
FLCC analyzes tempo, key, instrumentation density, dynamic range, and stereo width from a reference, then biases every agent to land closer to that blueprint — without copying audio.
Tempo
Key fit
Density
LUFS
Populated FLP compiler
You open a session that's already arranged.
Patterns laid out across the playlist. Mixer buses named and routed. Plugins loaded with presets. Tempo and key set. Markers placed at intro, drop, bridge, and outro.
Honest caveats
What FLCC is — and isn't.
It is
- A starting point that removes the empty-project tax
- Local-first; your plugins and prompts stay on your machine
- Genre-aware scaffolding you can rip apart and rebuild
It isn't
- A replacement for taste, ears, or arrangement decisions
- A guaranteed "hit generator" — no model does that honestly
- A way around plugin licensing — it only uses what you own
- A 100% deterministic compiler — sometimes the FLP needs a nudge
Roadmap
Shipping now → next → later.
Shipping now
- Windows desktop package (alpha)
- Beat / MIDI / vocal-chain agents
- Plugin scanner + setup wizard
- FLP compiler v1
Next
- macOS bridge parity
- Reference-match v2 (tonal balance)
- Per-genre agent profiles
- Render queue & batch export
Later
- Collaboration via session diffs
- Stem regeneration in place
- Plugin-aware mastering chain
- Bridge for other DAWs (research)
Stop staring at the empty timeline.
Install the command center, run the wizard, type your first prompt, and open a finished session.
Alpha. Windows first, macOS soon. Free during early access · no account required.