Thanks for that, Christian, I'll give some other netcat variants a go and
see what I can get back.
My Instrument Editor plugins are definitely being picked up by LInuxsampler
on start:
andrew@andrewlaptop:~/LSBuild$ linuxsampler
LinuxSampler 2.2.0.svn7
Copyright (C) 2003,2004 by Benno Senoner and Christian Schoenebeck
Copyright (C) 2005-2021 Christian Schoenebeck
Binary built: Dec 20 2021
Detected features: MMX SSE SSE2
Automatic Stacktrace: Off
Creating Sampler...OK
Registered sampler engines: 'GIG','SF2','SFZ'
Registered MIDI input drivers: ALSA,JACK
Registered audio output drivers: ALSA,JACK
Loading instrument editor plugins...OK
Registered instrument editors: 'gigedit'
Registered internal effect systems: LADSPA
no more csLADSPA plugins
failed to load DLL: '/usr/lib/ladspa/autotalent.so', cause:
/usr/lib/ladspa/a
utotalent.so: undefined symbol: __exp_finite
Registered internal effects: 354
Starting LSCP network server (0.0.0.0:8888)...OK
LinuxSampler initialization completed. :-)
and if I use a previously saved lscp commands from jsampler and simply
netcat it into linuxsampler, the engine cannot find a compatible instrument
editor for a gig file (I also tried to see what would happen if I edited
the nonexistant sampler channel 1).
and also, it will hang on attempting to control-C out of the server itself:
libjackBufferSizeCallback(1024)
jack_port_set_name: deprecated
libjackBufferSizeCallback(1024)
jack_port_set_name: deprecated
Jack: Cannot connect port 'AO-Strings:0' to port 'NONE'
jack_port_set_name: deprecated
Jack: Cannot connect port 'AO-Strings:1' to port 'NONE'
Starting disk thread...OK
EQ support: no
Scheduling '/home/andrew/Desktop/Samples/String_ensemble.gig' (Index=1) to
be
loaded in background (if not loaded yet).
Loading gig file '/home/andrew/Desktop/Samples/String_ensemble.gig'...OK
Loading gig instrument
('/home/andrew/Desktop/Samples/String_ensemble.gig',1)
...OK
Caching initial samples...OK
LSCPServer: Client connection established on socket:26.
Loading instrument editor plugins...OK
There is no instrument editor capable to handle this instrument
Invalid sampler channel number 1
LSCPServer: Client connection terminated on socket:4.
LSCPServer: Client connection terminated on socket:26.
^CFreeing gig file '/home/andrew/Desktop/Samples/String_ensemble.gig' from
me
mory ...OK
Stopping disk thread...OK
Unloading instrument editor plugins...OK
^C^C
JSampler, for example, doesn't exhibit this behaviour with the instrument
editor, strangely enough.
I fear I may be opening up a vast debugging can of worms here!!
On Tue, Dec 21, 2021 at 5:13 PM Christian Schoenebeck <
schoeneb...@linuxsampler.org> wrote:
> 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
>
>
>
>
> _______________________________________________
> Linuxsampler-devel mailing list
> Linuxsampler-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
