linuxsampler-devel — This list is for discussing LinuxSampler development issues and ideas

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

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

On Mittwoch, 22. Dezember 2021 21:09:39 CET Andrew C wrote:
> Hi Christian,
> 
> Not trying to be intentionally obtuse here. :)
> 
> I started completely from scratch again. Totally cleaned out /usr/local/
> (fresh ubuntu distro, so only Linuxsampler and co was living there from the
> last install attempt), deleted the LS SVN directories and redownloaded
> them.
> 
> Still getting the same error from Linuxsampler regarding no matching editor
> for a gig instrument. The plugin paths do appear to match too:

I just committed additional, more verbose error messages:
http://svn.linuxsampler.org/cgi-bin/viewvc.cgi?view=revision&revision=4010

There is now a clear distinguishment between whether there are any instrument 
editor plugins installed at all, or whether there are some but are binary 
incompatible, and also what to do about. The sampler also prints you the exact 
expected directory for the instrument editor plugins.

You should now have all the tools you need to resolve this installation issue. 
If you still cannot, then you have to debug it. I provided you all the code 
locations involved on both sides (LS and Gigedit).

Good luck!

CU
Christian

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

[Andrew C <cou...@gm...>]

Hi Christian,

Not trying to be intentionally obtuse here. :)

I started completely from scratch again. Totally cleaned out /usr/local/
(fresh ubuntu distro, so only Linuxsampler and co was living there from the
last install attempt), deleted the LS SVN directories and redownloaded
them.

Still getting the same error from Linuxsampler regarding no matching editor
for a gig instrument. The plugin paths do appear to match too:

andrew@andrewlaptop:~/LSBuild$ cd gigedit/
andrew@andrewlaptop:~/LSBuild/gigedit$ grep LINUXSAMPLER_PLUGIN_DIR
config.lo
g
LINUXSAMPLER_PLUGIN_DIR='${libdir}/linuxsampler/plugins'
andrew@andrewlaptop:~/LSBuild/gigedit$ grep '^libdir=' config.log
libdir='${exec_prefix}/lib'
andrew@andrewlaptop:~/LSBuild/gigedit$ grep '^exec_prefix=' config.log
exec_prefix='${prefix}'
andrew@andrewlaptop:~/LSBuild/gigedit$ grep '^prefix=' config.log
prefix='/usr/local'
andrew@andrewlaptop:~/LSBuild/gigedit$ cd ../linuxsampler/
andrew@andrewlaptop:~/LSBuild/linuxsampler$ grep config_plugin_dir
config.log
config_plugin_dir='/usr/local/lib/linuxsampler/plugins'
andrew@andrewlaptop:~/LSBuild/linuxsampler$  ls -l
/usr/local/lib/linuxsample
r/plugins
total 2480
-rw-r--r-- 1 root root 1610998 Dec 22 19:28 libgigeditlinuxsamplerplugin.a
-rwxr-xr-x 1 root root    1561 Dec 22 19:28 libgigeditlinuxsamplerplugin.la
-rwxr-xr-x 1 root root  920904 Dec 22 19:28 libgigeditlinuxsamplerplugin.so
andrew@andrewlaptop:~/LSBuild/linuxsampler$

Many thanks!

Andrew.


On Wed, Dec 22, 2021 at 5:35 PM Christian Schoenebeck <
sch...@li...> wrote:

> On Mittwoch, 22. Dezember 2021 17:04:14 CET Andrew C wrote:
> > Hi Christian,
> >
> > Thanks for the increased verbose output with that patch. I recompiled all
> > three of them again and I'm getting this in the console output of
> > Linuxsampler now:
> >
> > ERROR: Did not find a matching editor for instrument
> > ('/home/andrew/Desktop/S
> > amples/Booms/trailerhits.gig', 0) having data structure
> > ('libgig','4.3.0.svn3
> > 4')
> > There is no instrument editor capable to handle this instrument
>
> Yep, which proofs that you are using a mixed installation of an old
> gigedit
> version in combination with a new LS version. Otherwise gigedit would have
> barked as well now, which it didn't, right?
>
> Please read my other emails that I already sent on this topic. This is
> very
> unlikely a bug in LS, but simply a messy installation there. I know it's
> inconvenient, but that's how it is.
>
> To avoid confusion, I would start by getting rid of the other LS version
> that
> you obviously have installed somewhere in parallel on your system,
> otherwise
> you would not get two different behaviours when requesting to launch an
> instrument editor with JSampler when LS was already running vs. not
> running.
>
> QSampler and JSampler really just send a "EDIT CHANNEL INSTRUMENT
> <number>"
> command as ASCII text line to the sampler. There is absolutely no magic
> about
> it. The only thing that you could do wrong with netcat here was to supply
> a
> wrong channel number, which you can also very easily verify by sending
> "LIST
> CHANNELS" to get the current valid channel IDs.
>
> After you got rid of the other LS installation, make sure that the LS
> plugin
> path of gigedit and LS match. By default they do, but if you are fiddling
> with
> installation pathes then they might not:
>
>         $ cd YOUR_GIGEDIT_SOURCEDIR
>         $ grep LINUXSAMPLER_PLUGIN_DIR config.log
>         LINUXSAMPLER_PLUGIN_DIR='${libdir}/linuxsampler/plugins
>         $ grep '^libdir=' config.log
>         libdir='${exec_prefix}/lib'
>         $ grep '^exec_prefix=' config.log
>         exec_prefix='${prefix}'
>         $ grep '^prefix=' config.log
>         prefix='/usr'
>
>         $ cd YOUR_LS_SOURCEDIR
>         $ grep config_plugin_dir config.log
>         config_plugin_dir='/usr/lib/linuxsampler/plugins'
>         $ ls -l /usr/lib/linuxsampler/plugins
>         -rw-r--r-- 1 root root 1877636 May  9  2021
> libgigeditlinuxsamplerplugin.a
>         -rw-r--r-- 1 root root    1538 May  9  2021
> libgigeditlinuxsamplerplugin.la
>         -rw-r--r-- 1 root root 1004320 May  9  2021
> libgigeditlinuxsamplerplugin.so
>
> CU
> Christian
>
>
>
>
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>

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

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

On Mittwoch, 22. Dezember 2021 17:04:14 CET Andrew C wrote:
> Hi Christian,
> 
> Thanks for the increased verbose output with that patch. I recompiled all
> three of them again and I'm getting this in the console output of
> Linuxsampler now:
> 
> ERROR: Did not find a matching editor for instrument
> ('/home/andrew/Desktop/S
> amples/Booms/trailerhits.gig', 0) having data structure
> ('libgig','4.3.0.svn3
> 4')
> There is no instrument editor capable to handle this instrument

Yep, which proofs that you are using a mixed installation of an old gigedit 
version in combination with a new LS version. Otherwise gigedit would have 
barked as well now, which it didn't, right?

Please read my other emails that I already sent on this topic. This is very 
unlikely a bug in LS, but simply a messy installation there. I know it's 
inconvenient, but that's how it is.

To avoid confusion, I would start by getting rid of the other LS version that 
you obviously have installed somewhere in parallel on your system, otherwise 
you would not get two different behaviours when requesting to launch an 
instrument editor with JSampler when LS was already running vs. not running.

QSampler and JSampler really just send a "EDIT CHANNEL INSTRUMENT <number>" 
command as ASCII text line to the sampler. There is absolutely no magic about 
it. The only thing that you could do wrong with netcat here was to supply a 
wrong channel number, which you can also very easily verify by sending "LIST 
CHANNELS" to get the current valid channel IDs.

After you got rid of the other LS installation, make sure that the LS plugin 
path of gigedit and LS match. By default they do, but if you are fiddling with 
installation pathes then they might not:

	$ cd YOUR_GIGEDIT_SOURCEDIR
	$ grep LINUXSAMPLER_PLUGIN_DIR config.log
	LINUXSAMPLER_PLUGIN_DIR='${libdir}/linuxsampler/plugins
	$ grep '^libdir=' config.log
	libdir='${exec_prefix}/lib'
	$ grep '^exec_prefix=' config.log
	exec_prefix='${prefix}'
	$ grep '^prefix=' config.log
	prefix='/usr'

	$ cd YOUR_LS_SOURCEDIR
	$ grep config_plugin_dir config.log
	config_plugin_dir='/usr/lib/linuxsampler/plugins'
	$ ls -l /usr/lib/linuxsampler/plugins
	-rw-r--r-- 1 root root 1877636 May  9  2021 libgigeditlinuxsamplerplugin.a
	-rw-r--r-- 1 root root    1538 May  9  2021 libgigeditlinuxsamplerplugin.la
	-rw-r--r-- 1 root root 1004320 May  9  2021 libgigeditlinuxsamplerplugin.so

CU
Christian

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

[Andrew C <cou...@gm...>]

Hi Christian,

Thanks for the increased verbose output with that patch. I recompiled all
three of them again and I'm getting this in the console output of
Linuxsampler now:

ERROR: Did not find a matching editor for instrument
('/home/andrew/Desktop/S
amples/Booms/trailerhits.gig', 0) having data structure
('libgig','4.3.0.svn3
4')
There is no instrument editor capable to handle this instrument

Andrew.


On Wed, Dec 22, 2021 at 3:06 PM Christian Schoenebeck <
sch...@li...> wrote:

> On Mittwoch, 22. Dezember 2021 14:15:20 CET Christian Schoenebeck 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'
> [...]
> > > 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.
>
> I just made this more clear by showing more detailed error messages on
> terminal, both on gigedit side:
> http://svn.linuxsampler.org/cgi-bin/viewvc.cgi?view=revision&revision=4008
>
> and on linuxsampler side:
> http://svn.linuxsampler.org/cgi-bin/viewvc.cgi?view=revision&revision=4009
>
> CU
> Christian
>
>
>
>
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>

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

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

On Mittwoch, 22. Dezember 2021 14:15:20 CET Christian Schoenebeck 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'
[...]
> > 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.

I just made this more clear by showing more detailed error messages on 
terminal, both on gigedit side:
http://svn.linuxsampler.org/cgi-bin/viewvc.cgi?view=revision&revision=4008

and on linuxsampler side:
http://svn.linuxsampler.org/cgi-bin/viewvc.cgi?view=revision&revision=4009

CU
Christian

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

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

On Mittwoch, 22. Dezember 2021 14:45:59 CET Andrew C wrote:
> 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.

And that in turn sounds like you have two different LS versions somewhere 
(e.g. /usr/bin vs. /usr/local/bin/, etc.).

Both QSampler and JSampler are able to launch linuxsampler automatically if 
needed. If the sampler is not running yet, they will try to start linuxsampler 
by their configurable linuxsampler binary path, e.g. "/usr/bin/linuxsampler".

If the sampler is already running (i.e. if they can connect to TCP port 8888), 
then the will not start linuxsampler and just use the already running sampler 
instance. Which is handy, because you can quickly play around with a developer 
version of LS for instance without needing to install it anywhere. I am using 
that a lot.

CU
Christian

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

[Andrew C <cou...@gm...>]

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 <
sch...@li...> 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
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>

Re: [Linuxsampler-devel] JSampler java classes bugfixes?

[Grigor I. <gr....@gm...>]

On Wed, Dec 22, 2021 at 3:07 PM Christian Schoenebeck
<sch...@li...> wrote:
> Any clue which JRE version starts to make this necessary?

I think it is Java 9 - when the module system was introduced (Jigsaw).

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

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

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

Re: [Linuxsampler-devel] JSampler java classes bugfixes?

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

On Dienstag, 21. Dezember 2021 19:00:00 CET Andrew C wrote:
> Hi Grigor,
> 
> Thanks a bunch for that add-exports switch. JSampler is working fine now,
> save for some creaky warning messages on JRE 18.
> 
> Andrew.
> 
> On Tue, Dec 21, 2021 at 5:04 PM Grigor Iliev <gr....@gm...> wrote:
> > Hi Andrew,
> > You should be able to launch JSampler with latest JRE using the
> > following command:
> > 
> > java --add-exports java.desktop/sun.swing.plaf.synth=ALL-UNNAMED -jar
> > /path/to/Fantasia-0.9.jar

Good to know that this is working, thanks Grigor!

Any clue which JRE version starts to make this necessary?

CU
Christian

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

[Andrew C <cou...@gm...>]

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 <
sch...@li...> 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
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>

Re: [Linuxsampler-devel] JSampler java classes bugfixes?

[Andrew C <cou...@gm...>]

Hi Grigor,

Thanks a bunch for that add-exports switch. JSampler is working fine now,
save for some creaky warning messages on JRE 18.

Andrew.

On Tue, Dec 21, 2021 at 5:04 PM Grigor Iliev <gr....@gm...> wrote:

> Hi Andrew,
> You should be able to launch JSampler with latest JRE using the
> following command:
>
> java --add-exports java.desktop/sun.swing.plaf.synth=ALL-UNNAMED -jar
> /path/to/Fantasia-0.9.jar
>
> There might also be other module permission/access issues, which
> should be easy to fix by using additional --add-exports and
> --add-opens options, if needed.
>
> Unfortunately, I don't have spare time for free projects anymore and I
> don't think that I'll be able to find time to work on JSampler in near
> future.
>
> Regards,
> Grigor.
>
> On Mon, Dec 20, 2021 at 11:53 AM Andrew C <cou...@gm...> wrote:
> >
> > Hi all,
> >
> > I'm running into some critical errors with openJDK/JRE versions 16/18
> and trying to run JSampler. It appears there are some older classes that
> are no longer supported in these versions or perhaps need a bit more
> wriggling to accommodate the JSampler code?
> >
> > Exception in thread "AWT-EventQueue-0" java.lang.IllegalAccessError:
> class
> > org.jsampler.view.fantasia.basic.PixmapPane (in unnamed module
> @0x248d4f4a)
> > cannot access class sun.swing.plaf.synth.Paint9Painter (in module
> java.des
> > ktop) because module java.desktop does not export sun.swing.plaf.synth
> to u
> > nnamed module @0x248d4f4a
> >
> > I know this is/was(?) Grishata's project and I lack the knowledge to
> even begin trying to fix this up, but was wondering if anyone else has
> encountered this and if there are workarounds for it?
> >
> > The alternative, if I cannot get it working would have to be diving into
> sending LSCP commands to Linuxsampler via Netcat. That should be fun! ;)
> >
> > A question for Christian, but is it possible through LSCP to tell
> Linuxsampler to open gigedit "Live" on an instrument, so as to edit in
> real-time, or was that a special function of JSampler?
> >
> > Cheers,
> >
> > Andrew.
> > _______________________________________________
> > Linuxsampler-devel mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>

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

Re: [Linuxsampler-devel] JSampler java classes bugfixes?

[Grigor I. <gr....@gm...>]

Hi Andrew,
You should be able to launch JSampler with latest JRE using the
following command:

java --add-exports java.desktop/sun.swing.plaf.synth=ALL-UNNAMED -jar
/path/to/Fantasia-0.9.jar

There might also be other module permission/access issues, which
should be easy to fix by using additional --add-exports and
--add-opens options, if needed.

Unfortunately, I don't have spare time for free projects anymore and I
don't think that I'll be able to find time to work on JSampler in near
future.

Regards,
Grigor.

On Mon, Dec 20, 2021 at 11:53 AM Andrew C <cou...@gm...> wrote:
>
> Hi all,
>
> I'm running into some critical errors with openJDK/JRE versions 16/18 and trying to run JSampler. It appears there are some older classes that are no longer supported in these versions or perhaps need a bit more wriggling to accommodate the JSampler code?
>
> Exception in thread "AWT-EventQueue-0" java.lang.IllegalAccessError: class
> org.jsampler.view.fantasia.basic.PixmapPane (in unnamed module @0x248d4f4a)
> cannot access class sun.swing.plaf.synth.Paint9Painter (in module java.des
> ktop) because module java.desktop does not export sun.swing.plaf.synth to u
> nnamed module @0x248d4f4a
>
> I know this is/was(?) Grishata's project and I lack the knowledge to even begin trying to fix this up, but was wondering if anyone else has encountered this and if there are workarounds for it?
>
> The alternative, if I cannot get it working would have to be diving into sending LSCP commands to Linuxsampler via Netcat. That should be fun! ;)
>
> A question for Christian, but is it possible through LSCP to tell Linuxsampler to open gigedit "Live" on an instrument, so as to edit in real-time, or was that a special function of JSampler?
>
> Cheers,
>
> Andrew.
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

Re: [Linuxsampler-devel] JSampler java classes bugfixes?

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

On Dienstag, 21. Dezember 2021 17:36:24 CET Andrew C wrote:
> My bad, I had forgotten about QSampler. I'll try that out instead and
> perhaps hunt down an older Java SDK version if possible.
> 
> Cheers,
> Andrew.

Maybe it is time to mark JSampler as orphaned (e.g. on the website) to make it 
more clear that nobody has been working on it for 10 years. If it no longer 
runs with a recent Java SDK version, then it is probably time to reflect the 
facts.

CU
Christian

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

[Andrew C <cou...@gm...>]

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.

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?

Many thanks,

Andrew.


On Tue, Dec 21, 2021 at 4:31 PM Christian Schoenebeck <
sch...@li...> wrote:

> On Dienstag, 21. Dezember 2021 15:46:17 CET Andrew C wrote:
> > Hi,
> >
> > I'm hacking together a quick-and-dirty bash script for
> controlling/setting
> > up audio/midi interfaces in Linuxsampler by sending LSCP commands.
> >
> > Sending the commands seems absolutely fine, but using the 'GET' commands
> to
> > recieve data from Linuxsampler, for example info about a sampler channel,
> > don't appear to return data consistently or "in time"?
> >
> > Command I'm using:
> > echo "GET CHANNEL INFO 1" | nc -q 1 -t localhost 8888
> >
> > Sometimes it'll return the channel info immediately, other times
> > Linuxsampler returns nothing at all, though the connection is established
> > and terminated.
>
> I guess you were sending another LSCP command in parallel while that
> happened,
> e.g. loading an instrument in foreground.
>
> The LSCP server is currently single-threaded:
>
> http://svn.linuxsampler.org/cgi-bin/viewvc.cgi/linuxsampler/trunk/src/network/lscpserver.h?revision=2534&view=markup
>
> So the LSCP server only executes one command at a time, which explains why
> your "GET CHANNEL INFO" sometimes takes a moment before completing. So far
> this was not an issue for anybody, at least nobody complained FWIW in all
> these years.
>
> In the meantime you might just load your instruments in the background for
> not
> blocking the LSCP server for too long.
>
> BTW we also have a dedicated command line utility that might be a bit more
> convenient to play around with LSCP:
> http://doc.linuxsampler.org/Release_Notes/LinuxSampler_2_0_0/#lscp_shell
>
> > Thanks,
> >
> > Andrew.
>
>
>
>
>
>
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>

Re: [Linuxsampler-devel] JSampler java classes bugfixes?

[Andrew C <cou...@gm...>]

My bad, I had forgotten about QSampler. I'll try that out instead and
perhaps hunt down an older Java SDK version if possible.

Cheers,
Andrew.

On Tue, Dec 21, 2021 at 4:23 PM Christian Schoenebeck <
sch...@li...> wrote:

> On Montag, 20. Dezember 2021 10:52:50 CET Andrew C wrote:
> > Hi all,
>
> Hi,
>
> > I'm running into some critical errors with openJDK/JRE versions 16/18 and
> > trying to run JSampler. It appears there are some older classes that are
> no
> > longer supported in these versions or perhaps need a bit more wriggling
> to
> > accommodate the JSampler code?
> >
> > Exception in thread "AWT-EventQueue-0" java.lang.IllegalAccessError:
> class
> > org.jsampler.view.fantasia.basic.PixmapPane (in unnamed module
> @0x248d4f4a)
> > cannot access class sun.swing.plaf.synth.Paint9Painter (in module
> java.des
> > ktop) because module java.desktop does not export sun.swing.plaf.synth
> to u
> > nnamed module @0x248d4f4a
> >
> > I know this is/was(?) Grishata's project and I lack the knowledge to even
> > begin trying to fix this up, but was wondering if anyone else has
> > encountered this and if there are workarounds for it?
>
> Yes, one of the following, but probably not an answer that you like:
>
> - Use QSampler instead of JSampler.
>
> or
>
> - Use an older Java SDK.
>
> or
>
> - Try fixing the issue in JSampler's source code.
>
> When you look at the Subversion repository [1] you will see that the last
> change on JSampler was almost 10 years ago. It is almost a miracle that it
> still worked for such a long time without any maintenance changes.
>
> [1]
> http://svn.linuxsampler.org/cgi-bin/viewvc.cgi/jsampler/trunk/?view=log
>
> > The alternative, if I cannot get it working would have to be diving into
> > sending LSCP commands to Linuxsampler via Netcat. That should be fun! ;)
>
> Or you just use QSampler, setup your session with mouse as usual, and if
> you
> still want to use LSCP from the command line you can just save your session
> with QSampler which saves it as LSCP file. So you would have an easy
> starting
> point from there.
>
> > A question for Christian, but is it possible through LSCP to tell
> > Linuxsampler to open gigedit "Live" on an instrument, so as to edit in
> > real-time, or was that a special function of JSampler?
>
> Sure! Both JSampler and QSampler control the sampler via LSCP. So
> everything
> they do, you can do as well. In this case it is
>
>         EDIT CHANNEL INSTRUMENT <sampler-channel>
>
>
> http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html#rfc.section.6.9.1
>
> >
> > Cheers,
> >
> > Andrew.
>
>
>
>
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>

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

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

On Dienstag, 21. Dezember 2021 15:46:17 CET Andrew C wrote:
> Hi,
> 
> I'm hacking together a quick-and-dirty bash script for controlling/setting
> up audio/midi interfaces in Linuxsampler by sending LSCP commands.
> 
> Sending the commands seems absolutely fine, but using the 'GET' commands to
> recieve data from Linuxsampler, for example info about a sampler channel,
> don't appear to return data consistently or "in time"?
> 
> Command I'm using:
> echo "GET CHANNEL INFO 1" | nc -q 1 -t localhost 8888
> 
> Sometimes it'll return the channel info immediately, other times
> Linuxsampler returns nothing at all, though the connection is established
> and terminated.

I guess you were sending another LSCP command in parallel while that happened,
e.g. loading an instrument in foreground.

The LSCP server is currently single-threaded:
http://svn.linuxsampler.org/cgi-bin/viewvc.cgi/linuxsampler/trunk/src/network/lscpserver.h?revision=2534&view=markup

So the LSCP server only executes one command at a time, which explains why
your "GET CHANNEL INFO" sometimes takes a moment before completing. So far 
this was not an issue for anybody, at least nobody complained FWIW in all
these years.

In the meantime you might just load your instruments in the background for not
blocking the LSCP server for too long.

BTW we also have a dedicated command line utility that might be a bit more
convenient to play around with LSCP:
http://doc.linuxsampler.org/Release_Notes/LinuxSampler_2_0_0/#lscp_shell

> Thanks,
> 
> Andrew.

Re: [Linuxsampler-devel] JSampler java classes bugfixes?

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

On Montag, 20. Dezember 2021 10:52:50 CET Andrew C wrote:
> Hi all,

Hi,

> I'm running into some critical errors with openJDK/JRE versions 16/18 and
> trying to run JSampler. It appears there are some older classes that are no
> longer supported in these versions or perhaps need a bit more wriggling to
> accommodate the JSampler code?
> 
> Exception in thread "AWT-EventQueue-0" java.lang.IllegalAccessError: class
> org.jsampler.view.fantasia.basic.PixmapPane (in unnamed module @0x248d4f4a)
> cannot access class sun.swing.plaf.synth.Paint9Painter (in module java.des
> ktop) because module java.desktop does not export sun.swing.plaf.synth to u
> nnamed module @0x248d4f4a
> 
> I know this is/was(?) Grishata's project and I lack the knowledge to even
> begin trying to fix this up, but was wondering if anyone else has
> encountered this and if there are workarounds for it?

Yes, one of the following, but probably not an answer that you like:

- Use QSampler instead of JSampler.

or

- Use an older Java SDK.

or

- Try fixing the issue in JSampler's source code.

When you look at the Subversion repository [1] you will see that the last
change on JSampler was almost 10 years ago. It is almost a miracle that it
still worked for such a long time without any maintenance changes.

[1] http://svn.linuxsampler.org/cgi-bin/viewvc.cgi/jsampler/trunk/?view=log

> The alternative, if I cannot get it working would have to be diving into
> sending LSCP commands to Linuxsampler via Netcat. That should be fun! ;)

Or you just use QSampler, setup your session with mouse as usual, and if you
still want to use LSCP from the command line you can just save your session
with QSampler which saves it as LSCP file. So you would have an easy starting
point from there.

> A question for Christian, but is it possible through LSCP to tell
> Linuxsampler to open gigedit "Live" on an instrument, so as to edit in
> real-time, or was that a special function of JSampler?

Sure! Both JSampler and QSampler control the sampler via LSCP. So everything
they do, you can do as well. In this case it is

	EDIT CHANNEL INSTRUMENT <sampler-channel>

http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html#rfc.section.6.9.1

> 
> Cheers,
> 
> Andrew.

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

[Andrew C <cou...@gm...>]

Hi,

I'm hacking together a quick-and-dirty bash script for controlling/setting
up audio/midi interfaces in Linuxsampler by sending LSCP commands.

Sending the commands seems absolutely fine, but using the 'GET' commands to
recieve data from Linuxsampler, for example info about a sampler channel,
don't appear to return data consistently or "in time"?

Command I'm using:
echo "GET CHANNEL INFO 1" | nc -q 1 -t localhost 8888

Sometimes it'll return the channel info immediately, other times
Linuxsampler returns nothing at all, though the connection is established
and terminated.

Thanks,

Andrew.

[Linuxsampler-devel] JSampler java classes bugfixes?

[Andrew C <cou...@gm...>]

Hi all,

I'm running into some critical errors with openJDK/JRE versions 16/18 and
trying to run JSampler. It appears there are some older classes that are no
longer supported in these versions or perhaps need a bit more wriggling to
accommodate the JSampler code?

Exception in thread "AWT-EventQueue-0" java.lang.IllegalAccessError: class
org.jsampler.view.fantasia.basic.PixmapPane (in unnamed module @0x248d4f4a)
cannot access class sun.swing.plaf.synth.Paint9Painter (in module java.des
ktop) because module java.desktop does not export sun.swing.plaf.synth to u
nnamed module @0x248d4f4a

I know this is/was(?) Grishata's project and I lack the knowledge to even
begin trying to fix this up, but was wondering if anyone else has
encountered this and if there are workarounds for it?

The alternative, if I cannot get it working would have to be diving into
sending LSCP commands to Linuxsampler via Netcat. That should be fun! ;)

A question for Christian, but is it possible through LSCP to tell
Linuxsampler to open gigedit "Live" on an instrument, so as to edit in
real-time, or was that a special function of JSampler?

Cheers,

Andrew.

Re: [Linuxsampler-devel] SVN Gigedit compile errors on Ubuntu Studio 21.04

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

On Freitag, 17. Dezember 2021 10:37:54 CET Andrew C wrote:
> My bad here. I was mixing GTK versions.. Had installed libgtk2.4-dev, when
> I should've installed libgtk-3.0-dev. Gigedit (latest svn) compiles
> absolutely fine now.
> 
> This thread also sheds light on the issue:
> https://bb.linuxsampler.org/viewtopic.php?t=3379

Yes, unfortunately it is not the first time somebody ended up with an 
incompatible set of glib(mm)/gtk(mm) dev package combinations being installed 
and getting compiler errors like these.

As you might imagine, that's not something all Gtk apps out there should be 
obliged to verify by themselves individually. We already have more than enough 
work to support all kinds of Gtk(mm) versions out there. It is not realistic 
that we would even start trying to deal with all possible linear combinations 
of all those individual libs' versions.

If a header file of lib x depends on a certain mininum version of header files 
of lib y, then it should also check for that version and bark with an 
human=end-user readable message like:

   gtkmm 3.10.1 requires at least glibmm 2.50.0, found 2.10.1 though

All those libs already define macros with their exact versions with scheme:

	<LIBNAME>_MAJOR_VERSION
	<LIBNAME>_MINOR_VERSION
	<LIBNAME>_MICRO_VERSION

and they all know which minimum version of another lib they need (or should 
know). So that would not be hard to add such kind of check to their header 
files to stop such tedious issues.

Maybe you find some time to report or for sending patches to them.

CU
Christian

Re: [Linuxsampler-devel] SVN Gigedit compile errors on Ubuntu Studio 21.04

[Andrew C <cou...@gm...>]

My bad here. I was mixing GTK versions.. Had installed libgtk2.4-dev, when
I should've installed libgtk-3.0-dev. Gigedit (latest svn) compiles
absolutely fine now.

This thread also sheds light on the issue:
https://bb.linuxsampler.org/viewtopic.php?t=3379

Andrew.

On Fri, Dec 17, 2021 at 9:06 AM Andrew C <cou...@gm...> wrote:

> Hi, it's me again :)
>
> Getting a compile error with the latest svn version of gigedit on Ubuntu
> Studio 21.04:
>
> In file included from /usr/include/glib-2.0/glib/galloca.h:32,
>                 from /usr/include/glib-2.0/glib.h:30,
>                 from /usr/include/glibmm-2.4/glibmm/unicode.h:23,
>                 from /usr/include/glibmm-2.4/glibmm/ustring.h:21,
>                 from /usr/include/gtkmm-2.4/gtkmm/label.h:7,
>                 from wrapLabel.hh:28,
>                 from wrapLabel.cc:25:
> /usr/include/glib-2.0/glib/gtypes.h:545:26: note: declared here
>  545 | typedef struct _GTimeVal GTimeVal
> GLIB_DEPRECATED_TYPE_IN_2_62_FOR(GDateTime);
>      |                          ^~~~~~~~
> wrapLabel.cc: In constructor ‘view::WrapLabel::WrapLabel(const
> Glib::ustring&)’:
> wrapLabel.cc:69:44: error: ‘WORD_CHAR’ is not a member of ‘Pango::WrapMode’
>
>   69 |    get_layout()->set_wrap(Pango::WrapMode::WORD_CHAR);
>      |                                            ^~~~~~~~~
> make[4]: *** [Makefile:874: libgigedit_la-wrapLabel.lo] Error 1
> make[4]: Leaving directory
> '/home/ubuntu-studio/Downloads/svn/gigedit/src/gigedit'
> make[3]: *** [Makefile:935: all-recursive] Error 1
> make[3]: Leaving directory
> '/home/ubuntu-studio/Downloads/svn/gigedit/src/gigedit'
> make[2]: *** [Makefile:418: all-recursive] Error 1
> make[2]: Leaving directory '/home/ubuntu-studio/Downloads/svn/gigedit/src'
> make[1]: *** [Makefile:468: all-recursive] Error 1
> make[1]: Leaving directory '/home/ubuntu-studio/Downloads/svn/gigedit'
> make: *** [Makefile:398: all] Error 2
>
> Looking at this error, I realise this might be a GTK Library problem,
> rather than specific to Gigedit itself!
>
> On a related note, the latest official release of the Linuxsampler source
> has a compile error, but the latest svn compiles fine (think I may have
> reported that one?)
>
> I'm also seeing alot of "deprecated" due to -Wdeprecated-warning from
> c++11 by default in building libgig/linuxsampler/gigedit from svn.
>
> Thanks,
> Andrew.
>

[Linuxsampler-devel] SVN Gigedit compile errors on Ubuntu Studio 21.04

[Andrew C <cou...@gm...>]

Hi, it's me again :)

Getting a compile error with the latest svn version of gigedit on Ubuntu
Studio 21.04:

In file included from /usr/include/glib-2.0/glib/galloca.h:32,
                from /usr/include/glib-2.0/glib.h:30,
                from /usr/include/glibmm-2.4/glibmm/unicode.h:23,
                from /usr/include/glibmm-2.4/glibmm/ustring.h:21,
                from /usr/include/gtkmm-2.4/gtkmm/label.h:7,
                from wrapLabel.hh:28,
                from wrapLabel.cc:25:
/usr/include/glib-2.0/glib/gtypes.h:545:26: note: declared here
 545 | typedef struct _GTimeVal GTimeVal
GLIB_DEPRECATED_TYPE_IN_2_62_FOR(GDateTime);
     |                          ^~~~~~~~
wrapLabel.cc: In constructor ‘view::WrapLabel::WrapLabel(const
Glib::ustring&)’:
wrapLabel.cc:69:44: error: ‘WORD_CHAR’ is not a member of ‘Pango::WrapMode’
  69 |    get_layout()->set_wrap(Pango::WrapMode::WORD_CHAR);
     |                                            ^~~~~~~~~
make[4]: *** [Makefile:874: libgigedit_la-wrapLabel.lo] Error 1
make[4]: Leaving directory
'/home/ubuntu-studio/Downloads/svn/gigedit/src/gigedit'
make[3]: *** [Makefile:935: all-recursive] Error 1
make[3]: Leaving directory
'/home/ubuntu-studio/Downloads/svn/gigedit/src/gigedit'
make[2]: *** [Makefile:418: all-recursive] Error 1
make[2]: Leaving directory '/home/ubuntu-studio/Downloads/svn/gigedit/src'
make[1]: *** [Makefile:468: all-recursive] Error 1
make[1]: Leaving directory '/home/ubuntu-studio/Downloads/svn/gigedit'
make: *** [Makefile:398: all] Error 2

Looking at this error, I realise this might be a GTK Library problem,
rather than specific to Gigedit itself!

On a related note, the latest official release of the Linuxsampler source
has a compile error, but the latest svn compiles fine (think I may have
reported that one?)

I'm also seeing alot of "deprecated" due to -Wdeprecated-warning from c++11
by default in building libgig/linuxsampler/gigedit from svn.

Thanks,
Andrew.

Re: [Linuxsampler-devel] akaiextract loop start <-> loop end

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

On Dienstag, 16. November 2021 19:38:44 CET Kolja Koch wrote:
> > Looks like data corruption to me. Akai sounds are decades old. On what
> > medium did you have that Akai sound stored on; HD, burned vs. pressed
> > CDROM?
> The sounds come from an AKAI-image with looped brass-sounds. I don't really
> use these, just for testing purpose. It took me a while to see that the
> issues I had were not in my gig-creation, but in those wav-files instead...
> I managed to use some other wav-files containing loop information, those
> work as expected.

In all these years there were only a hand full of people that still wanted to 
access their old Akai sounds, because you would barely find a sound library in 
Akai format that would sound good enough even for standards 20 years ago.

I also still own numerous Akai CDs and Akai hardware sampler, but I haven't 
touched them in years. I once had plans to add support for S5000/S6000 format 
as well, but figured who would need that apart from nostalgic look backs.

> Since I don't own any other means of testing the AKAI-image, I cannot tell,
> how they would 'originally' sound when looped.

Like I said: you can visually see where the loop points are supposed to be, 
without even listening to them. When you open the wave in a wave editor you 
should easily be able to see two sections in the wave form that look 
identical.

Exceptions are typically synthetic sounds, e.g. sampled FM synths, as well as 
a bunch of thin analague synth sounds which have an almost static wave form 
throughout the entire sample, but natural sounds (like your brass sounds) 
typically have a high variance in their wave form, so those almost identical 
two loop sections of the two loop points visually pop out.

> Data corruption could theoretically be, though I didn't notice any other
> problems with those files,  only loop-start and -end and, consistent for
> all files I tested, those values would, theoretically, make sense when
> swapped.

Bit rot are very seldom bit flips that appear over years. It is not like that 
you would have several bit flips in a row or somewhere nearby. The next bit 
flip is usually various MBs or even GBs away. So data degradation in general 
is a very subtle and slow phenomenon, especially on uncompressed data like 
this one.

At most you might hear a pop sound somewhere in any of the samples. I 
encountered corrupt samples with such pop symptoms numerous times in the past, 
but it took me a while to actually realize, i.e. hear those issues back then. 
So there were good reasons why I revived the CRC32 checksum feature in the gig 
format and our tools, as it is not realistic to (re)verify sound libs by ears. 
These features will be extended in Gigedit was well.

> I don't know the details of how the data is stored in that filesystem but

Well, you know on which medium you have stored them on. I bet you have stored 
them as Akai image files on some ancient mechanical HD, which in turn would 
certainly have an ancient Linux or Windows file system, i.e. without self-
healing features.

If you even have it stored on a native Akai HD, same thing: all their 
filesystems were way more primitive. No self-healing.

> would assume it to be a very specific data corruption. Anyway, as I said,
> besides for testing my software I don't use these files, so that would have
> been more of an academic interest to me.

Exactly, same applies to all Akai owners I guess. :)

> > In general I highly recommend to use a modern filesystem (e.g. btrfs, ZFS)
> > nowadays with appropriate self-healing feature to prevent things like bit
> > rotting [1], especially for long-term storage.
> 
> Thanks for the advice, I will definitely keep that in mind!
> 
> 
> Cheers,
> Kolja

CU
Christian