-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latency Measurements #148
Comments
Something I have been thinking about doing, mostly because I don't know how good my coding or main loop would be. I see the GP2040 / GP2040-CE had some timing information in their project(s) - https://inputlag.science/controller/methodology But I have not yet setup any tooling for tests. If you have any suggests or PR, I think they would be welcome. Would be really cool if we have something like a GitHub Action that test per release or something. |
Been thinking about latency measurements and possible some sort of CI/CD for testing, to make sure we don't break anything. Was watching https://www.youtube.com/watch?v=82K3Pb0178g and this gave me an idea of setting up an local hosted runner for GitHub, with something like an Arduino, which can press or move the analog interfaces and monitor the input on a Raspberry Pi which is paired with the ESP32 device. Going to draw up a circuit diagram and make a test project, with some very basic tests, which could be the start of CI/CD pipe line. |
Thanks for pitching in @LeeNX Let me know if anything becomes apparent from the testing. Perhaps some tweaks to the code or some better examples are needed |
Ah... nothing since last year ? |
Has anyone attempted to measure the input latency of this implementation?
The text was updated successfully, but these errors were encountered: