Repository navigation
|
In the extension timer-support.h, a comment in clap_host_timer_support says "30hz should be allowed" but faster timers seem to work fine. However in wrapasvst.cpp, the register_timer function enforces a minimum timer period of 30ms, and raises the period to 30ms if it's lower. What's the rationale for this? If I comment out those lines in wrapasvst.cpp before building the wrapper, the shorter timers seem to work fine, at least when I test inside Reaper. Could it be unsafe in other hosts? |
Answered by
baconpaul
Apr 6, 2026
Replies: 1 comment 1 reply
|
i dont think its unsafe, but the timer approach is really meant for non-fd ui refreshes and the like so we never really thought about it. definitely a 1ms timer may work poorly in some hosts. |
1 reply
Answer selected by
nukelash
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
i dont think its unsafe, but the timer approach is really meant for non-fd ui refreshes and the like so we never really thought about it. definitely a 1ms timer may work poorly in some hosts.