Data

Tools

Indexes

Applications

Experiments

Open Source Science

Recent Releases of scarlatti_sonatas

scarlatti_sonatas - Updated paradata

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

scarlatti_sonatas - Metadata, prelims, README

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.

Domenico Scarlatti – Keyboard Sonatas (A corpus of annotated scores)

This corpus of annotated MuseScore files has been created within
the DCML corpus initiative and employs
the DCML harmony annotation standard.

While Italian-Spanish composer Domenico Scarlatti enjoyed generous royal patronage
throughout his career, his compositions were not widely circulated during his own lifetime.
He is best known today for 555 concise, one-movement keyboard sonatas, admired for
their stylistic breadth and variety, for their theatrical dramatic charge, and for their prophetic
formal innovations.

This corpus consists of 69 sonatas selected from the first 100 in Ralph Kirkpatrick's
chronological ordering. These earlier works display a comparatively restrained degree
of keyboard virtuosity and a considerable influence from the sequence-driven harmonic
rhetoric of Vivaldi and Corelli. Taken alongside our Corelli repository, these data will
provide rich material for study of the Italian Baroque precedents of sonata-allegro form.

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 Sonata K.1 has the following files:

  • MS3/K001.mscx: Uncompressed MuseScore 3.6.2 file including the music and annotation labels.
  • notes/K001.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/K001.measures.tsv: A table with relevant information about the measures in the score.
  • chords/K001.chords.tsv: A table containing layer-wise unique onset positions with the musical markup (such as dynamics, articulation, lyrics, figured bass, etc.).
  • harmonies/K001.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/K001.harmonies.tsv") notes = ms3.loadtsv("notes/K001.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). Domenico Scarlatti – Keyboard Sonatas (A corpus of annotated scores) [Data set]. Zenodo. https://doi.org/10.5281/zenodo.14992884

License

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

- Python
Published by github-actions[bot] over 1 year ago

scarlatti_sonatas - Eliminate Focused Warnings for requested WPs

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.

Domenico Scarlatti – Keyboard Sonatas

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 Sonata K.1 has the following files:

  • MS3/K001.mscx: Uncompressed MuseScore 3.6.2 file including the music and annotation labels.
  • notes/K001.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/K001.measures.tsv: A table with relevant information about the measures in the score.
  • chords/K001.chords.tsv: A table containing layer-wise unique onset positions with the musical markup (such as dynamics, articulation, lyrics, figured bass, etc.).
  • harmonies/K001.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) you'll be able to load any TSV like this:

```python import ms3

labels = ms3.loadtsv("harmonies/K001.harmonies.tsv") notes = ms3.loadtsv("notes/K001.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). Domenico Scarlatti – Keyboard Sonatas [Data set]. Zenodo. https://doi.org/{{ conceptdoi }}_

License

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

- Python
Published by github-actions[bot] over 1 year ago

scarlatti_sonatas - v0.1 Original annotations

Original annotations

These were among the first and oldest annotations created at the DCML's predecessor at TU Dresden. This release marks the point before the complete upgrade was undertaken. The README instructing the annotators read the following:

The harmonic annotations come from ancient times (hence harmonyversion 0.0.0) and have been handed down in the form of the TXT files contained in the folder `originalannotations`. A number of manual adjustments had to be made to allow their being written into the MuseScore files because their encoding is not very rigorous and was never algorithmically validated.

Apart from the syntactical inconsistencies and typical careless mistakes, the analyses look reasonable. However, since they predate last years' developments of the DCML standard, a couple of things will need to be corrected systematically, such as:

  • all modulations are expressed in absolute rather than relative terms;
  • repetition of identical labels;
  • the overuse of @none which, in this repertoire, can in principle always be avoided;
  • obvious syntax errors (e.g. I(M7));
  • absence of an overarching harmonic rhythm as a guideline for a consistent level of detail;
  • cadence labels (for example, QA ('Quintabsatz') was partially used for what we would label as HC);

During the update, these points can be corrected tacitly. Individual commits with explanatory messages should be created for changes to the actual analysis.

- Python
Published by johentsch over 1 year ago

scarlatti_sonatas - Domenico Scarlatti – Keyboard Sonatas v2.1

corpus_docs_commit: 40bce3e10e618a8e412643c4eccd738d718eb22c corpus_release: v2.1 data_reports_commit: 2f0de7dc9a29f1840c308943a07bc8ac95e6d82f dcml_commit: v2.6.9-ms3-1.2.4.post0.dev3-g5df6c9f-dimcat-0.3.0.post1.dev3-gde5198b example_fname: K001 example_full_title: the *Sonata K.1* example_subcorpus: .nan exclude_unannotated: 0 git_url: git@github.com:DCMLab/scarlatti_sonatas.git has_annotations: 1 has_submodules: 0 pretty_repo_name: "Domenico Scarlatti \u2013 Keyboard Sonatas" repo_main_commit: bd6441c91d8749215dcbd98cd4d1908cad840810 repo_name: scarlatti_sonatas workflow_version: .nan zenodo_badge_id: .nan

- Python
Published by ms3-bot almost 3 years ago