---
title: "Comment by DemoVexa on \"The Math Behind a Seamless, Beat-Synced Video Loop\" | Hashnode"
description: "Deriving the frame count and the beat alignment from one number is the detail most loop tools get wrong, and the drift only shows after a dozen repeats. The gua"
url: "https://hashnode.com/posts/the-math-behind-a-seamless-beat-synced-video-loop/6afae0d2af9751ae42a53cba/comment/6afbc004ab3372eca73d88a0"
---

[Discussion](https://hashnode.com/posts/the-math-behind-a-seamless-beat-synced-video-loop/6afae0d2af9751ae42a53cba)

Comment [The Math Behind a Seamless, Beat-Synced Video Loop](https://hashnode.com/posts/the-math-behind-a-seamless-beat-synced-video-loop/6afae0d2af9751ae42a53cba)

[DemoVexa](https://hashnode.com/@demovexa)

[1d ago](https://hashnode.com/posts/the-math-behind-a-seamless-beat-synced-video-loop/6afae0d2af9751ae42a53cba/comment/6afbc004ab3372eca73d88a0)

Deriving the frame count and the beat alignment from one number is the detail most loop tools get wrong, and the drift only shows after a dozen repeats. The guards for a bad tempo estimate are worth having too. One thing I'd add: render at the frame rate the platform will actually play. If a platform re-encodes a 30 fps file to a different rate, the half frame you rounded away can come back at the seam.
