Wellington Wallace

>Let the import dialogs start from the proper directories where community presets should be placed (@wwmm any hint here?); It seems that we just have to set https://docs.gtk.org/gtk4/property.FileDialog.initial-folder.html. But I...

>Implementing a guideline for packagers to be published here on Github explaining how to provide community presets (where to place them, how to do for avoiding conflicts, etc...); You are...

>Wouldn’t it be better to not have any presets at build time? And instead make some preset packages recommended pacman dependencies of easyeffects? So users can uninstall them easily, and...

>Should we establish a convention/recommendation on how to group/organize preset packages? I would let this decision to the package maintainers. As in the end the user will have to use...

>it does not really matter to us how the files will be inside the system easyeffects/presets directory. It is probably a good idea to separate input from output presets to...

>What do you think about this scheme? It seems good.

>I think to some degree using /usr/share/easyeffects for package manager provided presets would be ideal, as that is what that directory is there for. But /usr is read only sometimes....

>So just to decide so we don't need to revisit this, should it be /usr/share/easyeffects/presets then? In flatpak it can be /app/extensions/Presets, which is similar to where many audio plugins...

Run it in debug mode so we can see more information `G_MESSAGES_DEBUG=easyeffects flatpak run com.github.wwmm.easyeffects`.

>Updated main post with degug log. Sorry for excluding it! No problems. Under normal circumstances there would be many more lines. So it seems the process is failing in the...