Re: [Linuxsampler-devel] "GET" LSCP commands to linuxsampler sometimes don't return data

[Christian S. <sch...@li...>]

On Dienstag, 21. Dezember 2021 17:42:29 CET Andrew C wrote:
> Hi Christian,
> 
> Unfortunately no, I wasn't running a command in parallel to the GET
> command, all my instruments had already loaded by the time I tried the GET
> command.
> The LSCP shell/CLI utility works absolutely fine every time I send such a
> GET command, so perhaps it's my netcatting that's the issue here for some
> reason. Not sure if there would be more scriptable methods of reliably
> getting the data from Linuxsampler.

Ok, then you might just try some of the numerous other netcat derivates. 
Altough it sounds a bit strange that you got a much different latency with the 
LSCP shell than with nc.

As this is really a simple text based network protocol, there are endless of 
other possibilities, like writing a simple Python script or whatever.

> Also, on the note of using the lscp CLI/netcat commands to Linuxsampler for
> the instrument editor, it seems it doesn't work on my end:
> lscp=# EDIT CHANNEL INSTRUMENT 1
> ERR:0:There is no instrument editor capable to handle this instrument
> lscp=# EDIT CHANNEL INSTRUMENT 0
> ERR:0:There is no instrument editor capable to handle this instrument
> 
> Both files were loaded using the GIG engine and gigedit/Linuxsampler are
> installed in /usr/local.. Perhaps my PATH or ldconfig needs updating?

When linuxsampler is launched, you see a bunch of information, which also 
includes the following line:

	Registered instrument editors: 'gigedit'

If "gigedit" is missing in that line, then because the sampler did not find 
gigedit's plugin in the sampler's plugin directory. You can change the 
sampler's default plugin path at compile time:

	./configure --enable-plugin-dir=/some/where

As well as overriding it by environment variable before launching 
linuxsampler. From "man linuxsampler":

ENVIRONMENT VARIABLES
       LINUXSAMPLER_PLUGIN_DIR
              Allows to override the directory where LinuxSampler shall look 
              for instrument editor plugins.

Note, there is also --exec-after-init BTW.

CU
Christian