129 lines
5.7 KiB
HTML
Executable File
129 lines
5.7 KiB
HTML
Executable File
<html>
|
|
<body style="width:800px;">
|
|
<h1>P A R A L L A X I S</h1>
|
|
<h2>PERFORMANCE NOTES</h2>
|
|
|
|
|
|
<h3>FORCES ========</h3>
|
|
|
|
The score for parallaxis is in four parts and can be played by any
|
|
four melodic instruments, multiple quartets may perform simultaneously
|
|
under the direction of one or more directors.
|
|
|
|
<h3>NOTATION ======== </h3>
|
|
|
|
Parallaxis uses a combination of graphical, and more traditional
|
|
proportion style notation. There are three lines to the stave
|
|
representing the registral areas low, middle and high. The size of the
|
|
noteheads and thickness of lines represent dynamics - small note heads
|
|
are played most quietly, larger noteheads are louder.
|
|
|
|
There is very little traditional rhythmic notation, instead the score
|
|
adopts a "scrolling score" paradigm. The score appears from the right
|
|
of the screen and scrolls in a leftwards direction.
|
|
|
|
In the center of the screen are the shaded areas called the playzones,
|
|
in the center of these playzones is a vertical green line representing
|
|
the playhead, as the music passes over the playhead it is executed by
|
|
the performer.
|
|
|
|
Each of the parts plays back at a slightly different speed from the
|
|
others causing the parts to constantly shift in and out of phase with
|
|
one another.
|
|
|
|
<h3>SCREEN SCORE / PROJECTION ========</h3>
|
|
|
|
No special software is needed to view the screen score for
|
|
Parallaxix. It is written as a web app and runs in a web browser; for
|
|
best results use Google Chrome, Safari or Firefox. Avoid Internet
|
|
Explorer if you use windows.
|
|
|
|
The Score/s may be projected using a digital projector plugged into a
|
|
laptop. These projections maybe visible to both musicians and
|
|
audience. Optionally each member of the ensemble reads the score from
|
|
a laptop placed on a music stand. This maybe preferable where unusual
|
|
spatial arrangments of the musicians is prefered. The web based score
|
|
is designed in such a way that everyone connected to that page will
|
|
see the same thing - and that any controls touched on the directors
|
|
laptop will controls the scores in front of all the musicians.
|
|
|
|
<h3>DURATION ======== </h3> Each of the parts is cyclical, looping constantly
|
|
with the tail joining up with the head of the music seamlessly. This
|
|
means the piece is of indeterminate duration, but given the amount of
|
|
material presented in the score i would suggest between 8 and 12
|
|
minutes as an appropriate performance length.
|
|
|
|
At the bottom left of the screen is a timer indicating how long has
|
|
elapsed since the start of the piece - this is your reference for when
|
|
to finish the performance
|
|
|
|
For example the ensemble may decide collectively before a performance
|
|
that after 8 minutes on performer stops holding a sustained note and
|
|
each 20 seconds after that another performer also stops holding a
|
|
sustained note. When all performers have stopped following the score
|
|
and are sustaining a pitch they may graudually diminuendo to nothing
|
|
and the piece is over.
|
|
|
|
<h3>DIFFERENT POSSIBLE VERSIONS ========</h3> There are a number of different
|
|
strategies for making a piece using this score but there are two
|
|
fundementally different approaches: solosit recording multitrack tape
|
|
part and live ensemble version.
|
|
|
|
<h3>THE ROLE OF THE DIRECTOR ======== </h3> In the Ensemble version there is
|
|
another element - the role of the conductor/director. There need not
|
|
be a director of a performance - the score may simply be followed as
|
|
it appears with the different speed lines shifting phase with one
|
|
another. However, if a director is involved in a performance their
|
|
role is to make live interventions to the flow of the perfomance. A
|
|
director can alter the speeds of the individual parts using the + -
|
|
minus buttons seen on the left and right of the screen as well as
|
|
pausing individual parts by clicking on the playzones or depressing
|
|
and releasing the number keys 1 through 4, or the ensemble as a whole
|
|
using the full stop space bar keys. (click the help link for a full
|
|
list if directors keybindings)
|
|
|
|
|
|
<h3>MULTIPLE QUARTETS - MUTLIPLE SCORES ========</h3> Also, if a director is
|
|
involved the size of the ensemble may double and be divided into two
|
|
groups. In this case the director can use two laptops to control two
|
|
groups, each group playing different instances of the score. Here the
|
|
two groups ensemble will slip in and out of phase with one another the
|
|
same way as is happening internally within the individual groups! The
|
|
number of groups playing for independant scores need not be limited to
|
|
two. One director can manipulate as many groups as deemed appropriate
|
|
for the performance - there may also be more than one director.
|
|
|
|
<h3>SPATIAL POISTIONING OF MUSICIANS AND ENSEMBLES</h3>
|
|
|
|
TODO
|
|
|
|
|
|
|
|
<h3>SETTING THE INITIAL SPEEDS AND STARTING LOCATIONS ======== </h3>
|
|
OPTIONAL:
|
|
Each version can be made unique by setting new starting points for
|
|
each of the instrumental parts, as the score can be seen as a loop
|
|
there is no fixed starting point so new ones can be choosen for each
|
|
performance. Also the speed relationships between the parts may also
|
|
be changed. At the moment this involves changing the values in the
|
|
parallaxis.js file. TODO - add this facility to the web interface
|
|
|
|
|
|
<h3>THE SCORE SERVER ========</h3>
|
|
The score server is currently hosted in spc.org Greenwich, London
|
|
and can be accessed here: http://nodescore.kiben.net:8888/parallaxis.html
|
|
|
|
A Rapsberry Pi based score server is available as both hardware and a
|
|
flashable disk image, this is ideal when no network connection is
|
|
avalable in the concert space. The hardware version can be requested
|
|
for loan from the Contemporary Music Center of Ireland. The disk image
|
|
maybe downloaded from http://rob.kibe.net/parallaxis.html
|
|
|
|
<h4>The Server Kit contains:</h4>
|
|
One Raspberry Pi embedded Linux computer
|
|
SD Card containting custom operating system and score server.
|
|
Wireless and wired Network switch to create the PARALLAXIS access point.
|
|
|
|
</body>
|
|
</html>
|