Add new comment

Fluidsynth-DSSI allows it. It consists of creating a preset with a relative path.

Preset Example relative to session path "./2mb_gmgs.sf2":

<!DOCTYPE qtractorPlugin>
<preset name="FluidSynth-DSSI-2mg" version="1.5.2" type="FluidSynth-DSSI_2182">
 <configs>
  <config key="load">./2mb_gmgs.sf2</config>
  <config key="GLOBAL:polyphony">256</config>
  <config key="GLOBAL:gain"> 0,501187</config>
 </configs>
 <params/>
</preset>

Again, this is only for finished projects that need to be kept or shared.
It is a final phase after mastering, and in graphic arts it is called final art.

You clean out all the unnecessary stuff from the session.
You rename and reorder tracks to make it as presentable as possible.
You document.
You attach all sample dependencies to a session-relative url. For track samples, Qtractor does the job automatically with .qtz.
For plugin samples you have to do it by hand.
Since in Qtractor in LV2 that information is hidden (compressed), it is not possible.
Fortunately DSSI does allow you to edit the dependency path and make it relative.

I still think that by default, Qtractor should save session-relative paths if plugin samples are inside the session.

In fact, I think that should be the behavior in every application that works with external samples (be they audio, midi, text, video...). If I find a path that points inside the session, I save the path relative to the session. I don't care if the path is managed by me or a plugin. The only thing that matters is that I have a path, and it is relative to the current session.