There is a bit of a grey area as far as, should this be a feature request or a bug, first i’ll explain the ‘issue’ and repro steps
ISSUE
any automation written will play back (and bounce down!) differently based on the latency of the project
Reproduction steps
- open new project, add an audio track, set your audio latency to it’s lowest value
- add an audio event (noise… music anything)
- automate a mute event on this channel
- bounce (export) the section around the mute event
- change audio latency to something higher, like 16ms
- bounce (export) the section around the mute event
- import both new audio channels into the project and it will look something like this…
this was quite concerning to myself and the majority of users that have seen this photo and reproduced these steps, most users felt there was something ‘wrong’ with the automation sync but couldnt quite put their finger on what it was… this should make the ‘issue’ a lot clearer.
I beleive this to be a significant ‘issue’ because it means your project mixdown will sound different based on the latency set.
the latency should not affect the playback of the track (in my opinion)
it seems that most people diddnt know this happened… personally I have had a suspicion for a while, this is why I have been compensating my automation, but by ear.