sfz.github.io
sfz.github.io copied to clipboard
Unlisted ARIA opcodes
Per @redtide's request, I have managed the time to compile what I'm pretty sure is a complete list of ARIA opcodes not shown on the SFZFormat website. I've mentioned "hint_min_samplerate" before, and this was prompted after my finding some curvecc's for EG's (though not all) were also unlisted.
Regardless, attached is a text file listing all ARIA opcodes I've managed to confirm are unlisted, having examined the ARIA binary:
SFZ Format - Unlisted SFZ opcodes.txt
Also noteworthy is that I'm guessing "hint_load_method" is ARIA's equivalent of SFizz's "hint_ram_based"? By all means, correct me if I'm wrong there.
- [x] (amp/fil/pitch)eg_attack_curveccN
- [x] (amp/fil/pitch)eg_delay_curveccN
- [x] (amp/fil/pitch)eg_release_curveccN
- [x] (amp/fil/pitch)eg_start_curveccN
- [ ] display_factor_ccN
- [ ] display_format_ccN
- [ ] display_mode_ccN
- [ ] display_offset_ccN
- [ ] drive_shape
- [ ] drive_shape_onccN
- [ ] eqNbw*
- [ ] eqNgain*
- [ ] fil2_gain_ccN*
- [ ] fil2_gain_chanaft
- [ ] fil2_gain_curveccN
- [ ] fil2_gain_polyaft
- [ ] fil2_gain_random
- [ ] fil2_gain_smoothccN
- [ ] fil2_gain_stepccN
- [ ] fil_gain_ccN*
- [ ] fil_gain_chanaft
- [ ] fil_gain_curveccN
- [ ] fil_gain_polyaft
- [ ] fil_gain_random
- [ ] fil_gain_smoothccN
- [ ] fil_gain_stepccN
- [ ] hint_load_method
- [ ] hint_max_channels
- [ ] hint_min_samplerate
- [ ] loop_end_offset
- [ ] loop_length_curveccN
- [ ] loop_start_curveccN
- [ ] offset_curveccN
- [x] offset_mode
- [ ] pitch_curveccN
- [x] rt_decayN
- [x] rt_decayN_time
- [ ] sample_config
- [ ] sample_const_param
- [ ] sample_dyn_param
- [x] sample_dyn_paramN
- [ ] slice (?)
- [ ] trigger=legato_high
- [ ] trigger=legato_last
- [ ] trigger=legato_low
- [ ] user_labelN
Keys:
- * alias of a listed opcode
- (?) uncertain if actually a working opcode or not
Thank you! I've managed to update at least the v1 EGs curvecc modulations for now.
Regarding hint_* opcodes: we are not adding in any (except for some example) because those are custom, application specific settings, so that would be hard to maintain.
I guess only @paulfd can reply to your last question.