Does LSP sampler(s) work for you with Ardour? First of all I don’t know how to load a sample - when I click on this big black/dark gray field it spawns some tiny black empty nonamed window and that’s it. When I try to click some more it just crash Ardour
Yes this is what I did. When I click it, instead of a browser just a tiny black empty window pops up. What’s weird I don’t even have this “click to load” - just empty area.
Yes all LSP samplers crash. Arch package provides only lv2 no vst.
To narrow down the issue please double-check if official binaries from http://lsp-plug.in/ also have this issue and contact the Arch packager otherwise. Since the plugins work on other systems, this may be distro or system or configuration specific.
Ok thank you guys.
So I uninstalled Arch package and put official lv2 from http://lsp-plug.in/ into $HOME/.lv2 dir. Basically it’s still the same - no “click to load” and no browser. But now it doesn’t crash Ardour.
Thank you Rghvdberg, with your suggestion i was able to pin the issue down.
I tried different WMs and LSP worked fine in every one of them (including openbox).
And then I realized that in my default Xfce, Ardour launcher was modified to: env LANG=en ardour5
That was causing the problem. With simple ‘ardour5’ command LSP behave as it should.
Note that LANG=en is not a valid locale. Perhaps try LANG=en_US.UTF-8 and also make sure that the locale is generated in /etc/locale.gen or try LANG=C (default, C, C++ locale). You can also try to disable Preferences > General > Translation
We have actually seen some locale issues with certain plugins in the past, mostly concerning plugin-state: Some locales use comma as decimal separator e.g. “1,5” instead of “1.5”. Plugins need to save/restore state independent of the locale, some don’t.
Yes! Thank you Robin! env LANG=en_US.UTF-8 ardour5 works perfectly. No translation and LSP plugins are happy too.
For some reason disabling Preferences > General > Translation doesn’t work for me. That was the reason I’ve put this LANG=en there, probably mindlessly copy/paste it from somewhere. It just worked so I was like the hell with it
The similar problem was reported to me at this github issue:
With the help of reporter, we quickly fixed the problem that was a cause of non-standard locale settings.
Changes will be availiable in the upcoming 1.1.5 release.