You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
on Dischord someone had questions concerning latency handling for automation. At least I and @defiantnerd think we should document this better:
put the full explanation in latency.h. Some thoughts:
quoted from @defiantnerd's comment on Dischord: "Sending an event at timestamp n will result in audio at timestamp n+latency. [...] Latency is pre-delay-compensated. As every host does it (except FL Studio before version 9 or Magix Something (i forgot the name)) The host has to send the events that early so the plugin has time to apply it early enough for the announced latency."
I would add something like: the overall plugin latency applies to both audio and events together.
put some hint in all relevant places (like e.g. events.h, process.h, ...)
e.g. // for a discussion of latency see latency.h (as @baconpaul suggested)
The text was updated successfully, but these errors were encountered:
on Dischord someone had questions concerning latency handling for automation. At least I and @defiantnerd think we should document this better:
// for a discussion of latency see latency.h
(as @baconpaul suggested)The text was updated successfully, but these errors were encountered: