>After you updated LS to latest SVN it
>should apply the note/velocity changes to the MIDI event as well as to the
>voices, so it should behave as expected by you.
Well, I updated to the latest svn, but the MIDI data itself doesn't change
with change_note unfortunately, only the voice data. i.e chipmunk effect
occurs if I transpose C3 up to C4 using change_note, rather than triggering
the C4. :S
>ATM we don't have that event handler (and thus this first level of raw MIDI
>processing) yet. Mainly because so far I saw no huge benefit of having it.
But
>who knows, maybe I am also missing out a killer use case for that layer.
I can dig that. From what I read of other Kontakt scripts, the multiscript
stuff is mainly used for channel switching tricks, etc.
On Thu, May 25, 2017 at 7:46 PM, Christian Schoenebeck <
schoeneb...@linuxsampler.org> wrote:
> On Thursday, May 25, 2017 19:19:40 Andrew C wrote:
> > I'd consider the 'correct' behaviour of change_note/set_event_par to be
> to
> > change the incoming midi note data itself, as opposed to the voice data,
> > but the use of the two in tandem could give interesting results.
> > Could I suggest an extension of change_note, an optional argument to
> change
> > the voice data itself and/or the incoming midi data?
> > This might be silly feature creep though.
>
> I think I already addressed that today (as I was already at it when I added
> change_velo() and change_note() today). After you updated LS to latest SVN
> it
> should apply the note/velocity changes to the MIDI event as well as to the
> voices, so it should behave as expected by you. Which is a substantial
> behavior difference of course, since other samples would be triggered,
> mickey
> mouse effect, etc.
>
> I am actually not sure what the precise behavior of Kontakt is on that
> issue.
> I guess it also modifies the MIDI event directly, but not sure.
>
> Fact is Kontakt has two separate levels of event handling by scripts. One
> level are the event handlers which we also have right now in LS. Then they
> also have another raw MIDI event handler level called "Multi Script",
> which is
> modifying the raw MIDI data itself before it is actually passed to that 2nd
> level we have. That raw MIDI handling level of KSP has exactly one event
> handler:
>
> on midi_in
> ...
> end on
>
> It allows you to modify MIDI events, drop MIDI events and create completely
> new MIDI events on your own by script.
>
> ATM we don't have that event handler (and thus this first level of raw MIDI
> processing) yet. Mainly because so far I saw no huge benefit of having it.
> But
> who knows, maybe I am also missing out a killer use case for that layer.
>
> CU
> Christian
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Linuxsampler-devel mailing list
> Linuxsampler-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
