-
Notifications
You must be signed in to change notification settings - Fork 404
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
Tuning Center Note Calibration #1445
Labels
Tuning
Non-standard tuning extensions
Comments
Just an update before I put my laptop away for the year
So more work to do here. Also #1041 would solve a lot of the problem |
baconpaul
added a commit
to baconpaul/surge
that referenced
this issue
Jan 5, 2020
The tuning center note I had picked, inexplicably, was Midi 48 / Pitch 16 / Frequency 130. This meant retuning put notes at the wrong point vs an expected Midi60 constant. So fix this (which was a 2 line fix) but also add a collection of unit tests which exercise the tuning way more intelligently, including doing some rudimentary pitch detection on a running surge. Closes surge-synthesizer#1445
baconpaul
added a commit
to baconpaul/surge
that referenced
this issue
Jan 5, 2020
The tuning center note I had picked, inexplicably, was Midi 48 / Pitch 16 / Frequency 130. This meant retuning put notes at the wrong point vs an expected Midi60 constant. So fix this (which was a 2 line fix) but also add a collection of unit tests which exercise the tuning way more intelligently, including doing some rudimentary pitch detection on a running surge. Closes surge-synthesizer#1445
baconpaul
added a commit
that referenced
this issue
Jan 5, 2020
The tuning center note I had picked, inexplicably, was Midi 48 / Pitch 16 / Frequency 130. This meant retuning put notes at the wrong point vs an expected Midi60 constant. So fix this (which was a 2 line fix) but also add a collection of unit tests which exercise the tuning way more intelligently, including doing some rudimentary pitch detection on a running surge. Closes #1445
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As reported by @JackyLigon on slack
My plan of attack here is to tackle this in the unit test framework first so I'm ready for when I tackle KBM.
The text was updated successfully, but these errors were encountered: