Skip to content

Releases: cuthbertLab/music21

music21 v9.9.1

12 Oct 09:16

Choose a tag to compare

Python 3.14 Compatible

Music21 v9.9.1 brings full Python 3.14 compatibility to v9 -- there was one incompatibility regarding "NotImplemented" in v9.9.0 w/ Python 3.14 -- users who don't use Python 3.14 have no reason to upgrade from 9.9.0 (see #1830)

Also mark the pyproject.toml as Python 3.14 compatible.

No docs being uploaded here since they are unchanged from 9.9.0

pip install -U music21 to get the latest version.

Full Changelog: v9.9.0...v9.9.1

music21 v9.9.0

06 Oct 06:23
7842de3

Choose a tag to compare

Update summary

  • Support Dorico as MusicXML reader. by @knutnergaard in #1788
  • music21.text.assembleLyrics: support custom word separator by @oxygen-dioxide in #1797
  • Add github codespace support by @oxygen-dioxide in #1805
  • Modernization of Lilypond generated code (see below)
  • Since this will be the last release in the v9 line, music21 v9.9 is the last version to support Python 3.10. It has been tested on Python 3.14rc3 and looks good to go with that system.

What's Changed: Bug Fixes and smaller improvements

  • Improve Lilypond opening in Windows by @mscuthbert in #1773
  • Also merge spanners when calling stream.Score.partsToVoices by @guang-yng in #1796
  • Fix duration exceptions for slight rounding by @mscuthbert in #1802
  • Rewrite Docs upload script by @mscuthbert in #1804
  • Improve docs for Percussion Chords by @mscuthbert in #1803
  • Update of property assignment syntax for Lilypond conversion (issue #1791) by @jeremy9959 in #1800
  • Updated the FAQ + Build Docs by @mscuthbert in #1810
  • Fix to m21ToXML.py:parseFlatElements() by @gregchapman-dev in #1806
  • Consistant use of 1.0 instead of 1 or 1. by @mscuthbert in #1811
  • Braille translate - support smart quotes by @mscuthbert in #1814
  • Make UserSettings more dict-like by @mscuthbert in #1816
  • Support RepeatBrackets for pianos by @mscuthbert in #1818
  • Stream.template() gets a removeAll keyword and exemptFromRemoveAll keyword in PR1818. This allows for things like removing all spanners except RepeatBrackets (which is what we used it for.
  • Fixed links to my articles about music21 (I decided to leave academia.edu over their AI use policies)

New Contributors

Full Changelog: v9.7.1...v9.9.0

music21 v9.7.1

19 Jun 11:51
0ea1e00

Choose a tag to compare

Music21 v9.7.1 is a maintenance release that fixes a bug in the pip version of music21 which would not work with numpy 2.0. Now the dependencies of music21 are the same whether installed from source/requirements.txt or pip/pyproject.toml.

This release also fixes errors (typing and intervals with concrete notes) discovered by mypy 1.16 and incorporates grammar and spelling fixes in documentation discovered by Pratim Vasireddy.

What's Changed

New Contributors

Full Changelog: v9.7.0...v9.7.1

music21 v9.7

22 May 13:06
3ad399f

Choose a tag to compare

Music21 v9.7 is an incremental, but still substantial release focusing mainly on import and export quality and speed. MIDI Lyrics and improved, PedalMarks are added (with more to come). Substantial new tools for FretBend and other tablature-based work.

numpy 2.0–2.2 is now supported, which makes it possible to run music21 on Windows with Python 3.13 without a compiler -- this was
the main reason for moving up the release by a month!

An update to the CONTRIBUTING guidelines -- all AI contributions must be explicitly mentioned. AI-generated contributions (whether properly declared or suspected) that do not pass tests will be closed without comment -- see Simon Williamson's blog about how AI is shifting the coding burden from programmers to reviewers for context.

Thanks to @gregchapman-dev, @adhooge, @TimFelixBeyer, @jacobtylerwalls and many others for contributions to code. And new, special thanks to Anne G. Hamill who has been helping very much with the music21list through some very difficult Google Groups times!

What's Changed

  • MIDI + Lyrics now import #1769 and export #1779 -- thanks to @oxygen-dioxide . Lyrics are encoded in many recent MIDI files used in AI singing synthesis, so this is an important update!
  • Updated Linting/etc. by updating Astroid @mscuthbert in #1755
  • (Somewhat backwards incompatible: Discussed on list) midi.__init__ functions are now in midi/base.py or music21.midi.base -- matching most other formats. Added a lot of typing for MIDI conversion (by @mscuthbert in #1757 and #1758 and #1778)
  • Support enclosure == Enclosure.NO_ENCLOSURE which is different from enclosure == None by @gregchapman-dev in #1761
  • PedalMark support by @gregchapman-dev in #1762
  • FretBend supports alter (interval), prebend, and release by @adhooge in #1580
  • Roundtrip inverted chord symbols properly by @mscuthbert in #1775
  • Interpret empty tags as rests on Finale documents only (derived from PR #1636, thanks @TimFelixBeyer!) by @gregchapman-dev in #1777
  • Allow numpy 2.0+ with music21 by @mscuthbert in #1781

Thanks to two new contributors

Full Changelog: v9.5.0...v9.7.0

music21 v9.5.0

20 Feb 00:36
ff16dc2

Choose a tag to compare

Music21 v9.5 is a small bug-fix release that fixes a few hard to find bugs, takes advantage of updated dependencies, and adds a bit more typing in various places.

Fixes Introducing Tiny Incompatibilities

These incompatibilities have been removed from music21 in order to get correct typing. They were never documented nor promised to work, hence considering it okay with Semantic versioning.

  • interval.getWrittenLowerNote works on notes and pitches but both objects must be a Note or must be a Pitch. (This restriction guarantees that the type of object being returned as the lower one will not vary based on attributes, and lets these functions be properly typed). By @mscuthbert in #1749 (started in 1747 by mistake) -- same is true for the parallel methods getWrittenHigherNote, getAbsoluteHigherNote, and getAbsoluteLowerNote. Now your IDE/mypy etc. should know the type of object being returned by these poorly-named functions!
  • Removed the "ability" to do this: p = pitch.Pitch(pitch.Pitch('D')) to get a D. Never was documented before: Pitches now cannot take other pitch objects as arguments; this ability was just used in the pre-typed past where we were mixing strings and Pitch objects interchangeably and was only used in music21 in one place (reduceChords.py). The newly created Pitch objects lost a lot of information about harmonics, accidental display, etc. so this was a good catch. Contributed by first-time contributor @float3 in #1746

What's Changed

  • Fixed links to generated documentation by @jacobtylerwalls in #1741
  • Take advantage of Astroid 1015 bug being fixed by @mscuthbert in #1745 -- many overloaded functions in music21 were very verbose with code that did not actually run in order to pass mypy with Astroid bug no. 1015 (a tough bug!). Major contributions to fixing the bug were given by @jacobtylerwalls. Also better docs about why music21 has its own StrEnum package. Also 'highestTime' will forever be equivalent to OffsetSpecial.AT_END -- if you know about this, it's great. Most will not care.
  • Added some typing to graph modules by @mscuthbert in PR1745 above.
  • Updated typing on tablature and intervals by @mscuthbert in #1747
  • Code of Conduct Clarify by @mscuthbert in #1748
  • Update interval Typing overloads by @mscuthbert in #1749
  • Fix a case where octave transposing instruments like piccolo or double bass imported from MusicXML could have incorrect octave information and bad enharmonic transposition (C#s becoming Dbs) fixed by @gregchapman-dev in #1752 (this is unrelated to a question recently here and in StackOverflow about the difference between transposing by P8 and by 12 semitones (thanks to @vanderstel for answering).)
  • Bug fix: corpora (including the built in core corpus) which were indexed using Python 3.13 could not be read on other systems (like Mac to Linux); a pathlib.Path was being stored in the corpus accidentally. Fixed by @mscuthbert in #1754

New Contributors

Full Changelog: v9.3.0...v9.5.0

music21 v9.3

29 Oct 09:28
2d93372

Choose a tag to compare

Music21's development continues with v.9.3, the first release since Myke Cuthbert's year-long sabbatical and first since June 2023. Thanks to the community for great patience, new developments, new docs, new contributions, and extreme resilience during a summer 2024 spam attack (the first time I took 4 days off out of cell-phone range, they struck!) and doc/homepage problems as the project changed homes.

Music21 v.9.3 is the first release version to officially support both Python 3.12 and Python 3.13. It will probably also be the last to support Python 3.10 and the last to have primary compatibility for numpy v1 and matplotlib v2. The next version will move to the latest major versions of those libraries (if all goes well!) and work to take advantage of their new ecosystems. (However, there are some good PRs waiting to be merged, so there may be one more release before breaking compatibility)

It is designed to be mainly backwards compatible with v9.1 (the first v9 release) but there are a few little things that fix common errors that are not strictly backwards compatible.

This is a minor release with no major new features or changes, mostly bug-fixes, new compatibilities, fixed docs, etc. I want to single out @TimFelixBeyer for contributing a number of optimizations and speed ups, along with many new and long-time contributors (new contributors listed below).

New Home: Old Gratitude

This is the first version of music21 released since I left being a prof at MIT (my wife has been a professor of music at University of Hawai'i since just before the pandemic and the commute to Boston was too long; she supported my career for a decade and I'm proud to be able to do the same for her). I want to thank my colleagues, staff, students, and donors at MIT who helped music21 through its first nine versions. I'm still in the process of "unpacking the boxes" at https://www.music21.org/music21docs/ but things will go well. And thanking my co-founders and fellow music theory nerds at https://www.artusimusic.com/ for knowing the value of music21 as part of our ecosystem there.

What's Changed

New Contributors

Full Changelog: v9.1.0...v9.3.0

music21 v9

16 Jun 23:23
a243454

Choose a tag to compare

Music21 v9 (June 2023) is the latest release of music21, a toolkit for computational music research.

Version 9 contains about 600 new commits and features from the version 8 release from September 2022. It is the latest and best release in the industry standard toolkit for doing music research and composition ("traditional" computation and AI/ML) with musical scores.

As a new Version X release, music21 gains a lot of its power with a few non-backwards compatible changes that make the system easier to use, faster, and more up to date. People using music21 in existing environments should read the change logs to make sure their systems work with it before upgrading.

A big change in music21 is that v9 is compatible with Python 3.10 and 3.11 only. The version 9 release will be updated to be compatible with at least Python 3.12 when it is released. Users on Python 3.8 and 3.9 should stick with v8 and those on older versions should look at the README to see what version will be installed for their systems.

Two weeks from the release of version 9 (July 1, 2023), Michael Asato Cuthbert, the lead developer of music21 will take a 6-12-month sabbatical from monitoring the mailing list, answering questions/issues, and merging PRs in order to focus on what he does best and what is best for the community: developing core parts of the system and documenting what already exists. Working with the user community has been amazing, but given that he only has about 10-15 hours per week to devote to the project, it often means deviating from efforts that help a large number of people to instead work through PRs and issues that are important to a smaller community. This news will probably not be welcomed by some, but the results should be better for the larger community.

What's Changed

  • Music21 v9 is for Python 3.10 and 3.11 only and uses tools and speedups only available to those versions. Music21 drops its prior policy of supporting previous 3 versions and now supports the latest 2 versions only (to improve developer experience).
  • Notebook/Jupyter: All pages are now shown on .show(). Compatible with Jupyter 7.0beta and JupyterLab. MIDI improvements (@mscuthbert in #1592)
  • Added to corpus: (1) Queen Liliuokalani’s Aloha Oe, (2) J.R. Johnson’s Lift Every Voice And Sing (3) Vincente Lusitano’s madrigal Allor che Ignuda – part of a larger project to make the music21 corpus more representative.
  • Lots more typing! Use music21 in a modern IDE to see it. Uses Python 3.10 TypeGuards. Add common.classTools.holdsType([‘a’, ‘b’], str) which asserts that everything in a collection has the same type. (@mscuthbert in #1447). converter and corpus are fully typed.
  • Docs! Documentation of equality explained better. braille, corpus, converter much improved. (1) Much better aesthetics and utility @mscuthbert in #1455 and #1452). (2) Add “developerReference/startingOver” – mistakes made in designing music21 that are too late to fix, but the next generation of software should not emulate. (3) add docs about abcFormat support (@mscuthbert in #1484). (4) coreInsert (@mscuthbert in #1549). (5) layout (@mscuthbert in #1554). (6) clercqTemperley (RS100 dataset) format (#1558)
  • RomanText and related formats: (1) Repeats in RT and TSV are improved (@malcolmsailor in #1434, #1435, #1503) (2) anacrusis support (@mscuthbert in #1532) (3) measure numbers on ClercqTemperley (@mscuthbert in #1558)
  • harmony: (1) RomanNumerals and ChordSymbols with front accidentals (flat II, sharp IV, etc.) now take their 7ths, 9ths, etc. from the underlying keys (@mscuthbert w/ thanks to @malcolmsailor in #1439), (2) RomanNumeral’s writeAsChord works properly (@mscuthbert in #1445)
    and (3) transpose properly (@malcolmsailor in #1414). (4) roman.RomanNumeral(2, ‘C’) will now give d-minor, not d-major (@jacobtylerwalls in #1481), (5) preferSecondaryDominants implements V/x (@MarkGotham in #796).
  • MusicXML improvements: (1) TempoText is exported (@gregchapman-dev in #1437)
    (2) harmony/numeral figures are MusicXML 4.0 compatible (@mscuthbert in #1445) (3) Preserve multiple fingerings on chords in musicxml import (@jacobtylerwalls in #1475) (4) Translate "implicit" attribute of MusicXML measures (@jacobtylerwalls in #1493) (5) Synchronize Measure IDs on Musicxml out (@rigaux in #1490) (6) MusicXML sound tag finds metronome marks (@TimFelixBeyer in #1579) (7) Add MusicXML security warning (@mscuthbert in #1584)
  • Speed/Performance improvements on (1) deepcopy (@mscuthbert in #1464) (2) ABC (@mscuthbert in #1461) (3) LanguageDetector (@mscuthbert in #1456) (4) quantize() (@TimFelixBeyer in #1594) (5) use deques instead of pop(0) #1466, (6) searching/MetadataBundles cache in tests (@mscuthbert in #1511)
    (7) findGaps() on gapless streams (@jacobtylerwalls in #1515) (8) ChordSymbols (@jacobtylerwalls in #1527)
  • Braille – add segment.BrailleElementGrouping. Good amount of refactoring. (@mscuthbert in #1495)
  • Converter/Corpus: converter.toData – like .write or .show but gives the raw data as a string or byte by @mscuthbert in #1451
  • Frozen/Immutable objects can be created now; this will allow for creating, for instance, one default 4/4 meter that cannot be changed but used as a default in many places. common.FrozenObject and duration.FrozenDuration (@mscuthbert in #1460)
  • New subConverters register above default subConverters, so it is now possible to develop a subConverter like Greg’s converter21 project that handles a format music21 supports but do it differently or better. (@mscuthbert in #1520)
  • Ornaments/Expressions (all by @gregchapman-dev) – (1) ornament accidentals have a great new system and are aware of their measure and key context (#1545) (2) Mordents get placement like Turn and Trill (#1516) (3) Support for delayed turns (#1533)
  • Spanners: (1) Spanner.fill() – say you’ve set a slur to just include the first and last notes. .fill() will find all the intermediate notes. (@gregchapman-dev in #1486) (2) spanner.SpannerAnchor class allows a spanner to start and stop at a point where there is no other Music21Object at the offset (like a whole note crescendo that begins on beat 2 and ends on beat 3) (@gregchapman-dev in #1479). (3) Guitar: Hammer-on and Pull-off as Spanners (@louisbigo in #1142)
  • Streams – (1) new module stream.tools and stream.tools.removeDuplicates (e.g. keys, clefs, by @MarkGotham in #1454) . (2) stream.makeNotation.saveAccidentalDisplayStatus() context manager for restoring pitches’ accidentalDisplayStatus after a manipulation (like transposition by octave) @gregchapman-dev. (3) stream.makeNotation.makeOrnamentalAccidentals (#1545)
  • Percussion: (1) Implement useful PercussionChord.pitches property (@jacobtylerwalls in #1547), (2) Ignore Unpitched objects in key analysis (@jacobtylerwalls in #1543, (3) Search support (@mscuthbert in #1597)
  • MIDI: (1) Minimize gaps produced by quantization algorithm (@jacobtylerwalls in #1540) (2) fix jupyter/colab MIDI (@mscuthbert in #1565) (3) Increase default MIDI ticksPerQuarter for higher accuracy of tuplets (@TimFelixBeyer in #1577)
  • ABC: set version from I:abc-version information (@mscuthbert in #1589)
  • pitch module gets: isValidAccidentalName, standardizeAccidentalName.

Bug fixes

Read more

music21 v8.3.0

11 May 18:31

Choose a tag to compare

Music21 v8.3 is a maintenance release that fixes a few bugs in romanText/translate (thanks @malcolmsailor) already in v9alpha, but also fixes a change in the Github.io version of music21j that broke .show('midi') inside Jupyter notebooks.

What's Changed

Full Changelog: v8.1.0...v8.3.0

music21 v8

19 Sep 10:19
b1ea58e

Choose a tag to compare

I'm proud to release v8 of music21, the toolkit for computer-aided music analysis, score manipulation, computational musicology, etc. This release (technically 8.1) builds on 12.5 months of work from v7, and like all new big number releases has a few backwards incompatible changes from before, in exchange for cool new features.

Version 8 supports Python 3.8+, if you need Python 3.7 (such as on Google Colab which is now 3+ Python versions behind) stick to music21 v7. V8 is the first to fully support Python 3.10 and will receive patches to support Python 3.11 in the future. As Python 3.11 is due to be released any day now, keeping with the m21 policy of supporting three versions of Python, music21 v9 (work starts tomorrow!) will support Python 3.9 and above only.

Big Changes

  • The biggest new improvement in v8 is an all new Dublin-Core / MARC based metadata system that allows for encoding a huge amount of information about a score. Look at the new docs for music21.metadata for more information. Thanks to Greg Chapman for the big amount of work on this. (@gregchapman-dev in #1266)
  • Modern installation system, based on Hatch. If you have problems, please let me know -- I expect some growing pains on this.
  • ArpeggioMark and ArpeggioMarkSpanner classes. by @gregchapman-dev in #1337
  • Adding DCML v2 parsing to tsvConverter.py by @malcolmsailor in #1267
  • Explicit Keywords on all music21 objects by @mscuthbert in #1377
  • Continued Major improvements in Typing across music21. by @mscuthbert and @jacobtylerwalls. If you are using a modern IDE, you will find the number of music21-related bugs you create will go down hugely.
  • Ever more docs and more relevant (and diverse examples)

Other changes/fixes since v7.3

Significant Improvements and bugs Fixed from 7.1 to 7.3.3

Read more

music21 v8.0.0rc2

19 Sep 07:27
a4a640d

Choose a tag to compare

music21 v8.0.0rc2 Pre-release
Pre-release

Music21 v8 Release Candidate

testing a new deploy system.