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?
On 7/15/19 8:29 AM, Christian Schoenebeck wrote:
On Sonntag, 14. Juli 2019 21:27:31 CEST you wrote:
Christian,
I've exported just a single midi map, and also exported complete sampler
configuration. Right now it seems that using JS Classic to export the
complete sampler configuration loses the instrument maps on each
channel, as well as the audio channel routing. Fantasia seems to export
the configuration properly.
Good to know that this works for you this way with Fantasia.
Right now the frontends query all aspects of the sampler session on their own
and then assemble their LSCP files to restore the session later on. I planned
to add a "DUMP" command to the protocol which conveniently dumps everything
needed to restore the current sampler session, so that frontends no longer
have to do that error prone aspect on their own.
CU
Christian
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
