Closed kinwie closed 1 year ago
I link this issue for monitoring : https://github.com/redtide/test/issues/3
I break down the opcode details :
choke_group
: Given a new number ID for a region. This ID not related to group
/ off_by
opcodes and not related to polyphony
or note_poyphony
opcodes. Value : Integer. Default value : 0
choke_by
: When a new region with a choke_group
number equal to choke_by
plays, that region will be turned off. Value : Integer. Default value : 0
choke_mode
: Determinate how a region is turned off by a choke_by
opcode. Value : fast, normal, time. Default value : time.
choke_time
: When choke_mode
is set to time, this specifies the fadeout time for regions being muted by voice-stealing. Value : seconds. Default value : 0.006 seconds.
choke_shape
: The coefficient used by choke_curve
. Value and default, follows ARIA
choke_curve
: When choke_mode
is set to time, this specifies the math to be used to fade out the regions being muted by voice-stealing. Value and default, follows ARIA
Using ampeg_dynamic=1
can offer a workaround for this, by modulating ampeg_release
with off_mode=normal
But still there are some issues involved in the practical usage :
ampeg_dynamic
seems doesn't work with extended CC 133 (key number) to use the "key-mapped choke"
I know I seems greedy for opcode request, but really... we need a second set of Choke opcodes for drums and percussion stuff (especially cymbals) to simulate closer to the real instrument. So, they are :
Why we need two sets? Because we are using one_shot mode and we need two different offtime (release time)_ to define two different choke events :
In this simple example :
The crash is set to 1 polyphony,
group
id No. 1 and withoff_time
5 seconds, so it will self-choke and every previous hits will be decaying in 5 seconds.Then it has
choke_group
id No.10 and will be choked by key 62 which haschoke_group
id No.11. The off_time (choke_time
) is quick, in 0.3 seconds.