What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?
The most significant risks at this point in the project are just significantly lower accuracy for complicated pieces of music. While we can keep working to improve the accuracy, this isn’t that big of a deal because we are having success with easy and medium tiers of music and should have more than enough to demo with.
Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?
No changes made at this time.
Tests
List all unit tests and overall system test carried out for experimentation of the system. List any findings and design changes made from your analysis of test results and other data obtained from the experimentation.
We tested the system on three different levels of music, easy medium and hard. And we tested each of our five metrics, pitch, onset time, onset duration, alignment and delay.
In the timing algorithm we tested to make sure that the notes from the audio data aligned with the sheet music. This was manually verified as there was no way of automating this but we checked the similarity of the pitch, onset time, and onset duration of the two notes that got matched together.
To test the delay between the singer and the sheet music, we did a basic test where we tested to make sure two pieces with no delay didn’t have any delay feedback given by the system, and a pieces with a constant 5 second delay and make sure there was always a delay in all parts. This was done with a medium piece which was Fly Me to the Moon.
For the sheet music scanning, we ensured that the scanner
Overall, we found that most of our difficulties come with processing the piano music.