|
From: Jan F. <fl...@ze...> - 2021-12-26 11:57:50
|
Hi all, Which midi messages does Fantasia send for a note-off event after releasing a key on the keyboard from its main screen? I tried with midi-ox but that did not work. Kind regards, Jan Flikweert |
|
From: Andrew C <cou...@gm...> - 2021-12-26 16:48:24
|
Hi Jan,
I would imagine it's a simple enough NOTE_OFF event is all. Just to
illustrate the code from jlscp's event/MidiDataEvent:
ackage org.linuxsampler.lscp.event;
/**
* A semantic event which indicates that MIDI data has arrived.
* @author Grigor Iliev
*/
public class MidiDataEvent extends java.util.EventObject {
public static enum Type {
NOTE_ON ("NOTE_ON"),
NOTE_OFF ("NOTE_OFF"),
CC ("CC");
Andrew.
On Sun, Dec 26, 2021 at 11:58 AM Jan Flikweert <fl...@ze...> wrote:
> Hi all,
>
>
>
> Which midi messages does Fantasia send for a note-off event after
> releasing a key on the keyboard from its main screen?
>
>
>
> I tried with midi-ox but that did not work.
>
>
>
> Kind regards,
>
>
>
> Jan Flikweert
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>
|
|
From: Jan F. <fl...@ze...> - 2021-12-26 21:13:11
|
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. 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.
Kind regards,
Jan Flikweert
From: Andrew C [mailto:cou...@gm...]
Sent: zondag 26 december 2021 17:48
To: Jan Flikweert
Cc: linuxsampler-devel
Subject: Re: [Linuxsampler-devel] midi message fantasia note off
Hi Jan,
I would imagine it's a simple enough NOTE_OFF event is all. Just to illustrate the code from jlscp's event/MidiDataEvent:
ackage org.linuxsampler.lscp.event;
/**
* A semantic event which indicates that MIDI data has arrived.
* @author Grigor Iliev
*/
public class MidiDataEvent extends java.util.EventObject {
public static enum Type {
NOTE_ON ("NOTE_ON"),
NOTE_OFF ("NOTE_OFF"),
CC ("CC");
Andrew.
On Sun, Dec 26, 2021 at 11:58 AM Jan Flikweert <fl...@ze...> wrote:
Hi all,
Which midi messages does Fantasia send for a note-off event after releasing a key on the keyboard from its main screen?
I tried with midi-ox but that did not work.
Kind regards,
Jan Flikweert
_______________________________________________
Linuxsampler-devel mailing list
Lin...@li...
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
|
|
From: Christian S. <sch...@li...> - 2021-12-27 15:28:47
|
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 |
|
From: Jan F. <fl...@ze...> - 2021-12-28 06:07:59
|
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:sch...@li...] Sent: maandag 27 december 2021 16:29 To: lin...@li... 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 Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: Jan F. <fl...@ze...> - 2021-12-28 07:01:25
|
Christian, Probably more clear I translated the midi messages I send from jOrgan to LSCP: Note on: "SEND CHANNEL MIDI_DATA NOTE_ON 0 60 127" Note off: "SEND CHANNEL MIDI_DATA NOTE_OFF 0 60 0" Instrument/Stop on: "SEND CHANNEL MIDI_DATA CC 0 7 127" Instrument/Stop off: "SEND CHANNEL MIDI_DATA CC 0 1 0" "SEND CHANNEL MIDI_DATA CC 0 7 0" Kind regards, Jan Flikweert -----Original Message----- From: Christian Schoenebeck [mailto:sch...@li...] Sent: maandag 27 december 2021 16:29 To: lin...@li... 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 Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: Christian S. <sch...@li...> - 2021-12-29 17:44:27
|
On Dienstag, 28. Dezember 2021 08:01:06 CET Jan Flikweert wrote: > Christian, > > Probably more clear I translated the midi messages I send from jOrgan to > LSCP: > > Note on: > > "SEND CHANNEL MIDI_DATA NOTE_ON 0 60 127" > > Note off: > > "SEND CHANNEL MIDI_DATA NOTE_OFF 0 60 0" That's a note-off, hence release triggered samples *are* played at this point. > Instrument/Stop on: > > "SEND CHANNEL MIDI_DATA CC 0 7 127" That means "set channel volume to maximum". No release sample played. > Instrument/Stop off: > > "SEND CHANNEL MIDI_DATA CC 0 1 0" That means "set Modulation Wheel to minimum". No release sample played. > "SEND CHANNEL MIDI_DATA CC 0 7 0" That means "set channel volume to minimum". No release sample played. Release triggered samples are only played if *notes* are released, which is e.g. on note-off, sustain release CC, exclusive groups conflicts. That's the expected behaviour, not a bug, and is consistent among all players, not just LS. If you turn the volume down to zero, the notes are still there. They continue to play and still advance their playback positions accordingly. You just can't hear them, but that's it. If you want to play samples on CCs, you have to use CC triggered samples instead. That's supported on patch level both by SFZ and gig format. Additionally you can also write an NKSP script if you really want some fancy behaviour that goes beyond of what the built-in patch CC triggered mechanisms can do. CU Christian |
|
From: Jan F. <fl...@ze...> - 2021-12-29 20:59:29
|
Christian, Thanks for your explanation. I conclude that it is only needed to set notes on/off. Stops do not need on/off. If you do not need a instrument, do not sent notes to it. The next file sample-release-060-C.wav contains a sinus tone 220 hz. The file sample-Default-060-C.wav a normal principal. Using Fantasia / Linuxsampler works well. jOrgan / Linuxsampler does not work for the release part (only note on/off!) jOrgan / sForzando works correct sForzando is not advisable because it cannot handle large organs. Linuxsampler provides for me a beautiful organ with 150 instruments/stops. Of course they are not needed all at one time, but LS can handle them, load them. Kind regards, Jan Flikweert ------------------------------------- Test.sfz <group> lokey=36 hikey=96 <region> sample=release-060-C.wav trigger=release loop_mode=one_shot <region> sample=Default-060-C.wav loop_mode=loop_sustain loop_start=97041 loop_end=163161 ------------------------------------------- Kind regards, Jan Flikweert -----Original Message----- From: Christian Schoenebeck [mailto:sch...@li...] Sent: woensdag 29 december 2021 18:44 To: lin...@li... Subject: Re: [Linuxsampler-devel] midi message fantasia note off On Dienstag, 28. Dezember 2021 08:01:06 CET Jan Flikweert wrote: > Christian, > > Probably more clear I translated the midi messages I send from jOrgan to > LSCP: > > Note on: > > "SEND CHANNEL MIDI_DATA NOTE_ON 0 60 127" > > Note off: > > "SEND CHANNEL MIDI_DATA NOTE_OFF 0 60 0" That's a note-off, hence release triggered samples *are* played at this point. > Instrument/Stop on: > > "SEND CHANNEL MIDI_DATA CC 0 7 127" That means "set channel volume to maximum". No release sample played. > Instrument/Stop off: > > "SEND CHANNEL MIDI_DATA CC 0 1 0" That means "set Modulation Wheel to minimum". No release sample played. > "SEND CHANNEL MIDI_DATA CC 0 7 0" That means "set channel volume to minimum". No release sample played. Release triggered samples are only played if *notes* are released, which is e.g. on note-off, sustain release CC, exclusive groups conflicts. That's the expected behaviour, not a bug, and is consistent among all players, not just LS. If you turn the volume down to zero, the notes are still there. They continue to play and still advance their playback positions accordingly. You just can't hear them, but that's it. If you want to play samples on CCs, you have to use CC triggered samples instead. That's supported on patch level both by SFZ and gig format. Additionally you can also write an NKSP script if you really want some fancy behaviour that goes beyond of what the built-in patch CC triggered mechanisms can do. CU Christian _______________________________________________ Linuxsampler-devel mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: Christian S. <sch...@li...> - 2021-12-30 18:22:29
|
On Mittwoch, 29. Dezember 2021 21:59:13 CET Jan Flikweert wrote: > Christian, > > Thanks for your explanation. I conclude that it is only needed to set notes > on/off. Stops do not need on/off. If you do not need a instrument, do not > sent notes to it. > > The next file sample-release-060-C.wav contains a sinus tone 220 hz. The > file sample-Default-060-C.wav a normal principal. > > Using Fantasia / Linuxsampler works well. > jOrgan / Linuxsampler does not work for the release part (only note on/off!) > jOrgan / sForzando works correct > > sForzando is not advisable because it cannot handle large organs. > Linuxsampler provides for me a beautiful organ with 150 instruments/stops. > Of course they are not needed all at one time, but LS can handle them, load > them. > > Kind regards, > > Jan Flikweert > > ------------------------------------- > Test.sfz > <group> > lokey=36 > hikey=96 > > <region> > sample=release-060-C.wav > trigger=release > loop_mode=one_shot > > <region> > sample=Default-060-C.wav > loop_mode=loop_sustain > loop_start=97041 > loop_end=163161 > ------------------------------------------- Have you tried flipping the order of those two regions, i.e. release trigger region after attack region? CU Christian |
|
From: Jan F. <fl...@ze...> - 2021-12-30 21:04:46
|
Hi, I tried flipping the order of those regions. That did not work. Kind regards, Jan Flikweert -------------------- CU Wrote: Have you tried flipping the order of those two regions, i.e. release trigger region after attack region? CU Christian |
|
From: Christian S. <sch...@li...> - 2021-12-31 18:12:03
|
On Donnerstag, 30. Dezember 2021 22:04:37 CET you wrote: > Hi, > > I tried flipping the order of those regions. That did not work. > > Kind regards, Fixed. Works now as expected: http://svn.linuxsampler.org/cgi-bin/viewvc.cgi?view=revision&revision=4013 The order of the regions in the sfz file does not matter for LS BTW. I just saw before that it does for other players. CU Christian |
|
From: Jan F. <fl...@ze...> - 2022-01-01 17:52:35
|
CU wrote: Fixed. Works now as expected: http://svn.linuxsampler.org/cgi-bin/viewvc.cgi?view=revision&revision=4013 The order of the regions in the sfz file does not matter for LS BTW. I just saw before that it does for other players. CU Christian -------------- Thank you very much for this solution and the things I learned. It works. Kind regards, Jan Flikweert |
|
From: Jan F. <fl...@ze...> - 2022-01-02 07:27:31
|
JanFl. Wrote:" Thank you very much for this solution and the things I learned. It works." The solution does not work for gig files. The funny thing is that gig files can also play a release sample after aloop from a sample. The dimension is called releasetrigger. One dimension has a normal loop and the release sample has no loop. Kind regards, Jan Fl. |
|
From: Doug G. <dou...@gm...> - 2022-01-02 12:00:42
|
For the record my Studiologic SL88 keyboard controller does send note off with a measured velocity value. I have verified this myself since the sfz file I am using has key off sounds. This velocity is measured at key release. I see the documentation states that the note on velocity is reused for note off but I suggest that that should only be the case when note off velocity is actually zero. I don’t think it is likely at least for triple sensor that ‘most midi controllers’ send zero velocity note-off. It would be good to verify this. Doug Gray > On 2 Jan 2022, at 6:28 pm, Jan Flikweert <fl...@ze...> wrote: > > JanFl. Wrote:" Thank you very much for this solution and the things I > learned. It works." > > The solution does not work for gig files. > > The funny thing is that gig files can also play a release sample after aloop > from a sample. The dimension is called releasetrigger. One dimension has a > normal loop and the release sample has no loop. > > Kind regards, > > > Jan Fl. > > > > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: Christian S. <sch...@li...> - 2022-01-02 12:18:12
|
Mja, that behaviour could likewise easily be adjusted for the gig engine as I did for the sfz engine this week. From the sfz docs I see, people seem to expect that the note-on velocity is always used instead of the note-off velocity? Hence I just changed that exactly this way for the sfz engine this week. For the gig engine: I agree with Dough here, if you have a keyboard that supports note-off velocity, you want to use it. But the fact that most MIDI keyboards just send note-off velocity zero still applies. So this must coexist. Doug, does your keyboard *ever* send a note-off with velocity zero? If it does not, then simply checking for velocity zero might indeed be the way to go. Maybe even for the sfy engine, too? CU Christian On Sonntag, 2. Januar 2022 13:00:28 CET Doug Gray wrote: > For the record my Studiologic SL88 keyboard controller does send note off > with a measured velocity value. I have verified this myself since the sfz > file I am using has key off sounds. This velocity is measured at key > release. I see the documentation states that the note on velocity is reused > for note off but I suggest that that should only be the case when note off > velocity is actually zero. I don’t think it is likely at least for triple > sensor that ‘most midi controllers’ send zero velocity note-off. It would > be good to verify this. > > Doug Gray > > > On 2 Jan 2022, at 6:28 pm, Jan Flikweert <fl...@ze...> wrote: > > > > JanFl. Wrote:" Thank you very much for this solution and the things I > > learned. It works." > > > > The solution does not work for gig files. > > > > The funny thing is that gig files can also play a release sample after > > aloop from a sample. The dimension is called releasetrigger. One > > dimension has a normal loop and the release sample has no loop. > > > > Kind regards, > > > > > > Jan Fl. > > > > > > > > _______________________________________________ > > Linuxsampler-devel mailing list > > Lin...@li... > > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: Jerash m. <rmo...@gm...> - 2022-01-02 13:43:08
|
Having worked with (and repairing) many midi keyboard controllers, I can say that release velocity is not very common. Mainly available on high range keyboard, often with weighted keys, piano style. Keyboard rubbers with triple sensors offer greater definition so to have the release velocity, but it can be implemented in the device firmware or not, at manufacturer’s choice. Keyboard rubber with double sensor could also do release velocity, but may miss some when the key is not fully pressed before actual release. Here, again, the sent message depends on firmware implementation. >I suggest that that should only be the case when note off velocity is actually zero. I do agree with this, it totally makes sense to me. My 2 cents, Raphaël > Le 2 janv. 2022 à 13:00, Doug Gray <dou...@gm...> a écrit : > > For the record my Studiologic SL88 keyboard controller does send note off with a measured velocity value. I have verified this myself since the sfz file I am using has key off sounds. This velocity is measured at key release. > I see the documentation states that the note on velocity is reused for note off but I suggest that that should only be the case when note off velocity is actually zero. > I don’t think it is likely at least for triple sensor that ‘most midi controllers’ send zero velocity note-off. It would be good to verify this. > > Doug Gray > >> On 2 Jan 2022, at 6:28 pm, Jan Flikweert <fl...@ze...> wrote: >> >> JanFl. Wrote:" Thank you very much for this solution and the things I >> learned. It works." >> >> The solution does not work for gig files. >> >> The funny thing is that gig files can also play a release sample after aloop >> from a sample. The dimension is called releasetrigger. One dimension has a >> normal loop and the release sample has no loop. >> >> Kind regards, >> >> >> Jan Fl. >> >> >> >> _______________________________________________ >> Linuxsampler-devel mailing list >> Lin...@li... >> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > > > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: Christian S. <sch...@li...> - 2022-01-02 13:53:43
|
On Sonntag, 2. Januar 2022 14:42:55 CET Jerash music wrote: > Having worked with (and repairing) many midi keyboard controllers, I can say > that release velocity is not very common. Mainly available on high range > keyboard, often with weighted keys, piano style. > > Keyboard rubbers with triple sensors offer greater definition so to have > the release velocity, but it can be implemented in the device firmware or > not, at manufacturer’s choice. Keyboard rubber with double sensor could > also do release velocity, but may miss some when the key is not fully > pressed before actual release. Here, again, the sent message depends on > firmware implementation. > >I suggest that that should only be the case when note off velocity is > >actually zero. > I do agree with this, it totally makes sense to me. > > My 2 cents, > Raphaël Ok, but the core question still is: can we expect keyboards *with* note-off velocity sensors to *never* send note-off velocity zero? CU Christian |
|
From: Jerash m. <rmo...@gm...> - 2022-01-02 17:19:24
|
> Le 2 janv. 2022 à 14:53, Christian Schoenebeck <sch...@li...> a écrit : > > On Sonntag, 2. Januar 2022 14:42:55 CET Jerash music wrote: >> Having worked with (and repairing) many midi keyboard controllers, I can say >> that release velocity is not very common. Mainly available on high range >> keyboard, often with weighted keys, piano style. >> >> Keyboard rubbers with triple sensors offer greater definition so to have >> the release velocity, but it can be implemented in the device firmware or >> not, at manufacturer’s choice. Keyboard rubber with double sensor could >> also do release velocity, but may miss some when the key is not fully >> pressed before actual release. Here, again, the sent message depends on >> firmware implementation. >>> I suggest that that should only be the case when note off velocity is >>> actually zero. >> I do agree with this, it totally makes sense to me. >> >> My 2 cents, >> Raphaël > > Ok, but the core question still is: can we expect keyboards *with* note-off > velocity sensors to *never* send note-off velocity zero? Mmm, …yes it may be possible. it may be possible to send a zero release velocity if the firmware calculates a release velocity and includes a « timeout » for the maximum release time, and then decides that timed out values are zero. But I have not expressly tested it, and each manufacturer could have his own vision. I’ve been explained by Yamaha that the three contact rubbers are especially useful for retriggering calculation of half pressed keys, but they did not talk about release velocity calculation. Maybe Doug Gray could try the following on his SL88 : « Release the key as slow as possible in about 4 seconds » to try to reach the minimum release velocity value. As the keyboard rubber has three contacts, it could potentially send a zero release velocity if you reach a timeout between two contacts releases. I’m not sure if it is humanly possible to reach this potential timeout, as the contact points are really really close. The real duration of this timeout is not documented so needs testing. Raphaël |
|
From: Doug G. <dou...@gm...> - 2022-01-03 01:59:04
|
I have run a test on the SL-88, the lowest reported release velocity seems to be 0x01. I have tried to release keys as gently as I can but have not yet seen a release velocity of zero. It’s easy to hit the 0x01 so I’m quite confident it is the lowest possible value. This was not what I expected but makes good sense. Doug Gray Sent from my iPhone > On 3 Jan 2022, at 4:19 am, Jerash music <rmo...@gm...> wrote: > > > >> Le 2 janv. 2022 à 14:53, Christian Schoenebeck <sch...@li...> a écrit : >> >>> On Sonntag, 2. Januar 2022 14:42:55 CET Jerash music wrote: >>> Having worked with (and repairing) many midi keyboard controllers, I can say >>> that release velocity is not very common. Mainly available on high range >>> keyboard, often with weighted keys, piano style. >>> >>> Keyboard rubbers with triple sensors offer greater definition so to have >>> the release velocity, but it can be implemented in the device firmware or >>> not, at manufacturer’s choice. Keyboard rubber with double sensor could >>> also do release velocity, but may miss some when the key is not fully >>> pressed before actual release. Here, again, the sent message depends on >>> firmware implementation. >>>> I suggest that that should only be the case when note off velocity is >>>> actually zero. >>> I do agree with this, it totally makes sense to me. >>> >>> My 2 cents, >>> Raphaël >> >> Ok, but the core question still is: can we expect keyboards *with* note-off >> velocity sensors to *never* send note-off velocity zero? > > Mmm, …yes it may be possible. > it may be possible to send a zero release velocity if the firmware calculates a release velocity and includes a « timeout » for the maximum release time, and then decides that timed out values are zero. > But I have not expressly tested it, and each manufacturer could have his own vision. > > I’ve been explained by Yamaha that the three contact rubbers are especially useful for retriggering calculation of half pressed keys, but they did not talk about release velocity calculation. > Maybe Doug Gray could try the following on his SL88 : « Release the key as slow as possible in about 4 seconds » to try to reach the minimum release velocity value. > As the keyboard rubber has three contacts, it could potentially send a zero release velocity if you reach a timeout between two contacts releases. I’m not sure if it is humanly possible to reach this potential timeout, as the contact points are really really close. The real duration of this timeout is not documented so needs testing. > > Raphaël > > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: Raphaël M. <rmo...@gm...> - 2022-01-03 18:30:09
|
thanks for the tests, it makes sense from a firmware perspective to set 0x01 as a minimum. I'll try to have a look at how another keyboard reacts when I have one at hand, probably during this week or next one, and I'll report back. Raphaël Le 03/01/2022 à 02:58, Doug Gray a écrit : > I have run a test on the SL-88, the lowest reported release velocity seems to be 0x01. I have tried to release keys as gently as I can but have not yet seen a release velocity of zero. It’s easy to hit the 0x01 so I’m quite confident it is the lowest possible value. > This was not what I expected but makes good sense. > Doug Gray > > > Sent from my iPhone > >> On 3 Jan 2022, at 4:19 am, Jerash music <rmo...@gm...> wrote: >> >> >> >>> Le 2 janv. 2022 à 14:53, Christian Schoenebeck <sch...@li...> a écrit : >>> >>>> On Sonntag, 2. Januar 2022 14:42:55 CET Jerash music wrote: >>>> Having worked with (and repairing) many midi keyboard controllers, I can say >>>> that release velocity is not very common. Mainly available on high range >>>> keyboard, often with weighted keys, piano style. >>>> >>>> Keyboard rubbers with triple sensors offer greater definition so to have >>>> the release velocity, but it can be implemented in the device firmware or >>>> not, at manufacturer’s choice. Keyboard rubber with double sensor could >>>> also do release velocity, but may miss some when the key is not fully >>>> pressed before actual release. Here, again, the sent message depends on >>>> firmware implementation. >>>>> I suggest that that should only be the case when note off velocity is >>>>> actually zero. >>>> I do agree with this, it totally makes sense to me. >>>> >>>> My 2 cents, >>>> Raphaël >>> Ok, but the core question still is: can we expect keyboards *with* note-off >>> velocity sensors to *never* send note-off velocity zero? >> Mmm, …yes it may be possible. >> it may be possible to send a zero release velocity if the firmware calculates a release velocity and includes a « timeout » for the maximum release time, and then decides that timed out values are zero. >> But I have not expressly tested it, and each manufacturer could have his own vision. >> >> I’ve been explained by Yamaha that the three contact rubbers are especially useful for retriggering calculation of half pressed keys, but they did not talk about release velocity calculation. >> Maybe Doug Gray could try the following on his SL88 : « Release the key as slow as possible in about 4 seconds » to try to reach the minimum release velocity value. >> As the keyboard rubber has three contacts, it could potentially send a zero release velocity if you reach a timeout between two contacts releases. I’m not sure if it is humanly possible to reach this potential timeout, as the contact points are really really close. The real duration of this timeout is not documented so needs testing. >> >> Raphaël >> >> _______________________________________________ >> Linuxsampler-devel mailing list >> Lin...@li... >> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel -- Raphaël |
|
From: Christian S. <sch...@li...> - 2022-01-04 16:18:38
|
I changed the behaviour for both the SFZ engine and gig engine to distinguish by note-off velocity being exactly zero for now: http://svn.linuxsampler.org/cgi-bin/viewvc.cgi?view=revision&revision=4020 That should fix expected release trigger behaviour for both keyboards with and without key release sensors appropriately. If it turns out that some MIDI keyboards with release sensors do send note-off velocity zero (which I doubt), then this behaviour can still be changed to some more complicated MIDI-learn mechanism. BTW the original MIDI v1 specs say keyboards that do not support note-off velocity should send 64 as note-off velocity value. Probably one of the very few mistakes made in the ancient MIDI specs, at least IMO. I haven't looked into latest MIDI v2 specs yet. I noticed though there was some voting process on a note-off related change on midi.org, that thread on midi.org is password protected though, so no idea what this was exactly about. CU Christian On Montag, 3. Januar 2022 19:29:58 CET Raphaël Mouneyres wrote: > thanks for the tests, it makes sense from a firmware perspective to set > 0x01 as a minimum. > > I'll try to have a look at how another keyboard reacts when I have one > at hand, probably during this week or next one, and I'll report back. > > Raphaël > > Le 03/01/2022 à 02:58, Doug Gray a écrit : > > I have run a test on the SL-88, the lowest reported release velocity seems > > to be 0x01. I have tried to release keys as gently as I can but have not > > yet seen a release velocity of zero. It’s easy to hit the 0x01 so I’m > > quite confident it is the lowest possible value. This was not what I > > expected but makes good sense. > > Doug Gray > > > > > > Sent from my iPhone > > > >> On 3 Jan 2022, at 4:19 am, Jerash music <rmo...@gm...> wrote: > >> > >> > >> > >>> Le 2 janv. 2022 à 14:53, Christian Schoenebeck <sch...@li...> a écrit : > >>>> On Sonntag, 2. Januar 2022 14:42:55 CET Jerash music wrote: > >>>> Having worked with (and repairing) many midi keyboard controllers, I > >>>> can say that release velocity is not very common. Mainly available on > >>>> high range keyboard, often with weighted keys, piano style. > >>>> > >>>> Keyboard rubbers with triple sensors offer greater definition so to > >>>> have > >>>> the release velocity, but it can be implemented in the device firmware > >>>> or > >>>> not, at manufacturer’s choice. Keyboard rubber with double sensor could > >>>> also do release velocity, but may miss some when the key is not fully > >>>> pressed before actual release. Here, again, the sent message depends on > >>>> firmware implementation. > >>>> > >>>>> I suggest that that should only be the case when note off velocity is > >>>>> actually zero. > >>>> > >>>> I do agree with this, it totally makes sense to me. > >>>> > >>>> My 2 cents, > >>>> Raphaël > >>> > >>> Ok, but the core question still is: can we expect keyboards *with* > >>> note-off > >>> velocity sensors to *never* send note-off velocity zero? > >> > >> Mmm, …yes it may be possible. > >> it may be possible to send a zero release velocity if the firmware > >> calculates a release velocity and includes a « timeout » for the maximum > >> release time, and then decides that timed out values are zero. But I > >> have not expressly tested it, and each manufacturer could have his own > >> vision. > >> > >> I’ve been explained by Yamaha that the three contact rubbers are > >> especially useful for retriggering calculation of half pressed keys, but > >> they did not talk about release velocity calculation. Maybe Doug Gray > >> could try the following on his SL88 : « Release the key as slow as > >> possible in about 4 seconds » to try to reach the minimum release > >> velocity value. As the keyboard rubber has three contacts, it could > >> potentially send a zero release velocity if you reach a timeout between > >> two contacts releases. I’m not sure if it is humanly possible to reach > >> this potential timeout, as the contact points are really really close. > >> The real duration of this timeout is not documented so needs testing. > >> > >> Raphaël > >> > >> _______________________________________________ > >> Linuxsampler-devel mailing list > >> Lin...@li... > >> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > > > > _______________________________________________ > > Linuxsampler-devel mailing list > > Lin...@li... > > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: Doug G. <dou...@gm...> - 2022-01-07 07:30:09
|
I've crawled around a number of product manuals and discovered a variety of behaviours for note off. Some do send v=64 including some recent models (Casio Privia PXS series, Yamaha CP88, YC88 to name a few notables). On the other hand the Yamaha Arius ADP Series of console pianos send v=1-127, ie zero is not sent. I have verified this today myself on an Arius ADP-164. Some older designs send a zero velocity, possibly the lower end of the spectrum of controllers such as the Masterkey49. Unfortunately the higher profile midi keyboards such as the Kawai(VPC-1), Native Instruments, Arturia don't share the detail in their product manuals, at least not that I could find. So not as definitive as I expected. On Wed, 5 Jan 2022 at 03:19, Christian Schoenebeck < sch...@li...> wrote: > I changed the behaviour for both the SFZ engine and gig engine to > distinguish > by note-off velocity being exactly zero for now: > http://svn.linuxsampler.org/cgi-bin/viewvc.cgi?view=revision&revision=4020 > > That should fix expected release trigger behaviour for both keyboards with > and > without key release sensors appropriately. > > If it turns out that some MIDI keyboards with release sensors do send > note-off > velocity zero (which I doubt), then this behaviour can still be changed to > some more complicated MIDI-learn mechanism. > > BTW the original MIDI v1 specs say keyboards that do not support note-off > velocity should send 64 as note-off velocity value. Probably one of the > very > few mistakes made in the ancient MIDI specs, at least IMO. I haven't > looked > into latest MIDI v2 specs yet. I noticed though there was some voting > process > on a note-off related change on midi.org, that thread on midi.org is > password > protected though, so no idea what this was exactly about. > > CU > Christian > > On Montag, 3. Januar 2022 19:29:58 CET Raphaël Mouneyres wrote: > > thanks for the tests, it makes sense from a firmware perspective to set > > 0x01 as a minimum. > > > > I'll try to have a look at how another keyboard reacts when I have one > > at hand, probably during this week or next one, and I'll report back. > > > > Raphaël > > > > Le 03/01/2022 à 02:58, Doug Gray a écrit : > > > I have run a test on the SL-88, the lowest reported release velocity > seems > > > to be 0x01. I have tried to release keys as gently as I can but have > not > > > yet seen a release velocity of zero. It’s easy to hit the 0x01 so I’m > > > quite confident it is the lowest possible value. This was not what I > > > expected but makes good sense. > > > Doug Gray > > > > > > > > > Sent from my iPhone > > > > > >> On 3 Jan 2022, at 4:19 am, Jerash music <rmo...@gm...> wrote: > > >> > > >> > > >> > > >>> Le 2 janv. 2022 à 14:53, Christian Schoenebeck > <sch...@li...> a écrit : > > >>>> On Sonntag, 2. Januar 2022 14:42:55 CET Jerash music wrote: > > >>>> Having worked with (and repairing) many midi keyboard controllers, I > > >>>> can say that release velocity is not very common. Mainly available > on > > >>>> high range keyboard, often with weighted keys, piano style. > > >>>> > > >>>> Keyboard rubbers with triple sensors offer greater definition so to > > >>>> have > > >>>> the release velocity, but it can be implemented in the device > firmware > > >>>> or > > >>>> not, at manufacturer’s choice. Keyboard rubber with double sensor > could > > >>>> also do release velocity, but may miss some when the key is not > fully > > >>>> pressed before actual release. Here, again, the sent message > depends on > > >>>> firmware implementation. > > >>>> > > >>>>> I suggest that that should only be the case when note off > velocity is > > >>>>> actually zero. > > >>>> > > >>>> I do agree with this, it totally makes sense to me. > > >>>> > > >>>> My 2 cents, > > >>>> Raphaël > > >>> > > >>> Ok, but the core question still is: can we expect keyboards *with* > > >>> note-off > > >>> velocity sensors to *never* send note-off velocity zero? > > >> > > >> Mmm, …yes it may be possible. > > >> it may be possible to send a zero release velocity if the firmware > > >> calculates a release velocity and includes a « timeout » for the > maximum > > >> release time, and then decides that timed out values are zero. But I > > >> have not expressly tested it, and each manufacturer could have his own > > >> vision. > > >> > > >> I’ve been explained by Yamaha that the three contact rubbers are > > >> especially useful for retriggering calculation of half pressed keys, > but > > >> they did not talk about release velocity calculation. Maybe Doug Gray > > >> could try the following on his SL88 : « Release the key as slow as > > >> possible in about 4 seconds » to try to reach the minimum release > > >> velocity value. As the keyboard rubber has three contacts, it could > > >> potentially send a zero release velocity if you reach a timeout > between > > >> two contacts releases. I’m not sure if it is humanly possible to reach > > >> this potential timeout, as the contact points are really really close. > > >> The real duration of this timeout is not documented so needs testing. > > >> > > >> Raphaël > > >> > > >> _______________________________________________ > > >> Linuxsampler-devel mailing list > > >> Lin...@li... > > >> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > > > > > > _______________________________________________ > > > Linuxsampler-devel mailing list > > > Lin...@li... > > > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > > > > > > > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > |
|
From: Christian S. <sch...@li...> - 2022-01-11 12:59:39
|
On Freitag, 7. Januar 2022 08:29:49 CET Doug Gray wrote: > I've crawled around a number of product manuals and discovered a variety of > behaviours for note off. Some do send v=64 including some recent models > (Casio Privia PXS series, Yamaha CP88, YC88 to name a few notables). > On the other hand the Yamaha Arius ADP Series of console pianos send > v=1-127, ie zero is not sent. I have verified this today myself on an Arius > ADP-164. > Some older designs send a zero velocity, possibly the lower end of the > spectrum of controllers such as the Masterkey49. > Unfortunately the higher profile midi keyboards such as the Kawai(VPC-1), > Native Instruments, Arturia don't share the detail in their product > manuals, at least not that I could find. > So not as definitive as I expected. Mmm, that's unfortunate. Thanks for the research though! For now I keep the current simple implementation (check for zero velocity). In future this should probably be changed to a MIDI learn mechanism and/or checking for this feature according to MIDI v2. Again, haven't checked the MIDI v2 specs yet, but I read somewhere they have added capability negotiation. CU Christian |
|
From: Jerash m. <rmo...@gm...> - 2022-08-01 13:53:44
|
Late reply, but minimum velocity release of 1 is also confirmed on many IK.multimedia keyboards ans korgs. Could never find a keyboard with 0 release velocity. Hope that helps. Raphaël Le mar. 11 janv. 2022 à 14:00, Christian Schoenebeck < sch...@li...> a écrit : > On Freitag, 7. Januar 2022 08:29:49 CET Doug Gray wrote: > > I've crawled around a number of product manuals and discovered a variety > of > > behaviours for note off. Some do send v=64 including some recent models > > (Casio Privia PXS series, Yamaha CP88, YC88 to name a few notables). > > On the other hand the Yamaha Arius ADP Series of console pianos send > > v=1-127, ie zero is not sent. I have verified this today myself on an > Arius > > ADP-164. > > Some older designs send a zero velocity, possibly the lower end of the > > spectrum of controllers such as the Masterkey49. > > Unfortunately the higher profile midi keyboards such as the Kawai(VPC-1), > > Native Instruments, Arturia don't share the detail in their product > > manuals, at least not that I could find. > > So not as definitive as I expected. > > Mmm, that's unfortunate. Thanks for the research though! > > For now I keep the current simple implementation (check for zero > velocity). In > future this should probably be changed to a MIDI learn mechanism and/or > checking for this feature according to MIDI v2. Again, haven't checked the > MIDI v2 specs yet, but I read somewhere they have added capability > negotiation. > > CU > Christian > > > > > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > |