Urgent¶

1. Check that polyphonic context works;
2. Ensure that program change messages work;
3. Ensure key presses work. (Niels: Buttons now sometimes turn red when you click on them. But this does not seem to happen consistently; i.e. most of the time no response is given; this might confuse participants when it suddenly works and then doesn't);
4a. Ensure that ratings and reaction times are recorded - also when numeric keys are used;
4b. Ensure that responses are recorded after the end of the melody;
5. Check why some chords (particularly the first one in each cadence) are played twice inside the programme. This is not the case when played outside the programme; thus, it should not be a problem with the MIDI files themselves, but a problem with the programme's interpretation of the MIDI files. This problem does not seem to occur when Marcus runs the programme on his Mac laptop, but DOES occur when running the programme on another PC;
6. Investigate why MIDI files are played inside the programme with a lot of reverb even though this reverb is not present when MIDI files are played outside the programme. I have tried changing the <midi device> argument, but it doesn't seem to make any difference;
7. Incorrect "Melody not finished playing" messages.

Other issues¶

1. Check that probes are activated at the correct note;
2. Tatum can sometimes be too short, giving a very fast clock playback;
3. Check that subject ID doesn't already exist;
4. Too many fixed order command line options make configuration rather unwieldy. Replace with property list file.
5. Move response labels to either end of button row.