Changelog

0.0.3

  • Add support for packaging and installing MDATA libraries (Mirage)
  • Add tooltips to the settings GUI
  • Add new Info panel featuring info about installed libraries. ‘About’, ‘Metrics’ and ‘Licenses’ have been moved here too instead of being separate panels.
  • Add new fields to the Lua API to support license info and attribution, such as CC BY
  • Add attribution-required panel which appears when needed with generated copyable text for fulfilling attribution requirements. Synchronised between all instances of Floe. Makes complying with licenses like CC BY easy.
  • Enable selecting multiple package to install at once
  • Make notifications dismiss themselves after a few seconds
  • Fixed externally deleted or moved-to-trash libraries not being removed from Floe
  • Fixed not installing to the chosen location

0.0.2

  • Fix Windows installer crash
  • Don’t show a console window with the Windows installer
  • Better logo for Windows installer
  • Remove unnecessary ‘Floe Folders’ component from macOS installer

0.0.1

This is the first release of Floe. It’s ‘alpha quality’ at the moment - there will be bugs and there are a couple of missing features. This release is designed mostly to test our release process.

This release only contains the CLAP plugin. The VST3 and AU plugins will be released soon.

Mirage

Floe used to be called Mirage. Mirage contained many of the same features seen in Floe v0.0.1. But there are large structural changes, and some new features and improvements:

  • Use multiple different libraries in the same instance.
  • CLAP version added - VST3 and AU coming soon, VST2 support dropped.
  • New installer: offline, no account/download-tickets needed. Libraries are installed separately.
  • Ability for anyone to develop sample libraries using new Lua-based sample library format. The new format features a new system to tag instruments and libraries. Hot-reload library development: changes to a library are instantly applied to Floe.
  • New comprehensive documentation.
  • Floe now can have multiple library and preset folders. It will scan all of them for libraries and presets. This is a much more robust and flexible way to manage assets rather than trying to track individual files.
  • New, robust infrastructure:
    • Floe settings are saved in a more robust way avoiding issues with permissions/missing files.
    • Improved default locations for saving libraries and presets to avoid permissions issues.
    • New format for saving presets and DAW state - smaller and faster than before and allows for more expandability.
  • New settings GUI.
  • Floe packages: a robust way to install libraries and presets. Floe packages are zip files with a particular layout that contain libraries and presets. In the settings of Floe, you can install these packages. It handles all the details of installing/updating libraries and presets. It checks for existing installations and updates them if needed. It even checks if the files of any existing installation have been modified and will ask if you want to replace them. Everything just works as you’d expect.

Technical changes:

  • Huge refactor of the codebase to be more maintainable and expandable. There’s still more to be done yet though.
  • New build system using Zig; cross-compilation, dependency management, etc.
  • Comprehensive CI/CD pipeline for testing and creating release builds.
  • New ‘sample library server’, our system for providing libraries and audio files to Floe in a fast, async way.