Try adding permission filesystems=host-os to ~/.local/share/flatpak/overrides/com.bitwig.BitwigStudiosweet_trip wrote: Tue May 10, 2022 11:08 pm Flatpak is working for me so far. My only gripe with Bitwig moving to Flatpak is this, from https://www.bitwig.com/support/technical_support/52/:
I have a handful of Linux VST3 plugins that are installed to /usr/lib/vst3 by default, and there is no way to tell an installer to choose another location. I guess for now on, I'll be forced to move and chown anything that gets installed to /usr/lib/vst3.We recommend installing any VST plug-ins using Flatpak. VST plug-ins that cannot be installed via Flatpak should be installed in a folder that is reachable by Bitwig Studio, like your home directory. Be aware that anything installed in /usr/lib won’t be available to Bitwig Studio.
You can edit the override file directly or use Flatseal GUI.
Then launch Bitwig and add a plugin location: /var/run/host/usr/lib/vst
and or /var/run/host/usr/lib/vst3
You should then see whatever VSTs are in there. Although, anything dynamically linked won't work.
Btw, the default is filesystems=host, which means everything is accessible, which I wouldn't do.
About launching different Bitwig Flatpak versions:
Last installed Beta:
/usr/bin/flatpak run --branch=master --arch=x86_64 --command=bitwig-studio com.bitwig.BitwigStudio
Latest stable:
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=bitwig-studio com.bitwig.BitwigStudio
---
My question to anyone who knows: I have some plugins that want access to libcurl-gnutls.so, located in /usr/lib, for online activation/validation; does anyone know how to make a proper alias so the plugins can find it within the sandbox?
