Skip to content

Release Trigger adjustment #372

@kinwie

Description

@kinwie

Current sfizz release trigger have some disadvantages.
These are what I think may need to be adjusted :

  1. Sfz specs default behavior: By setting trigger to release or release_key will automatically set the region into one-shot mode.
    *Current state in sfizz : It is not and we need to put ampeg_hold= or ampeg_release= with high value to make the release region play, which is no needed if it automatically put into loop_mode=one_shot.

  2. Playing notes with sustain pedal down (especially repeated notes) then release the pedal, need note_polyphony=1 to limit each released notes to 1 voice per key.
    *Current state in sfizz :

  • note_polyphony not yet recognized by the release regions, so for example, with sustain pedal down, playing fast 10 notes of the same key, then release the pedal, all 10 released notes will play. It should be limited follow the note_polyphony value.
  • off_time not yet working properly. Sfizz default to off_mode=normal and depends on the ampeg_release value for the attack region's fade-out time, so we can't set different fade-out time independently. This can be an issue for the high undampened piano keys which have long release time, but to have a shorter off_time (In Aria, this is set to off_mode=time by default).
  1. Adding note_polyphony=1 will also cause both the attack and release regions of the same key, muting each other (bi-directional). This is the default behavior with no group= set (both attack and release regions are in the same group=)
    *Current state in sfizz : release region can't get muted by the attack region because the use of long ampeg_release value for it to play

Point #3 could be just gone if #2 fixed

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions