Quantcast
Channel: KVR Audio
Viewing all articles
Browse latest Browse all 3377

Samplers, Sampling & Sample Libraries • Re: SFZ format documentation

$
0
0
rgc:audio didn't support cc130 or on_cc triggering.
Yes, you are right. Old player is not supporting cc130 and on_lo/hicc opcodes.

So, for the Polyaft events, i take a look again at one midi file i recorded with Roland TD-1KV.
For Cymbal 1 pad as example, it sent 2 polyaft messages at once when we grab the cymbal pad to choke. In picture are note 49 and 55, these are the note number messages with CC value 127 then followed by 0 when we released the pad. But it didn't send note-on or note-off messages. That's why Polyaft event can't triggering a region in sfz.
Polyaft_td1kv.png
Thus, i use on_lo/hicc to trigger the choke samples, either *silence or cymbal tail samples. I checked again and now it also works in sfizz.

Code:

<region>sample=crash.wavloop_mode=one_shotkey=49group=1off_by=2<region>sample=*silencekey=49 // <-- note number info for polyaft eventgroup=2locc130=127 // to limit polyaft cc rangehicc130=127 // to limit polyaft cc rangeon_locc130=127 // for triggeringon_hicc130=127 // for triggering
I think yeah, it depends on how the Midi controller sending Polyaft messages. Roland and maybe other brand like Yamaha, Alesis, etc, do the same, not sending note-on/off messages. I don't know how about TrapKat, and maybe newer keyboard controller can sent note-on/off for Polyaft messages, I'm not sure.

Statistics: Posted by kinwie — Fri Jun 07, 2024 5:28 am



Viewing all articles
Browse latest Browse all 3377

Trending Articles