![]() ![]() Though some combinations seem worse than others. These kinds of problems happen with all key switched instruments, not just Kontakt and not just SONAR. Is this likely to be a problem with Sonar just not sending MIDI information accurately, or could it be a problem in Kontakt? The exact same thing happens with Session Strings - Sonar does not seem to get the keyswitches to Kontakt bang on the beat, and if they're not bang on the beat then the articulation doesn't change correctly. The notes are fully quantized, but unfortunately it's as if Sonar's MIDI is being sent to Kontakt a little out of time because the palm muted note doesn't register in time for the start of the measure - it plays another full strum. ![]() So I change the keyswitch note for these occasions, and enter the original MIDI note at the start of the next bar to change back to the palm muted pattern. I have a palm muted strumming pattern that needs to change to a full strum at the end of every few measures. I remember having an awful time trying to use keyswitches in NI's Session Strings, and now I'm having the same problem with Strummed Acoustic. Sometimes when I'm programming a Kontakt part that uses keyswitches, I find that the MIDI does not trigger the keys accurately. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |