Skip to main content

Piano and Guitar duet v.2 - realisation

It's been two months between deciding the system I'd use for this duet, and actually implementing it. Inevitably a few things have shifted, but it's essentially the same as described in the first post here.

Part of the delay was laziness about transferring the stream of numbers into notes on Sibelius, which it turns out was solved easily by using the 'seq' object in Max to turn the stream of numbers into a midi file, which could then be opened in Sibelius. Easy!

The other delay was in trying to work out how the notation would work to (a) allow the guitar and piano to be together but drift apart at times, and (b) still allow the ensemble to play over the duet without requiring the players follow the conductor too strictly. The delay was one of those situations where I decided to just let me brain work on it without me (mulling it over sometimes without actually thinking about it too hard), and then some helpful chats with other composers made it fall into place.

I also had to figure out how to generate the drifts between the two instruments. In the end I took the generated stream of numbers and colour coded it to easily show the head motif—pitches 5, 9, 15, 19, 23, which equals E, G#, D, F#, A#: in Ex.1 the head proceeds from darker to lighter shades of orange, non-motif pitches are white—then anywhere there was a partial version of the head I would double it with a complete version. The pink section in ex.1 shows a very incomplete motif in the upper line against a complete one in the lower line. In the score, these two would either literally overlap (one instrument plays the complete version while the other plays the drifted version) or hybridise the lines by working some of the drifted notes into the complete motif.

In hindsight, I could have then started overlapping incomplete (already drifted) versions of the motif against even more drifted versions to take this further, maybe I'll do that later...

Ex.1: overlapping the head motif to create drifts.

In the actual realisation, I take more intuitive approach, taking the longer drift sections and sometimes lining them up against more complete motifs, but sometimes distributing the notes differently, transferring some from one instrument into the other. See ex.2, and more significant drifting shown in ex.3.
Ex.2: showing transformation from generated stream of notes (bottom stave) to guitar/piano.

Ex.3 more significant drifts from the original motif.
Guitarists maybe scratching their heads at the harmonics, but the guitar is in a scordatura tuning (E, G#, D, F#, A#, E) to allow the head motif to be played as 12th-fret harmonics.

Commentary notes:

While the system generated the sequence of notes (from a carefully tweaked algorithm), there is a lot of intuition in how this section unfolds. Many of the drifting sequences are distributed between guitar and piano in a highly unsystematic way, focussing on particular harmonies or timbres etc, but always in direct response to what I'm presented with. at that moment.


Popular posts from this blog

cello solo v1

Cello solo v1 The cello solo will use my prepared cello: not a million miles from a prepared piano as mentioned in previous blog post. The preparations make pitch quite indeterminate, so rather than generate a stream of pitches (like for the guitar/piano) what I wanted to generate was essentially a tablature score for the cellist to create a stream of actions that would limit the indeterminate pitches in different ways to create loose patterns. Tablature notation differs from standard notation be being more about telling the player what do (what actions to carry out, where to put fingers etc.) rather than what sound/note to make. It can be especially useful in situations where the specific pitch result is indeterminate so instead the notation deals with timing, positions etc. See Aaron Cassidy's scores and writings on this as a good example. Below is a page of his solo for any bowed-string instrument, with staves for: (top) fingerings and bowing on the four strings; (middle) fing…

piano & guitar 3 - orchestration

[general apologies for the images in this post, which don't always link easily to the text. My parameter names kept changing over the few days spent composing this, which looks confusing now because the parameter names (descriptors) aren't always the same.]
Having generated the phrases for the guitar and piano, I need to decide how this 5-mins of duet will relate to the rest of the ensemble. I decided to use the Xenakis rotating-cubes technique to generate a phrase-by phrase orchestration behaviour. Crucially, this only defines the type and size of orchestration, not the specifics: I could have generated very specific limitations on instruments etc but wanted to keep this free to save time really, and allow a more intuitive shaping of that aspect. I also wanted to avoid this being too 'blocky' and only mirroring the phrasing of the duet, so I allowed for some orchestrations to reach forward or backwards into neighbouring phrases. My first thoughts on this is that I ne…

Magic Squares


I took my original 5-note sequence (E, G#, D, F#, A#) and extended it into a 6x6 magic square following Maxwell Davies' approach of (a) ensuring the sequence goes out of phase from line to line (because sequence of 5 pitches along lines 6 units long), and (b) transposing each subsequent sequence. The transpositions aren't always the same, because I was getting repetitions; because going up in minor-3rds ends up in the same place after four cycles (12 chromatics divided by 3 semitones = 4), so after the 4th cycle (when it should return to E) I transposed up a further semitone to push the whole cycle of four sequences a semitone higher than the first four. The square is (mostly) transposed by minor 3rds because the original 5-note sequence is whole-tone (the two possible whole-tone sets are six notes each), so minor 3rds give pitches not in the original whole-tone set. [commentary point] This solves the whole-tone problem of only having six notes to work with (or t…