Bitwig in Flatpak

Official support for: bitwig.com
RELATED
PRODUCTS
Bitwig Studio 6-25%$299.00Buy

Post

Renich wrote: Mon May 23, 2022 6:44 pm IMHO, it's OK. You have the host filesystem allowed to Bitwig.

https://github.com/flathub/com.bitwig.B ... o.yaml#L23
'--filesystem=host' is not enough to get access to most paths of a system (actually to anything 'interesting'). For example access to '/usr' is forbidden, that's where the plugins are installed to (as default).

https://docs.flatpak.org/en/latest/sand ... tem-access

Post

ReleaseCandidate wrote: Mon May 23, 2022 7:08 pm '--filesystem=host' is not enough to get access to most paths of a system (actually to anything 'interesting'). For example access to '/usr' is forbidden, that's where the plugins are installed to (as default).

https://docs.flatpak.org/en/latest/sand ... tem-access
Ah, you're right. They're blacklisted even. Maybe you can add them at runtime, if you need any. If this works, you can edit your launcher so that it mounts them everytime. It seems to be as easy as passing more --filesystem=/path/to/x flags.

It's not user-friendly, but it might work.

Post

hey guys,
do you know how i can use my windows vsts with wine an yabridge having Bitwig installed via Flatpak?

It seems like bitwig can´t see the vst, maybe i did something wrong.

Thanks

Post

I wouldn't know. Never tried that.

You could always try using:

Code: Select all

flatpak run --filesystem=/path/to/your/plugins
And see if that works. What

Code: Select all

--filesystem=
does is expose that part of your filesystem to the flatpak.

It's usually better, though, to just put them somewhere within $HOME. Some paths are off-limits to flatpak.

Code: Select all

/var/lib64
for example.

In my case, I tried setting up GSnap (linux vst) and put it within

Code: Select all

/home/renich/Downloads/VST
and told Bitwig Studio about it (setup > locations) and it worked fine.
You do not have the required permissions to view the files attached to this post.

Post

i haven´t installed wine via flatpak, instead it´s a deb file and therefore my system is a mixture.
Bitwig ist installed via flatpak but most of the vstś are linux native vst or windows vst with wine and yabridge.

so in my case i want to run melodyne which is windows and therefore needs wine, and bitwig running as a flatpak..

Post

Right. Wine shouldn't be installed via flatpak.

I think I heard of some wine project to get windows VST software running on linux.

Here's the first thing that Google showed me: https://madskjeldgaard.dk/posts/improve ... -wine-tkg/

And another one that looks promising: https://github.com/osxmidi/LinVst

Post

Ah, look. This one mentions Bitwig: https://github.com/robbert-vdh/yabridge

Post

Renich wrote: Wed Oct 26, 2022 5:00 pm I wouldn't know. Never tried that.

You could always try using:

Code: Select all

flatpak run --filesystem=/path/to/your/plugins
And see if that works. What

Code: Select all

--filesystem=
does is expose that part of your filesystem to the flatpak.

It's usually better, though, to just put them somewhere within $HOME. Some paths are off-limits to flatpak.

Code: Select all

/var/lib64
for example.

In my case, I tried setting up GSnap (linux vst) and put it within

Code: Select all

/home/renich/Downloads/VST
and told Bitwig Studio about it (setup > locations) and it worked fine.
Great information!!! So is there a documented FAQ for this somewhere that you are aware of? I'd like to find a published Flatpak solution.

I was going to suggest trying "Flatseal" to open all permissions for the host. Do you know if that helps get around the issue without workarounds? That may be another solution. I use Reaper which doesn't come as a Flatpak, but I've been watching the Flatpak technology with great interest to see how things may (or may not) work with plugins (both with or without flatpak technology).

Thanks for confirming that this can work!! :D

Edit: I did some searching after reading this and found the following document to be very useful:

https://www.bitwig.com/support/technica ... latpak-52/

In particular, I found the following very interesting:

We've pre-configured Bitwig Studio to run with suitable permissions. However, should you wish to adjust permissions, you can use Flatseal here...

Working With VST Plug-ins and Flatpak
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.
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.:mad:
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
:roll:

Post

i will try again, but i think i sticked to the guide on the bitwig page pretty close, but maybe i am wrong

Post Reply

Return to “Bitwig”