Hi. Sorry for the late reply.
No, there's no way at the moment.
The automation's points are fixed to time units of audio frames, not metered ticks.
It's because of the way audio automation grew up in MusE.
You might notice the same thing happens with wave parts, moves them around if the tempo changes. 
But with wave parts, there is hope:
Wave parts (along with almost everything else) use an 'agnostic' unit of time which could be switched
between time units of audio frames and metered ticks, if we wanted.
It's just that wave parts and midi parts were programmed to use the audio frames and metered ticks
of this agnostic unit of time, respectively.
It may have been a mistake to make audio automation use frames.
The automation should either be switched to use ticks instead of frames, or use the agnostic unit of time and use its ticks,
in anticipation of one day switching the wave parts over to units of ticks instead of frames.
Why were wave parts programmed to use frames not ticks?
It's because using ticks requires audio time stretching and tricky concepts such as beat matching,
to deal with the changes in length resulting from tempo changes.
Libraries and code to do these things were not readily available back in the day. So we left the waves using frames.
Time stretching has been added (see the wave editor), but not yet at the level of automatic stretching according to tempo changes.
It has been a grand scheme of mine to one day get it all done. There's even an old unfinished branch with a bunch 'o changes.
Florian also had a branch where he demonstrated his take on a new kind of agnostic timing, and beat matching.
Statistics: Posted by Tim E. Real — Sun Mar 16, 2025 3:20 am