Author: asell

I have spent time this week working on the ethics assignment and building out a basic prototype of the timing algorithm. I have implemented the data structure I want to use which is a list of (pitch, onset time, duration) in python. I created a basic event list with uniform notes of the same pitch and duration with different onset times. I duplicated these and created a basic comparison between two lists. I also started working on the MQTT communication and setup an ingestion pipeline to take the data from the sheet music in the form of MusicXML and transform that into an event list.

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?

For the next week I want to continue to build up the algorithm by beginning to develop and test using data from the music xml files.

I spent the most amount of time working on the design document with my teammates. I worked heavily on sections regarding my sub-system which is the timing algorithm, while also making changes to our block diagram, and working on all the other miscellaneous sections to ensure the document was completed on time.

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 slightly behind schedule because I didn’t have as much time to work on prototyping as I thought last week because of midterms and the time spent working on the design doc. Overall it isn’t that big of a deal because my goals were ambitious for last week and I am still on track.

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

I hope to have a basic prototype of the timing algorithm done by the end of the week with a working demo with midi files.

This week comprised of completing the design presentation and doing some initial prototyping on the timing comparison algorithm. I have built out a basic timing algorithm prototype in python using the expected data coming from the sheet music and audio data. From the sheet music I am getting data in the form of ‘d1/4′ for a note where the d stands for the music note d and the 1/4 stands for a quarter note. From the audio data I am going to be receiving a tuple in the form of (onset time, pitch) which is going to look like this:  (0, ‘d’) where 0 is the onset time and d is the music note d.

In terms of implementation I have been thinking about what kind of data transformations I want to implement in order to properly analyze this data. I have considered transforming the sheet music into an array based on the what beat we are on, but the issue with this is it doesn’t distinguish between a new note and a sustained note. Because we are focusing on note onset for this timing data, I was considering using this array, and only focus on note onset for this beginning prototype. For example, if I receive  the data [‘d1/4′, ‘d1/4’, ‘d1/2’, ‘d1/2’], because 1 beat is a quarter note, I would create a per beat data structure that would be [d, d, d, s, d, s] where s stands for sustained. I need to consider other edge cases such as notes that are less than a beat but that can be solved by just using an increment that is some fraction of a beat and scaling accordingly. 

I have also started a github repo to contain our project code and pushed some prototype code to this.

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

Progress is on schedule so far.

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

For the next week I want to focus on getting real data from the music we have recorded and determine what the current timing latency is with python and if I should use a c++ implementation. I also want to finish a basic prototype before spring break based on the data we recorded. I have three exams next week so I might not be able to accomplish all of these but I think that this can be reasonably done.

This week required a lot of brainstorming and thinking about how we were going to implement our project. I spent a lot of time working on the design presentation after we had an initial meeting with the School of Music musicians and collected some ground truth timing data.

I am ideating how to implement the timing algorithm because after discussing with Prof. Dannenberg it appears that real time feedback may not be feasible and that I should spend more time focusing on the post performance feedback. This means that most of the focus will be on post performance. I have attached my current plan for the timing algorithm below and will continue researching on how to deal with edge cases and complex scenarios with my teammates.

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

Progress is on schedule so far.

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

For next week the deliverables are going to be completing the design presentation and beginning to build out a basic timing algorithm prototype.

This week involved delivering the proposal presentation and finalizing some of our project details. My role in the project was to work on the algorithm to determine the musicians’ timings. Other than working on this presentation I worked doing some cursory research onto how we we would integrate the FPGA and Raspberry Pi along with coordinating some logistics around recording the musicians.

I also setup the WordPress website and made sure everything was good to go on that end of things.

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?

In the next week, I plan on researching Raspberry Pis and putting in a purchase order for one and beginning to record audio from the school of music performers and begin some cursory analysis of the audio recordings.