Philippe Manoury
Updated at
Do you notice a mistake?
flute
Detailed staff comes from Brahms, send mail to ressources-contenus@ircam.fr for correction.
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.
All the electronic part is produced by the jupiter-max-2023-light max patch.
The audio signals routing is done In the "Grand-Central" subpatch
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).
The electroacoustic part of Jupiter consists in the following modules
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 ...)
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.
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.
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 :
To initialize the patch:
Please refer to the composer's "notes pour l'execution" in the printed score.
The flute sound should be slightly amplified to balance well with the electronic part.
Updated at
Do you notice a mistake?