User Tools

Site Tools


proj

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
proj [2021/03/31 18:20] bilproj [2022/05/05 15:26] (current) bil
Line 3: Line 3:
 ====== EECS 2311 Project ====== ====== EECS 2311 Project ======
  
-====== New requirements added on March 3! ====== 
- 
-  - The system must allow the user to improve the MusicXML output **by editing the input text tab**. For example, if the output for measure 42 is not what the user was hoping for when they load your output onto a viewer, your system must present this measure (or a range of measures) so that the user can edit accordingly. This includes metadata such as setting a different time signature for some of the measures. 
-  - The system must allow the user to save any edits made to the input text tab by the user, including any metadata edits, e.g. song title, time signature etc. 
-  - The system must support [[https://www.musicxml.com/tutorial/the-midi-compatible-part/repeats/|repeated measures]]. The drum example below contains many instances of repeats. See an example in the Useful Resources section below. 
-  - The system must also support [[https://usermanuals.musicxml.com/MusicXML/Content/EL-MusicXML-grace.htm|grace notes]]. For guitar, any sequence of hammer-ons, pull-offs, or slides that is preceded by the character "g" should be treated as grace notes. For drums, flams (designated by the character "f" in the tab) must be implemented as grace notes. See an example in the Useful Resources section below. 
-  - The system must deal with errors in the input in a user-friendly way. Minor errors should be treated as warnings but should not stop the conversion process. Major errors in particular measures must be presented to the user to fix them. 
-  - The system must of course support all three instruments and as many as possible of the features shown in the two examples below. 
  
 <html><!--  <html><!-- 
Line 50: Line 42:
  
   * An example of a {{:graceexample.txt|guitar text tab with a grace note}}, and the {{:graceexample.musicxml.txt|corresponding MusicXML file}}. Unfortunately, the online viewer posted above does not show grace notes in tablature, so you should use MuseScore to test grace note functionality.   * An example of a {{:graceexample.txt|guitar text tab with a grace note}}, and the {{:graceexample.musicxml.txt|corresponding MusicXML file}}. Unfortunately, the online viewer posted above does not show grace notes in tablature, so you should use MuseScore to test grace note functionality.
 +
 +====== New requirements added on March 3! ======
 +
 +  - The system must allow the user to improve the MusicXML output **by editing the input text tab**. For example, if the output for measure 42 is not what the user was hoping for when they load your output onto a viewer, your system must present this measure (or a range of measures) so that the user can edit accordingly. This includes metadata such as setting a different time signature for some of the measures.
 +  - The system must allow the user to save any edits made to the input text tab by the user, including any metadata edits, e.g. song title, time signature etc.
 +  - The system must support [[https://www.musicxml.com/tutorial/the-midi-compatible-part/repeats/|repeated measures]]. The drum example below contains many instances of repeats. See an example in the Useful Resources section below.
 +  - The system must also support [[https://usermanuals.musicxml.com/MusicXML/Content/EL-MusicXML-grace.htm|grace notes]]. For guitar, any sequence of hammer-ons, pull-offs, or slides that is preceded by the character "g" should be treated as grace notes. For drums, flams (designated by the character "f" in the tab) must be implemented as grace notes. See an example in the Useful Resources section below.
 +  - The system must deal with errors in the input in a user-friendly way. Minor errors should be treated as warnings but should not stop the conversion process. Major errors in particular measures must be presented to the user to fix them.
 +  - The system must of course support all three instruments and as many as possible of the features shown in the two examples below.
  
 <html><!-- <html><!--
proj.txt · Last modified: 2022/05/05 15:26 by bil