niceeee!!! …except i’m getting xruns with the prebuilt binaries from kxstudio, but the source code on the website is still 1.2.23 - will .24 source code be available soon?
Thanks again for these absolutely stellar plugins!!!
Is there any way to avoid or undo the lost of automation when we update the LV2 version of the plugins?
Every update changes my automation on Parametric EQ’s
The automation on the “CHH 2” track was some rectangular ups and downs.
The Filter Mute 0 on the “Chords 02” track wasn’t created by me.
And the Parametric EQ Frequency 0 was important to the project but it’s gone.
Thanks, grabbed the 1.2.24 source and compiled myself. Performance is somewhat better now, but still several % higher DSP load than 1.2.23 - also, when loading a session in Ardour (8 or 9) with LSP plugins, i’m getting tons of these:
warning: patch:Set for unknown property
warning: patch:Set for unknown property
warning: patch:Set for unknown property
warning: patch:Set for unknown property
…which seems to be from Ardour9/libs/ardour/lv2_plugin.cc - any ideas?
Edit: it might be related to Toni Link’s issue above?
Edit2: something i forgot to mention (this is probably an issue with Ardour or Carla) …plugins that use external files, like impulse responses, when saved in Carla as an Ardour plug-in, “forget” where the files are located once saved and reloaded: it says “Unsupported format” in red where the waveform would be.
Edit2: something i forgot to mention (this is probably an issue with Ardour or Carla) …plugins that use external files, like impulse responses, when saved in Carla as an Ardour plug-in, “forget” where the files are located once saved and reloaded: it says “Unsupported format” in red where the waveform would be.
Does the problem persist if you put plugins without Carla?
Changing parameters or re-ordering breaks sessions (just like with other plugin standards).
Other plugin standards require indices, so I wonder how you handle this with LV1 or VST2/3?
–
PS. You are correct that Ardour SHOULD store/restore LV2 parameters by name; yet since most plugins come in different formats and other formats require consecutive IDs it has not been an issue in the real world.
VST3 and CLAP require non-sequential parameter index. That means that I can compute a hash value from the name and use it as a parameter identifier. I have written a special tool that detects parameter name clashes and hash value collisions at a build time so if there will be found one, I will be forced to choose another name for the new parameter.
Both LADSPA and VST2 also have parameter names so host can use them to identify parameters, too. The VST2 has restricted parameter name to 7 characters (or 8 with the trailing zero). So for all plugins I restrict the length of the parameter name/identifier to 7 characters.
Nope, LSP plugins (like IR) directly in Ardour works fine.
…but unfortnately there’s no way to grab a bunch of plugins from a Carla rack and dump them in Ardour - at least not without doing weird processing on the xml files and reopening the project. I suspect it has something to do with the way Carla stores plugin states.
LSP Impulse response in Carla (stand-alone), reload rack → works
LSP Impulse response in Ardour, reload project → works
LSP Impulse response in Carla as a plugin in Ardour, reload either Ardour project or Carla rack → “Unsupported format”
After the update I’m getting a lot of those “Error writing from plugin to UI”. They do not interfere with sound nor cause xruns, but Ardour keeps sending allerts.
In the 1.2.23 the Sampler Stereo has this side panel that enable to select another sample from the same folder. Now, in the 1.2.24 single or double click on the side panel list does not alternate the sample. The up and down arrows works. Another option is to click over the sample and open the folder again, like the older versions, but it takes more time.
