music21 | music21 is a Toolkit for Computational Musicology | Database library

Yes, one of the improvements in music21 v.7 is that files imported from MIDI now have a similar representation to files imported from MusicXML and other formats. Specifically, Parts now have Measures, which may or may not have Voices, rather than Parts directly containing Voices. Code should not depend on finding Voices directly contained in Parts, which is what this example was doing.

Instead, use this code to find all the measure-voices:

From the github repo:

At present it's not possible to run outside of the browser. :-( But we're working on removing certain JQuery patches that should make it easier to do. You may however need to use ES6-style imports.

geopandas 0.10.1

• have noted that your data is on kaggle, so start by sourcing it
• there really is only one issue shapely.geometry.MultiPoint() constructor does not work with a filtered series. Pass it a numpy array instead and it works.
• full code below, have randomly selected a point to serve as gpdPoint

1

.show() is nice at a glance when debugging but not ideal for structured output. Have a look at recurse(). music21 has a container ontology: objects are "in" voices, "in" measures, "in" parts, "in" scores. So if you start top-down from a score and want to walk every nested container, just use recurse():

If you're using ipython, you can try just muting the section you're trying to execute:

Lord have mercy I needed to pass forceSource=False into the midiTracksToStreams call as well:

The current version from PyPI (7.1.0) seems to always add one quarter note of silence at the end. This can be changed by setting music21.defaults.ticksAtStart, despite its name. The units are MIDI ticks defined by music21.defaults.ticksPerQuarter. The default value of both is 1024.

Be aware that some MIDI players will stop synthesizing when the file ends, so the sound will stop dead when the last note is released instead of dying away if there is no padding.

Also, some players may pad to a measure boundary no matter what you do. There is no way to encode a pickup measure in MIDI, other than inserting rests.

music21 v.7.1 started making measures in parts parsed from MIDI files. For that reason, the .timeSignature property is not very useful when called on a Part (example from docs: "This property is not recursive, so a Part will not have the time signature of the measure within it"). The fact that this used to work for MIDI files was inconsistent with the rest of the system.

If you just want the first time signature, perform a recursive search:

Old syntax (still works): myPart.recurse().getElementsByClass(music21.meter.TimeSignature)[0]

New shortcut syntax (v7): myPart[music21.meter.TimeSignature][0]

Equivalently, you can use strings such as 'TimeSignature' in the getter instead of class names.

You could also index into the first measure and access the .timeSignature property there: myPart['Measure'][0].timeSignature.

You can do this by getting list of images from directory and iterate over them.