Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OnsetDetect precision: Third decimal place is always rounded to 0. #506

Closed
jie-chen opened this issue Sep 3, 2022 · 1 comment
Closed

Comments

@jie-chen
Copy link

jie-chen commented Sep 3, 2022

Hi, when running binary of OnsetDetector, OnsetDetectorLL or CNNOnsetDetector. The third decimal place is always rounded to zero. Anyway to disable it?

@superbock
Copy link
Collaborator

The reason is that the resolution of those methods is 100 frames per second, thus when printing with 3 decimals, the last one will always be 0. The reason we're printing 3 decimals is that some other methods use a higher frame rate and hence produce results with a higher precision.

You can change the fmt argument of madmom.io.write_events to change the behaviour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants