2.1. When I select a default preset, it remains visible as long as the plugin window stays open. However, once I close and reopen the window, the box that previously displayed the preset name appears empty.
Hello Hattori:
VeeOne consists of desktop applications ported to the LV2 format—they are not apps originally designed to be plugins.
It would have been simpler the other way around: if they had been plugins ported into desktop applications.
The issue here is that the preset name is not part of the plugin’s parameters; therefore, it is not saved as part of the plugin's state.
Furthermore, the preset field is not designed to retrieve data from the state—remember, this is a ported desktop application.
Consequently, when the window is closed, that information simply disappears.
I suppose a solution could still be found. The problem, in this case, is that the code for the desktop application and the plugin would diverge, which would exponentially complicate maintenance and development. It might be possible to fix it without branching the code, but that would require implementing a complex system of conditional logic.
It was also confusing to me at the time, and I brought it up; the response I got was: "That’s just how it is, LV2 doesn’t store the preset name".
Back then, I didn’t understand why it was so complicated to fix something that seemed so trivial.
The real question is whether it is worth fixing, and that is a decision only Rui can make.
_
On Arch, there is a bug that previously existed on Debian with the Vee One Suite.
Currently, it is not possible to save presets in the suite’s four plugins.
The problem wasn't with Debian, but rather with MX—and now Rui has explained why; I hadn't been aware of this. They don't compile using static Qt.
I’m tired of advising people never, ever to install plugins at the system/administrator level. Never, ever rely on a Linux distribution to install plugins; rely on the developer instead.
The correct way to install them is not via .deb or .rpm packages. Simply decompress the .deb or .rpm file, extract the plugin, and place it in your local plugin directory.
But no one listens to me.
By design, a plugin only makes sense at the user level. It should be portable and free of dependencies, allowing it to work with any software that supports it.
More and more developers have stopped distributing their software as .deb or .rpm packages (thank goodness!) and now provide them as .zip files, making it much easier for users to manage them.
Perhaps I’m mistaken, but in all likelihood, if you take the plugin folders that work on Debian and simply copy them over to Arch, everything should work fine.
You can get the generic plugin from SourceForge. If you want to ensure that it has been compiled specifically for your distribution, you can find it here: https://build.opensuse.org/project/show/home:rncbc.
Hello Hattori:
VeeOne consists of desktop applications ported to the LV2 format—they are not apps originally designed to be plugins.
It would have been simpler the other way around: if they had been plugins ported into desktop applications.
The issue here is that the preset name is not part of the plugin’s parameters; therefore, it is not saved as part of the plugin's state.
Furthermore, the preset field is not designed to retrieve data from the state—remember, this is a ported desktop application.
Consequently, when the window is closed, that information simply disappears.
I suppose a solution could still be found. The problem, in this case, is that the code for the desktop application and the plugin would diverge, which would exponentially complicate maintenance and development. It might be possible to fix it without branching the code, but that would require implementing a complex system of conditional logic.
It was also confusing to me at the time, and I brought it up; the response I got was: "That’s just how it is, LV2 doesn’t store the preset name".
Back then, I didn’t understand why it was so complicated to fix something that seemed so trivial.
The real question is whether it is worth fixing, and that is a decision only Rui can make.
_
The problem wasn't with Debian, but rather with MX—and now Rui has explained why; I hadn't been aware of this. They don't compile using static Qt.
I’m tired of advising people never, ever to install plugins at the system/administrator level. Never, ever rely on a Linux distribution to install plugins; rely on the developer instead.
The correct way to install them is not via .deb or .rpm packages. Simply decompress the .deb or .rpm file, extract the plugin, and place it in your local plugin directory.
But no one listens to me.
By design, a plugin only makes sense at the user level. It should be portable and free of dependencies, allowing it to work with any software that supports it.
More and more developers have stopped distributing their software as .deb or .rpm packages (thank goodness!) and now provide them as .zip files, making it much easier for users to manage them.
Perhaps I’m mistaken, but in all likelihood, if you take the plugin folders that work on Debian and simply copy them over to Arch, everything should work fine.
You can get the generic plugin from SourceForge. If you want to ensure that it has been compiled specifically for your distribution, you can find it here: https://build.opensuse.org/project/show/home:rncbc.