[SOLVED] x-fade is not working properly

[denishessberger]

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.

[sneaker]

Sorry, then function is pretty pointless in my opinion. I understand X-Fade as a crossfade between two states in the time in which I move the fader. Like a crossfader on the DJ desk. I don't know the fade time before in most cases. I would like to go from a scene to another  individually in live use e.g. in time with the music.

When the fade times are known before I build a cuelist and step through it. It's the same.

[denishessberger]

I think you misunderstood - you do not need to know the fade actual fade time before, however for the console to be able to calculate the actual crossfade value, the cues in the cuelist need to have a fade time bigger than 0 seconds.

I'll post an example later today.

[denishessberger]

Here you go.

https://youtu.be/pkl41q5LJWY