Bitwig in Flatpak

[Josephhh]

Well, as far as I know, you just need to add some flags to the flatpak command. Judging from:

Code: Select all

flatpak run --help

; I'd say it would be enough to do:

Code: Select all

flatpak run --filesystem=/home/whatever-your-user-is/path/to/vst/folder com.bitwig.BitwigStudio

or something like that.

Yeah, that's what I thought ... It picks up the .so files correctly.... but comes up with an async error ...

It's all good, happy to use the other version.... seems to run ok

[pc999]

Wow flatpack version now, I need to try it with Fedora and pipewire

Very cool

[Beerhunter]

Yeah, is great to see that it´s in the Software center on Ubuntu.

I have been using Pipewire for quiet some time now and i can say it is fun and easy to use.
I am excited how things will evolve over the next year.


@Renich, great to see that you are still working trying to find new ways to get Bitwig work on more Distros. Thanks Man, you and Abique rock!

[Renich]

Thanks, Beerhunter!

Abique deserves all the credit, though. He's been maintaining it on his own for quite a while and has done an awesome job!

[webmob]

Hello
Use Bitwig flatpak 4.1.6 on endeavouros.
With pipewire 3.47 the mono input is only output on the left stereo channel in the hardware instrument.
With the AUR version of Bitwig, the mono input signal in the HW Instrument is output on both channels.

[Renich]

@webmob, yeah, happens to me as well.

Maybe it would be a good idea to let abique know via an issue report here: https://github.com/flathub/com.bitwig.BitwigStudio

[webmob]

Hi
Have already done there, but he said this is the wrong place and I should contact support for bugs.
I reported it to the normal support. Hope this was the right way now.
Greetings

[webmob]

Flatpak bitwig 4.2.1 and "mono input monitoring" works well if you use the alsa driver. The signal is played out on both channels.

[Renich]

Thank you for doing that. I hope it can get fixed soon. It's kind of annoying.

[webmob]

I am not sure if the problem is on bitwig or pipewire side.

[Renich]

... or flatpak's side...

[OdoSendaidokai]

Are there any news on flatpack ?
Jack doesn't work (switched to pipewire) and VSTs and access to system installed presets outside users home directory don't work e.g. SurgeXT .

[ReleaseCandidate]

VSTs and access to system installed presets outside users home directory don't work e.g. SurgeXT .

That - sandboxing everything inside the flatpack and _not_ accessing the real file system - is one of the main _features_ of Flatpack.

[Benutzername]

VSTs and access to system installed presets outside users home directory don't work e.g. SurgeXT .

That - sandboxing everything inside the flatpack and _not_ accessing the real file system - is one of the main _features_ of Flatpack.

One of the main _features_ of any DAW is to load arbitrary code from arbitrary sources. That code may itself load arbitrary resources from all over the place. This concept is known as 'plugins' and it will never work with sandboxing unless you have a closed system like RE. Additionally all DAWs also need to access resources from almost everywhere (samples from external drives, network shares, drop box, common preset folders for all local users etc). So home directory sandboxing makes absolutely no sense here.

flatpak is a nice concept to distribute binaries and dependencies and it seems to work great on most distributions if the application is self contained. If you just use Bitwig's internal devices then it works fine too but this is not how the real world looks like. A DAW without external resources and plugins is pretty useless at the end of the day.

[Renich]

IMHO, it's OK. You have the host filesystem allowed to Bitwig.

https://github.com/flathub/com.bitwig.B ... o.yaml#L23

In the end, one compromises security for usability. One day, maybe, flatpak will allow the user to grant, on the fly, access to specific locations in an amicable way. Fow now, Bitwig has access to the entire filesystem even when in Flatpak.