Christian, Thanks. Your explanation of binary midi is clear to me and is equal to the decimal jOrgan midi.
jOrgan uses the LSCP protocol through localhost/8888 to send the .lscp file. jOrgan uses midi protocol through an midiport to toggle note on/off and toggle stops on/off. Fantasia/QSampler use LSCP protocol to toggle note on/off and toggle stops on/off. That works fine in jOrgan, but not using in SFZ trigger=release to play a given release part of a sample. Is this an error of Linuxsampler? How to play a given release part of a sample GIG/SFZ through MIDI? Kind regards, Jan Flikweert -------------------------- -----Original Message----- From: Christian Schoenebeck [mailto:schoeneb...@linuxsampler.org] Sent: maandag 27 december 2021 16:29 To: linuxsampler-devel@lists.sourceforge.net Subject: Re: [Linuxsampler-devel] midi message fantasia note off On Sonntag, 26. Dezember 2021 22:13:05 CET Jan Flikweert wrote: > Hi, > > I will explain my problem. > > I am working with release samples/sfz. This works good using fantasia. Not > good using jOrgan. jOrgan/Linuxsampler works very good, but without > release. JSampler and QSampler both control the sampler purely via network protocol (called "LSCP"), in this case it is this LSCP command: SEND CHANNEL MIDI_DATA <midi-msg> <sampler-chan> <arg1> <arg2> http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html#rfc.section .6.4.39 > I suppose it has to do with the note_off/note_on messages in > jOrgan. Note on in jorgan is only set 144,set 36, set velocity. Note off is > set 128,set 36,.. and set 176,set 1, set 0 which is cc 1. MIDI note-off is [1]: 1000nnnn 0kkkkkkk 0vvvvvvv MIDI note-on is: 1001nnnn 0kkkkkkk 0vvvvvvv MIDI control change is: 1011nnnn 0ccccccc 0vvvvvvv Where nnnn is the MIDI channel number (0..15) kkkkkkk is the key/note number (0..127) ccccccc is the controller number (0..127) vvvvvvv is velocity (note-on / note-off) or the new controller value (0..127) (control change) Note: - Note-On with velocity 0 means "note-off". - MIDI allows to omit the status byte on subsequent messages, which is called "running status". That's basically just a simple way of data compression [2]. [1] https://www.midi.org/specifications-old/item/table-1-summary-of-midi-message [2] http://midi.teragonaudio.com/tech/midispec/run.htm CU Christian _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
