Data

Tools

Indexes

Applications

Experiments

Open Source Science

Recent Releases of monteverdi_madrigals

monteverdi_madrigals - Updated paradata


Published by github-actions[bot] 10 months ago

monteverdi_madrigals - Update README.md

Fixed linebreaks! Just took a little research


Published by github-actions[bot] 12 months ago

monteverdi_madrigals - Metadata upgrades and README note

This is a README file for a data repository originating from the DCML corpus initiative and serves as welcome page for both

For information on how to obtain and use the dataset, please refer to this documentation page.

Claudio Monteverdi – Madrigals (A corpus of annotated scores)

This corpus of annotated MuseScore files has been created within the DCML corpus initiative and employs the\r DCML harmony annotation standard. Claudio Monteverdi's nine books of madrigals span the entirety of the composer's\r career, from his adolescence to his very old age. For this reason, they evince the transition, Monteverdi's\r great innovation, from the blended interlocking lines of Renaissance polyphony to the solid verticals and\r speech-like rhythms of Baroque operatic homophony. Arguably the centrepiece of this collection is the\r ubiquitous and sensational "Cruda Amarilli," whose striking unprepared dissonances scandalized fellow\r composer Giovanni Artusi and prompted an infamous feud between the two musicians. Besides a selection\r of madrigals, this repository also features the stunning and energetic "Laudate pueri," a posthumously\r published psalm setting that merges rich Renaissance-style imitation with definitively Monteverdian\r text-setting techniques.

Getting the data

Data Formats

Each piece in this corpus is represented by five files with identical name prefixes, each in its own folder. For example, the 12th madrigal from the 2nd book has the following files:

  • MS3/2-12.mscx: Uncompressed MuseScore 3.6.2 file including the music and annotation labels.
  • notes/2-12.notes.tsv: A table of all note heads contained in the score and their relevant features (not each of them represents an onset, some are tied together)
  • measures/2-12.measures.tsv: A table with relevant information about the measures in the score.
  • chords/2-12.chords.tsv: A table containing layer-wise unique onset positions with the musical markup (such as dynamics, articulation, lyrics, figured bass, etc.).
  • harmonies/2-12.harmonies.tsv: A table of the included harmony labels (including cadences and phrases) with their positions in the score.

Each TSV file comes with its own JSON descriptor that describes the meanings and datatypes of the columns ("fields") it contains, follows the Frictionless specification, and can be used to validate and correctly load the described file.

Opening Scores

After navigating to your local copy, you can open the scores in the folder MS3 with the free and open source score editor MuseScore. Please note that the scores have been edited, annotated and tested with MuseScore 3.6.2. MuseScore 4 has since been released which renders them correctly but cannot store them back in the same format.

Opening TSV files in a spreadsheet

Tab-separated value (TSV) files are like Comma-separated value (CSV) files and can be opened with most modern text editors. However, for correctly displaying the columns, you might want to use a spreadsheet or an addon for your favourite text editor. When you use a spreadsheet such as Excel, it might annoy you by interpreting fractions as dates. This can be circumvented by using Data --> From Text/CSV or the free alternative LibreOffice Calc. Other than that, TSV data can be loaded with every modern programming language.

Loading TSV files in Python

Since the TSV files contain null values, lists, fractions, and numbers that are to be treated as strings, you may want to use this code to load any TSV files related to this repository (provided you're doing it in Python). After a quick pip install -U ms3 (requires Python 3.10 or later) you'll be able to load any TSV like this:

```python import ms3

labels = ms3.loadtsv("harmonies/2-12.harmonies.tsv") notes = ms3.loadtsv("notes/2-12.notes.tsv") ```

Version history

See the GitHub releases.

Questions, Suggestions, Corrections, Bug Reports

Please create an issue and/or feel free to fork and submit pull requests.

Cite as

Johannes Hentschel, Yannis Rammos, Markus Neuwirth, & Martin Rohrmeier. (2025). Claudio Monteverdi – Madrigals (A corpus of annotated scores) [Data set]. Zenodo. https://doi.org/{{ concept_doi }}

License

Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License (CC BY-NC-SA 4.0).


Published by github-actions[bot] 12 months ago

monteverdi_madrigals - v2.0: Re-extracts all files using ms3 v2.5.4

Changes to the TSV facets

Updated filenames

The TSV files have been renamed and now come with a suffix specifying the data facet that they represent. The four facets are

  • measures
  • notes
  • harmonies
  • chords

so, for example, the file measures/2-12.tsv has been renamed to measures/2-12.measures.tsv.

Added resource descriptors

Each TSV file is now accompanied with a JSON resource descriptor following the frictionless specification for Tabular Data Resources. They can and have be used to validate the tabular data.

These files have the same names as the TSV files they describe but replacing the .tsv extension with .resource.json. For example, the file measures/2-12.tsv has the corresponding descriptor measures/2-12.resource.json.

These metadata files replace the previous csv-metadata.json files (which followed the CSVW standard) that had described the data inadequately.

Added column quarterbeats_all_endings

The quarterbeats column (also known as qstamp) that had already been available does not provide values for first or third endings, expressing the dimensions of a singular playthrough without taking into account any repeats. The newly added column quarterbeats_all_endings does not have any empty values, providing continuous positions as if each measure followed the previous one.

Renamed index column

The first column of metadata.tsv was renamed from fname to piece.

Changes to the reviewed folder

The _reviewed.mscx files compare the current set of annotation labels against those from the previous version (v2.1). They are identical, so no differences are displayed.

Wherever the MuseScore parser throws one or several warnings (e.g. because an annotation label does not match the score very well), these warnings appear in a .warnings file. For example, the warnings for 2-12 can be seen in reviewed/2-12.warnings. One goal for future versions of this dataset would be to reduce the number of warnings to the point of addressing all of them.

Frictionless datapackage

This release is the first one that has a frictionless datapackage attached (below). It consists of

  • monteverdi_madrigals.zip, a ZIP file containing one TSV file per facet, that corresponds to a concatenation of the TSV files in the respective folder, that is
    • monteverdi_madrigals.expanded.tsv
    • monteverdi_madrigals.measures.tsv
    • monteverdi_madrigals.metadata.tsv (concatenation of a single file)
    • monteverdi_madrigals.notes.tsv
    • monteverdi_madrigals.chords.tsv
  • monteverdi_madrigals.datapackage.json, the package descriptor.

If one has the frictionless framework installed, one can use the descriptor to validate the package using the command

bash frictionless validate monteverdi_madrigals.datapackage.json


Published by github-actions[bot] about 1 year ago

monteverdi_madrigals - v1.0

What's Changed

  • Upgraded to 3.6.2, moved labels to RNA layer by @johentsch in https://github.com/DCMLab/monteverdi_madrigals/pull/1
  • Remove duplicate of 4-19 (4-20). by @yrammos in https://github.com/DCMLab/monteverdi_madrigals/pull/2

Full Changelog: https://github.com/DCMLab/monteverdi_madrigals/commits/v1.0


Published by johentsch about 1 year ago