LV2 Vitalium settings do not restore correctly when a project is saved and reopened

[loplkc]

LV2 Vitalium settings do not restore correctly when a project is saved and reopened

[plainoldcheese]

I also have these issues with Vitalium and some other lv2 plugins. On arch linux in Reaper (also using the package from the arch linux community repositories)

[mycroftsnm]

Same issue here, Arch linux and reaper, with the arch repository package

[jcelerier]

Can confirm the same on ossia score. Official "Vital.so" VST3 from ArchLinux package vital-synth does reload correctly.

[ZhekaHauska]

I have the same issue with Vitalium on Manjaro. I have to pick again every instrument preset after Ardour, LMMS restart since settings are altered.

[magnetophon]

Same here, with Vitalium in Ardour, using NixOS.

[loplkc]

I am now on Debian (same machine) and have Vitalium installed from the kxstudio repository. The issue still persists.

[nengisuls]

Same here. Vitalium in Ardour 6.9 on Linux Mint. I've opted to save the presets and reload for the moment. Is there any other logs or info I can provide devs to help resolve this? Sorry, I'm new to contributing to bug tracking.

[falkTX]

Does the same happen with swankyamp from disthro-ports? It is made with the same juce version as vitalium, would help to find out where the issue is.

[nengisuls]

I was able to save states in swankyamp lv2. BTW both my versions are from the kx studio repo, if that helps.

[CameronAsselin]

Also having this issue on Arch using Reaper as a DAW.

EDIT: Switched to VST3 and it's working perfectly now. You might need to add the path /usr/lib/vst3 to the plugin path list on your DAW. I also added /usr/lib/vst and /usr/lib/lv2 as distrho-ports installs plugins there but those paths weren't specified in Reaper for me.

[DarkRTA]

This seems like a bit of a race condition.

Loading a patch causes vitalium to change a large number of its parameters at once, and some hosts choke on this and end up missing some of the changes, resulting in what vitalium has being out of sync with what the host has.

If I modify a parameter by hand after loading the patch, the odds of the host not saving that specific parameter correctly go down considerably, as the host should now have the correct value for that parameter.

[xard-dev]

I can also confirm this.

Though for a race condition the symptoms are very systematic. For example when loading a project with LV2 instance using certain patches the patches always fail in same way when reloading the project.