@mathiasbredholt and me are having the problem with Link on ESP32 that most of the jitter is <100uS, but in random time intervals (but apparently in a ~30s grid) overshoots of 6000-20000uS appear, which causes the clock to be late. This is especially a problem when the clock pulse is multiplied by another device and causes the whole session to run out-of-sync. I also see this problems on other projects using link on ESP32.
The FreeRTOS Tick Rate is set to 1000Hz, Example which can be used for testing: https://github.com/mathiasbredholt/link-esp-example
Just be sure to adjust tick rate to 1000HZ in menuconfig - this is not yet done in sdkconfig.defaults.
@mathiasbredholt and me are having the problem with Link on ESP32 that most of the jitter is <100uS, but in random time intervals (but apparently in a ~30s grid) overshoots of 6000-20000uS appear, which causes the clock to be late. This is especially a problem when the clock pulse is multiplied by another device and causes the whole session to run out-of-sync. I also see this problems on other projects using link on ESP32.
The FreeRTOS Tick Rate is set to 1000Hz, Example which can be used for testing: https://github.com/mathiasbredholt/link-esp-example Just be sure to adjust tick rate to 1000HZ in menuconfig - this is not yet done in sdkconfig.defaults.
Please see the detailed issue at https://github.com/Ableton/link/issues/109#issuecomment-997212801