Fall2014.CITA180Homework3 History

Show minor edits - Show changes to markup

Changed lines 42-43 from:
  1. 1-page paper (printed, submitted in class) describing your musical and aesthetic objectives in

creating this adaptation of Bach.

to:
  1. One-page paper (printed, submitted in class) describing your musical and aesthetic objectives in creating this adaptation of Bach.
Changed line 56 from:
  • Avril 14 (MIDI and Python), by Daniel Hanf
to:
  • (old - to be updated) Avril 14 (MIDI and Python), by Daniel Hanf
Changed line 45 from:

name, project number and title (Project #1: Transforming Bach), course (MUSC 131), and date.

to:

name, project number and title (Project #1: Transforming Bach), course, and date.

Deleted lines 56-66:
  • Nonsense (MIDI and Python), by Samuel Cooper (original)
  • Intro (MIDI and Python), by Hudson Jones
  • Take Five (MIDI and Python), by Johnathan Hegler and George Woolston

Relevant Quote

"Any amount of work can be done in any amount of time... only the quality varies." ~Joao Meidanis

Reference

  1. Cooper, D. and Clancy, M. (1985) "Oh! Pascal", 2nd ed., W.W. Norton & Company, New York, p. 42.
Deleted lines 50-90:

In class we worked through several programs that put all Jython Music data structures into practice. Write a Jython program that generates an interesting piece of music.

Documentation

Follow the Golden Rule of Style: "A program should be as easy for a human being to read and understand as it is for a computer to execute." [1]

In general, you should comment any variable, obscure statement, block of code, etc. you create. Follow the textbook examples on how to document code.

Additionally, your code should always include opening comments as follows:

(:source lang=Python tabwidth=3 -trim :)

  1. Author: Your names
  2. Email: Your email addresses
  3. Class: CITA 180
  4. Assignment: Homework #2
  5. Due Date: The assignment's due date
  6. Purpose: Provide a simple, yet complete description of the task being
  7. performed by this program. It may be several sentences long.

(:sourcend:)

Submissions

You will submit your assignment via OAKS. Be prepared to demo your music to the rest of the class. Your submission consists of:

  1. Your Python program. Give it a meaningful name.
  2. The MIDI file generated from your program.
  3. A printout of your program - to be submitted in class during the performance.

Grading

Your grade will be based on how well you followed the above instructions, and the depth/quality of your work.

Added lines 1-108:

Assigned Date: Monday, Sep. 15, 2014
Due Date: Monday, Sep. 22, 2014
Due Time: 9:55am

Last modified on October 28, 2014, at 08:41 AM (see updates)

Assignment created by Dr. Blake Stevens.

Objectives

  1. To prompt creative thought about musical transcription, arrangement, and recomposition.
  2. To apply in practice skills in reading traditional notation and using jythonMusic.
  3. To gain a deeper understanding of Bach’s compositional style.

Assignment Instructions

Pick one of the works included in the score packet or any of the movements of the ''Goldberg Variations'' (posted on OAKS); working independently, use jythonMusic to create a transcription, arrangement, or recomposition of the work of at least 50 seconds in length. Be creative in your treatment of sound, including timbre (instrumentation), dynamics, and panning, to produce an interesting piece of music. Consider three different ways of “transforming Bach” in this project:

Transcription: transferring a piece of music from one instrumental medium to another - for example, from violin to lute, guitar, or keyboard. This is the most “literal” form of adaptation, although the transfer of the work from the keyboard to the medium of the computer (with its wide range of sounds) will nonetheless entail creative thought.

Arrangement: adaptation or development of an existing work that preserves a clear, perceptible correspondence to the original work, although features such as voicing, register, timbre, and instrumentation are more significantly altered than in a transcription.

Recomposition: transformation or appropriation of elements of an existing work to create a new work; with new parts or voices, rhythms (including percussion), basslines, and freely-composed music added by the composer, the original work now functions as a “template” or “scaffolding” on which a new work or performance is built, or as a mine of musical “material” to be exploited. is technique is related to “plunderphonics,” the sampling of audio recordings to create sound collages (see John Oswald, “Plunderphonics, or Audio Piracy as a Compositional Prerogative”).

Submit

  1. MIDI recording of your project on OAKS (also to be played in class, Monday, September 22).
  2. 1-page paper (printed, submitted in class) describing your musical and aesthetic objectives in

creating this adaptation of Bach.

  1. Printout (submitted in class) of fully documented program, including (as comments) your

name, project number and title (Project #1: Transforming Bach), course (MUSC 131), and date.

Grading

Projects will be graded according to the requirements listed above and the creativity/work demonstrated in the resulting work.

In class we worked through several programs that put all Jython Music data structures into practice. Write a Jython program that generates an interesting piece of music.

Documentation

Follow the Golden Rule of Style: "A program should be as easy for a human being to read and understand as it is for a computer to execute." [1]

In general, you should comment any variable, obscure statement, block of code, etc. you create. Follow the textbook examples on how to document code.

Additionally, your code should always include opening comments as follows:

(:source lang=Python tabwidth=3 -trim :)

  1. Author: Your names
  2. Email: Your email addresses
  3. Class: CITA 180
  4. Assignment: Homework #2
  5. Due Date: The assignment's due date
  6. Purpose: Provide a simple, yet complete description of the task being
  7. performed by this program. It may be several sentences long.

(:sourcend:)

Submissions

You will submit your assignment via OAKS. Be prepared to demo your music to the rest of the class. Your submission consists of:

  1. Your Python program. Give it a meaningful name.
  2. The MIDI file generated from your program.
  3. A printout of your program - to be submitted in class during the performance.

Grading

Your grade will be based on how well you followed the above instructions, and the depth/quality of your work.

Some Interesting Submissions

Here are some interesting submissions:

  • Avril 14 (MIDI and Python), by Daniel Hanf
  • Nonsense (MIDI and Python), by Samuel Cooper (original)
  • Intro (MIDI and Python), by Hudson Jones
  • Take Five (MIDI and Python), by Johnathan Hegler and George Woolston

Relevant Quote

"Any amount of work can be done in any amount of time... only the quality varies." ~Joao Meidanis

Reference

  1. Cooper, D. and Clancy, M. (1985) "Oh! Pascal", 2nd ed., W.W. Norton & Company, New York, p. 42.