-
Notifications
You must be signed in to change notification settings - Fork 30
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
Model Clock time signature change behavior after Ableton's #212
Comments
Implementation thoughts:
|
Starting the clock would look like:
We're going to have to rework the existing ClockState's All measure math / measure offset math needs to be relative to the last recorded downbeat. |
Might be able to drop the Consider:
I'm honestly not sure what the utility of the Anyways, this also opens up the possibility of a
... where |
When changing time signature, it applies retroactively against the last time signature change marker - effectively the time origin or wherever a time signature change marker was created.
Time signature change markers always create a new downbeat, even if that means truncating the measure preceding them (e.g. 3/8 of the way into a 4/4 bar).
The text was updated successfully, but these errors were encountered: