Difference between revisions of "Rwong"
From CCRMA Wiki
(→Current Questions) |
|||
| Line 2: | Line 2: | ||
My original idea was to enhance the chord progression maker I made from Music 220B. But upon realizing that Music 220C might be my last chance to make a composition, I've decided to put that idea off for now and instead think about creating an electronic music response to the first movement of Beethoven's Symphony No. 5, composed mostly in Chuck. | My original idea was to enhance the chord progression maker I made from Music 220B. But upon realizing that Music 220C might be my last chance to make a composition, I've decided to put that idea off for now and instead think about creating an electronic music response to the first movement of Beethoven's Symphony No. 5, composed mostly in Chuck. | ||
| + | |||
| + | ==Files== | ||
| + | |||
| + | * None yet. Check back next time! | ||
==Current Ideas== | ==Current Ideas== | ||
| Line 16: | Line 20: | ||
* The original work can create an intimidating effect by having all of the instruments play. Can I achieve a similar ff effect in Chuck? | * The original work can create an intimidating effect by having all of the instruments play. Can I achieve a similar ff effect in Chuck? | ||
* Should fermatas be hardcoded into the Chuck file, or should they be held for as long as the person running the program wishes? (The person may press a key to end a fermata)? | * Should fermatas be hardcoded into the Chuck file, or should they be held for as long as the person running the program wishes? (The person may press a key to end a fermata)? | ||
| + | |||
| + | ==Timeline== | ||
| + | |||
| + | * Week 2: Present idea and get feedback. | ||
| + | * Week 3: Have preliminary outline of form and orchestration. | ||
| + | * Week 4: Implement first quarter. | ||
| + | * Week 5: Implement second quarter. | ||
| + | * Week 6: Implement third quarter. | ||
| + | * Week 7: Implement fourth quarter. | ||
| + | * Week 8: Revise. | ||
| + | * Week 9: Present final work for final comments | ||
Revision as of 10:52, 7 April 2011
Project Idea
My original idea was to enhance the chord progression maker I made from Music 220B. But upon realizing that Music 220C might be my last chance to make a composition, I've decided to put that idea off for now and instead think about creating an electronic music response to the first movement of Beethoven's Symphony No. 5, composed mostly in Chuck.
Files
- None yet. Check back next time!
Current Ideas
- I want to write a piece that doesn't just reflect its musical characteristics, but also reflects the reputation it has developed. Maybe I should consider incorporating material from composers after Beethoven as well?
- The HevyMetl and BandedWG will most definitely be in the piece.
- I want to use panning at some point in the piece.
- I do not plan to have a chord texture as thick as in the original. Having multiple instruments play chords takes a long time--and isn't terribly original.
Current Questions
- To what extent should this piece a (1) re-orchestration, (2) an arrangement, and (3) an response that is highly contrasted with the original overall?
- The original's opening is extremely important and distinctive. It's also quiet assertive and loud. Should my opening be assertive and loud as well, or would it be more interesting to make it mysterious and quiet?
- The original work can create an intimidating effect by having all of the instruments play. Can I achieve a similar ff effect in Chuck?
- Should fermatas be hardcoded into the Chuck file, or should they be held for as long as the person running the program wishes? (The person may press a key to end a fermata)?
Timeline
- Week 2: Present idea and get feedback.
- Week 3: Have preliminary outline of form and orchestration.
- Week 4: Implement first quarter.
- Week 5: Implement second quarter.
- Week 6: Implement third quarter.
- Week 7: Implement fourth quarter.
- Week 8: Revise.
- Week 9: Present final work for final comments
