Reverse Conducting Data for:Mazurka in A Minor, Op. 7, No. 2 performed by Chiu (1999)
Raw Data
Below are the 20 individual tempo tapping trials for the reverse conducting of this performance. Click on a trial number to view the timing data for a particular trial.
Header information from first trial file:
The individual trials are combined into a single file for analysis in Mathematica:
In order to estimate the time offset of the of the beat tap points in the original audio file, the following tap time data were extracted manually from the original audio file:
Analysis Data
Here is the raw analysis file output from Mathematica:
The raw Mathematica output is then formated into a Humdrum file for eventual linking to the Humdrum **kern data for the score:
The meanings of each column in this file:
The absolute beat times in the music are extracted from pid9048-06.avg and stored in a plain text file. The following data is useful for generating clicktracks for the audio recording of the performance.
Next, the offsets analyzed in Mathematica are added to each individual trial in another combined trial file for use in further analysis of the individual trials. The average values of the data in the following file whould give you the average performance times listed in the above file:
Score Alignment Data
The beat times are first attached to the original score:
Then the times of sub-beats are interpolated from the beat times:
Performance Analysis Data
Finally, the timing information for all individual notes in the score are extracted to a file for use in automatic note identification in an audio file of the performance:
Where the columns represent the following information about a note:
Manually Corrected Beat Times
The average tap times for this performance were manually corrected to match the beat times in the performance using a sound editor to listen to the audio in detail. Here is a file which contains the corrected absolute beat times:
The first column in the file contains the absolute beat number, starting with beat "0". Enumerating the beats in this way is useful for evaluating automatic beat position determinations. Some beats occur where there are no events, so automatic finding of events won't detect anything at those times. |