Category: Uncategorized

This week, I worked mostly on testing and final reports/posters. I participated in systems testing with the rest of the team, by playing the saxophone and helping analyse the results from the testing. I also started working on the poster and final report with the rest of the team.

There are currently no roadblocks, except maybe time, since testing is on a tight schedule now. For next week, our plan is to finish up the testing, prepare for the demo, and finish the final report.

This week our team discussed about the modifications we need to make to each individual part to move towards integration. I changed the logic of my app to let the user play after clicking on start, and click on replay to display the diagrams and feedback generated from the fingerings and pitch data in the practice session. Since the expected outputs from our pitch detection system and fingerings system contain timestamps of start and end for each fingering/note,  I was able to tolerate a mismatch for 0.5s in the synchronized reference data and user data to allow users play in a way that is not perfectly aligned with the reference.

I am on track this week. Next week I will test with the actual results from other parts to see if the web app will function as expected, and also check whether the 0.5s threshold is suitable for real-world data.

This week I continued to work on my web app part. As I mentioned in the meeting, I was struggling with the misplacement of diagram parts and the strange display of the user interface. Since I had exams on Wednesday and interviews after that, I didn’t have much time to fix the problem. Currently the problem still persists, and I am considering researching some graphic libraries to solve it.

Since our group has decided a new schedule, I am almost on track this week. Next week is the interim demo week, and after the interim demo, I am planning to work with my teammates to start the integration.

This week I was working on the other pages of our web app. Since these pages only involved some static descriptive text, the process went smoothly. I also refined a bit the practice page’s UI to make it look clearer. I was not able to start mapping the contents of the practice page with specific inputs, so my progress was still slightly behind the overall schedule, but last week’s plan was almost fulfilled. I will try to work more on this this weekend.

Next week I think I have to start the user testing and the mapping of the contents, and plan to prepare for the integration.

Last week, my efforts were concentrated on crafting the foundational elements of the practice page for the web app. I have processed and integrated fingering diagrams for common fingerings, enabling the display of these diagrams within the application interface. Additionally, I was able to display pre-determined, hard-coded feedback related to common fingering mistakes. This feedback, though not dynamically generated based on real-time user input, serves as an initial step towards an interactive practice page.

My progress is slightly off track, but not much, mostly because I planned to work during spring break, but several personal stuff prevented me from that. To mitigate the delay and catch up with the overall project timeline, I plan to extend the time I will work on this project in the upcoming week. This effort will mainly focus on filling in the contents in other pages and preparing for user testing. The integration of dynamic feedback mechanisms and fingering diagrams based on real-time user inputs is a complex feature, so I hope to tackle it as part of the user testing phase, which will be split into work in next week and the week after next.

The most significant risk now is that all of us are slightly behind schedule, since we all have midterms coming and assignments due. To manage this risk, we will discuss, revise our plan and work together in next week’s mandatory lab to keep up with the schedule as quickly as possible.

An existing change made to our design is on the audio processing side. After the presentation on Wednesday, we received some suggestions from instructors about the rhythm processor. We initially planned to merely use a pitch detector when processing the audio, but as we should be dealing with rhythms instead of several single notes, a rhythm processor is definitely needed. So Lin is researching on the rhythm processor by researching papers and learning from previous projects now, and other teammates will also help if there are some problems implementing it.

an updated schedule is below:

This week I was busy preparing exams and finishing assignments, so I had little time working on the project. I have discussed with my teammates about this.

I am currently a bit off track, so my next week’s goal is to continue with the existing work and quickly catch up.

This week my primary focus is to design the web app interface, decide on the functionalities it should offer and set up its structural framework. I have outlined a few pages in our app, including user authentication, user statistics(where a user can check history error rate of each practice song),  basic knowledge about learning saxophone, practice and feedback. Here’s a block diagram that shows my design for our web app, 

Currently, I’ve managed to implement a basic user authentication system that operates locally.  Additionally, I’ve completed the navigational framework between pages, although the content on those pages is still in the placeholder stage. 

My progress is on track this week. Next week I intend to focus on developing the content for our practice and feedback pages, aiming to dynamically display text based on one or two hardcoded inputs. I also plan to begin collecting saxophone fingering charts and images for various notes. Hopefully I can also get the input diagram completed by the end of next week. Below is an example sketch illustrating my envisioned layout for this page: