robertaramar wrote:thanks for the answer. I guess I will not subscribe to the mailing list. I am really, really old, but mailing-lists are still older

Isn't there any other way to communicate with the devs?
You mean like a LinuxSampler WhatsApp group?

No, the only reliable and fastest way to discuss developer issues is the
linuxsampler-devel maling list. It is simply the least common denominator, because not everybody uses Google+, FB, etc. , but everybody got an email address. I would agree with you if it was an 80s style newsgroup (where you had to use special clients etc.), but in case of mailing lists I don't really see a disadvantage.
robertaramar wrote:I don't know whether this is the proper fix, but it cures my problem:
InstrumentsDb.cpp#1654:
int res = sqlite3_bind_text(pStmt, Index, Text.c_str(), -1, SQLITE_TRANSIENT);
That fix is correct. SQLITE_TRANSIENT causes the supplied Text to be copied immediately, which was not the case with SQLITE_STATIC, and hence this was a severe bug causing undefined behavior of libsqlite, since "Text" is just a temporary variable.
I am not used to the instruments DB code, but there may still be further bugs like this one. For example sqlite3_prepare() should probably be replaced by sqlite3_prepare_v3(). The
SQLite docs are not clear on that, but it could be that the old sqlite3_prepare() function is not copying the original SQL statement text, which then might also cause undefined behavior due to the same cause as above.