You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
II noticed the time signature meta-event hardcodes the last 2 arguments (clocks per tick, 32nd notes per beat) to the values {1, 96} in the time_signature meta-event:
static message time_signature(int numerator, int denominator)
{
int n = 1;
int powTwo = 0;
while (n < denominator)
{
n <<= 1;
++powTwo;
}
return {0xff, 0x58, 0x04, static_cast<uint8_t>(numerator), static_cast<uint8_t>(powTwo),
1, 96};
}
Maybe it can take optional parameters with defaults? e.g. int clocks_per_tick = 24, int 32nd_notes_per_beat = 8?
Also, are {1, 96} placeholders? From my research, {24, 8} are more typical.
The text was updated successfully, but these errors were encountered:
Hello!
II noticed the time signature meta-event hardcodes the last 2 arguments (clocks per tick, 32nd notes per beat) to the values {1, 96} in the time_signature meta-event:
Maybe it can take optional parameters with defaults? e.g.
int clocks_per_tick = 24, int 32nd_notes_per_beat = 8
?Also, are {1, 96} placeholders? From my research, {24, 8} are more typical.
The text was updated successfully, but these errors were encountered: