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

timestamp missing #1

Closed
RobinTournemenne opened this issue Aug 17, 2022 · 1 comment · Fixed by #3
Closed

timestamp missing #1

RobinTournemenne opened this issue Aug 17, 2022 · 1 comment · Fixed by #3
Assignees

Comments

@RobinTournemenne
Copy link

Hello !
Very nice piece of code. The only difficulty was to guess the timestamp of each predicted pitch value. Maybe you could add in the output file the timestamp like in the CREPE algorithm.
Regards,
Robin

@Sytronik Sytronik self-assigned this Dec 13, 2023
@Sytronik
Copy link
Owner

Sorry, it's too late, but thank you for the suggestion. I'll add that functionality asap.

Now, you can calculate the timestamp by hop_ms * [0-based index of the output pitch sequence] (in milliseconds).
hop_ms can be set by the command line argument, and the default is frame_ms/4.

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

Successfully merging a pull request may close this issue.

2 participants