I compile the plugins on my machines (no more glibc symbol not found) and install them in /usr/local/lib/ladspa, lv2, vst, vst3 or clap
That's default for most of the plugins' build systems.
The disadvantage of relative paths would be that the plugins are not found if the song directory goes one level up or down.
But there's another solution:
How about stripping the plugins' path completely, only leaving the filename in the session file? Qtractor would load them via the configured plugin paths.
Instead of
<filename>/usr/lib/ladspa/amp.so</filename>
we'd use
<filename>amp.so</filename>
I compile the plugins on my machines (no more glibc symbol not found) and install them in /usr/local/lib/ladspa, lv2, vst, vst3 or clap
That's default for most of the plugins' build systems.
The disadvantage of relative paths would be that the plugins are not found if the song directory goes one level up or down.
But there's another solution:
How about stripping the plugins' path completely, only leaving the filename in the session file? Qtractor would load them via the configured plugin paths.
Instead of
<filename>/usr/lib/ladspa/amp.so</filename>
we'd use
<filename>amp.so</filename>