Audio Setup

ADC

1. Flute input (the mic as close as possible to the flute).

DAC

1. Stereo Left;
2. Stereo Right;
3. Quadriphony Front Left;
4. Quadriphony Front Right;
5. Quadriphony Rear Right;
6. Quadriphony Rear Left;
7. Flute simulation (1/2): for testing purpose, not for the concert;
8. Flute simulation (2/2): idem.

Midi setup

A MIDI mixer with at least 9 faders (cf. MIDI-Mix sub-patch on the main patch) can be used optionally to control the internal mixing of the electronic layers.

Software installation

All the electronic part is produced by the jupiter-max-2023-light max patch.

• Open jupiter-max-AE-2022.maxproj project with Max 8.

• Configure the DSP Status Options :

  • Fe = 48000 Hz;
  • IO Vector Size = 512;
  • Signal Vector Size = 64;
  • Scheduler in Overdrive ON;
  • Scheduler in Audio Interrupt ON;

Patch presentation

Main patch

Main sub-patch (“grand-central”)

In this subpatch you find the “pitch_fol” sub-patch for the pitch detection (and the sfplay~ for simulation) to automatically trigger the events (cf. also the “QLIST” sub-patch in the main patch).

Message syntax

The electroacoustic part of Jupiter consists in the following modules

• reverb (r)
• 4 harmonizers (h)
• frequency shifter (f)
• synthese : pafs (o:oscilator)
• noise (n)
• sampler (t:trevor)

The messages used to connect the modules use the following syntax :
htor = hamonizer level to reverberation, fto2 = frequency shifter level to stereo output, etc.

Warning : stor controls synthesis to reverberation (ntor and otor), while stor~ controls the level of the flute samples to the reverb. (can be quite confusing …)

Shortcuts

• ESC = DSP on/off;
• TAB or enter = next event;
• 0 = follower off;
• , = follower on.

Rythmic interpolations

In the original version the electronic rythmic sequence played in sections V and IX were recorded repectively in sections II and VII. They are now hard coded in the patch
Consequently, to hear this sequences correctly during the rehearsals it is no more necessary play these sections in the right order.

live vs prerecorded sequence

In this version some effects are performed on prerecorded soundfiles and not on the live flute sound as in the originary version. You can switch back to the “full real time” version with the toggle located above pd samples.

System calibration and tests

1. Play section 8 event 2 (this is a sequence of tam-tam sounds) (click on the button “NEXT” to manually trigger the events).

2. Adjust the patch input level to have a nice flanging effect at XI.18.`

3. Test the score follower with the flute simulation :

• Start section 1.
• Open the sub-patch “Simulation”.
• Click on the message box to begin the simulation.
• You can listen to the whole piece (outputs 7 and 8 play the flute simulation).

Score following

Events are mainly triggered by the score follower (using the scofo pd object), except in sections V, VIII, IX, X and XIII where events should be triggered manually for safety reasons.
The “manual” events are :

• .
• ..
• …

Initialization routine

To initialize the patch:

1. Turn audio ON;
2. Click the init button “Start here: 0”: the “follower on” toggle is ON;
3. Click on the button “Section 1” and on the button “NEXT” to trigger the first event.
4. The events can be triggered
   • by the computer music performer (preferably)
   • or automatically triggered with the score follower (using the max detonate object).

Performance notes

Please refer to the composer’s “notes pour l’execution” in the printed score.

Flute amplification

The flute sound should be slightly amplified to balance well with the electronic part.