Hi Christian,
Can confirm that is the order I compiled and installed the 3 pieces on this
new Linux installation.
JSampler opens the editor in real-time mode, as does the LSCP commandline
**but** only when JSampler has previously connected to LinuxSampler. In a
standalone mode with simply netcatting the same lscp commands JSampler uses
to set up the midi, audio and sampler channels, using the LSCP commandline
"EDIT INSTRUMENT CHANNEL 0" produces the error about no suitable instrument
editor being found.
Thanks,
Andrew.
On Wed, Dec 22, 2021 at 1:15 PM Christian Schoenebeck <
schoeneb...@linuxsampler.org> wrote:
> On Dienstag, 21. Dezember 2021 19:18:44 CET Andrew C wrote:
> > 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
>
> Most likely reason for this: you compiled LS, but are using a third-party
> compiled gigedit version. For live-editing support with gigedit all
> involved
> components need to be binary compatible, because in live-editing mode they
> share the same process and in memory data.
>
> I recommend you recompile
>
> 1. libgig
> 2. linuxsampler
> 3. gigedit
>
> in this order. And make sure that you have actually installed the
> respective
> component (in the same order) before compiling the next one, because in
> that
> sequence they will access the header files of the former during
> compilation.
>
> 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
