helio-sequencer
helio-sequencer copied to clipboard
Submit to Flathub
Have you considered submitting the app to Flathub? It's basically an app store for GNU/Linux, using the distribution-independent Flatpak package format. The Flathub repository comes pre-installed on a number of major distributions and is easy to enable on others, so it's great for getting more visibility for your app.
Thanks for pointing that out, I'll take a look.
I have had that application on my radar and I have made a preliminary flatpak (before I found this issue).
Just a few notes:
- Jack will not work. Fortunately it doesn't seem be a serious problem, Helio fallback gracefully
- ~~There doesn't seem to be a way to tell Helio where to find the VST plugins (VST_PATH seems to be completely ignored)~~ nevermind, I found where in the UI to tell to scan the plugins in the specified path
- I'll submit a patch for the .desktop file that doesn't validate and the appstream .appdata file that is missing.
My biggest problem is the Helio doesn't seem to like to be sandboxed. No UI appear but it runs the VST initialisation and then hang.
Reading this blog article it sounds like plugins have to be packaged as flatpaks too. The developer wants to write a detailed description for this.
The problem is more that it doesn't honour VST_PATH or LXVST_PATH and the use has to set it up manually to find VST. But that's nothin comparing to not working at all sandboxed.
I went be to it and version 3.10 has no problem with sandboxing.
JUCE needs a couple of patches though.
Submitted it https://github.com/flathub/flathub/pull/3826
let us know if any maintainer want write access to the future repo. It's no obligation to maintain.
I tried messing around in Flatseal and it looks like even though the VST_PATH environment variables are set, it is not given access to the directories:
Could this be the problem?
Also it doesn't show any window content under XFCE (x11, xfwm4), is that an isolated issue?
I do have access to the installed plugins. Did you install the right ones? (the flatpak UX for that is kinda suboptimal)
Update: it seems the VST3 are not found at the moment. That's not normal.
Oh, sorry, I misread this to mean 'it doesn't work at all sandboxed' and assumed it not having access to the directories that the VST_PATH variables have set would be a problem and why it couldn't access plugins not installed via flatpak.
The problem is more that it doesn't honour VST_PATH or LXVST_PATH and the use has to set it up manually to find VST. But that's nothin comparing to not working at all sandboxed.
Oh, and it doesn't have access to LXVST_PATH either.
What about this:
Is it an x11 or xfce problem? It's clearly not Flatpak because you have it running fine...
I don't use xfce.
I know that, but what do you use? x11 or wayland? If it works fine on another x11 system it's probably an issue on my end.
Helio will use X11 in any cases. So here it's Xwayland
Update: it seems the VST3 are not found at the moment. That's not normal.
It actually does. False alarm.
helio is on flathub now, should this issue be closed?