Vee One Suite, Presets und ein Paar Probleme (Bugs?)
-
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. When clicking in the box where the cursor blinks, it is impossible to type a name for a new preset using the keyboard.
This issue does not occur on Debian when using the versions provided via the PPA. -
A general issue regarding preset handling in the Vee One Suite (on both Debian/PPA and Arch Linux):
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.
2.2. The same behavior occurs with custom presets: once the window is closed and reopened, the preset name is no longer displayed.
This behavior is not observed with other synthesizers, such as those from the Surge team (e.g., SurgeXT, Monique) or OB-fX.
This is quite inconvenient when opening saved projects, as it makes it impossible to immediately identify which preset was loaded in the Vee One Suite plugins upon opening the plugin window.
- Furthermore, with the Samplv1 and Drumkv1 plugins, the "Help" button (and its associated menu) is often not visible—or only partially visible (showing just the letter "H")—when the plugin window is opened. Resizing (stretching) the plugin window causes the menu to appear.
The issues described above were observed on various PCs running Arch and Debian (using KDE Wayland) with the latest available versions for each distribution.
I have just discovered that…
I have just discovered that saving presets works when using Ardour and the Vee One Suite on Arch with KDE, but it does not work with Qtractor.
A few days ago, I sent an email to the maintainer of the Qtractor and Vee One Suite packages for the Arch repositories, but I have yet to receive a response, and there have been no updates.
However, the second issue—where preset names are not visible after reopening the plugin window—still persists regardless of the DAW being used.
The problem with the menu in the plugin window also remains, but since there is a known workaround, it is not really a major issue.
In the Arch version of Ardour, opening a plugin from the Vee One Suite always results in two windows appearing: one is empty, while the plugin itself is visible only in the other. Has it always been this way? On the plus side, the menu is always visible, meaning the plugin window in Ardour seems to display everything correctly.
re. I have just discovered that…
what exactly doesn't work? how are you saving presets on the vee-ones and qtractor that doesn't work but does in ardour?
you're probably using the Arch supplied packages to both ardour and the vee-ones lv2 plugins...
it happens that these Arch's packages of the plugins are not built to Qt6-static and thus are not self-contained and depending on system provided shared libraries which is a big issue for plugins, most specially in Ardour: all bad and strange things might happen then, if it doesn't crash on show or barely work at all.
hth.
thanks
ps. for the vee-ones, in any case or distro, you're recommended to source the repos for the safe, static builds for the lv2 plugins.
pps. on those cases (Arch) where it's showing bizarre GUI things, most probably due to wayland, try to launch with this command line prefix if you can:
QT_QPA_PLATFORM=xcb ardour9and maybe things behave a little better on the vee-one's.lv2 front;
re. 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.
_
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.
re2. appears empty
Forget what follows the ellipsis.
I just ran a test by manually exporting them to LV2; while the management via the context menu is consistent, it doesn't align with what the GUI displays—logically, the original preset name should appear in the box.
First, we would need to address the current limitation, and then—if we so choose—we could add a feature to automatically generate LV2 presets based on those configured in the options.
Once again, a lot of work for very little benefit.
....
I’ve come up with a viable solution for the LV2 format.
We could add an "Export for LV2" button next to the existing one.
You would save the files to your local LV2 folder—or, better yet, to the directory configured in Qtractor for LV2 presets.
While the preset name wouldn't be directly accessible via the UI, it would be available through Qtractor’s context menu.
Actually, on second thought... I think this could even be done automatically, without needing a specific button. Since the LV2 standard allows for querying the plugin host path, the software could simply check if the directory is writable. When the "Export" action is triggered, in addition to the current operations, it could automatically create or overwrite the
synthv1-presets.lv2folder.If there are presets but the folder doesn't exist, it would be created automatically.
Something like this could be quite useful.
The only reason I prefer LV2 over CLAP is that it allows presets to be accessed directly from the menu.
If multiple plugins offer the same functionality, I’ll always choose the one that implements its presets in the LV2 format—precisely for this reason.
re3. appears empty
Hello again, Hatorri.
What you can do is manually export each preset as an LV2 file via the properties menu; once that’s done, you can manage them directly from the context menu.
It might be a bit tedious the first time—there are no categories, just a list—but, on the plus side, you can easily switch between presets without needing to open the GUI, and the selected preset will be saved as part of your session.
Add new comment