PyFLP
PyFLP is an unofficial parser for FL Studio project and preset files written in Python.
| CI |
|
|---|---|
| PyPI |
|
| Activity |
|
| QA |
|
| Other |
|
From a very general point-of-view, this is the state of what is currently implemented. Click on a link to go to the documentation for that feature.
| Group | Feature | Issues | |
|---|---|---|---|
|
Arrangements |
🎼 Playlist |
|
|
| 🎞️ Tracks |
|
||
|
Channel Rack |
📈 Automations |
|
|
| 🎹 Instruments |
|
||
| 📚 Layer |
|
||
| 📁 Sampler |
|
||
|
Mixer |
🎚️ Inserts |
|
|
| 🎰 Effect slots |
|
||
|
🎶 Patterns |
🎛 Controllers |
|
|
| 🎵 Notes |
|
||
| 🚩 Timemarkers |
|
||
| Plugins | Native - 8 effects, 1 synth |
|
|
| VST 2/3 |
|
||
| Project - Settings and song metadata |
|
||
⏬ Installation
CPython 3.8+ / PyPy 3.8+ required.
python -m pip install -U pyflp
▶ Usage
Load a project file:
import pyflp
project = pyflp.parse("/path/to/parse.flp")
If you get any sort of errors or warnings while doing this, please open an issue.
Save the project:
pyflp.save(project, "/path/to/save.flp")
It is advised to do a backup of your projects before doing any changes. It is also recommended to open the modified project in FL Studio to ensure that it works as intended.
Check the reference for a complete list of useable features.
🙏 Acknowledgements
- Monad.FLParser: https://github.com/monadgroup/FLParser
- FLPEdit (repo deleted by author)
✨ Contributors
Thanks goes to these wonderful people:
nickberry17 💻 |
zacanger 🐛 📖 |
Tim 📖 💻 🚧 |
This project follows the all-contributors specification. Contributions of any kind are welcome!
Please see the contributor's guide for more information about contributing.
📧 Contact
You can contact me either via issues
and discussions or through
email via demberto(at)proton(dot)me.
© License
The code in this project has been licensed under the GNU Public License v3.
Metadata
Release files for pyflp 2.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pyflp-2.2.1.tar.gz | 1.5 MB | Without provenance | Details for pyflp-2.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyflp-2.2.1-py3-none-any.whl | Python 3 | none | any | Details for pyflp-2.2.1-py3-none-any.whl |
Total release size: 1.6 MB
Release files / pyflp-2.2.1.tar.gz
| Download URL | pyflp-2.2.1.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0926b8a8cb4832e3f33a711c7d43ded27d18a6dafef2497c45ce2e9acd9e8ad
|
|
BLAKE2b-256 checksum How to use checksums |
fd5177cf0f4c0207b457158e1babcd8a49fe036943778ad0af83acaedb4d40a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.3
|
Release files / pyflp-2.2.1-py3-none-any.whl
| Download URL | pyflp-2.2.1-py3-none-any.whl |
|---|---|
| Size | 79.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
14ee87f1ec07066bc5b41ca13a40254c529267fc6472ec8bbf33c1fff2b1e40b
|
|
BLAKE2b-256 checksum How to use checksums |
507df3a637ace13094d9b8c33d5ede30fe98a3b5724bc1717a0336486854c67d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.3
|
Security for pyflp 2.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.