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.

Sign up for GitHub

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

Jump to bottom

maintain internal clock when no external clock is used #10

Closed
1 task done
wraybowling opened this issue Sep 2, 2020 · 2 comments
Closed
1 task done

maintain internal clock when no external clock is used #10

wraybowling opened this issue Sep 2, 2020 · 2 comments
Milestone
The Clock

Comments

@wraybowling
Copy link
Member

wraybowling commented Sep 2, 2020 •
edited
Loading

Created from #5
Not everyone has a Pam's. I think the most obvious solution would be to detect if there are changes happening on the Tempo input.

  • research the tempo of the factory firmware
@wraybowling wraybowling added this to the The Clock milestone Sep 2, 2020
This was referenced Sep 2, 2020
Closed
Open
@wraybowling
Copy link
Member Author

As a side-effect to using the Peaks pattern detection algorithm, this seems to already be in place! Factory tempo is harder to measure as it appears to be a percentage of whatever baseline was set by the tempo of the recorded beat.

@wraybowling
Copy link
Member Author

Assuming the tempo knob is centered when recording, the left is 73% speed and right is 130% speed

Screen Shot 2020-09-10 at 6 52 34 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
The Clock
Development

No branches or pull requests
1 participant
@wraybowling