@unfa no, this version will have no online features at all. I will change icon->logo, thanks

@unfa and changed :)

@unfa could I ask for some testing? you are used to this synth as you used it before. this one is too complex for me to assess if it is working correctly or not.

@falktx @unfa I am building it now.

@falktx @unfa Thanks for doing the work to replace those Makefiles with Meson.

@falktx @unfa Maybe "original Vital plugin by Matt Tytel, Vitalium fork by falkTX"? I suggest asking Matt's opinion on that.

@be I like that wording! will change to that

@be done.

@falktx also the logo vector could use a bit more space for padding around the edges, imo

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

@falktx I guess it's mainly the logo in the top left that needs more spacing

@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 audio plugins in flatpak cant really be a thing unless tied to the same libraries as the ones used in the host.

@falktx they are a thing now, daws installed through flatpak need all audio plugins to be installed the same way (the ardour flatpak optionally requires everything under org.freedesktop.LinuxAudio.Plugins)

@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...

@falktx no, those packages are accessible by any flatpak daw that wants to use audio plugins (and they're not ardour-specific)

you can do `flatpak search linuxaudio` to show all the existing available ones

@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.

@be @falktx I've been using Vital since it came out earlier this year, extremely good synth. Haven't tried Vitalium bc I don't have too much of a reason to, but I'm super happy that it's open sourced and packaged in the kx repos now. Should make moving from system to system easier in the future if I do decide to use it.