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

Re: [Linuxsampler-devel] bug tracker disabled

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

On Wednesday, September 28, 2016 18:05:27 Rui Nuno Capela wrote:
> On 09/28/2016 04:44 PM, Christian Schoenebeck wrote:
> > Sorry Rui for all the trash you received today!
> 
> hey. i have no trash here, received from bb.linuxsampler.org today or in
> the last days. zero.
> 
> maybe the spam filters do work after all  :)

Ja ja, let me guess what your spam filter is:

	s/.*linuxsampler.org$/ > /dev/null

Bullet proof spam protection. ;-)

CU
Christian

Re: [Linuxsampler-devel] bug tracker disabled

[Rui N. C. <rn...@rn...>]

On 09/28/2016 04:44 PM, Christian Schoenebeck wrote:
>
> Sorry Rui for all the trash you received today!
>

hey. i have no trash here, received from bb.linuxsampler.org today or in 
the last days. zero.

maybe the spam filters do work after all  :)


regards
-- 
rncbc aka. Rui Nuno Capela

[Linuxsampler-devel] bug tracker disabled

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

Now they even run spam bots to attack bug trackers. Unbelievable.

I disabled self registration for now on bugs.linuxsampler.org until we have an 
appropriate solution for that (i.e. question-answer game like on 
bb.linuxsampler.org).

Sorry Rui for all the trash you received today!

CU
Christian

Re: [Linuxsampler-devel] Windows builds

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

On Monday, September 26, 2016 18:30:21 Andreas Persson wrote:
> I tried to copy the dll files from the build server
> (/usr/lib/gcc/i686-w64-mingw32/4.9-win32), and then linuxsampler.exe
> starts without errors, but neither gigedit nor qsampler work. I think we
> must find or build new versions of the Qt and gtkmm libs compatible with
> the newer gcc.

I was actually currently trying another approach, I was playing on the
libgig-win32 target and added "-static-libgcc -static-libstdc++" and removed
"--disable-static". It builds fine but fails when it tries to link one of the 
command line tools, because some of the static symbols are now tried to be 
included to both the libgig DLLs as well as the command line applications.

I give up for today. Maybe tomorrow ...

CU
Christian

Re: [Linuxsampler-devel] Windows builds

[Andreas P. <and...@ou...>]

Andreas Persson wrote:
> Christian Schoenebeck wrote:
>> In case you encounter any issues with the new LinuxSampler Windows installer 
>> version from today (linuxsampler_20160925_setup.exe) or later, then just let 
>> me know!
> The 32 bit programs are now broken, as the gcc and stdc++ dll files are
> missing in the installer.
I tried to copy the dll files from the build server
(/usr/lib/gcc/i686-w64-mingw32/4.9-win32), and then linuxsampler.exe
starts without errors, but neither gigedit nor qsampler work. I think we
must find or build new versions of the Qt and gtkmm libs compatible with
the newer gcc.

The 64 bit version of gigedit however seems to work fine.

/Andreas

Re: [Linuxsampler-devel] Windows builds

[Andreas P. <and...@ou...>]

Christian Schoenebeck wrote:
> In case you encounter any issues with the new LinuxSampler Windows installer 
> version from today (linuxsampler_20160925_setup.exe) or later, then just let 
> me know!
The 32 bit programs are now broken, as the gcc and stdc++ dll files are
missing in the installer.

/Andreas

[Linuxsampler-devel] Windows builds

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

Hi Windows users,

I just updated the cross compilers for the Windows platform on our build 
server. One of them had an ancient old version which I got tired of dealing 
with on source code level.

In case you encounter any issues with the new LinuxSampler Windows installer 
version from today (linuxsampler_20160925_setup.exe) or later, then just let 
me know!

CU
Christian

[Linuxsampler-devel] gig file integrity checks

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

Hi,

yesterday I realized that our sample integrity implementation for gig files 
was never really working. The gig format always used CRC32 checksums to be 
able to detect if sample data had been damaged or been modified unintenionally 
for some reason. Unfortunately the respective checksum table was always 
damaged or completely lost whenever the file structure of the respective gig 
file was changed by libgig, which happens quite easily even on minor changes 
with gigedit for example.

This problem should now be fixed with libgig 4.0.0.svn8. I added two new 
options to the command line tool "gigdump" (coming with libgig), which allows 
you to check whether your gig files are affected:

	gigdump --verify foo.gig

and

	gigdump --rebuild-checksums foo.gig

Please refer to "man gigdump" for more detailed descriptions about those new 
options. "--verify" will tell you both, whether samples were damaged, as well 
as whether the checksum table itself was damaged.

In case you still encounter damaged checksum tables after updating to
libgig 4.0.0.svn8, please let me know!

CU
Christian

[Linuxsampler-devel] [ANN] The QStuff* End of Summer'16 Release

[Rui N. C. <rn...@rn...>]

Howdy!

Modesty on the side, this is the ultimate Qstuff* End of Summer'16 
release frenzy.

Nothing less than the following gems:

* QjackCtl 0.4.3
* Qsynth 0.4.2
* Qsampler 0.4.1
* QXGEdit 0.4.1
* QmidiCtl 0.4.1
* QmidiNet 0.4.1

are now released to the masses.

Enjoy and have (lots of) fun!


**QjackCtl - JACK Audio Connection Kit Qt GUI Interface [1]**

    QjackCtl 0.4.3 (end of summer'16) released!

QjackCtl [1] is a(n ageing but still) simple Qt [7] application to 
control the JACK [8] sound server, for the Linux Audio [12] infrastructure.

Website:
    http://qjackctl.sourceforge.net

Project page:
    http://sourceforge.net/projects/qjackctl

Downloads:
    http://sourceforge.net/projects/qjackctl/files
- source tarball:
    http://download.sf.net/qjackctl/qjackctl-0.4.3.tar.gz
- source package:
    http://download.sf.net/qjackctl/qjackctl-0.4.3-26.rncbc.suse.src.rpm
- binary packages:
    http://download.sf.net/qjackctl/qjackctl-0.4.3-26.rncbc.suse.i586.rpm
    http://download.sf.net/qjackctl/qjackctl-0.4.3-26.rncbc.suse.x86_64.rpm

Git repos:
    http://git.code.sf.net/p/qjackctl/code
    https://github.com/rncbc/qjackctl.git
    https://gitlab.com/rncbc/qjackctl.git
    https://bitbucket.com/rncbc/qjackctl.git

Change-log:
- Fix build error caused by variable length array.
- Fix some tooltip spelling (patch by Jaromír Mikeš, thanks).
- Translation (not) fix for the default server name "(default)".
- Old "Start minimized to system tray" option returns to setup.
- Dropped the --enable-qt5 from configure as found redundant given 
that's the build default anyway (suggestion by Guido Scholz, while for 
Qtractor [15], thanks).
- Late again French (fr) translation update (by Olivier Humbert aka. 
trebmuh, thanks).


**Qsynth - A fluidsynth Qt GUI Interface [2]**

    Qsynth 0.4.2 (end of summer'16) released!

Qsynth [2] is a FluidSynth [10] GUI front-end application written in C++ 
around the Qt [7] framework using Qt Designer.

Website:
    http://qsynth.sourceforge.net

Project page:
    http://sourceforge.net/projects/qsynth

Downloads:
    http://sourceforge.net/projects/qsynth/files
- source tarball:
    http://download.sf.net/qsynth/qsynth-0.4.2.tar.gz
- source package:
    http://download.sf.net/qsynth/qsynth-0.4.2-8.rncbc.suse.src.rpm
- binary packages:
    http://download.sf.net/qsynth/qsynth-0.4.2-8.rncbc.suse.i586.rpm
    http://download.sf.net/qsynth/qsynth-0.4.2-8.rncbc.suse.x86_64.rpm

Git repos:
    http://git.code.sf.net/p/qsynth/code
    https://github.com/rncbc/qsynth.git
    https://gitlab.com/rncbc/qsynth.git
    https://bitbucket.com/rncbc/qsynth.git

Change-log:
- Old "Start minimized to system tray" option returns to setup.
- Dropped the --enable-qt5 from configure as found redundant given 
that's the build default anyway (suggestion by Guido Scholz, while for 
Qtractor [15], thanks).


**Qsampler - A LinuxSampler Qt GUI Interface [3]**

    Qsampler 0.4.1 (end of summer'16) released!

Qsampler [3] is a LinuxSampler [11] GUI front-end application written in 
C++ around the Qt [7] framework using Qt Designer.

Website:
    http://qsampler.sourceforge.net

Project page:
    http://sourceforge.net/projects/qsampler

Downloads:
    http://sourceforge.net/projects/qsampler/files
- source tarball:
    http://download.sf.net/qsampler/qsampler-0.4.1.tar.gz
- source package:
    http://download.sf.net/qsampler/qsampler-0.4.1-18.rncbc.suse.src.rpm
- binary packages:
    http://download.sf.net/qsampler/qsampler-0.4.1-18.rncbc.suse.i586.rpm
    http://download.sf.net/qsampler/qsampler-0.4.1-18.rncbc.suse.x86_64.rpm

Git repos:
    http://git.code.sf.net/p/qsampler/code
    https://github.com/rncbc/qsampler.git
    https://gitlab.com/rncbc/qsampler.git
    https://bitbucket.com/rncbc/qsampler.git

Change-log:
- Fixed a race condition on creating sampler channels that ended in 
duplicate channel strips; also fixed channel auto-arrange.
- Dropped the --enable-qt5 from configure as found redundant given 
that's the build default anyway (suggestion by Guido Scholz, while for 
Qtractor [15], thanks).
- Automake: set environment variable GCC_COLORS=auto to allow GCC to 
auto detect whether it (sh/c)ould output its messages in color.


**QXGEdit - A Qt XG Editor [4]**

    QXGEdit 0.4.1 (end of summer'16) released!

QXGEdit [4] is a live XG instrument editor, specialized on editing MIDI 
System Exclusive files (.syx) for the Yamaha DB50XG [14] and thus 
probably a baseline for many other XG devices.

Website:
    http://qxgedit.sourceforge.net

Project page:
    http://sourceforge.net/projects/qxgedit

Downloads:
    http://sourceforge.net/projects/qxgedit/files
- source tarball:
    http://download.sf.net/qxgedit/qxgedit-0.4.1.tar.gz
- source package:
    http://download.sf.net/qxgedit/qxgedit-0.4.1-8.rncbc.suse.src.rpm
- binary packages:
    http://download.sf.net/qxgedit/qxgedit-0.4.1-8.rncbc.suse.i586.rpm
    http://download.sf.net/qxgedit/qxgedit-0.4.1-8.rncbc.suse.x86_64.rpm

Git repos:
    http://git.code.sf.net/p/qxgedit/code
    https://github.com/rncbc/qxgedit.git
    https://gitlab.com/rncbc/qxgedit.git
    https://bitbucket.com/rncbc/qxgedit.git

Change-log:
- Dropped the --enable-qt5 from configure as found redundant given 
that's the build default anyway (suggestion by Guido Scholz, while for 
Qtractor [15], thanks).


**QmidiCtl - A MIDI Remote Controller via UDP/IP Multicast [5]**

    QmidiCtl 0.4.1 (end of summer'16) released!

QmidiCtl [5] is a MIDI remote controller application that sends MIDI 
data over the network, using UDP/IP multicast. Inspired by multimidicast 
[16] and designed to be compatible with ipMIDI [17] for Windows. 
QmidiCtl [5] has been primarily designed for the Maemo [18] enabled 
handheld devices, namely the Nokia N900 [19] and also being promoted to 
the Maemo Package repositories [20]. Nevertheless, QmidiCtl may still be 
found effective as a regular desktop application as well.

Website:
    http://qmidictl.sourceforge.net

Project page:
    http://sourceforge.net/projects/qmidictl

Downloads:
    http://sourceforge.net/projects/qmidictl/files
- source tarball:
    http://download.sf.net/qmidictl/qmidictl-0.4.1.tar.gz
- source package:
    http://download.sf.net/qmidictl/qmidictl-0.4.1-9.rncbc.suse.src.rpm
- binary packages:
    http://download.sf.net/qmidictl/qmidictl-0.4.1-9.rncbc.suse.i586.rpm
    http://download.sf.net/qmidictl/qmidictl-0.4.1-9.rncbc.suse.x86_64.rpm

Git repos:
    http://git.code.sf.net/p/qmidictl/code
    https://github.com/rncbc/qmidictl.git
    https://gitlab.com/rncbc/qmidictl.git
    https://bitbucket.com/rncbc/qmidictl.git

Change-log:
- Dropped the --enable-qt5 from configure as found redundant
    given that's the build default anyway (suggestion by Guido
    Scholz, while for Qtractor [15], thanks).


**QmidiNet -  A MIDI Network Gateway via UDP/IP Multicast [6]**

    QmidiNet 0.4.1 (end of summer'16) released!

QmidiNet [6] is a MIDI network gateway application that sends and 
receives MIDI data (ALSA-MIDI and JACK-MIDI) over the network, using 
UDP/IP multicast. Inspired by multimidicast [16] and designed to be 
compatible with ipMIDI [17] for Windows.

Website:
    http://qmidinet.sourceforge.net

Project page:
    http://sourceforge.net/projects/qmidinet

Downloads:
    http://sourceforge.net/projects/qmidinet/files
- source tarball:
    http://download.sf.net/qmidinet/qmidinet-0.4.1.tar.gz
- source package:
    http://download.sf.net/qmidinet/qmidinet-0.4.1-10.rncbc.suse.src.rpm
- binary packages:
    http://download.sf.net/qmidinet/qmidinet-0.4.1-10.rncbc.suse.i586.rpm
    http://download.sf.net/qmidinet/qmidinet-0.4.1-10.rncbc.suse.x86_64.rpm

Git repos:
    http://git.code.sf.net/p/qmidinet/code
    https://github.com/rncbc/qmidinet.git
    https://gitlab.com/rncbc/qmidinet.git
    https://bitbucket.com/rncbc/qmidinet.git

Change-log:
- Dropped the --enable-qt5 from configure as found redundant given 
that's the build default anyway (suggestion by Guido Scholz, while for 
Qtractor [15], thanks).


License:
    All of the Qstuff* are free, free, open-source Linux Audio [12] 
software, distributed under the terms of the GNU General Public License 
(GPL [13]) version 2 or later.


References:

   [1] QjackCtl - A JACK Audio Connection Kit Qt GUI Interface
       http://qjackctl.sourceforge.net

   [2] Qsynth - A fluidsynth Qt GUI Interface
       http://qsynth.sourceforge.net

   [3] Qsampler - A LinuxSampler Qt GUI Interface
       http://qsampler.sourceforge.net

   [4] QXGEdit - A Qt XG Editor
       http://qxgedit.sourceforge.net

   [5] QmidiCtl - A MIDI Remote Controller via UDP/IP Multicast
       http://qmidictl.sourceforge.net

   [6] QmidiNet - A MIDI Network Gateway via UDP/IP Multicast
       http://qmidinet.sourceforge.net

   [7] Qt framework, C++ class library and tools for
       cross-platform application and UI development
       http://qt.io/

   [8] JACK Audio Connection Kit
       http://jackaudio.org

   [9] ALSA, Advanced Linux Sound Architecture
       http://www.alsa-project.org/

[10] FluidSynth - A SoundFont Synthesizer
       A real-time software synthesizer based on SoundFont 2 specifications
       http://www.fluidsynth.org

[11] LinuxSampler - The Linux Sampler Project
       A modular, streaming capable, realtime audio sampler
       http://www.linuxsampler.org

[12] Linux Audio consortium of libre software for audio-related work
       http://linuxaudio.org

[13] GPL - GNU General Public License
       http://www.gnu.org/copyleft/gpl.html

[14] Yamaha DB50XG
       http://www.soundonsound.com/sos/1996_articles/may96/yamahadb50xg.html

[15] Qtractor, an audio/MIDI multi-track sequencer
       http://qtractor.sourceforge.net

[16] multimidicast - sends and receives MIDI from ALSA sequencers over 
network
       http://llg.cubic.org/tools/multimidicast

[17] ipMIDI - MIDI over Ethernet ports - send MIDI over your LAN
       http://nerds.de

[18] Maemo.org - Home of the Maemo community
       http://www.maemo.org

[19] Maemo.org Wiki - Nokia N900
       http://wiki.maemo.org/Nokia_N900

[20] Maemo.org - Downloads: QmidiCtl
       http://maemo.org/downloads/product/Maemo5/qmidictl


See also:
    http://www.rncbc.org/drupal/node/1696


Enjoy && keep the fun, always!
--
rncbc aka. Rui Nuno Capela

Re: [Linuxsampler-devel] gigedit crashes when adding dimensions

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

On Saturday, July 30, 2016 05:53:21 Joshua Cearley wrote:
> > I just committed something to SVN which should fix this issue in more
> > general way (gigedit 1.0.0.svn21 / SVN revision 2976). Because this bug
> > was actually also triggered when interacting with the dimension manager
> > dialog in other ways as well.
> > 
> > Let me know if it works for you, and if not, please tell me which precise
> > GTKMM version you are using on your system.
> > 
> > By the way: the "sample channel" dimension is usually automatically
> > created
> > for you when you assign a stereo sample to your dimension region(s). And
> > that particular dimension type only has a meaning with stereo samples. So
> > usually there should be no need to create that dimension type manually.
> 
> I can confirm that the latest SVN no longer crashes when simply adding
> and removing dimensions.
> 
> Tree errors persist when attempting to add a dimension of a larger
> size than allowed. You see the "this would exceed 8 bits" message, and
> then gigedit crashes. (Attempting to merge multiple instruments can
> result in the same error, however the crash does not occur.)

The "would exceed 8 bits" error is caused by the fact that the original 
GigaStudio format only permitted up to 256 dimension regions. So that's 
normal. I also hit this limit once in a while, so I thought about raising it 
(as unofficial format extension). We will see.

Obviously however gigedit should not crash in this case. Am I right that just 
before this crash happens the "Change Dimension Type" dialog appears 
unexpectedly and then you close the "Dimension Manager" dialog which results 
in the crash, right?

CU
Christian

Re: [Linuxsampler-devel] gigedit crashes when adding dimensions

[Joshua C. <jos...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


> I just committed something to SVN which should fix this issue in more general
> way (gigedit 1.0.0.svn21 / SVN revision 2976). Because this bug was actually
> also triggered when interacting with the dimension manager dialog in other
> ways as well.
>
> Let me know if it works for you, and if not, please tell me which precise
> GTKMM version you are using on your system.
>
> By the way: the "sample channel" dimension is usually automatically created
> for you when you assign a stereo sample to your dimension region(s). And that
> particular dimension type only has a meaning with stereo samples. So usually
> there should be no need to create that dimension type manually.

I can confirm that the latest SVN no longer crashes when simply adding
and removing dimensions.

Tree errors persist when attempting to add a dimension of a larger
size than allowed. You see the "this would exceed 8 bits" message, and
then gigedit crashes. (Attempting to merge multiple instruments can
result in the same error, however the crash does not occur.)

$ pkg-config --version gtkmm
0.29.1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXnIceAAoJEPq43HY1YMclmkEH/jNGemlB5Z7l2NGiJvfY6EhZ
0uhDnjboDyFpYu+kGuiwN18EaFXPqLAjAknCxqfDOSpY6l5k9cyOwOKcPY5tsMRD
mLkULmLOU4pQWDyzUdgOzYvwaj6ImhwuL6L34XmIl5PcPBwylWUImNDgm8K6+ZNg
wBTH/AgeTqQ5ldHcz9h4tF72c8XLLEj5NTM6NCfVMqQ8FQolSNtG9hiOxpK6LSFV
TqFwSxWLKdlSGR8jEWQk3rK4yz3r4G0g1fFzohYZmHOKBdRKba2QNL4yomuBAkOF
qO00W+NDF24MWQdXV/bqdxcMRt74/YOmskZS/b2Naqp6lppP3uMXIUB9Q2G6rkY=
=5PRv
-----END PGP SIGNATURE-----

Re: [Linuxsampler-devel] gigedit crashes when adding dimensions (+ a patch)

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

On Wednesday, July 27, 2016 23:34:16 Joshua Cearley wrote:
> I found that gigedit has a fatal assertion error when attempting to
> add dimensions to a region which already has a Sample dimension. If
> there is no sample loaded in an instrument, no crash. 

As far as I can see it this is not actually related to the "sample channel" 
dimension. This crash seems to happen with any dimension type. It's actually 
rather related to whether you closed the dimension manager dialog in between. 
That is i.e.:

1. Open dimension manager dialog.
2. Add some dimension.
3. Close dimension manager dialog.
4. Open dimension manager dialog
5. Add another dimension -> Crash.

> It appears the
> assertion is caused by a tree being updated in the middle of the
> change. The system in question is an Arch x86 machine (so, the latest
> gtk3 et all is installed.)
> 
> This patch works around the crash. I've been able to put together a
> few simple gig files with multiple dimension regions after writing it.

I just committed something to SVN which should fix this issue in more general 
way (gigedit 1.0.0.svn21 / SVN revision 2976). Because this bug was actually 
also triggered when interacting with the dimension manager dialog in other 
ways as well.

Let me know if it works for you, and if not, please tell me which precise 
GTKMM version you are using on your system.

By the way: the "sample channel" dimension is usually automatically created 
for you when you assign a stereo sample to your dimension region(s). And that 
particular dimension type only has a meaning with stereo samples. So usually 
there should be no need to create that dimension type manually.

CU
Christian

[Linuxsampler-devel] gigedit crashes when adding dimensions (+ a patch)

[Joshua C. <jos...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I found that gigedit has a fatal assertion error when attempting to
add dimensions to a region which already has a Sample dimension. If
there is no sample loaded in an instrument, no crash. It appears the
assertion is caused by a tree being updated in the middle of the
change. The system in question is an Arch x86 machine (so, the latest
gtk3 et all is installed.)

This patch works around the crash. I've been able to put together a
few simple gig files with multiple dimension regions after writing it.

- -JC

diff --git a/src/gigedit/dimensionmanager.cpp b/src/gigedit/dimensionmanager.cpp
index 9724f91..fc73771 100644
- --- a/src/gigedit/dimensionmanager.cpp
+++ b/src/gigedit/dimensionmanager.cpp
@@ -521,6 +521,7 @@ void DimensionManager::onColumnClicked() {

 void DimensionManager::addDimension() {
     Gtk::Dialog dialog(_("New Dimension"), true /*modal*/);
+    ignoreColumnClicked = true;
     // add dimension type combo box to the dialog
     Glib::RefPtr<Gtk::ListStore> refComboModel =
Gtk::ListStore::create(comboModel);
     for (int i = 0x01; i < 0xff; i++) {
@@ -657,9 +658,11 @@ void DimensionManager::addDimension() {
             msg.run();
         }
     }
+    ignoreColumnClicked = false;
 }

 void DimensionManager::removeDimension() {
+    ignoreColumnClicked = true;
     Glib::RefPtr<Gtk::TreeSelection> sel = treeView.get_selection();
     Gtk::TreeModel::iterator it = sel->get_selected();
     if (it) {
@@ -724,4 +727,5 @@ void DimensionManager::removeDimension() {
             msg.run();
         }
     }
+    ignoreColumnClicked = false;
 }
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXmYsZAAoJEPq43HY1YMcl9v8H/j9s7n4logi3BAfgdRhyUpGj
qwYRmiysz12r/CWZ9MF2cxg613UesDQcMfuDZOyqUXQrmfW+zjSdLqkH+InWC7Vi
Fm2jCAb/dBol8/bUK0yu7YKAjoD2l2hYZYCCQDHSTE4tnPBXqRWB1LqEEse9z7x9
+YScOO2rtHfhrPKTucQknyjDa7isSxXDCzmstirA5jIFpHLhlXewWA+13wEWRJRU
wEho/DkDd6vaFDPdTM7yVXqYDIVS9pkrEXar4N+4/St3oa8WrYRnMzKzSFYBqEVg
5/NK53tCgvmoCChSrrgTuR37idw6Cfs/bWrHMZRGvzQJYPXXgjeJK6wnHXg+K3k=
=Tclz
-----END PGP SIGNATURE-----

Re: [Linuxsampler-devel] Fwd: LS licensing -- was Linuxsampler and Zynthian Project

[RDP <gli...@gm...>]

On 11 July 2016 at 11:25, Christian Schoenebeck
<sch...@li...> wrote:
> On Sunday, July 10, 2016 19:19:47 RDP wrote:
>> On 9 July 2016 at 12:49, Christian Schoenebeck

> Even though I am not convinced about phpbb's overall settings design, in this
> particular case there is no issue. It behaves just as expected. The sorting
> criteria in the forum is:
>
>         1. is topic "sticky"?
>         2. time stamp of last post of topic
>
> So the sticky topics are displayed always before non-sticky topics, and both
> are then sorted by criteria 2. And when you look at the topics of the forum,
> it really did that.

The definition of what is 'sticky', and whether it should be classed as so,  is
debatable ( and configurable ).  For example how can a topic be considered
sticky, in other words easily accessible and current, when it has last post
date of Sat Mar 22, 2014 9:50 am??

Current/recent topics, really should bubble to the top of a board.  If
this is not
the case then a board just stagnates.. which is what seems to have happened
to the linuxsampler one..

Regards,


Chris.

Re: [Linuxsampler-devel] Fwd: LS licensing -- was Linuxsampler and Zynthian Project

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

On Sunday, July 10, 2016 19:19:47 RDP wrote:
> On 9 July 2016 at 12:49, Christian Schoenebeck
> 
> <sch...@li...> wrote:
> > On Thursday, July 07, 2016 18:56:40 RDP wrote:
> >> You mentioned previously, bumping licensing to a separate forum
> >> section, and making it 'sticky'.  Possily still worth doing, so as the
> >> matter doesn't get lost in the myriad of postings! ;o)
> > 
> > As soon as there is some real activity on that matter I will make the post
> > sticky. And in case this issue really spawns several "hot" topics on the
> > forum one day, then I'll make a separate forum section and move those
> > posts there. However ATM there is no reasonable general forum activity
> > right now anyway.
> A post will only spawn 'hot topics' if it can be found, and not lost
> in either the deafening
> silence or the noise!  

There is currently no information in that particular post yet. As said, as 
soon as there is some real activity, I will take the appropriate actions 
(sticky, separate section, etc.).

> For example, surely recent ( as in by date and
> time ) posts  should bubble to the top of the board by default, taking
> the appropriate board topic with it?  Dates and topics seem to be all
> over the shop.  Humbly and respectfully suggest those board settings
> need tweaking a tad! ;o)

Even though I am not convinced about phpbb's overall settings design, in this 
particular case there is no issue. It behaves just as expected. The sorting 
criteria in the forum is:

	1. is topic "sticky"?
	2. time stamp of last post of topic

So the sticky topics are displayed always before non-sticky topics, and both 
are then sorted by criteria 2. And when you look at the topics of the forum, 
it really did that.

CU
Christian

[Linuxsampler-devel] Fwd: LS licensing -- was Linuxsampler and Zynthian Project

[RDP <gli...@gm...>]

On 9 July 2016 at 12:49, Christian Schoenebeck
<sch...@li...> wrote:
> On Thursday, July 07, 2016 18:56:40 RDP wrote:
>> You mentioned previously, bumping licensing to a separate forum
>> section, and making it 'sticky'.  Possily still worth doing, so as the
>> matter doesn't get lost in the myriad of postings! ;o)
>
> As soon as there is some real activity on that matter I will make the post
> sticky. And in case this issue really spawns several "hot" topics on the forum
> one day, then I'll make a separate forum section and move those posts there.
> However ATM there is no reasonable general forum activity right now anyway.

A post will only spawn 'hot topics' if it can be found, and not lost
in either the deafening
silence or the noise!  For example, surely recent ( as in by date and
time ) posts  should bubble to the top of the board by default, taking
the appropriate board topic with it?  Dates and topics seem to be all
over the shop.  Humbly and respectfully suggest those board settings
need tweaking a tad! ;o)

Cheers!


Chris.

Re: [Linuxsampler-devel] Kontakt KSP scripts & endless loops

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

On Saturday, July 09, 2016 17:13:24 Christian Schoenebeck wrote:
> Intuitively the right way to fix the upper script, would be something like
> this:
> 
> on note
>   while (1)
>     wait(200000)
>     if (note_is_gone($EVENT_ID))
>       exit()
>     end if
>     change_vol($EVENT_ID, -20000)
> 
>     wait(200000)
>     if (note_is_gone($EVENT_ID))
>       exit()
>     end if
>     change_vol($EVENT_ID, 0)
>   end while
> end on
> 
> But as far as I can see it, Kontakt does not provide a built-in function
> (like "note_is_gone()" in the latter pseudo solution) for checking whether
> notes/voices are gone, is there any?

Never mind guys. I just found out Kontakt got a function event_status() which 
just does this.

CU
Christian

[Linuxsampler-devel] Kontakt KSP scripts & endless loops

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

Any Kontakt users out there?

As I've just been working on adding synthesis parameter functions to our 
instrument script engine, I wondered how endless loops are usually hanndled 
with Kontakt KSP scripts?

Let's assume you want to implement a simple stuttering effect by using an 
instrument script, you could do it like with the following one:

on note
  while (1)
    wait(200000)
    change_vol($EVENT_ID, -20000)
    wait(200000)
    change_vol($EVENT_ID, 0)
  end while
end on

This works, however the problem is that this script will run forever, even if 
your note and/or voices are long dead and gone. So since execution of this 
particular script will *never* stop, this is certainly not what you want to 
end with. How do Kontakt KSP script authors usually handle this?

Intuitively the right way to fix the upper script, would be something like 
this:

on note
  while (1)
    wait(200000)
    if (note_is_gone($EVENT_ID))
      exit()
    end if
    change_vol($EVENT_ID, -20000)

    wait(200000)
    if (note_is_gone($EVENT_ID))
      exit()
    end if
    change_vol($EVENT_ID, 0)
  end while
end on

But as far as I can see it, Kontakt does not provide a built-in function (like 
"note_is_gone()" in the latter pseudo solution) for checking whether 
notes/voices are gone, is there any?

Another "solution" would be to force quitting execution of such an endless 
script by the script engine itself as soon as the respective notes/voices are 
gone. But IMO auto killing scripts would not be a desirable solution either, 
because a script author might intentionally i.e. want to trigger new voices 
with play_note() after the original voices are gone (i.e. for delay effects). 
So IMO it should be up to the script author to define when his endless loops 
should stop and when not.

Anybody?

BTW, these are the 3 new NKSP functions just been added & implemented:

http://doc.linuxsampler.org/Instrument_Scripts/NKSP_Language/Reference/change_vol_function/
http://doc.linuxsampler.org/Instrument_Scripts/NKSP_Language/Reference/change_tune_function/
http://doc.linuxsampler.org/Instrument_Scripts/NKSP_Language/Reference/change_pan_function/

CU
Christian

Re: [Linuxsampler-devel] LS licensing -- was Linuxsampler and Zynthian Project

[Robin G. <ro...@ga...>]

On 07/07/2016 07:56 PM, RDP wrote:
> On 6 July 2016 at 17:28, Christian Schoenebeck
> <sch...@li...> wrote:
[..]
>> Anyway, I approved your forum user, so you should be able to post now on all
>> forums without moderation. And I also changed the board's settings so that
>> newly registered users can at least immediately post on the "Newbies &
>> Support" section without having to wait for a moderator passing by after
>> weeks. ;-)
> 
> Thank you.  After recent list exchanges I decided to start the ball
> rolling.. however, I rather suspect now, that apathy will reign and
> silence on the matter will be truly deafening!
> 
> You mentioned previously, bumping licensing to a separate forum
> section, and making it 'sticky'.  Possily still worth doing, so as the
> matter doesn't get lost in the myriad of postings! ;o)

Cool, thanks a lot.

I do have a drafted reply to an earlier message on the ML here. I'll
copy that over there.

Cheers!
robin

Re: [Linuxsampler-devel] LS licensing -- was Linuxsampler and Zynthian Project

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

On Thursday, July 07, 2016 18:56:40 RDP wrote:
> > Anyway, I approved your forum user, so you should be able to post now on
> > all forums without moderation. And I also changed the board's settings so
> > that newly registered users can at least immediately post on the "Newbies
> > & Support" section without having to wait for a moderator passing by
> > after weeks. ;-)
> 
> Thank you.  After recent list exchanges I decided to start the ball
> rolling.. however, I rather suspect now, that apathy will reign and
> silence on the matter will be truly deafening!

Yes, that happens mostly.

> You mentioned previously, bumping licensing to a separate forum
> section, and making it 'sticky'.  Possily still worth doing, so as the
> matter doesn't get lost in the myriad of postings! ;o)

As soon as there is some real activity on that matter I will make the post 
sticky. And in case this issue really spawns several "hot" topics on the forum 
one day, then I'll make a separate forum section and move those posts there. 
However ATM there is no reasonable general forum activity right now anyway.

CU
Christian

Re: [Linuxsampler-devel] LS licensing -- was Linuxsampler and Zynthian Project

[RDP <gli...@gm...>]

On 6 July 2016 at 17:28, Christian Schoenebeck
<sch...@li...> wrote:
> On Sunday, July 03, 2016 20:12:12 RDP wrote:
>> On 2 July 2016 at 12:47, Christian Schoenebeck
>>
>> <sch...@li...> wrote:
> I was not even aware that posts of newly registered users were forced for
> moderation. Quite a bunch of permission levels with phpbb which make it
> confusing sometimes to see which permissions actually apply.

One learns something every day, doesn't one? ;o)    I have similar
issues keeping track of  a mediawiki installation ( for another, now
well unmaintained 'legacy'  project ). on one of my servers.

> Anyway, I approved your forum user, so you should be able to post now on all
> forums without moderation. And I also changed the board's settings so that
> newly registered users can at least immediately post on the "Newbies &
> Support" section without having to wait for a moderator passing by after
> weeks. ;-)

Thank you.  After recent list exchanges I decided to start the ball
rolling.. however, I rather suspect now, that apathy will reign and
silence on the matter will be truly deafening!

You mentioned previously, bumping licensing to a separate forum
section, and making it 'sticky'.  Possily still worth doing, so as the
matter doesn't get lost in the myriad of postings! ;o)

Regards,


Chris.

[Linuxsampler-devel] Bug Tracker back online

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

Just for your information: you might have noticed that our Bug Tracker

	http://bugs.linuxsampler.org/

was partly unavailable (old reports were readable, but i.e. new user 
registrations were impossible).

I just corrected those issues now, so the entire site should work again as 
expected.

CU
Christian

Re: [Linuxsampler-devel] LS licensing -- was Linuxsampler and Zynthian Project

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

On Sunday, July 03, 2016 20:12:12 RDP wrote:
> On 2 July 2016 at 12:47, Christian Schoenebeck
> 
> <sch...@li...> wrote:
> > Well, you can simply start a topic on bb.linuxsampler.org and update your
> > (i.e. upper most) post with the latest version of the text. Of course I
> > can
> > also make a separate forum section and make the specific thread with the
> > license text sticky (so that it stays on top).
> 
> Initial posting on the matter, submitted by user RedDwarfPlanet.  Once
> moderated, t'will appear
> under General LinuxSampler Discussion.

I was not even aware that posts of newly registered users were forced for 
moderation. Quite a bunch of permission levels with phpbb which make it 
confusing sometimes to see which permissions actually apply.

Anyway, I approved your forum user, so you should be able to post now on all 
forums without moderation. And I also changed the board's settings so that 
newly registered users can at least immediately post on the "Newbies & 
Support" section without having to wait for a moderator passing by after 
weeks. ;-)

CU
Christian

Re: [Linuxsampler-devel] LS licensing -- was Linuxsampler and Zynthian Project

[RDP <gli...@gm...>]

On 2 July 2016 at 12:47, Christian Schoenebeck
<sch...@li...> wrote:
> Well, you can simply start a topic on bb.linuxsampler.org and update your
> (i.e. upper most) post with the latest version of the text. Of course I can
> also make a separate forum section and make the specific thread with the
> license text sticky (so that it stays on top).

Initial posting on the matter, submitted by user RedDwarfPlanet.  Once
moderated, t'will appear
under General LinuxSampler Discussion.

Away you go..  ;o)


Chris.

Re: [Linuxsampler-devel] LS licensing -- was Linuxsampler and Zynthian Project

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

On Wednesday, June 29, 2016 21:09:20 Robin Gareus wrote:
> On 06/29/2016 08:17 PM, RDP wrote:
> > On 28 June 2016 at 23:12, Robin Gareus <ro...@ga...> wrote:
> >> On 06/28/2016 11:39 PM, Christian Schoenebeck wrote:
> >>> .. if you really want license issues to be addressed, sit down,
> >>> elaborate and suggest clear license terms by yourself which could
> >>> become a candidate to resolve those overall issues.
> >> 
> >> Ok here it goes: I suggest to take the GPLv2. amend Section 1 with the
> >> non commercial exception and change the name to LinuxSampler License.
> > 
> > Might it not be a good idea for this discussion to be taken here,
> > 
> >    http://bb.linuxsampler.org/
> > 
> > .. with some drafts published  ( wiki style ), so that such a beast
> > can be formalised?
> 
> wiki-style sounds good to me. As to where I don't care. Does
> http://bb.linuxsampler.org/ facilitate editing a shared topic?
> or a google-doc or page on wiki.linuxaudio.org - Can you set this up?
> 
> As for discussion while editing #lad IRC on freenode.net
>    http://webchat.freenode.net/?channels=lad
> would be a good idea.

Well, you can simply start a topic on bb.linuxsampler.org and update your 
(i.e. upper most) post with the latest version of the text. Of course I can 
also make a separate forum section and make the specific thread with the 
license text sticky (so that it stays on top).

Whether there is some kind of shared/wiki feature on the forum, I don't know, 
it's a (more or less) standard phpbb installation after all. So you may check 
that on the phpbb website.

Since the license is a fundamental issue of this project, I would rather 
prefer to keep its discussions and working versions on our sites.

> ..to roll the ball a bit further, the goal is a proper valid license
> which directly answers the following questions without doubt:
> 
> 
>   * Under what conditions can I use Linuxsamler ?
> use: GPL

Why? If there is going to be specific clear license text (whatever it will be 
named) then that should apply.

>   * Can I change linuxsampler and redistribute the sources?
> 
> yes, that's how you send patches & contribute

Yes, but the commercial exceptions stay valid. So that means the distribution 
might be OK (i.e. consider a public web server) but the user might face the 
actual restrictions (requires permission for commercial products).

>   * Can I build and distribute binaries not for profit? Even if the
> target host is a commercial system?
> 
> probably :)  --- needs clarification

What exactly did you have in mind?

>  * Can automate compilation and binary distribution not for profit
> ...and accept donations for it? --  Even if the target host is a
> commercial system?
> 
> probably not. --- needs clarification

If it is really a "donation" and not a hidden way to force the user charging 
for something, then yes it should be OK. My understanding of a "donation" is 
that the user is not forced in any way to actually donate/pay, right? However 
there are some sites which claim to provide software for a donation, and you 
have no way to get that specific software (version) without "donating". So the 
latter is not actually a donation from my point of view.

>   * Who needs to accept the license?
> 
> both: distributor and user.

Sure, everybody who "does" something with the software needs to act according 
to the license.

>   * Can I include binaries pre-installed on commercial hardware?
> 
> No.

Of course not. Commercial actors need prior permission to do so.

>   * Can I use GPLed parts of the source in a GPLv2 application?
> 
> I suppose so. --- needs clarification

No, the sources were released with commercial exception from day one (even the 
proof of concept code where I was not even on board yet). When there is a 
final license text, I would probably talk with the developers and update the 
header of the individual files one by one to explicitly clarify for the source 
code reader which exact terms apply to which source file. For certain source 
files it would make sense to release them under pure GPL.

>   * What commercial licensing options are available?
> 
> -> send email to ...

Yes, or it would also be possible to create a commercial license text as well 
and release the software dual licensed that way. But obviously that has less 
priority than clarifying the non-commercial license first.

CU
Christian