SFZ format documentation

[DSmolken]

Extended MIDI CC implementation isn't always complete for every CC... so if 130 doesn't support locc/hicc, that would be good to verify and document. I think I found slightly weird behavior with... one of them... where it'll work fine if I put it in as a hdcc with decimals. So maybe try that, just to see.

Which ext cc number that is weird? I've tested all and seems they are okay in sforzando.

See the hihdcc stuff in https://sfzformat.com/tutorials/legato/ ... led-legato - it seemed to do nothing with hicc141, but hihdcc141 was totally fine.

[pljones]

Ok, let me check the original rgc sfz player for how it behaves with cc130 and lo/hipolyaft and also the midi file i recorded with TD-1KV to makr sure the polyaft message has note-on/offor not.

rgc:audio didn't support cc130 or on_cc triggering.

[vvveeerrraaa]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Anytime I try to use an opcode like 'ampeg_attackccN' sforzando does not accept it as a valid opcode even though it is copy-pasted directly from the list of opcodes on https://sfzformat.com/opcodes (https://sfzformat.com/opcodes).

[DSmolken]

Oh, try ampeg_attack_onccN, for example ampeg_attack_oncc24 - that's copied from an instrument I know is working.

ampeg_attack_onccN, ampeg_attack_ccN and ampeg_attackccN should all be aliases but we need to check which actually work in sforzando and which don't, and update the wiki... I remember having to change this somewhere because I tried the wrong alias.

[pljones]

https://sfzformat.com/opcodes/ doesn't actually say ampeg_attackccN works in any version of SFZ

[DSmolken]

Oh, I see the same instrument also has ampeg_attackcc29 so both of those work, though I mostly use the _onccN syntax for controls in my stuff...

So, if ampeg_attackccN doesn't work, the question becomes are you replacing the N with a number?

But I do also vaguely remember some alias not working for some control, maybe amplitude or tune.

[kinwie]

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: Select all

<region>
sample=crash.wav
loop_mode=one_shot
key=49
group=1
off_by=2

<region>
sample=*silence
key=49 // <-- note number info for polyaft event
group=2
locc130=127 // to limit polyaft cc range
hicc130=127 // to limit polyaft cc range
on_locc130=127 // for triggering
on_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.

[kinwie]

See the hihdcc stuff in https://sfzformat.com/tutorials/legato/ ... led-legato - it seemed to do nothing with hicc141, but hihdcc141 was totally fine.

Yeah, 140 and up are ARIA specific ext midi cc, works in special cases

[pljones]

That's why Polyaft event can't triggering a region in sfz.

Yep!

Code: Select all

key=49 // <-- note number info for polyaft event
locc130=127 // to limit polyaft cc range
hicc130=127 // to limit polyaft cc range

So what happens if you leave this off the region? Equally for these?

Code: Select all

on_locc130=127 // for triggering
on_hicc130=127 // for triggering

They all need to be there?

As far as I can tell, the lo/hicc130 (as they're just region selectors and not used for triggering) need some trigger: but they're definitely polyphonic in Sforzando (i.e. I hold one cymbal choked and can sound another cymbal that's also choke-sensitive). So Sforzando definitely uses the note number in the polyaft message for that much, at least.

[Chalisque]

is it possible to do sliced drum loops with a single sample file, rather than having to extract the slices to individual .wav files?

[DSmolken]

Yes. The opcodes you need are offset (to make the sample play from some part in the middle) and I think https://sfzformat.com/opcodes/end/

[pljones]

Yep, the original rgc:audio site had examples, I seem to remember.

[Etienne1973]

Is it possible to modulate pan with lfo(s) per voice polyphonically?

[DSmolken]

Yes. LFOs are separate per region, so all you have to do is give each region different modulation depths, speeds and/or whatever else you want.

I think Bear Sax has the breath noise being modulated in the opposite direction of the note signal when doing diaphragm vibrato... you could look that up on Github, change volume to pan and it should give you an idea of how this can be done.

[Etienne1973]

@DSmolken: Thank you! Ok. Great. I guess I got it.

I have sampled a synth pad from key c1 to key c7 in minor 3rds. Accordingly I have transposition from root keys going on b/c there are less regions than keys in total.

Question: Should I, to make it perfect, add transposed root key "ghost" regions for not represented, missing keys? I mean so absolutely every key can trigger its own LFO setting?