That makes sense now. Thanks!
On 7/15/19 9:24 AM, Christian Schoenebeck wrote:
On Montag, 15. Juli 2019 08:55:21 CEST you wrote:
Thanks for the info. Regarding your last statement that "frontends
query all aspect" and then assemble their LSCP files from that, should
LSCP files assembled from the different frontends be identical? Have
you ever noticed frontends assembling slightly different LSCP files?
That's the point; different frontends will currently write different LSCP
files. ATM they query the sampler backend for every single configuration
parameter (their implementation currently knows of) and then assemble an LSCP
file by themselves that is supposed to restore that session next time, hence
error prone and requires manual updates to the frontend implementations on new
sampler backend features. And that explains the issue you had with JS Classic.
So that's why I planned to add that "DUMP" command to the sampler backend's
network protocol to simplify sampler session saving / restoring for frontends
in general.
CU
Christian
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
