Looks pretty good from the web page! How does this differ from Decent Sampler though? There's probably obvious differences but I haven't had a chance to dive into figuring that out for myself.
You should see if you can get a mention on the Sonic State / Sonic Talk podcast. Especially if you can get on episode with Yoad Nevo (the guy behind so many of the Waves plugins), or Ty Unwin and his Kontakt-based composing for the BBC. They'd probably have good constructive feedback while giving you a mention. I think Sonic Talk use Decent Sampler for their sample libraries for members, but maybe this will convince them to switch to Floe?
Thank for the excellent suggestions! I'll definitely take a look.
Perhaps the key difference is that Decent Sampler allows you to create a custom GUI for your sample library. Floe does not, it's a standard, complete set of parameters that explore into the realm of sample-based-synthesis moreso than just performing virtual instruments.
I do wonder about offering an API for creating custom GUIs, but I'm unsure how it would interact with the existing firmly ingrained GUI. Maybe it would have to be a wrapper API mostly - allowing sample libraries to 'grab' into the existing set of parameters and expose and reconfigure them into custom elements.
It can run from any path so long as your plugin host or DAW is happy to load it from there (the plugin APIs define standard folders plugins should be installed to, but lots of host allow other paths).
Not quite as generic as that. I suppose there's 2 types of users at the moment.
Musicians who just want load up virtual instruments (whether that's 'real' instrument, or synthesised-based), play them, but then also use Floe's GUI to morph the sound into something different using layers, granular, FX, etc.
Or alternatively, sample library developers who want to create a curated sample library package for musicians. They configure the sample library using Lua (and set a background image and icon) and create a bank of presets - and then musicians can load that packagr into their Floe instance.
i couldn't find any information about it but i still see an AGENTS.md file at the root of the source tree so: how much AI was used in the making of this? how was it used?
Since early 2026 it's mixed AI and handwritten. Before that it was mostly written by hand. Quite a lot of the code goes back to 2018 even. Typically, I do back and forth with Claude Code agents on new features and bug fixes, reading and editing code along with it.
Looks pretty good from the web page! How does this differ from Decent Sampler though? There's probably obvious differences but I haven't had a chance to dive into figuring that out for myself.
You should see if you can get a mention on the Sonic State / Sonic Talk podcast. Especially if you can get on episode with Yoad Nevo (the guy behind so many of the Waves plugins), or Ty Unwin and his Kontakt-based composing for the BBC. They'd probably have good constructive feedback while giving you a mention. I think Sonic Talk use Decent Sampler for their sample libraries for members, but maybe this will convince them to switch to Floe?
Thank for the excellent suggestions! I'll definitely take a look.
Perhaps the key difference is that Decent Sampler allows you to create a custom GUI for your sample library. Floe does not, it's a standard, complete set of parameters that explore into the realm of sample-based-synthesis moreso than just performing virtual instruments.
I do wonder about offering an API for creating custom GUIs, but I'm unsure how it would interact with the existing firmly ingrained GUI. Maybe it would have to be a wrapper API mostly - allowing sample libraries to 'grab' into the existing set of parameters and expose and reconfigure them into custom elements.
This looks great, I'll be excited to see this progressively become pure Zig and drop C++
Would be great to have something like Kontakt without all the cruft
Is the plug in portable? In a sense: can I run it from any path, or does it require operating system's well known hard coded paths?
It can run from any path so long as your plugin host or DAW is happy to load it from there (the plugin APIs define standard folders plugins should be installed to, but lots of host allow other paths).
Once running it will try to create some directories in known locations on your OS for storing libraries, presets, preferences, etc. https://floe.audio/docs/reference/file-locations
Is this essentially "roll your own VST plugin" or something else?
Not quite as generic as that. I suppose there's 2 types of users at the moment.
Musicians who just want load up virtual instruments (whether that's 'real' instrument, or synthesised-based), play them, but then also use Floe's GUI to morph the sound into something different using layers, granular, FX, etc.
Or alternatively, sample library developers who want to create a curated sample library package for musicians. They configure the sample library using Lua (and set a background image and icon) and create a bank of presets - and then musicians can load that packagr into their Floe instance.
i couldn't find any information about it but i still see an AGENTS.md file at the root of the source tree so: how much AI was used in the making of this? how was it used?
Since early 2026 it's mixed AI and handwritten. Before that it was mostly written by hand. Quite a lot of the code goes back to 2018 even. Typically, I do back and forth with Claude Code agents on new features and bug fixes, reading and editing code along with it.
whos this actually for? , your icp to be precise What would make the next 90 days a success for you?
This looks great. Maybe a Kontakt killer? There's definitely a niche for something like this. It's good cross-promotion for your sound libraries too.