status
where bambi has been tried, and what does not work yet
tested
| macOS | Windows | Linux | |
|---|---|---|---|
| every plugin, automatically | built and checked | built and checked | built and checked |
| REAPER | vst3 and clap | not yet | not yet |
| Ableton Live | through the host | not yet | no Linux version |
| Logic Pro | needs Audio Units |
used and listened to in the DAWbuilt and checked automatically on every change, not listened tonot tried yet
Tried bambi in a host that is not here? Tell us how it went, and it joins the table.
known gaps
- the hostThe host runs on macOS and comes with the macOS installer. Live sends its tracks through bambi’s virtual audio driver, built on BlackHole; its device in Live is a Max for Live device, so it needs Live Suite, or Live Standard with Max for Live. Windows, and DAWs other than Live, are open: say on GitHub which one you work in.
- signingThe macOS installer and plugins are signed and notarised. The Windows builds are not signed: Windows may warn when the zip is unpacked, and the plugins run as they are.
- HRTF personalisationThe decoder’s personalise page gives its instructions only: finding the head and ears sliders by ear, against a real loudspeaker, is not built yet. The sliders themselves work.
- Logic Probambi is VST3 and CLAP. Logic only loads Audio Units, so it cannot load bambi yet.
- speaker layoutsA layout file the speakers tool exports carries each speaker’s direction, distance, gain and cuts. bambi’s decoder uses the directions and distances, with distance compensation on the distances; it keeps the gains but does not apply them yet, and has no equaliser for the cuts yet.
- names over CLAPIn REAPER, an instance loaded as CLAP shows its id instead of its track’s name; as VST3 it shows the name. Everything else works the same.
ask for something
Found a problem, or missing something? Both go to GitHub, where what comes next is planned in the open.