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).  

A big change we had in the project was a pivot from live feedback to feedback after the fact. As expressed in the last few status reports, we were having a lot of problems with integrating javascript recordings with the python django backend. Unfortunately, because we had spent so much time on this, we decided it was time to pivot.

Because we had valid recording strategies, as well as a working conversion between ogg and wav files, we pivoted to having the user sing, download their singing as an ogg file, upload this same file, and then view the scoring and feedback on this singing input. Although this required giving up our goal of real time feedback, we decided this was worth moving to, as the integration between the javascript recording and pitch detection was difficult, and we haven’t made any progress, despite focusing on this for the last few weeks.

On my end, this required a few things. I set up a web framework that allowed navigation between recording, downloading, and viewing results.

Before this week, the recording user view was very basic. This week, I adjusted it to play the song, show the song process, with lyrics. I added a rudimentary song playing interface. The interface shows the song playing, as well as how far the user is in the current chunk. Afterwards, I changed the view to show a download link to be followed before the user proceeds to the next page.

Upon proceeding to the next page, the user uploads the recording that they just downloaded. Once ready, the user plays their recording. This shows the graphic, as developed earlier, where the user input is integrated with the target pitches, comparing their performance. Again, the interface is somewhat simple, but adding specific information should not be difficult for the final demo. After the user performance plays, the web application displays an overall score. This score is calculated using Anita’s scoring algorithm.

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

Because we were not able to complete integration between the frontend and backend as planned, we are behind. However, we have adjusted our project accordingly, so it is no longer required, so no actions are necessary.

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

Next week, I hope to greatly polish the web application user interface. While functional, it is currently pretty rudimentary and not appealing. I would also like to add a lot more feedback on user performance post factum. Lastly, I know there are a lot more checks and safeguards I should implement before the web application can be used securely.

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).  

This week, our focus as a team was to work on the design report. During our first team meeting, we divided work and agreed on what we wanted to say in each section, in broad strokes. Before our meeting on Thursday, we wrote a draft for each section we had been assigned. During this next meeting, we discussed parts that were unclear and made sure we weren’t covering anything redundant.

At this point, we had to finalize the block diagram for the web application. To do so, we needed to understand exactly how the mechanism for recording audio works in web applications, which we had not agreed on. I ended up looking through some resources and chose to use the MediaStream Recording api, which creates an audio stream in javascript and returns the current data when it is requested, which can be done with AJAX.

A large portion of the work I did this week was familiarizing myself with MediaStream. I followed an example from GitHub to understand how to use this api. I then played with this code to pivot it to using just audio, since we are not interested in video recordings.

I added this play tested example to the website. It requests permission to record upon the request stream button being pressed, after which the button disappears. Then a recording can be started and stopped, which updates the recording that is visible.

This plan to use the MediaStream is outlined in a bit more detail in the design report. The plan is to use the ondataavailable event handler with AJAX to send the current audio information to the python backend.

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

Overall, I am hitting the targets I want to, other than displaying target pitch. Because of the time the design report took as a team, we have not been able to have a discussion together about the way we want to store target pitch information, and we don’t have the specific data for our melodies. I will discuss this during next week’s meetings and make sure we have a plan going forward. Overall, I am not too concerned about not having started on that metric yet.

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

In the next week, I hope to get started on displaying target graphics. Additionally, I want to combine the audio recording and audio playing pages.