Replies: 1 comment 1 reply
-
Well...they should all be quarter note rather than beat. Did you remember where beats occur in the doc? In general, I think beat is a rather vague concept in music. The issue about bpm vs qpm is somewhat similar to key vs key signature issue. MIDI does a really bad job on specifying symbolic features that do not affect playback. We could support this, but I doubt if there exist any files that contain such information without the need of inferring. Is there any field for such information in MusicXML other than time signatures? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is the formula for calculating the measure length in time steps? Could this information be added to the docs? https://muspy.readthedocs.io/en/latest/timing.html
A time signature specifies the number of beats per bar and how long a beat is. So the length of a bar in quarter notes should be something like
numerator * 4 // denominator
. But in time steps, it could be eithernumerator * 4 * resolution // denominator
, or justnumerator * resolution
. Which of these is it? It's not clear because the docs sometimes say thatresolution
is the number of time steps per beat and sometimes per quarter note.Moreover, there are compound meters like 6/8 and 9/8, where the beat duration is actually 3/8 and not 1/8. This is how
pretty_midi
handles them.It's hard for me to wrap my head around all this. Should
TimeSignature
have another attribute specifying the number of time steps per beat or bar? This could be automatically computed, but perhaps it should be possible to set it explicitly in order to achieve some weird compound signatures.Beta Was this translation helpful? Give feedback.
All reactions