Dataset Open Access
Con Espressione Game Dataset
A piece of music can be expressively performed, or interpreted, in a variety of ways. With the help of an online questionnaire, the Con Espressione Game, we collected some 1,500 descriptions of expressive character relating to 45 performances of 9 excerpts from classical piano pieces, played by different famous pianists. More specifically, listeners were asked to describe, using freely chosen words (preferably: adjectives), how they perceive the expressive character of the different performances. The aim of this research is to find the dimensions of musical expression (in Western classical piano music) that can be attributed to a performance, as perceived and described in natural language by listeners.
The Con Espressione Game was launched on the 3rd of April 2018.
Listeners’ Descriptions of Expressive performance
piece_performer_data.csv: A comma separated file (CSV) containing information about the pieces in the dataset. Strings are delimited with
". The columns in this file are:
music_id: An integer ID for each performance in the dataset.
performer_name: (Last) name of the performer.
piece_name: (Short) name of the piece.
performance_name: Name of the the performance. All files in different modalities (alignments, MIDI, loudness features, etc) corresponding to a single performance will have the same name (but possibly different extensions).
composer: Name of the composer of the piece.
piece: Full name of the piece.
album: Name of the album.
performer_name_full: Full name of the performer.
year_of_CD_issue: Year of the issue of the CD.
track_number: Number of the track in the CD.
length_of_excerpt_seconds: Length of the excerpt in seconds.
start_of_excerpt_seconds: Start of the excerpt in its corresponding track (in seconds).
end_of_excerpt_seconds: End of the excerpt in its corresponding track (in seconds).
con_espressione_game_answers.csv: This is the main file of the dataset which contains listener’s descriptions of expressive character. This CSV file contains the following columns:
answer_id: An integer representing the ID of the answer. Each answer gets a unique ID.
participant_id: An integer representing the ID of a participant. Answers with the same ID come from the same participant.
music_id: An integer representing the ID of the performance. This is the same as the
answer: (cleaned/formatted) participant description. All answers have been written as lower-case, typos were corrected, spaces replaced by underscores (
_) and individual terms are separated by commas. See
cleanup_rules.txtfor a more detailed description of how the answers were formatted.
original_answer: Raw answers provided by the participants.
timestamp: Timestamp of the answer.
favorite: A boolean (0 or 1) indicating if this performance of the piece is the participant’s favorite.
translated_to_english. Raw translation (from German, Russian, Spanish and Italian).
performer. (Last) name of the performer. See
piece_name. (Short) name of the piece. See
performance_name. Name of the performance. See
participant_profiles.csv. A CSV file containing musical background information of the participants. Empty cells mean that the participant did not provide an answer. This file contains the following columns:
participant_id: An integer representing the ID of a participant.
music_education_years: (Self reported) number of years of musical education of the participants
listening_to_classical_music: Answers to the question “How often do you listen to classical music?”. The possible answers are:
registration_date: Date and time of registration of the participant.
playing_piano: Answer to the question “Do you play the piano?”. The possible answers are
cleanup_rules.txt: Rules for cleaning/formatting the terms in the participant’s answers.
translations_GERMAN.txt: How the translations from German to English were made.
Related meta data is stored in the
Alignments. This folders contains the manually-corrected score-to-performance alignments for each of the pieces in the dataset. Each of these alignments is a text file.
ApproximateMIDI. This folder contains reconstructed MIDI performances created from the alignments and the loudness curves. The onset time and offset times of the notes were determined from the alignment times and the MIDI velocity was computed from the loudness curves.
Match. This folder contains score-to-performance alignments in Matchfile format.
Scores_MuseScore. Manually encoded sheet music in MuseScore format (.mscz)
Scores_MusicXML. Sheet music in MusicXML format.
Scores_pdf. Images of the sheet music in pdf format.
Audio features computed from the audio files. These features are located in the
Loudness: Text files containing loudness curves in dB of the audio files. These curves were computed using code provided by Olivier Lartillot. Each of these files contains the following columns:
performance_time_(seconds): Performance time in seconds.
loudness_(db): Loudness curve in dB.
smooth_loudness_(db): Smoothed loudness curve.
Spectrograms. Numpy files (
.npy) containing magnitude spectrograms (as Numpy arrays). The shape of each array is (149 frequency bands, number of frames of the performance). The spectrograms were computed from the audio files with the following parameters:
sr): 22050 samples per second
fps): 31.3 fps
Since the dataset consists of commercial recordings, we cannot include the audio files in the dataset. We can, however, share the 2 synthesized MIDI performances used in the Con Espressione game (for Bach’s Prelude in C and the second movement of Mozart’s Sonata in C K 545) in mp3 format. These performances can be found in the