|
|
Intermediate Electronic Music Final Project
DescriptionThe final project is a composition created on the hardware and software in the electronic music studio. Generally, it is a sequencer performance, although you may perform parts live if you wish.
Assignment GoalsThe purpose of the project is to demonstrate your ability to apply the variety of techniques that you learn in this class to the creation of a piece. It is a practical demonstration of what you know about the hardware and software in our studio.
FormatThe project must have a duration of between 3 and 5 minutes. (You may do several shorter projects that add up to this length.) You must receive approval at least 1 week before the due date if your project is going to be longer or shorter than this.
The project must use Reason and Logic. There are two basic ways to accomplish this, and either is acceptable.- You could do the Reason portion of your piece entirely in the Reason program and then simply synchronize the playback of your Reason tracks to Logic using the rewire functionality.
- You could also use rewire to route audio output of Reason tracks (either separately or together from the Reason mixer) into Logic audio tracks and record them.
Your piece must incorporate at least one example of each of the following - best to think of each as being on its own track. (Spring 2007 students - please see the optional project format described at the bottom of this page.)
In Logic:
- One Logic audio track using an "Apple Loop" (via the Loop Browser).
- One Logic audio track using imported an audio file ("Import Audio") which could come from any source - in must synchronize with the sequence tempo.
- Two or more Logic tracks using different Logic instruments ("Inst") with preset sounds.
- One set of three (or more) tracks using an addition single Logic Instrument ("Inst") part. (A drum part spread across several tracks is a good option for this.)
- At least one Logic track using a Logic instrument ("Inst") that you have designed yourself or created by "tweaking" an existing Logic instrument. You may use any of the Logic instruments for this. Be prepared to open the instrument in Logic and explain how it works.
- On the Logic mixer (or using the Arrange window) set each channel's volume and panning. On at least two channels volume and panning must change at least once during the piece.
- Also on the mixer, make sure that no tracks "peak" and light the peak level indicator. (Lighting a peak indicator during playback of your piece is an automatic small grade deduction!)
- Whew... You may use additional tracks of any sort as you wish.
In Reason:
- At least two tracks in Reason using different synth/sampler
modules. At least one of the two must use a sound that you designed or
created by "tweaking" existing Reason instruments. Be prepared to open
the instrument in Logic and explain how it works.
- At least one
effects module (such as a reverb, delay, etc.) in Reason, either
connected in series to one of the synths or via a bus on the Reason
mixer.
- At least one Reason track using an NNXT or NN19 instrument that you create from your own sample(s).
Integrating Logic and Reason (starting Fall 2008):
- Create two Reason rewire objects in the Logic environment, each of which uses a different instrument in your Reason rack.
- Record MIDI events in Logic for each of these Reason instrument - assign a Logic "MIDI" track for each of these instruments.
- Also in Logic, bring the audio from your Reason rack into the Logic program - either as the stereo output from the Reason mixer, or as individual audio inputs from each Reason instrument
- Apply at least one controller to each of the Logic "MIDI" tracks as per above - for example, automate volume.
- Assign at least one Logic to the audio coming from Reason
Practice playing back your composition before the final exam session. You want to make sure that you have all settings automatically configured or that you know exactly how to configure them manually.
Be prepared to do a final mix down to CD and/or mp3 at the last meeting prior to the final exam session. Please bring a blank CD to this session if you want a copy of your piece or of any other files currently stored on your computer.
Failure to submit a final project may result in a failing grade for the course.
Regarding the track requirements: Although you must include tracks with examples of each of the resource described above, it is not required that each track play continuously though the entire piece. It is also possible to combine requirements on a single track, but be prepared to explain where and how you did this.
There are no limitations on what style or genre of music may be used for the project. The piece may be an original composition, an arrangement, a recorded improvisation, etc. Your grade will be affected by factors including following the project format outlined above, the accuracy of your performance (i.e., pitch and rhythm), the appropriateness of the sounds selected, and other musical aspects. While creativity and musicality will count, the primary factor will be the technical quality of your project.Important Note for Spring 2007: The requirements for this project may - but probably won't - change before the due date. All changes will be noted here and described in class.
GradingYou will be graded on technical aspects of the assignment. The
assignment will not be graded on its musical merits. This includes
the following:
- Correct length
- Required number and types of tracks.
- Inclusion of program changes and mixer settings.
- Accurate rhythm through careful playing, step entry and/or quantizing.
- No obvious wrong notes.
- Project plays correctly without manual adjustments at playback.
The musical quality of your piece does not determine your grade.
However, imagination can't hurt! Especially on the final project, you will likely want to make sure that you have plenty of time for careful adjustment and final editing of your piece. The assignment description is
intentionally vague so that there is room for you to exercise your
imagination. Try to come up with an interesting piece within the
guidelines of this project.Due DateFinal projects are due at the scheduled final exam date for this class. Consult the course green sheet and course calendar.Be sure to attend your tutoring sessions while working on the project and let the instructor know immediately if you are encountering problems with the studio equipment or the project itself.Plan on finishing your project before final exam week. The demand for studio time will be intensive during the week preceding finals. Start your project as soon as possible to avoid the last minute rush. Your project should be finished by your last tutoring session before final exams.
If you have any questions or problems on this assignment please talk to me as soon as possible during your tutoring session, see me during my office hours, send email to mitchelldan@deanza.edu, watch for me on IM, etc.OPTIONAL ALTERNATIVE FINAL PROJECT REQUIREMENTS. A student in the spring 2007 Intermediate class made a point about the
final project that has some validity. For this reason I am
offering an alternative option on this project which reduces the number
of Logic components and increases the number of Reason components. At your option, you may complete the project as originally described above or you may instead choose to complete a version of the project meeting the "Alternative" requirements described below.
Optional Alternative Final Project
In Logic:
- (Eliminated)
- One Logic audio track using imported an audio file ("Import
Audio") which could come from any source - in must synchronize with the
sequence tempo.
- Two or more Logic tracks using different Logic instruments ("Inst") with preset sounds.
- (Eliminated)
- At least one Logic track using a Logic instrument ("Inst") that
you have designed yourself or created by "tweaking" an existing Logic
instrument. (This could be one of the two Logic INST tracks described above.) Be
prepared to open the instrument in Logic and explain briefly how you modified it.
- On the Logic mixer (or using the Arrange window) set each
Logic channel's volume and panning. On at least two channels volume and
panning must change at least once during the piece.
- Also on the mixer, make sure that no tracks "peak" and light the
peak level indicator. (Lighting a peak indicator during playback of
your piece is an automatic small grade deduction!)
- Whew... You may use additional tracks of any sort as you wish.
In Reason:
- At least five tracks in Reason using different synth/sampler
modules. At least one of the five must use a sound that you designed or
created by "tweaking" existing Reason instruments. Be prepared to open
the instrument in Logic and explain how it works. (number of tracks increased.)
- At least one Reason track must be a Redrum drum machine part. (added to original project)
- At least four
sampler tracks using the NNXT and NN19 instruments. You must include at
least one instance of each of the two samplers - e.g., you may not use only the NNXT or only the NN19. (number of tracks increased)
- At least one of the NNXT or NN19 instruments mentioned above must use a sound that you create from your own imported and edited sample(s). (clarified)
- At least four
effects module (such as a reverb, delay, etc.) in Reason, either
connected in series to synths or via a bus on the Reason
mixer. (The latter is preferable.) (increased the number of effects)
Integrating Logic and Reason (starting Fall 2008):
- Create two Reason rewire objects in the Logic environment, each of which uses a different instrument in your Reason rack.
- Record MIDI events in Logic for each of these Reason instrument - assign a Logic "MIDI" track for each of these instruments.
- Also in Logic, bring the audio from your Reason rack into the
Logic program - either as the stereo output from the Reason mixer, or
as individual audio inputs from each Reason instrument
- Apply at least one controller to each of the Logic "MIDI" tracks as per above - for example, automate volume.
- Assign at least one Logic track to accept the audio coming from Reason
|
|
