including "Under the hood, this is essentially just a Python wrapper around JUCE (https://juce.com), a comprehensive C++ library for building audio applications. We at Spotify needed a Python library that could load VSTs and process audio extremely quickly for machine learning research, but all of the popular solutions we found either shelled out to command line tools like sox/ffmpeg, or had non-thread-safe bindings to C libraries. Pedalboard was built for speed and stability first, but turned out to be useful in a lot of other contexts as well."
BespokeSynth supports VST3, AudioUnit, LV2,: https://github.com/BespokeSynth/BespokeSynth/issues/1614
One day, I found a number of open source patch bay implementations. They may be useful for building a GUI with pedalboard:
- https://github.com/Houston4444/HoustonPatchbay :
> [HoustonPatchBay is] a patchbay for JACK used by RaySession and Patchance, usable by other python Qt5 softwares.
- RaySession: https://github.com/Houston4444/RaySession is a patchbay for JACK
- Patchance: https://github.com/Houston4444/Patchance is JACK patchbay gui w/ ALSA MIDI support
> It is a direct alternative to Catia or Patchage
- org.pipewire.helvum: https://gitlab.freedesktop.org/pipewire/helvum https://flathub.org/apps/org.pipewire.Helvum :
> Helvum is a GTK-based patchbay for pipewire, inspired by the JACK tool catia.
- easyeffects: https://github.com/wwmm/easyeffects ; pipewire + GStreamer -> just pipewire
camtarn•9h ago
Sadly, although it supports realtime processing, it doesn't say anything about latency, which is a make-or-break quality for most realtime audio processing. Definitely feels like a batch processing library which has had realtime support bolted on. The VST support is extremely cool though!
nicoloren•9h ago
What would be really exciting is a hardware device with all the standard plug-and-play inputs, capable of running Python... essentially a true open-source pedalboard for guitar enthusiasts.
Archit3ch•7h ago
No, what would be really exciting is a Digitally-Controlled Analog device, like the FreqTube FT1. Then python would control actual switches.
camtarn•7h ago
The ruggedness and built-in controls are really important. I used to gig with a standard laptop + audio interface + multiple MIDI controllers. The external gear was a real hassle to set up, even with everything labelled with bright coloured tape so I could just match colour to colour while plugging it in. And eventually the laptop got knocked over and fell a couple of feet onto a wooden stage - and even that minor impact smashed the screen, which was glued in so I couldn't replace it. I also have a horror story about a machine rebooting to apply Windows updates in the middle of a gig and requiring the rest of the band to improvise until I was done! I don't really gig any more, but if I took it up again, I would switch to using as much hardware as I could.
But I really don't care about actual analog devices. I already have a decent few DSP-powered pedals on my pedalboard and I cannot tell the difference, other than the true analog ones are more noisy!
lambda•6h ago
camtarn•4h ago
anton-c•3h ago
https://m.youtube.com/watch?v=dJG5IMOVYmI
Also just normal computer footpedals that were like 34.99 worked great for controlling the software if there's extra things u still need to assign
timlod•4h ago
Ultimately it depends on how much work you do and how efficient an audio thread you built. pedalboard is not a library which does audio playback itself, it just effects buffers you give it. I used python-sounddevice, which are bindings for PortAudio - if you don't use much CPU you can comfortably run plugins in realtime.
Obviously you're still beholden to the GIL in Python (until further notice) so if worse comes to worst you might experience the unlucky dropout.