24-09-2020, 05:37 PM
This is not particularly a bug; x-fade fades all parameters with their individual timings, with the highest timing (fade + delay) being taken as 100%, all other timings are multiplied with the equivalent factor (highest = * 1) so if there is a fade time 0 the result of this multiplication will always be zero.
Example:
fix 1 is having a fade time of 0, fix 2 of 1.5, fix 3 of 3. Now 3s equals 100% of the crossfade, 1.5s equals 50% and 0... well will always be zero.
As soon as we would change that the crossfade is crossfading all values between 0 and 100 percent regardless of the time, we'd loose the ability to have these individual timings taken into account. It's one way or the other unfortunately.
Example:
fix 1 is having a fade time of 0, fix 2 of 1.5, fix 3 of 3. Now 3s equals 100% of the crossfade, 1.5s equals 50% and 0... well will always be zero.
As soon as we would change that the crossfade is crossfading all values between 0 and 100 percent regardless of the time, we'd loose the ability to have these individual timings taken into account. It's one way or the other unfortunately.