![\"\"](\"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s21-teamd7\/wp-content\/uploads\/sites\/148\/2021\/05\/Screen-Shot-2021-05-08-at-11.25.38-PM.png\")
![\"\"](\"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s21-teamd7\/wp-content\/uploads\/sites\/148\/2021\/05\/Screen-Shot-2021-05-08-at-11.25.30-PM.png\")
<\/p>\nThis past week, I was able to integrate Carlos’ pitch detection and feedback algorithm with the user interface. I used the metrics from the algorithm to get the voice range evaluation. The algorithm outputs a note range, and I wrote some code to map that note range to a voice range category (“Soprano” , “Alto”, “Bass”, etc) to show to the user. I also wrote code to use this category to generate pitch lessons, and send expectancy metrics to the pitch feedback so that each user gets a custom lesson and evaluation based on their voice range. I designed the web app so that users can update this voice range at any time. I used the metrics from the pitch detection\/feedback algorithm to show a user how sharp and flat a user and how well a user was able to hold each using charts from chart.js library. The pictures of this feedback can be found in the team status report. I’ve attached a picture of the example voice range feedback I got for my own voice range.<\/p>\n
<\/p>\n
Using the feedback I got from the user experience surveys last week, I made modifications to the pitch exercise so that there are now pop-up instructions, and more navigation buttons (exit buttons, back buttons etc).\u00a0![\"\"](\"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s21-teamd7\/wp-content\/uploads\/sites\/148\/2021\/05\/Screen-Shot-2021-05-08-at-11.27.32-PM.png\")
<\/p>\n
The pitch detection algorithm can return empty metrics if the recording is flawed, so I added a case where if the detection algorithm detects a faulty recording, I put in an error message and tell the user to try recording again for both the pitch exercises and the voice range evaluation. This was the best alternative to a page just crashing.<\/p>\n
I’ve actually been able to accomplish everything I’ve wanted to put into the web application, and am on schedule. Right now I am just hoping deployment works out.<\/p>\n
For the upcoming week, I’ll keep cleaning up and refining the user interface, adding more instructions and navigation for the exercises, and working the welcome page.<\/p>\n","protected":false},"excerpt":{"rendered":"
This past week, I was able to integrate Carlos’ pitch detection and feedback algorithm with the user interface. I used the metrics from the algorithm to get the voice range evaluation. The algorithm outputs a note range, and I wrote some code to map that note range to a voice range category (“Soprano” , “Alto”, … <\/p>\n