Closed clementabary closed 8 months ago
While minor performance variations can be expected due to different package versions and seeds, obtaining consistently poor results implies a more significant underlying issue. For a sample with a tempo of 120, the beat intervals should be 0.5 seconds. Both runs initiate from the same beat time and their detections are fairly accurate for the initial 5 samples e.g. first run's (4.02, 4.52, 5.02, 5.54, 6.04). However, from 6.04 to 9.34, a phenomenon of half-tempo error occurs, indicating a need to adjust the jump back alpha parameter. I have also forwarded my GTZAN test log to you via LinkedIn message. I hope it helps.
Hi, I installed the package and run it for GTZAN evaluation reproduction and got fairly bad results. I ran it on the debug sample
808kick120bpm.mp3
in the BeatNet repository and got those outputs. I get:Beat times are clearly off/missing, plus results are different at each run actually. I don't know what is wrong, I wonder if someone took a dive in the code and found a quick fix? Thanks in advance!