psykon

Thanks to your question I tried it out and found that there are some fundamental issues with getting yabridge to work with flatpak. Most of them described on these issues: https://github.com/robbert-vdh/yabridge/issues/135 https://github.com/bitwig/bitwig-studio-flatpak/issues/24 so yeah. I might also have to switch to a different bitwig distribution or wait for a new solution to use windows vsts in bitwig.

Oh wow. I did not know about that project. Will try that one out soon. Thanks a lot.

Oh, and regarding the affinity tools: So far I have had no luck with getting them to run on Linux (tried different wine and proton configs, but I’m still learning). So far I’ve managed to do most of my gfx tasks with open source tools (Krita, natron), but I definitely miss the Affinity suite.

I use Bitwig on an Arch Based distro. It works really well. Thanks to the flatpak package of bitwig, your choice of distro should not matter that much (in regard to running bitwig). So far I’ve only used bitwig and vst/clap plugins with a native vst version (vcv rack for example) those also work great. So far, I have not tried to get windows plugins to work. But that’s a Todo item for the future. I plan to use yabridge for this, but as you have read yourself, current NI plugins are a hassle and hardware specific plugins especially. I face similar issues with overbridge for my elektron machines…

At least when it comes to native Linux audio software like bitwig and reaper, my experience is highly positive. But the landscape is a lot smaller then on windows and some things do require more reading and tinkering so I’m not recommending it to everyone but certainly encourage it if one can live with some downsides.

Obsidian is great. I’ll also throw https://logseq.com/ into the discussion. I just switched from obsidian to it because it better suits my workflow for taking notes.