Posted on

Team Status Report for 3/13/2021

We finished our design presentation and began working on our design report this past week2. We finalized the final design of our product in terms of what will look like as well as what algorithms and features we will be implementing/creating vs. what algorithms and features we will be downloading or using open sources for.

The biggest risk we are facing right now is falling behind the schedule that we have set for ourselves. We have been focusing on making sure our web application is well-planned out to satisfy the requirements of the design presentation and design report and that’s where most of our time has been going, to the presentations and report. We haven’t budgeted time to focus on actually starting our work. 

We will try to mitigate this risk by trying to get our design report finished ahead of time so that we can get a start on implementing our individual tasks as soon as possible. As is it is midterm season for this past week and the upcoming week,  we definitely to need to try to proactively set time for implementation for a few hours during most of the days of the week.

No changes were made to our design, since we’ve received mostly positive feedback. However for the design report, we plan on organizing the main system diagram and color coding it based on off-the-shelf, own implementation, etc. We also need to consider the processing time + runtime to account for latency issues and mention this in our report.

For the upcoming week, we plan on working on our design report and beginning work on coding the UI, algorithms, and database implementation.

Posted on

Sai’s Status Report for 3/6/21

This week, I worked on:

  • Flow diagram for optical flow of the web application 
  • System Diagram of User inputs + Application Outputs
  • Feedback Visuals
  • Explicit Wireframes for Pitch Exercise (Scale) and Rhythm Exercise (Clapping) Pages
  •  
  • Voice Range Evaluation will be a part of the user registration, came up with visual representation for that
  • Worked on design review slides:  https://docs.google.com/presentation/d/1T3X5lNBo8QEb4_bPB_0_1S9zrcxBrfxpWwo3TOec-fM/edit?usp=sharing
  • Came up with testing for the User Experience – Focus Group surveys
    • Will come up with a few tasks for users to work on (navigating to a specific exercise/page, doing an exercise)
    • Will have them screen share their activity on the web application and take note of how long it takes for them and their ease of use

This upcoming week:

  • Work on design report
  • Start coding the UI for one of the pitch exercise pages (work on html template)
  • Start Django code on UI for rhythm exercise page (html template)

 

 

 

Posted on

Sai’s Status Report for 2/27/21

This week, I presented our proposal and received some feedback from Professor Sullivan on simplifying our product more. We acknowledged that providing real-time feedback on audio input and video input will have many latency issues. This has pushed us to simplify our project.  Since our team shifted the product’s use case from users being able to practice songs to doing short singing exercises, without real-time feedback, but with feedback after recording, I was able to brainstorm a few ideas for singing exercises and how the user interaction would roughly look like for them.  I attached the wireframes for those below.

I was also able to design an UX flow/system integration diagram for what our team planned as our new design for the product’s transition to non-realtime and singing exercise focus. This diagram can be found in the team status report.

I also did some research on microphones with good noise cancelling ability and webcams with high resolution. We also decided today that we want the user to able to have headphones to listen to their audio. Here are some of the best options we have:

Camera: https://www.logitech.com/en-us/products/webcams/c270-hd-webcam.960-000694.html

Microphones/Headphones: https://www.jabra.com/business/office-headsets/jabra-evolve/jabra-evolve-75##7599-832-109

My progress is a little behind of what I planned, but this is due to the pivot in our design that we planned originally before our proposal presentation. Some actions I will take to catch up to the project schedule will be to put in some research and work into the project for at least an hour almost everyday this week with documentation/notes and to plan according to the design presentation specifications.

For next week, I want to think of other singing exercises we could implement and how the UI would look for those. I want to get a comprehensive understanding of how WebAudio API works and plan out exactly how I will use it for the UI. I also want to figure out the best way (best visualizations/infographics) to show users their feedback on their singing and their progress reports for their overall performance history. I also want to plan out our Django Framework organization (views/models/controller) so that I can get started on coding that the next week.

Posted on

Team Status Report for 2/20/21

One of the main risks our team might be facing is not having a clear definition of baseline features and functionalities of product. Another risk is underestimating the time requirement and difficulty of each task. These two risks can be managed by further researching how feasible each possible feature could be and narrow them down to a smaller set of features to implement. We are in the early stages of our design and just came up with our first prototype.

 

Posted on

Sai’s Status Report for 2/20/21

This week, me and my team were able to narrow down and finalize our baseline requirements for the project based on feedback from Professor Sullivan. I came up with a prototype for the user interface of the web application and got started on a story board for the user experience with the app.  I feel that my progression is on schedule. I’ll be presenting our proposal so I need to prepare my presentation delivery soon. For the next week, I hope to be able to come up with a final User Interface and Storyboard design for the web application, begin research on Web Audio API, and get a start on the basic wireframe of the application.