using the Draw Tool to edit an Automation Track, I realized that editing events that already exist in the track highlights an issue.
In fact, after modifying an event in the Automation Track through the Lower Zone using the Draw Tool, the modified event is correctly displayed and correctly associated with the new Start and Value, but the execution of the automation seems to refer to the values set before the modification and this until you move to another Song.
In Song 1, open the editor of the Automation Track located in the Lower Zone
Identify the automation event placed in measure 0002.1.1: the event, once reached in the execution timeline, determines a coherent action (mute Song1 channel in Mixer)
Using the Draw Tool, alter the Value associated with the existing automation event in the measure 0002.1.1 by setting the value to 0
Rerun the track and note that, once the modified event is reached in the timeline, the action associated with the event is not consistent with the modification, but with the Value set to 1 before its modification (Song1 mixer channel is mistakenly muted)
Move to Song 2 and then return to the previous Song 1
You notice now that, once the previously modified event has been reached in the timeline, the action associated with the event is consistent with the new Value value obtained after the modification (Song1 mixer channel is now set correctly with Mute not activated)
Thank you much for your project and your help. We could reproduce it now …
… how do you manage that one with the Draw-Tool? The event value is currently not updated while mouse is moving. And so it is very difficult to set 0 as a value? But we’ve fixed it. Next version and you can change the value while mouse is moving.
First of all , thank you for your feedback, Michael.
Using the DrawTool, inside the AUTOMATION window in the Lower Zone, click slightly to the right of the point that represents the event whose value you want to change and drag the mouse until you reach the desired position (in our case the one corresponding to the value 0).
I hope now to have clarified how I actually obtained the change of the value associated with the automation event, even if then this change seems not to be immediately taken into consideration.
since I have not received any further feedback on this minor issue, I have not understood whether it was possible to reproduce the issue according to the instructions provided.
At a certain point I thought I understood that the issue had been fixed, but, according to my tests, the issue is also present in the new software version 2.1.1.