Visual Delay Compensation (Ableton vs others ?)

[v1o]

1) That's not the topic of the discussion

Higher FPS = reduced latency

2) That's not true - R12 pre-buffers the GUI every time it's launched so after the project's loaded first time it lags a lot until everyting is buffered

On my system it builds the buffers only once. Not every time it's launched like you say.

3) Many DAWs will refresh the GUI as fast as your GPU and screen allow, so e.g. Studio One runs at 144fps here

The frame rate and the screen refresh rate are different. It's highly unlikely that S1 is animating UI elements at 144 fps.

[antic604]

1) That's not the topic of the discussion

Higher FPS = reduced latency

2) That's not true - R12 pre-buffers the GUI every time it's launched so after the project's loaded first time it lags a lot until everyting is buffered

On my system it builds the buffers only once. Not every time it's launched like you say.

3) Many DAWs will refresh the GUI as fast as your GPU and screen allow, so e.g. Studio One runs at 144fps here

The frame rate and the screen refresh rate are different. It's highly unlikely that S1 is animating UI elements at 144 fps.

1) In general that's true, but - again - that's not what is being discussed here. In Ableton, if you have say 1000ms latency in your project, the GUI - transport, meters, etc. - will run 1s ahead of audio, which is not the case in most other DAWs.

2) It does? Are you on Windows (like I am) or macOS?

3) It definitely feels much more responsive than other 60fps DAWs (Live, Reason when it's pre-buffered), but I haven't measured it. Cubase also has a user-defined cap, so it can go above 60fps as well.