ARIA's unimplemented SFZ 2.0 opcodes

Discussion on the SFZ implementation and opcodes available in the ARIA engine.

Moderators: eric_telemaque, davidv

davidv
Site Admin
Posts: 1567
Joined: Tue Mar 02, 2004 7:23 pm
Contact:

ARIA's unimplemented SFZ 2.0 opcodes

Postby davidv » Mon Aug 24, 2009 3:03 pm

General unimplemented opcodes:

direction
loop_type
All sample playback is forward, no current support for backwards and alternate, so those to opcodes have no effect in ARIA

<effect> unimplemented opcodes :
all effect types in use by Dimension and Cakewalk products,
we are instead using a "type=com.vendor.product" style logic using a currently private SDK.

wet, dry and bus: currently being worked on.


implemented but mis behaving as of ARIA 1.0.7.6:

rt_dead :
applies rt_dead=off regardless. If you need release triggers with no previous attack (and dont care about sustain and sostenuto switches)... use trigger=release_key instead

stop_beats we are only using start_beats with an end statement instead
polyphony=legato_XXX : (we are using custom MIDI procs for that)

SFZ 2.0 LFO-related unimplemented opcodes
No lfo->lfo link.
lfoXX_step : being worked on.
lfoXX_fade
All expression-engine destinations

SFZ 2.0 EG-related unimplemented opcodes

egXX_glide_time : instead of defining glide_time as a destination, we implement portamento/glide using standard pitch destination and CC140 (delta between two previous keys - ARIA specific)
All expression-engine destinations
more to come
David Viens,
Plogue Art et Technologie Inc. Montreal.
http://www.plogue.com

Return to “SFZ Programming”

Who is online

Users browsing this forum: No registered users and 1 guest