BUG: transition timeline interacts with destination fade-in

When the destination has a micro-fade-in in the main timeline, after a transition timeline, it behaves strangely, as if the fade-in were longer (even though the transition timeline doesn’t have fades at all).

1 Like

Hey Alcibiade,

The behaviour does seem odd, however, it is actually the intended behaviour, but the reasoning does require a little explanation.

With transition timelines, we interpolate the values of all automation and fade curves. We take the value where you transition from and at the destination and we move from one to the other over the length of the transition timeline. This means that you will avoid having any unintended jumps in automation/fade curves that are on the main timeline through a transition, but it does mean that fade curves and automation will be more smoothed out than you would otherwise expect.

That’s odd indeed! What’s the benefit of this behavior, instead of simply summing all automations/fades?
Here’s a video, for the ones wondering what we’re talking about:

1 Like

Digging into this further - I think you are right, and we should change this for instrument fade curves. We actually already have a task in our backlog to improve this which I had forgotten about.

This is a bit of a tangent, but automation curves are a bit different - you can edit them for the transition timeline, and if unedited, you have two values to draw from (source and destination), which could be overlapping, so a simple lerp makes the most sense.

Fade curves currently share an implementation with automation, so we would need to separate them to have fade curves work better with transition timelines.