I haven't been able to get it to work in another LV2 plugin, but for me, this is more than sufficient.
---
# Other observations:
The other plugins tested were Ninja2, LiquidSFZ, and SFIZZ.
I believe Ninja2 doesn't implement LV2 paths.
LiquidSFZ does, and although they are paths to SFZ files, they are paths nonetheless, so I believe they should work. Of course, the entire SFZ library was saved in the project root. It only works as an absolute path; as soon as the project folder is moved, it stops working.
SFIZZ has them implemented, but in a diferent way. In the code, it references the plugin's binary path (self).
PS: It seems SFIZZ's proposal for portability is that its samples be binary-relative. While this is a valid approach (my samples aren't lost, they travel with me), SFIZZ doesn't check if the path provided by the state matches its actual current path, nor does it modify and update it in the state. Without these checks, portability is lost. But only they can fix that.
---
# Conclusion:
It doesn't depend solely on whether it's LV2, but on how it's implemented in the plugin.
In this case, having Samplv1 and Drumkv1 function as expected is more than enough.
Furthermore, it makes sample behavior in Qtractor more consistent, since the plugin samples (in this case, only Samplv1 and Drumkv1) behave the same way as Qtractor's own samples in its tracks.
In other words, you ensure consistent sample usage between RNCBC creations.
Drumkv1 and Samplv1 work perfectly.
I haven't been able to get it to work in another LV2 plugin, but for me, this is more than sufficient.
---
# Other observations:
The other plugins tested were Ninja2, LiquidSFZ, and SFIZZ.
I believe Ninja2 doesn't implement LV2 paths.
LiquidSFZ does, and although they are paths to SFZ files, they are paths nonetheless, so I believe they should work. Of course, the entire SFZ library was saved in the project root. It only works as an absolute path; as soon as the project folder is moved, it stops working.
SFIZZ has them implemented, but in a diferent way. In the code, it references the plugin's binary path (self).
PS: It seems SFIZZ's proposal for portability is that its samples be binary-relative. While this is a valid approach (my samples aren't lost, they travel with me), SFIZZ doesn't check if the path provided by the state matches its actual current path, nor does it modify and update it in the state. Without these checks, portability is lost. But only they can fix that.
---
# Conclusion:
It doesn't depend solely on whether it's LV2, but on how it's implemented in the plugin.
In this case, having Samplv1 and Drumkv1 function as expected is more than enough.
Furthermore, it makes sample behavior in Qtractor more consistent, since the plugin samples (in this case, only Samplv1 and Drumkv1) behave the same way as Qtractor's own samples in its tracks.
In other words, you ensure consistent sample usage between RNCBC creations.