Team Status Report 2/22

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?

One of our risks right now is making sure that we will be ready for relevant builds in a reasonable timeframe. As Professor Sullivan mentioned during our meetings, it is important to order parts with significant time due to potential shipping delays. It will be important to place orders for our project early this week, presumably after having our meeting with our staff on Monday to confirm our feedback from the presentation, so that we can have our relevant hardware accessible. After the parts are ordered, we should make sure to actively track parts, including over spring break, to allow for pivoting if a part is heavily delayed.

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?

All of our existing design goals are aligned with what we presented at the design presentation. We did more heavily spec out our existing design decisions for the design presentation, including selecting our audio processing style, specific hardware decisions (e.g. using the Arduino Nano BLE), and lyric sourcing mechanisms from our potential options. We also prepared a more in depth GANTT chart than we had for the first presentation. However, we are prepared to use for potential feedback from our design presentation to adjust accordingly next week.

Aleks Status Report 2/22

What did you personally accomplish this week on the project? Prove to the reader that you put sufficient effort into the project over the course of the week.
This week I spent time significant time on Sunday working on fine-tuning our design presentation slides. I also worked through one of the provided Spotify API tutorials, which should be useful in starting our development with Spotify. I did a bit of research into website scrapers as well, as I will be constructing one for our lyric retriever and I don’t have historical experience. Finally, I spent some time working on getting our design report started and understanding the relevant information that we will need to collect.
Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?
My progress is on schedule.
What deliverables do you hope to complete in the next week?
Next week will probably be mostly spent working collaboratively with my team continuing to work on our design report. With any additional time, I hope to do expand my work with Spotify API to provide relevant proof of concept for integration with Hugo’s audio processing.

Aleks’ Status Report 2/8

This weekend, I prepared to present our project proposal presentation. During the week, I looked more deeply into Spotify API to analyze exact functionalities that would be useful and make sure all of our use cases for their data followed their usage guidelines. I found some interesting audio analysis features that are notated as deprecated, but I want to do more research into. I also set up our GitHub repository and initialized the Django Webapp so I can do some work through Spotify’s tutorials next week to make sure we can load the music appropriately. I also did some review and practice coding web applications to brush up on my skills. Additionally, I met with my team to brainstorm through some of our system design decisions based off of presentation feedback. Next week, I plan to dig into our design decisions next week to determine our best design plans. I will ensure Spotify works for our use cases and look into best methods for procuring our lyrics, especially using a potential fix that a student in our section (Maya Doshi) told us could be useful.

Introduction and Project Summary

Despite its popularity, karaoke at home is still a tedious and fragmented process. Our project is a seamless karoake experience which removes audio from user’s personal Spotify library and provides feedback for improvement via audio and motion processing to analyze pitch and tempo.