Skip to content

FLP Implementation Notes

p0nce edited this page Nov 23, 2023 · 1 revision

FruityPlug Implementation Notes

  • As of 23th Nov 2023, the FruityPlug SDK has no licence, so it's not clear if Image-Line would approve our endeavour to better integrate with their host, and it probably depends upon the quality of our implementation? Do not release FLP yet.

  • The engineering at Image-Line is extremely impressive - very far from the early reputation of FLStudio - as evidenced by Vocodex and Harmor plug-ins, or the fact the public SDK still work 10 years later.

  • There are a lot of features we don't do currently:

    • "Hybrid" plugins have voices managed by the host, which is very interesting. No support in Dplug.
    • MIDI CC, Channel pressure, Channel Pitch Bend are not well supported.
    • Because Dplug is based upon a MIDI 1.0 abstraction, it doesn't support per-note pitch bend very well. But FL format does this since forever.
    • The goal was to fit the "common denominator" of Dplug plug-ins first.
  • Do not create name clashes, for example it's important that your plug-in name is unique in the FL universe. FLStudio plugin directories do nothing to avoid name clashes AFAIK.

  • Built-in 32-bit plugins were removed from FLStudio in version 21. The bridge still work, but the builtin effects ship in 64-bit only. That's why we don't support 32-bit FLP in Dplug.

  • Because FruityPlug isn't that popular a format, Image-Line has limited time to document and update the SDK, and the new changes aren't reflected in the public SDK.