Automation bug in T2?

[ik]

Please see image above.

Automation: I was just recording a plain

[off->on->off->on->off] sequence

with that little 'test lamp', and I got that strange automation curve, insted of

[min->max->min->max->min]

as I expected.

Is this a bug? .... or am I missing something?

Thanks for any feedback,
ik.
(btw, I T2)

[markmann]

On/off automation could have a curve like this. When you play it back, does the plug-in repeat the on/off moves you originally made? You should test that. I'll bet it does. On is represented by 1 and off is represented by 0. So I don't think the plug-in will switch states until the curve gets all the way to one or all the way to zero.
Mark

[Mr. Tingle]

There's some options in the automation button of the lower left of edit screen. One of them is called something like 'simplify automation points', you don't want this ticked.

[ik]

On/off automation could have a curve like this. When you play it back, does the plug-in repeat the on/off moves you originally made?

No it doesn't. I started to record as lamp=off, and as you see on the curve, it starts as lamp=on, and on playback, it doesn't follow the switch movements as recorded. To be more exact, it does follow the curve correctly, but the recorded curve inconsistent with the swith movements.

ik.

[ik]

There's some options in the automation button of the lower left of edit screen. One of them is called something like 'simplify automation points', you don't want this ticked.

I've tried this unchecked:
Now it starts as it should, lamp=off, but still doesn't follow the pattern recorded. The curve 'triangle-wave' like, and I expected to see a 'square-wave' like .... Looks like each recorded point goes continously to the next one, with no jumps. Is it a bug or feature?

ik.
(I still T2!)

[Beno]

It's not a bug per se but it is expected with the current implementation. You see Tracktion has no way of knowing that this parameter has only two states. It just knows it accepts a value between 0 and 1. So it doesn't know that the transition should be imediate. All it knows is that it had a value of 0 and then a bar or two later you changed it to 1. It then connects the dots. We are working on ways of improving this behavior to be as expected.
Ben

[ik]

Thanks Beno for the explanation!
A 'Hold value' as one of the automation options would do the trick ....
Thanks,
ik.