When reversing an automation region with curved segments by choosing "Reverse Automation" in the region's context menu, the resulting curve will be erroneous (slopes reverted to 50%, deleted key-frames or wrong curved segments) depending on the number of key-frames and their selection status at the time of reversal. I've found the following examples:
- With up to three unselected key-frames and a curved segment, the resulting curve will revert to a slope of 50%.
- With up to three key-frames and at least two selected, and a curved segment, the resulting curve will have a missing key-frame.
- With more than three unselected key-frames, the resulting curve will have the wrong segment assigned the curved slope.
- With more than three key-frames and at least two selected, and a curved segment, the resulting curve will have missing key-frames.
Chrome 73.0.3683.86 official build, 64 bits, Linux Ubuntu 18.04.2 LTS
Comments (2)
Thanks for the clarification André. The truth is that this particular bug (reversing curved automations) had a big variety of behaviours depending on the amount of key-frames involved, if they are selected or not, etc. So I don't think I tested every possibility and I assumed a few things. I'd need to spend more time than I have now testing and noting each condition and behaviour. I also tested the "Inverse Automation" function and it seems to work fine but again, I just did a quick test with a single curved segment.
Yes, that was really a mind-fuck, reversing a curve with more than two segments, one of them curved, and trying to see the logic of where the curved segment ended up in the resulting curve. Thanks for explaining.