Posted on

Aleks Status Report 4/13

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.

This week, I worked on cleaning up some of our UI including pulling, displaying playlists, lyric display, and miscellaneous CSS. I also used some sample data to simulate output from Hugo and Kiera’s scoring algorithms to allow for

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 track. However, it will be a push to integrate the components of my group members works into my application.

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

As above, I will integrate Hugo and Kiera’s components into the web application. Additionally, I will deploy the web application so it’s accessible by URL (or at least port) instead of needed to be locally deployed.

Posted on

Group Status Report 3/29

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?

The most significant risk towards our success are running into integration issues while we begin working on combining the individual aspects of our project. As we should have most of our hardware components delivered by early next week, we should be past our risks with regard to shipping delays. However, it’s possible if we need to order more parts due to any unexpected issues we could run into delays. Even if so, we should be in good shape given our predicted slack time.

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?

No changes have been made to our existing block diagram. We will post an updated GANTT chart of our schedule in a blog post tomorrow.

Posted on

Hugo Status Report 3/29

I’ll write it up asap This week I was finishing up preparing my two main deliverables for interim demo. The first is the filtration circuit I have been spending most of my time on. Unfortunately, due to delays on parts I ordered, I am still yet to have a fully functional hardware circuit, but I have finished building it and incorporated some tweaks as advised by Professor Sullivan.

The biggest was adding in an RC high pass filter to filter out unwanted DC offset. Here is the calculation I did to get the best values:
DC Offset calculation- In order to do this, we know that DC has a frequency of 0 Hertz and the lower end of the frequency range of most music is 20 Hertz. This means that the high pass filter needs to be as low as possible (in order to prevent distortions of the music) but still clear the 0 Hertz. We know the cutoff frequency of a high pass filter is given by 1/2piRC, and I wanted it to be less than 5 Hertz. Using the standard values of resistors and capacitors that I had available, and attempting to ensure that the capacitance is as small as possible to prevent charging time from adding delays, I calculated using my largest resistor value (100KOhms) and solved C = 0.637 microfarads in order to achieve this. However, because I don’t have a 0.637 microfarad capacitor, I calculated using a 1 microfarad capacitor and found a cutoff frequency = 1.59 Hertz.

Additionally, I began working on the second deliverable, scoring using STT. At this moment, I have made it so that we have a streaming STT model that can get a transcription of the user’s audio. The transcription is aligned with timestamps for each word, or in this case lyrics, and I am comparing that with the timed lyrics gathered from lyricsify. This process is not yet finished but will be done before demo.

Next week I will primarily be focused on doing demos, but I also hope to get the last parts delivered and built into the circuit during the week, even if it is not ready for the first day of demos.

Right now, my biggest challenge will be interfacing the circuit with laptop output and ensuring that the circuit is operating as expected. Additionally, if my parts don’t arrive soon I am a little worried that it will lead to a big time crunch towards the end. However, because of this, I am focusing most of my effort into perfecting and implementing scoring.

Posted on

Aleks Status Report 3/29

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.

This week, I worked on cleaning and integrating the different parts of my project together: the UI, Spotify integration, and Lyricsify lyric scraper. The work is still in process and I will post a blog post with updated materials ahead of the intermediate demo.

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 should be back on track as long as the integration is fully completed by tomorrow.

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

Next week I plan to use feedback from the intermediate demo to improve my deliverables. I will also work on integrating Kiera and Hugo’s aspects into the web application.

Posted on

Aleks Status Report 3/22

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.

This week, I worked on making the lyric scraper for Lyricsify. I did some work with pandas and mimicked the form of Spotify API’s output to iteratively search for tracks lyrics and recover timed data. I did some work parsing the data into an appropriate form to begin displaying the data.

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 also slightly behind schedule however I should be able to catch up this coming week.

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

Next week I plan to finish linking the work I’ve done with Spotify API with Lyricsify and complete a draft UI of our timed lyrics.

Posted on

Aleks Status Report 3/8

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 all of my time working on the design report. I worked on our introduction and project management sections, updated our block diagram to be more readable, set up templates for some the sections, and filled in the areas relevant to my expertise in our software system, web application, and lyric retrieval mechanisms across the paper.
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 slightly behind, as I forecasted would occur last week. I did not have time to work on any deliverables for this week due to spending all of my time on the design report. I will double down to make up the progress when we’re back, which should be very doable given fewer miscellaneous course deadlines demanding my attention.
What deliverables do you hope to complete in the next week?
I will implement our full integration with Spotify API and do some basic renders of our front end. Given time, I will start work on our lyric scraper.

Posted on

Hugo Status Report 2/22

This week I continued working on the specifics of the design for the filter system. I have started to look into the benefits of using a PCB for our circuit instead of the original / current plan which was to simply breadboard it. I am in the process of finalizing the actual design as I completed my matlab tests and am mostly satisfied with the current output of the vocal removal. Before I go into fine tuning, I first want to try breadboarding the circuit and seeing how well the filter works in real time analog. This is going to be my primary work for next week and my priority is finding out whether or not the system will perform with the same level of quality in our actual system. This week I also took time to analyze our new scoring method for the singing. Having pivoted to our new method of subtracting the original from the final signal and analyzing the remainder, I wrote up some additional matlab tests to see what this result would look like. These tests have been promising, but again, I need to test the results with signals in real time. Overall, next week will be centered around developing the first real circuit prototypes for the filter.

Posted on

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.

Posted on

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.