Skip to main content

Opening Section + Magic Squares

Sai-Kung folded rock

This section has no solos, it's a simple contrast of two strata: (1) descending rapid scales, and (2) sustained chords swelling and receding. Listen to the opening page (score below) here:



Ex.1: score p.1

The pitches for both are derived from the magic square. The chords are most straightforward, they simply read the horizontals of the square as 6-note chords. The piece starts with the uppermost vertical (the main material + high G), and works its way down.


EG#DF#A#G
BFAC#A#D
G#CEC#FB
D#GFAD#G
BG#CF#A#D
BD#AC#FA#

Ex.2: magic square, showing different transposed 5-note sequences (alternating red and blue)

Here are the voicings; which I just worked on the piano intuitively by starting with the horizontal as written, then moving notes around to form triads where possible. Note also that I opted for a smoother orchestration across the three woodwind and three brass by dividing the 6-notes into two sets (reeds vs brass) that are often triadic, or nearly so in most cases.

Ex.3: the six-note chords and their bar numbers in score: flageolet (diamond) noteheads are woodwind, black are brass
In looking back over my notes, I found that I had wanted to emphasise the fact that each horizontal  of the square overlaps notes from two transposed copies (see the red and blue in the square above) of the same chord (the main material of the piece, which could be read as a sharp-11th chord in jazz terms). I had considered sustaining the 'root' of the chord into the next sustained wind chord, to emphasise this root: also emphasising the process of the square/transpositions because this root would keep moving up in register. See ex.4 for my sketch:
Ex.4: "magic square with "roots" sustained; emphasising the harmonic basis of the square.


The other stratum is descending scales, here on the three flutes as one group, and guitar/piano as the other. The guitar/piano lines are arpeggiated versions of the sustained chords, but reading from the bottom of the square up rather than top down. Originally these were supposed to be completely free-time, but I simplified this to molto rubato. The balance is not great here, as the guitar/piano are often only audible between ensemble chords.

The flutes part was significantly more complex (and took ages...) Essentially, the flutes all read the square the same way—backwards from bottom right—but each flute both places those pitches differently, and subdivides the intervening time and pitch spaces independently. Each interval between successive notes on the square is then subdivided, which may result in microtones. I used a max patch to generate the following, bar-by-bar:
  1. [numNodes] The number of "nodes" in this bar. That's the number of notes from the magic square sequence used in that phrase; also defining the position of these in the bar (i.e. four nodes with a 3/4 bar = dotted quaver each).
    1. this means that each instrument moves through the square at a slightly different rate, (forming momentary canons, though not really audible due to the rest of the process) but always averaging out across the full section.
    2. Also, because there's only a few possible values here, there's a good chance that these notes will line-up across the three flutes, accenting the harmony of the square, and relegating the extra subdividing notes as more of a distorting background harmony.
  2. [numNotes] the number of notes between each of the nodes above. I did my best to evenly subdivide the intervals (in terms of pitch as well as duration) to avoid overly complex notation. Microtones were avoided in fast runs (not perceivable), and nested tuplets avoided. 
    1. Ex.5 below shows the patch and some of its output. For each bar it generates a number of nodes that subdivide the bar, then subdivisions for each of those nodes.
Ex.5: Max patch (and its output on right) generating each flute's path through the square.
You can see above that numNodes and numNotes are weighted to prefer the middle values, to avoid the parts being too choppy. Once Max had generated the numbers, I had to work out how to assign notes and durations. Ex.6 shows my working-out for this.

Ex.6: showing (left) original thoughts for the system, and (right) the specific realisation of each bar (from b.1)
As an example of the above, the first bar is 4/4, made up of three nodes each for flutes 1 and 2, and four nodes for flute 3. All three lines start from the square bottom right corner A#, and since the scales are descending I begin with the highest A# on the flute. The three lines read along the square, A#, F, C# (+ A for fl.3 who has an extra node) [EDIT: I just noticed a mistake in b.1 *sigh*. The second "node" of the sequence should be F not G. Ah well... I'll call it G since that's what's in score.] Since flutes 1 and 2 have the same number of nodes, their A#, G, C# are aligned but flute 3 is not: the 4 beats divided into 3 nodes of 1+1/3 crotchets for flutes 1 and 2, and four crotchets for flute 3. Then the numNotes part of the algorithm creates a further layer of distortion by adding extra pitches between the nodal pitches derived from the square: up to now, the system is simply three overlapping readings of the square, a dynamically shifting three-voice canon, but this layer makes each line independent, with the pitches from the square acting as "nodes" to connect the lines. E.g. Flute-2 the A#-G is divided into two, so the midpoint pitch is A-quarter-flat (splitting the minor third into 2 x three-quarter-tone). Flute-2 second node (G-C#) is subdivided in 3, so in this case I chose three pitches inside that interval but slightly unevenly (F#, E, D#) to avoid needing 1/3-tones. I wasn't always strict with these subdivisions, often being pragmatic where the strict application would lead to wasted rehearsal time in a fast and dense section where that detail wouldn't be audible.

The structure of these sections is partially driven by the materiality of the flutes. When the descending line reaches the bottom of their register, it starts again from the top: the whole group goes back up together if any of them reach the bottom, so they sound as a disjointed group rather than coming apart completely. Although notated as fff throughout, this dynamic cannot be maintained in the low register, and the lower notes are often submerged under the sustained chords (intentionally).

The structuring principle of this section is is repetition followed by a slight inversion/change. I repeat this opening strata several times while the sustained chords work their way through the full square. Then at b.22 the material is slightly changed to destabilise the pattern. The flutes abandon the scales in favour of sustained multiphonics, but because these are unstable, the pitches move in and out of focus, leading to a disjoined soundworld that isn't a total change from the scales: an etiolated version for sure (see Ligeti's organ work Volumina for a similar concept). The guitar/piano come more to the fore here, briefly, before the wind chords take over.

Commentary notes:

  • The magic square is the core of the harmony throughout: and since the square is made of the same 5-note chord transposed, this section is a multiple of a multiple, an almost fractal quality. The square's pitches are slightly emphasised in the flutes by accenting them. The two different materials (scales and chords) are simplistically opposed to each other in terms of texture, but they use the same basic pitch material. The scales have the additional distortion of the interwoven pitches between them.
  • The readings of the square are quite simplistic, but then overlaid in a kaleidoscopic way, and with further distortion by the randomising process of the Max patch.



Comments

Popular posts from this blog

Sax & cymbals duet

The second section (bars 34–71 of the finished score v1) of the piece is an improvised duet for tenor saxophone and bowed cymbals. I've already referred to the ensemble part for this section, see here for an explanation of the system used to generate the asynchronous ensemble part from the magic square. The duet uses exclusively multiphonics on both instruments. "Multiphonics" are not chords (collections of single notes played simultaneously on different vibrating objects), rather they are multiple-sounds, metastable vibrations where more than one pitch is vibrating simultaneously on the same object so   they interfere with each other to form complex timbres of difference tones. Playing multiphonics requires practicing a specific skill to learning to balance the multiple-pitches. For saxophone, the tonal flexibility of the usual monophonic (single pitch) technique is sacrificed because the multiphonic will only stay balanced with a very specific mix of embouchure-pos...

cello solo v2 - orchestration

Re-working the generated part: Before I get to orchestrating the cello solo, I decided I need to re-work the generated line. The previous line (ex.1 below) wasn't too practical, and didn't give the cellist enough leeway to work with the prepared-string to bring out the desired sounds: the whole point here is that the preparations allow for different harmonics and multiphonics to emerge, and that the tablature-style notation constrains the player's actions to limit what specific sounds emerge. Ex.1: cello solo v1 (notation explained below) In the notation (as explained in earlier post ) there's a 6-line stave to indicate not pitches but bow positions, between the preparation (bottom) and bridge (top); essentially sul-tasto to sul-pont . The part mostly only uses the right hand for playing, with the left hand occasionally used for timbre variation through interference (see b.143–145). To generate the part, I allowed the isorhythm (ex.2) to run for nine iterat...