Closed FrostyNick closed 1 year ago
Name | Link |
---|---|
Latest commit | 1fe4bf5b2370eea9e0c42b052f1b0195b36d5d60 |
Latest deploy log | https://app.netlify.com/sites/projectrhythmswipe/deploys/6486427b675da60008a59963 |
Deploy Preview | https://deploy-preview-20--projectrhythmswipe.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Please also change to V1.2.1.
Yeah, I should elaborate on that. The reason why I moved the red cube to that position is so the cube can be synced to the beat and the white box when it reaches there. It's supposed to be exactly 50% of the frame distance towards the beat to hit (assuming all songs have two beats in between but that could change; thus needing to be repositioned). It's pretty much the right way to time the beats.
Yeah, I should elaborate on that. The reason why I moved the red cube to that position is so the cube can be synced to the beat and the white box when it reaches there. It's supposed to be exactly 50% of the frame distance towards the beat to hit (assuming all songs have two beats in between but that could change; thus needing to be repositioned). It's pretty much the right way to time the beats.
Screenshot
Sounds good! I will improve the beat detector sometime this week and will do a pull request.
I'll try to merge this with upcoming branches if that works.
On this PR: