Inspect an FL Studio project's channels, patterns, and mixer settings from a script or AI agent
Export an FL Studio arrangement as a standard MIDI file plus a manifest of FL specific instrument data
Programmatically apply targeted edits to tempo, notes, or mixer routing without touching the original project file
Let an AI coding assistant in VS Code inspect and edit FL Studio projects through the built in MCP server
| jihadkhawaja/music2daw | anton-petrov/rsabackdoor | danx299/simdrop | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | C# | C# | C# |
| Last pushed | — | 2015-01-20 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | hard | moderate | easy |
| Complexity | 4/5 | 3/5 | 1/5 |
| Audience | developer | researcher | general |
Figures from each repo's GitHub metadata at analysis time.
Requires the .NET 10 SDK and FL Studio itself to build, launch, and verify projects.
Music2DAW is a .NET toolkit for inspecting, editing, and exporting FL Studio project files, the .flp files created by the FL Studio music production software. It is built for developers and AI agents that need a reliable, repeatable way to look inside an FL Studio project, make specific changes to it, export the results in other formats, and then open the project back up in FL Studio to actually listen to it. The tool can read an FLP file and report on its channels, instruments, samples, patterns, piano roll notes, playlist clips, mixer settings, and effect plugins. It can export the arrangement as a standard MIDI file along with a JSON file describing FL specific details that MIDI cannot capture, such as instrument and mixer information. It can also write a modified copy of a project with targeted changes to tempo, channels, routing, notes, playlist clips, or mixer settings, always writing to a new file rather than changing the original project. There is also a command to launch a given FLP file directly in FL Studio. You can use Music2DAW two ways: as a command line tool you run from a terminal, or as a local MCP server that plugs into VS Code so that AI coding assistants like Copilot can inspect, edit, export, and launch FL Studio projects as part of an AI driven music workflow. The documented workflow is to inspect a project, write a description of the desired musical changes, turn that into a structured edit request, generate a new FLP file, inspect and verify the output, export supporting files, then listen to the result in FL Studio. Because the FLP format is undocumented and can change between FL Studio versions, the parser has only been verified against a specific FL Studio build, and results from other versions should be checked carefully before being relied on. Third party plugin presets are treated as opaque data that Music2DAW preserves but cannot fully interpret. The project requires the .NET 10 SDK to build and is licensed under the GNU General Public License version 3 or later, and it bundles a modified copy of another GPL-3.0 licensed FLP parser project.
A .NET toolkit and MCP server for inspecting, editing, and exporting FL Studio project files, built so developers and AI agents can safely automate music production edits.
Mainly C#. The stack also includes C#, .NET 10, MCP.
You may use and modify the code, but any distributed derivative work must also be released under the same GPL license and its source made available.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.