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.
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.
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.
Hugo Status Report 3/22
This week, I focused on building and testing the first real circuit prototypes for the filter system. I breadboarded the initial design and ran real-time tests to evaluate how well the vocal removal performs in an actual analog setup. I was not able to make a functional system yet, but was able to make a few of the small subsystems. I was working with some parts I had available but also placed orders for everything that I did not have yet. Next week, I plan to continue working on the circuit and incorporating in a way to filter off DC noise with capacitors. Looking ahead, my priority is finalizing a stable and optimized breadboard version of the circuit before deciding whether to transition to a PCB. This will also involve additional real-time tests to ensure that the system maintains consistent performance.
 |
ReplyForward
|
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.
Team Status Report 3/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?
After receiving our components this week, our most significant risk is not being able to catch up to schedule. The slack time we added into our schedule, as well as the work/additional planning we did around the parts we were waiting to receive, should give us enough extra time to catch up. Additionally, we are willing to put in extra time when needed to help get ourselves back on track.
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.
Kiera’s Status Repot 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, after receiving my microphone components, I was able to upload the code I wrote last week onto the Arduino and get the motion data collection aspect of the microphone. Additionally, I began connecting our microphone component to the system and working on accurately collecting and sending audio data to the software.
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 still slightly behind schedule however I am on track to catch up within the next couple of weeks. I will continue to work on the vocal data collection portion of the microphone system for the next week.
What deliverables do you hope to complete in the next week?
By next week I hope to have a fully working microphone prototype.
Team Status Report 3/15
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?
We still have worries about getting our components and pieces delivered on time, but we have now placed orders for most of our fundamentals. Because of this, we are feeling on track to be able to overcome this block. A new risk is in recent changes made to our design. We scrapped our original scoring idea and so we are now a little bit behind schedule again and working to get back to speed. As far as contingency, we have our most simplistic method of scoring ready to put in if it does not work.
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?
We have adapted our scoring system from the original method. Our original method would execute the scoring primarily via hardware, subtracting the final speaker output from the original music track. We changed because due to advice from Professor Sullivan, our scoring would be inaccurate and not particularly useful. Even the natural differences in people’s voices would cause unpredictable differences in the output signal. There is only a small additional latency which will come from using software speech-to-text systems, but this will be the only change and will not largely affect our ability to provide a response in real time.
Status Report 3/15
Accomplishments this week:
This week, we sought to address our number one concern which was not having our parts on time. I ordered most of my crucial hardware components, mainly the speaker and splitter wires I needed to get started building the filter system. In addition to this, after some feedback from Prof. Sullivan, I reassessed our options for scoring the user’s audio. Originally, we had a feedback system which would subtract the final combined output from the original song. Because this would be overly complicated and provide very poor quality feedback, I looked into a new system to do it all on the software side. I helped pivot our design to include a speech to text system that compares the lyrics the user sings which we will now use for scoring instead.
Schedule Update:
I am still behind schedule because we have not prototyped or built anything. The GANTT chart states that I should’ve been wrapping up most of the work for vocal removal and scoring by now. However, we will redistribute because since all of the design work is laid out and most has been tested, I should be able to quickly catch up with the real prototypes for these parts.
Next week:
I will start by trying to source op amps and other fundamental components for breadboarding the filter. Once I know if this is possible or not I will order the components on Monday in order to make progress. By the end of next week, I want to have either prototyped our filter or made the first iteration for our scoring.