Slight differences in BPM Reporting in SlicerT
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
The BPM mentioned in the beats files like: techno_synth02 - 140 BPM, is different compared to what SlicerT reports. eg. in this case 125. Most beats have slightly different reporting here in SlicerT.
Audacity reports them as they are mentioned in their filenames.
| Beat sample | in Filename ( or in Audacity) | in SlicerT |
|---|---|---|
| brief01 | 140 | 138 |
| tb303_01 | 123 | 124 |
| techno_bass01 | 140 | 147 |
| techno_bass02 | 140 | 138 |
| techno_synth02 | 140 | 125 - huge difference |
| techno_synth03 | 130 | 131 |
How to reproduce:
- check the bpm as tagged in filename.
- Open the sample in Audacity to check authenticity.
- Load the sample in SlicerT and see the BPM as calculated.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the discrepancy in SlicerT with the listed samples, comparing each reported BPM with its filename and Audacity. Trace the BPM calculation entry point and identify why values differ; done means SlicerT reports the expected BPM consistently for the affected samples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- audio-video-rtc, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100