falktx @falktx@mastodon.falktx.com

@sjaehn is there a non-video version?

@be Ask on the LV2 mailing list then. I do not think this is the place for such questions..

@unfa
I actually built and run that once, on Linux. But it was quite uninteresting as they disable plugins

@weirdconstructor the synth itself is not lazy by any means, but the way the code was released was, to a certain degree.

but I am grateful we have that now

@hoergen Write vitalium related issues at https://github.com/DISTRHO/DISTRHO-Ports/issues

but note that many fixes are still pending to be applied. so crashes and bugs are not helpful just yet.

@FrankyFire @unfa I think unfa thought you would create a creator account for me. small confusion, where you meant to create a user account, in order to be able to help out / be a patron of someone else :)

@be you mean Matt? It is worth asking, even if I do not feel like it will be very fruitful.

@be not sure yet...

vital has some custom juce patches that I still need to apply to distrho juce fork.
so I need to manually diff the vital juce code dump, because damn it, it was really just a lazy dump of code for that release 😡
there is no history, or use of submodules for anything that could be a little clean...
so maybe after those changes are applied it works better, will verify soon.

also, the public code is old compared to latest commercial release, I bet we are missing bugfixes

I was curious and tried Vitalium on macOS.
It has the same crashes and issues that appear on Linux LOL.
Yay for cross-platform consistent crashes! 😂

(The same presets that crash lv2 version on Linux also crash it on macOS, and the same GL state mess on window re-creation is there too)

Vitalium builds ready!
Now in the KXStudio repositories, direct deb files in https://kx.studio/Repositories:Plugins as usual.

Still a few quirks to iron out, but looking very promising.

There are no presets, not sure about license for those. But you can rename/copy `~/.local/share/vital` to vitalium and have those accessible in the forked version.

Stories like these make me happy 😃
Also infuriating too, but this time with a nice end result.
https://fsfe.org/news/2021/news-20210302-01.en.html

@tromino I dont have flatpak setup here. but anyway, this will become a problem when mixing shared libraries.we already have that issue with ardour and aubio libs.. but this is likely not the place for this type of discussion.

to summarize, not coming to flatpak from my side, as I prefer to build things statically (so a binary will work on any system). but of course anyone is free to package/add them to flatpak, I can review such package.

@tromino ah yes, true. I will open a ticket about this so I dont forget.
this is quite the minimal compared to other issues, but still, thanks for bringing that up.

@tromino not really sure how that works...
so ardour has its own set of plugins that can be installed for it? because if/when other daws have different library versions, this will require alternative versions of these plugins as well.
there are a LOT of sorta-duplicated-but-not-really binaries of plugins and libraries...

@tromino not sure what you mean.. the logo being bigger than the text in the about page is an intentional visual/design choice.

@tromino audio plugins in flatpak cant really be a thing unless tied to the same libraries as the ones used in the host.

@be done.

@be I like that wording! will change to that