1) Ok, I understand the problem and I will accept the current state:)
2) But is it possible (and easy to implement) to remember current preset name in Qtractor's generic plugin's interface (called "properties") and inside Vee One plugins? It's like in graphic application: you open or create some file called "image1.png" and even after some changes it is still the same file, unless you save it as "image2.png". The only difference is Qtractor would keep the change across sessions with name "preset1" and signal that it was changed. Same for Vee One. Big hopes here:)
3) Yes, 0.5.11 is still in Debian Testing but I see 0.6.1 has recently entered Unstable. So I will try both the new Qtractor and LV2 + VST versions of Obxd and report the results here.
Thanks for the answers;)
1) Ok, I understand the problem and I will accept the current state:)
2) But is it possible (and easy to implement) to remember current preset name in Qtractor's generic plugin's interface (called "properties") and inside Vee One plugins? It's like in graphic application: you open or create some file called "image1.png" and even after some changes it is still the same file, unless you save it as "image2.png". The only difference is Qtractor would keep the change across sessions with name "preset1" and signal that it was changed. Same for Vee One. Big hopes here:)
3) Yes, 0.5.11 is still in Debian Testing but I see 0.6.1 has recently entered Unstable. So I will try both the new Qtractor and LV2 + VST versions of Obxd and report the results here.
Cheers