Posted on

Jordan’s Status Report for 3/30

This week, I mainly focused on a change of design. I changed the cable used to connect the sensor to the mainboard from normal wires to DuPont-style connectors, which are easier to work with, as well as easier disassembly. I measured the distances between the keys and the board, as well as estimated the magnet location to ensure proper detection. Assembly onto the saxophone will begin once the new wires arrive, and this will be my task for next week.

The software is also coming along, and as a team we will also decide the format of transmission by next week. Right now, the plan is to send both the raw fingering data and the note information to the web app, but this will be finalized next week.

Schedule changes are reflected in the team report.

Posted on

Team Status Report for 3/30

Our major concern for now is that the subsystems are not yet finalized but the demo is next Monday. Lin is still working on code for pitch detection and Junrui is still finishing implementation for the webapp practice page. We’ll do what we can to make our part perfect. Another concern is that we might not have enough time to integrate each subparts together. We’re still discussing what platform to use for webapp deployment. After we finish the demo, we’ll start working on integration immediately.

We have updated our schedule as in the graph. There’s not much change compared to the original one, but we postponed the integration process by one week.

Posted on

Lin’s Status Report for 3/30

This week I mainly work to finalize the audio processing part to prepare for the coming demo. I keep working on the integration of rhythm and pitch. I have tested an input audio recorded by Jordan, and I noticed some issues. The major issue is that the environment noises cause some pitch detection inaccuracy, and it seems that the current band-pass filter I applied doesn’t filter out the noises. I’m still working to revise the code to reduce the effect of noises. 

I am on track of schedule. I’ll keep working on my subpart to finalize it before the demo and start integrating the system with webapp frontend once we finish the demo.

Posted on

Junrui’s Status Report for 3/30

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.

Posted on

Team’s status report for 3/23

The most significant risks we face now is that the integration may start later than we planned in schedule, so if some problems occur in integration part, we may not have enough time to fix them. The contingency plan for this is to ensure the systems function after integration, but lower the metrics we need to reach. Also, we try to refine each component to make sure that they can work independently, and we believe that it will greatly reduce the burden of debugging the mistakes in integration.

There is no change made to our existing design this week.

Posted on

Junrui’s status report for 3/23

This week I managed to display different text and diagrams based on different inputs. I hardcoded the user input into a vector, where 0 indicates a key is unpressed and 1 indicates the key is pressed, and the diagram and feedback to  correct fingering would change based on this vector. Currently the practice page is almost finished.

I am on track this week. Next week I am planning to link the database and implement the history statistics, and also check local hosting methods. If time permits, I will work with Lin to start integration with the pitch detection system.

Posted on

Lin’s Status Report for 3/23

This week I worked on the integration of rhythm processing and pitch detection. It takes the output array of rhythm, which is a list of 0s and 1s, and the output array of pitch, which is a list of music notes. And then it pairs the note with the rhythm and stores the result in a dictionary. I also worked on the pre-processing of the input audio by adding a band-pass filter to it to make sure the signal is in the range of 300hz- 2500hz (this value is still under testing and may change).

I am on track of schedule. Next week, I’ll start testing the system with real-life saxophone input played by Jordan. I will see if it meets the accuracy requirement we aimed for in the proposal and make adjustments to my code based on the result.

Posted on

Jordan’s status report for 3/23

This week, I completed more soldering work for the saxophone fingering system. The soldering of the sensors took a longer than expected due to the small size of the sensor, and getting the PCB for the sensor into its small shape also took longer with a minor injury as well. Due to this, the completion of the system will be pushed back one week to two weeks from now. However, I have also completed testing of all work done, which contributed to the delay, but it means less testing down the line. Specifically, I made sure that each sensor worked, and that the response time was within spec. The response time is not noticeable for typical use case, and whatever delay there is will not impact user experience.

For next week, I aim to finish installing the magnets and sensors onto the saxophone.

Posted on

Junrui’s status report for 3/16

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.

Posted on

Team Status Report for 3/16

The biggest risk we face right now is the hardware component finishing behind. Jordan has put in more time to catch up from his sickness, and we are confident he can finish it on time in our schedule. The contingency plan is to shorten system tests, but instead focus more time on independent component tests, especially since the software component can be tested independently from hardware.

There are currently no changes to our design.