Anita’s Status Report for 2/25

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours). 

I presented our design review powerpoint! It was a pretty enjoyable experience presenting, and I feel like I’ve grown as a public speaker after being a TA for so long. I still talk very fast though and tend to ramble due to some nerves >___< I prepared as I would for a recitation, and it paid off! 

I spent most of this week continuing to flesh out the implementation plan. I mentioned I did this last week too, but the design report requires a lot more detail and consideration that we previously did not have.

In the course of doing more research on our implementation plan and obtaining feedback from our design review powerpoint, there were multiple details added to our project. 

We added some new use case requirements. While presenting, there was a question about different octave singers– baritones vs. sopranos– and how we would handle these frequencies. After doing some research, the range of notes that the average human voice can produce is 85 to 1100 Hz. For male singers, the range of notes in songs usually spans between F2 (87.31 Hz) to G4 (392.00 Hz).  For female singers, the range of notes in popular songs typically spans between A3 (220.00 Hz) to C6 (1046.50 Hz) range. So, for our app to be most effective and accessible, we must be able to support most ranges of casual singers.

We’ve also made some modifications to our latency and accuracy requirements. According to the Web Audio API specification, a popular API used for “processing and synthesizing audio in web applications,” a latency of 30 milliseconds or less is recommended for real-time audio processing. We previously were using the human reaction speed as a metric to determine our latency requirement, but human perceptions of audio delays are a lot faster. We will have to bring this up to our advisors to see if this is even feasible, but we’ve lowered our accuracy requirement to compensate for a much higher latency bar we must meet. 

More details to come, after we have finished our design review 🙂

As mentioned last week, I’ve also ideated a scoring algorithm for a post-analysis scoring. I’m starting off a basic linear range– anything outside a range of notes will get a 0, otherwise, the score one gets will be linearly proportional to how close they are to the actual note. 

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule? 

We are still on track. Deliverables such as design reports and presentations should ideally be included in our Gantt chart, as they take a substantial amount of time and effort to make. So, this week has been a bit more work than previous weeks to stay on track, but it’s still manageable.

What deliverables do you hope to complete in the next week? 

The main deliverable is the design report. This is a substantial report that will allow us to move forward confidently with our solution.