Tag: status report

Anita’s Status Report for 04/08

Anita’s Status Report for 04/08

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 (12+ hours).  This week was the interim demo. It 

Anita’s Status Report for 04/01

Anita’s Status Report for 04/01

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 (12+ hours).  So I started off the week integrating 

Anna’s Status Report for 04/01

Anna’s Status Report for 04/01

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 (12+ hours).  

This week, I continued working on the visuals for the game mode. Right now, the format in which I plan to store the information on the target pitch is a json file, with elements consisting of dictionaries with length, target pitch, and lyrics keys. Each element contains what will be shown on the screen at a given time – so each song is divided into these chunks that are delineated in the json. The target pitch was generated by using Kelly’s pitch detection script, and the chunks were separated and lyrics were added manually. I think this method works for the scope of our project, where we only plan to make only so many songs available, although I may look into other methods.

[

   {

       "length": 160,

       "target": [396.79, 395.99, 395.41, . . . ],

       "lyrics" : "happy birthday to you"

   },

   . . . 

]

Right now, the sample I have working is “Happy Birthday to You”, and the user pitch is pre-recorded, as Kelly and I have not finished on integrating pitch detection to the web application. We are pretty close to complete, however a few bugs mean that we are keeping these parts separate, for the sake of the demo.

“Happy Birthday to You” has four chunks, each of which is a line in the song. Currently, for our demo, the user can start the song, and the visual cues begin, in sync with the music.

I did not use Kelly’s newer pitch detection script, that filters out really high or low frequencies (caused by breaths or pauses), I used the raw version, which you can see in the few peaks and valleys. Another reason for the user pitch (pink) deviation from the target pitch (blue) is that the user pitch is me singing, and I do not sing well.

I have also switched from using stepped line charts to traditional line charts with tension, for smoothing. The reason I originally used stepped line charts was we for some time thought that the target pitch would have much fewer data points, and a stepped line chart works better for that, as you could see on last week’s update. However, since each chunk contains 100-200 data points, a smoothed line chart was more appropriate.

I also made pause/play work with graphics.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?  

I am on track. As planned, I am currently working on the target pitch graphics, and in the process of integrating pitch detection and the web application. I am happy with the progress.

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

I will work on adding more of the songs in. If we complete integration between pitch detection and the web application, I will combine the audio recording + pitch detection with the target pitch graphics and playing songs.

Team Status Report for 04/1

Team Status Report for 04/1

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 as of right now is linking the backend PDA with the front end web application. This 

Kelly’s Status Report for 4/1

Kelly’s Status Report for 4/1

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 (12+ hours).  This week, I took a deep dive 

Anita’s Status Report for 3/25

Anita’s Status Report for 3/25

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 (12+ hours). 

This week was admittedly a bit of a slow week. However because I picked up the pace last week, there was quite a bit of slack time that I could lean on. 

I first ramped up on Kelly’s code. While there are not too many lines of code to ramp up on, the lines of code were very dense and took a fair bit of research on what each method did. I then designed what would be the interface between the feedback and pitch detection algorithm, and coded a portion of it up.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule? 

Even though this week was chill, I’m still on track/ahead of schedule.

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

I am to finish the interface in preparation for the tech demo next week.

Team Status Report for 03/25

Team Status Report for 03/25

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? Right now, a big risk for our team is completing pitch detection integration with the web application. This element of 

Anna’s Status Report for 03/25

Anna’s Status Report for 03/25

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 (12+ hours).   This week, for capstone, we spent part 

Kelly’s Status Report for 3/25

Kelly’s Status Report for 3/25

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 (12+ hours). 

This week, I ramped up to the web application interface and started to integrate pitch detection with our web application. 

Integrating pitch detection with the current setup proved to be extremely difficult and I spent the majority of my time this week trying to debug these issues. First, my pitch detection algorithm needed an actual .wav file stored on disk, so I figured out that I could make use of Django’s built in storage in order to satisfy this, which worked well. Then, the file format wasn’t being read correctly so I read up on exactly how a .wav file is formatted and how our current setup is formatting the .wav file chunks. In short, a .wav file has something known as a RIFF header that details what exactly is in the .wav file for easy reading. Where I believe our current setup is going wrong is the ‘size of data’ section as the web application is essentially making an encoding of bytes and interpreting the file as a .wav file. However, this encoding of bytes that correspond to the users’ voice doesn’t have this detailed RIFF header that most .wav files do and therefore cannot be read by my pitch detector.

 

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule? 

This week I’m supposed to be integrating pitch detection into our web app so I’m on schedule :).

 

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

Next week, I hope to figure out how to deal with this missing RIFF header issue and if not pivot the web application to submit a fully formatted .wav file to the backend after all vocal recording is done. 

Anna’s Status Report for 03/18

Anna’s Status Report for 03/18

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 (12+ hours).   This week, we worked on the ethics