• Raymond Toy's avatar
    Optimize for automations that haven't started yet · 1e42b591
    Raymond Toy authored
    If automations are scheduled to start in the future, the slow
    automation path is run instead of the fast path where the AudioParam
    value is known to be constant.  For most nodes this doesn't matter,
    but for BiquadFilters that have a complicated relationship between the
    AudioParam values and the filter coefficients, this is a significant
    performance hit.
    
    So, if there are no automations scheduled to run in the current render
    quantum, we can still use the fast path.
    
    Bug: 795051
    Change-Id: Iad144c5ce0bcea4af1921ba879c6c55f210fcb16
    Reviewed-on: https://chromium-review.googlesource.com/830033
    Commit-Queue: Raymond Toy <rtoy@chromium.org>
    Reviewed-by: default avatarHongchan Choi <hongchan@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#527041}
    1e42b591
AudioParam.h 10.7 KB