{"id":150,"date":"2023-03-19T02:21:51","date_gmt":"2023-03-19T02:21:51","guid":{"rendered":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamb6\/?p=150"},"modified":"2023-03-19T02:21:51","modified_gmt":"2023-03-19T02:21:51","slug":"team-status-report-3-18","status":"publish","type":"post","link":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamb6\/2023\/03\/19\/team-status-report-3-18\/","title":{"rendered":"Team Status Report 3\/18"},"content":{"rendered":"

What<\/span> are<\/span> the<\/span> most<\/span> significant<\/span> risks<\/span> that<\/span> could<\/span> jeopardize<\/span> the<\/span> success<\/span> of<\/span> the\u00a0<\/span><\/strong>project?<\/span> How<\/span> are<\/span> these<\/span> risks<\/span> being<\/span> managed?<\/span> What<\/span> co<\/span>ntingency<\/span> plans<\/span> are<\/span> ready?<\/span><\/strong><\/p>\n

I think our most significant risks in how we are going to be integrated our different components and subsystems. In order to be able to work, we have different branches in our repo for CV, Interface, and Audio, and plan on integrating them together in the master branch. However, when CV and Audio are integrated together, we will probably have to write in some threading capabilities so that CV can continually run\u00a0 while MIDI timing is being taken with\u00a0 the pressure sensor, so we will require a timing mechanisms.<\/p>\n

In order to mitigate this, we will take a few steps. Firstly, we will edit points in our schedule so that we merge in each CV milestone with our interface. This will require us to set up the bare bones of the interface rather quickly, so we will be pushing the audio details later. In our interface, we will set up a software timer that runs\/is checked as necessary, with a minimum BPM of 30, so we will always merge the CV milestones with a timer in place and software interrupts are triggered by a note being played via the pressure sensors to check the timer and send the MIDI message.<\/p>\n

Our contingency plan is to have a MIDI message sent on each beat. This is not ideal, as we may have a note that starts on a half beat, but given that we are focusing on the note accuracy + volume and interface in this project, we feel that it would be okay to have this as a contingency plan.<\/p>\n

 <\/p>\n

Were<\/span> any<\/span> changes<\/span> made<\/span> to<\/span> the<\/span> existing<\/span> design<\/span> of<\/span> the<\/span> system<\/span> (requirements,\u00a0<\/span><\/strong>block<\/span> diagram,<\/span> system<\/span> spec,<\/span> etc<\/span>)?<\/span> Why<\/span> was<\/span> this<\/span> change<\/span> necessary,<\/span> what<\/span> costs\u00a0<\/span><\/strong>does<\/span> the<\/span> change<\/span> incur,<\/span> and<\/span> how<\/span> will<\/span> these<\/span> costs<\/span> be<\/span> mitigated<\/span> going<\/span> forward?<\/span> <\/strong><\/p>\n

Given the feedback on our design report, we have decided to edit our implementation of the audio processing flow. We will not spend time trying to figure out the frequency spectrums of each note, but rather use a piano package with MIDI available through Python to render our sounds. We are currently exploring a few different options for these packages. This will reduce a lot of workload by using work already available to us rather than starting from scratch and trying to build deep sounds. Although we received feedback that suggested we use a soundcard as we are under budget, 1) we want to play the sounds through the phone for the portability aspects, as we expect our user to be using their laptop for actual score writing, and 2) we want to minimize cost to the user, as outlined in our use case.<\/p>\n","protected":false},"excerpt":{"rendered":"

What are the most significant risks that could jeopardize the success of the\u00a0project? How are these risks being managed? What contingency plans are ready? I think our most significant risks in how we are going to be integrated our different components and subsystems. In order to be able to work, we have different branches in … <\/p>\n

Continue reading “Team Status Report 3\/18”<\/span><\/a><\/p>\n","protected":false},"author":663,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5],"tags":[],"_links":{"self":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamb6\/wp-json\/wp\/v2\/posts\/150"}],"collection":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamb6\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamb6\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamb6\/wp-json\/wp\/v2\/users\/663"}],"replies":[{"embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamb6\/wp-json\/wp\/v2\/comments?post=150"}],"version-history":[{"count":1,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamb6\/wp-json\/wp\/v2\/posts\/150\/revisions"}],"predecessor-version":[{"id":151,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamb6\/wp-json\/wp\/v2\/posts\/150\/revisions\/151"}],"wp:attachment":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamb6\/wp-json\/wp\/v2\/media?parent=150"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamb6\/wp-json\/wp\/v2\/categories?post=150"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamb6\/wp-json\/wp\/v2\/tags?post=150"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}