WindcryMusic
Senior Member
@WindcryMusic, you might be able to cut to the chase (and avoid testing anything) by turning off the Data Reduction feature on the Script. Doing so ensures that an articulation-switching message will be set at the start of every musical note -- as opposed to the default setting, where switching messages are only sent on an as-needed basis. The idea behind "as needed" is to stop the Script from "spamming" a patch with normally unnecessary, repetitive switching messages. But in practice I think you'll find that turning it off won't cause any timing issues as a result of all those extra events being sent; at the same time, if a palette is 'misfiring' for some reason, you can be assured that the proper articulation is being selected at the start of every single note.
That sounds like something that should be easy to try ... I'll see if I can do that test later on tonight.
Update: I just tried it. Recorded something where I could reproduce the misbehavior, then turned off Data Reduction. No effect ... the note drop-outs still happen in the same way. Again, the effect I'm seeing is not that certain notes play with the wrong articulation ... rather, certain notes don't sound AT ALL. The key still shows as having been pressed in Kontakt's keyboard pane, but there's nothing audible from that note. In this test, the offending notes were separated by 12 ticks, with the performance legato note played later than the other articulation (a simple long sustain). If I switch things around so that the performance legato note is sounded 12 ticks BEFORE the other articulation, then both articulations play back fine. I duplicated this same behavior in a couple of sections. In each case, if I slide the trailing legato note back to about 40 to 50 ticks after the other articulation, it seems to sound 100% of the time.
This feels to me like it could be an issue with the Spitfire performance legato not handling being switched off and then back on as a result of an intervening note using a different articulation, unless enough time is allowed for something in Spitfire's script to "reset". (I'm assuming it is Spitfire's scripting that is at fault at this point since, if it was an issue with ARTzID, one would expect it to happen regardless of which articulation was selected to play first.)