<link rel='alternate' type='application/rss+xml' title='RSS' href='index.xml' />
Background: #fff
Foreground: #000
PrimaryPale: #8cf
PrimaryLight: #18f
PrimaryMid: #04b
PrimaryDark: #014
SecondaryPale: #ffc
SecondaryLight: #fe8
SecondaryMid: #db4
SecondaryDark: #841
TertiaryPale: #eee
TertiaryLight: #ccc
TertiaryMid: #999
TertiaryDark: #666
Error: #f88
body {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}

a {color:[[ColorPalette::PrimaryMid]];}
a:hover {background-color:[[ColorPalette::PrimaryMid]]; color:[[ColorPalette::Background]];}
a img {border:0;}

h1,h2,h3,h4,h5,h6 {color:[[ColorPalette::SecondaryDark]]; background:transparent;}
h1 {border-bottom:2px solid [[ColorPalette::TertiaryLight]];}
h2,h3 {border-bottom:1px solid [[ColorPalette::TertiaryLight]];}

.button {color:[[ColorPalette::PrimaryDark]]; border:1px solid [[ColorPalette::Background]];}
.button:hover {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::SecondaryLight]]; border-color:[[ColorPalette::SecondaryMid]];}
.button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::SecondaryDark]];}

.header {background:[[ColorPalette::PrimaryMid]];}
.headerShadow {color:[[ColorPalette::Foreground]];}
.headerShadow a {font-weight:normal; color:[[ColorPalette::Foreground]];}
.headerForeground {color:[[ColorPalette::Background]];}
.headerForeground a {font-weight:normal; color:[[ColorPalette::PrimaryPale]];}

	border-left:1px solid [[ColorPalette::TertiaryLight]];
	border-top:1px solid [[ColorPalette::TertiaryLight]];
	border-right:1px solid [[ColorPalette::TertiaryLight]];
.tabUnselected {color:[[ColorPalette::Background]]; background:[[ColorPalette::TertiaryMid]];}
.tabContents {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::TertiaryPale]]; border:1px solid [[ColorPalette::TertiaryLight]];}
.tabContents .button {border:0;}

#sidebar {}
#sidebarOptions input {border:1px solid [[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel {background:[[ColorPalette::PrimaryPale]];}
#sidebarOptions .sliderPanel a {border:none;color:[[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel a:hover {color:[[ColorPalette::Background]]; background:[[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel a:active {color:[[ColorPalette::PrimaryMid]]; background:[[ColorPalette::Background]];}

.wizard {background:[[ColorPalette::PrimaryPale]]; border:1px solid [[ColorPalette::PrimaryMid]];}
.wizard h1 {color:[[ColorPalette::PrimaryDark]]; border:none;}
.wizard h2 {color:[[ColorPalette::Foreground]]; border:none;}
.wizardStep {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];
	border:1px solid [[ColorPalette::PrimaryMid]];}
.wizardStep.wizardStepDone {background:[[ColorPalette::TertiaryLight]];}
.wizardFooter {background:[[ColorPalette::PrimaryPale]];}
.wizardFooter .status {background:[[ColorPalette::PrimaryDark]]; color:[[ColorPalette::Background]];}
.wizard .button {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::SecondaryLight]]; border: 1px solid;
	border-color:[[ColorPalette::SecondaryPale]] [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryPale]];}
.wizard .button:hover {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::Background]];}
.wizard .button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::Foreground]]; border: 1px solid;
	border-color:[[ColorPalette::PrimaryDark]] [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryDark]];}

.wizard .notChanged {background:transparent;}
.wizard .changedLocally {background:#80ff80;}
.wizard .changedServer {background:#8080ff;}
.wizard .changedBoth {background:#ff8080;}
.wizard .notFound {background:#ffff80;}
.wizard .putToServer {background:#ff80ff;}
.wizard .gotFromServer {background:#80ffff;}

#messageArea {border:1px solid [[ColorPalette::SecondaryMid]]; background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]];}
#messageArea .button {color:[[ColorPalette::PrimaryMid]]; background:[[ColorPalette::SecondaryPale]]; border:none;}

.popupTiddler {background:[[ColorPalette::TertiaryPale]]; border:2px solid [[ColorPalette::TertiaryMid]];}

.popup {background:[[ColorPalette::TertiaryPale]]; color:[[ColorPalette::TertiaryDark]]; border-left:1px solid [[ColorPalette::TertiaryMid]]; border-top:1px solid [[ColorPalette::TertiaryMid]]; border-right:2px solid [[ColorPalette::TertiaryDark]]; border-bottom:2px solid [[ColorPalette::TertiaryDark]];}
.popup hr {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::PrimaryDark]]; border-bottom:1px;}
.popup li.disabled {color:[[ColorPalette::TertiaryMid]];}
.popup li a, .popup li a:visited {color:[[ColorPalette::Foreground]]; border: none;}
.popup li a:hover {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; border: none;}
.popup li a:active {background:[[ColorPalette::SecondaryPale]]; color:[[ColorPalette::Foreground]]; border: none;}
.popupHighlight {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
.listBreak div {border-bottom:1px solid [[ColorPalette::TertiaryDark]];}

.tiddler .defaultCommand {font-weight:bold;}

.shadow .title {color:[[ColorPalette::TertiaryDark]];}

.title {color:[[ColorPalette::SecondaryDark]];}
.subtitle {color:[[ColorPalette::TertiaryDark]];}

.toolbar {color:[[ColorPalette::PrimaryMid]];}
.toolbar a {color:[[ColorPalette::TertiaryLight]];}
.selected .toolbar a {color:[[ColorPalette::TertiaryMid]];}
.selected .toolbar a:hover {color:[[ColorPalette::Foreground]];}

.tagging, .tagged {border:1px solid [[ColorPalette::TertiaryPale]]; background-color:[[ColorPalette::TertiaryPale]];}
.selected .tagging, .selected .tagged {background-color:[[ColorPalette::TertiaryLight]]; border:1px solid [[ColorPalette::TertiaryMid]];}
.tagging .listTitle, .tagged .listTitle {color:[[ColorPalette::PrimaryDark]];}
.tagging .button, .tagged .button {border:none;}

.footer {color:[[ColorPalette::TertiaryLight]];}
.selected .footer {color:[[ColorPalette::TertiaryMid]];}

.sparkline {background:[[ColorPalette::PrimaryPale]]; border:0;}
.sparktick {background:[[ColorPalette::PrimaryDark]];}

.error, .errorButton {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::Error]];}
.warning {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::SecondaryPale]];}
.lowlight {background:[[ColorPalette::TertiaryLight]];}

.zoomer {background:none; color:[[ColorPalette::TertiaryMid]]; border:3px solid [[ColorPalette::TertiaryMid]];}

.imageLink, #displayArea .imageLink {background:transparent;}

.annotation {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; border:2px solid [[ColorPalette::SecondaryMid]];}

.viewer .listTitle {list-style-type:none; margin-left:-2em;}
.viewer .button {border:1px solid [[ColorPalette::SecondaryMid]];}
.viewer blockquote {border-left:3px solid [[ColorPalette::TertiaryDark]];}

.viewer table, table.twtable {border:2px solid [[ColorPalette::TertiaryDark]];}
.viewer th, .viewer thead td, .twtable th, .twtable thead td {background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::Background]];}
.viewer td, .viewer tr, .twtable td, .twtable tr {border:1px solid [[ColorPalette::TertiaryDark]];}

.viewer pre {border:1px solid [[ColorPalette::SecondaryLight]]; background:[[ColorPalette::SecondaryPale]];}
.viewer code {color:[[ColorPalette::SecondaryDark]];}
.viewer hr {border:0; border-top:dashed 1px [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::TertiaryDark]];}

.highlight, .marked {background:[[ColorPalette::SecondaryLight]];}

.editor input {border:1px solid [[ColorPalette::PrimaryMid]];}
.editor textarea {border:1px solid [[ColorPalette::PrimaryMid]]; width:100%;}
.editorFooter {color:[[ColorPalette::TertiaryMid]];}
.readOnly {background:[[ColorPalette::TertiaryPale]];}

#backstageArea {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::TertiaryMid]];}
#backstageArea a {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::Background]]; border:none;}
#backstageArea a:hover {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; }
#backstageArea a.backstageSelTab {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
#backstageButton a {background:none; color:[[ColorPalette::Background]]; border:none;}
#backstageButton a:hover {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::Background]]; border:none;}
#backstagePanel {background:[[ColorPalette::Background]]; border-color: [[ColorPalette::Background]] [[ColorPalette::TertiaryDark]] [[ColorPalette::TertiaryDark]] [[ColorPalette::TertiaryDark]];}
.backstagePanelFooter .button {border:none; color:[[ColorPalette::Background]];}
.backstagePanelFooter .button:hover {color:[[ColorPalette::Foreground]];}
#backstageCloak {background:[[ColorPalette::Foreground]]; opacity:0.6; filter:'alpha(opacity=60)';}
* html .tiddler {height:1%;}

body {font-size:.75em; font-family:arial,helvetica; margin:0; padding:0;}

h1,h2,h3,h4,h5,h6 {font-weight:bold; text-decoration:none;}
h1,h2,h3 {padding-bottom:1px; margin-top:1.2em;margin-bottom:0.3em;}
h4,h5,h6 {margin-top:1em;}
h1 {font-size:1.35em;}
h2 {font-size:1.25em;}
h3 {font-size:1.1em;}
h4 {font-size:1em;}
h5 {font-size:.9em;}

hr {height:1px;}

a {text-decoration:none;}

dt {font-weight:bold;}

ol {list-style-type:decimal;}
ol ol {list-style-type:lower-alpha;}
ol ol ol {list-style-type:lower-roman;}
ol ol ol ol {list-style-type:decimal;}
ol ol ol ol ol {list-style-type:lower-alpha;}
ol ol ol ol ol ol {list-style-type:lower-roman;}
ol ol ol ol ol ol ol {list-style-type:decimal;}

.txtOptionInput {width:11em;}

#contentWrapper .chkOptionInput {border:0;}

.externalLink {text-decoration:underline;}

.indent {margin-left:3em;}
.outdent {margin-left:3em; text-indent:-3em;}
code.escaped {white-space:nowrap;}

.tiddlyLinkExisting {font-weight:bold;}
.tiddlyLinkNonExisting {font-style:italic;}

/* the 'a' is required for IE, otherwise it renders the whole tiddler in bold */
a.tiddlyLinkNonExisting.shadow {font-weight:bold;}

#mainMenu .tiddlyLinkExisting,
	#mainMenu .tiddlyLinkNonExisting,
	#sidebarTabs .tiddlyLinkNonExisting {font-weight:normal; font-style:normal;}
#sidebarTabs .tiddlyLinkExisting {font-weight:bold; font-style:normal;}

.header {position:relative;}
.header a:hover {background:transparent;}
.headerShadow {position:relative; padding:4.5em 0 1em 1em; left:-1px; top:-1px;}
.headerForeground {position:absolute; padding:4.5em 0 1em 1em; left:0px; top:0px;}

.siteTitle {font-size:3em;}
.siteSubtitle {font-size:1.2em;}

#mainMenu {position:absolute; left:0; width:10em; text-align:right; line-height:1.6em; padding:1.5em 0.5em 0.5em 0.5em; font-size:1.1em;}

#sidebar {position:absolute; right:3px; width:16em; font-size:.9em;}
#sidebarOptions {padding-top:0.3em;}
#sidebarOptions a {margin:0 0.2em; padding:0.2em 0.3em; display:block;}
#sidebarOptions input {margin:0.4em 0.5em;}
#sidebarOptions .sliderPanel {margin-left:1em; padding:0.5em; font-size:.85em;}
#sidebarOptions .sliderPanel a {font-weight:bold; display:inline; padding:0;}
#sidebarOptions .sliderPanel input {margin:0 0 0.3em 0;}
#sidebarTabs .tabContents {width:15em; overflow:hidden;}

.wizard {padding:0.1em 1em 0 2em;}
.wizard h1 {font-size:2em; font-weight:bold; background:none; padding:0; margin:0.4em 0 0.2em;}
.wizard h2 {font-size:1.2em; font-weight:bold; background:none; padding:0; margin:0.4em 0 0.2em;}
.wizardStep {padding:1em 1em 1em 1em;}
.wizard .button {margin:0.5em 0 0; font-size:1.2em;}
.wizardFooter {padding:0.8em 0.4em 0.8em 0;}
.wizardFooter .status {padding:0 0.4em; margin-left:1em;}
.wizard .button {padding:0.1em 0.2em;}

#messageArea {position:fixed; top:2em; right:0; margin:0.5em; padding:0.5em; z-index:2000; _position:absolute;}
.messageToolbar {display:block; text-align:right; padding:0.2em;}
#messageArea a {text-decoration:underline;}

.tiddlerPopupButton {padding:0.2em;}
.popupTiddler {position: absolute; z-index:300; padding:1em; margin:0;}

.popup {position:absolute; z-index:300; font-size:.9em; padding:0; list-style:none; margin:0;}
.popup .popupMessage {padding:0.4em;}
.popup hr {display:block; height:1px; width:auto; padding:0; margin:0.2em 0;}
.popup li.disabled {padding:0.4em;}
.popup li a {display:block; padding:0.4em; font-weight:normal; cursor:pointer;}
.listBreak {font-size:1px; line-height:1px;}
.listBreak div {margin:2px 0;}

.tabset {padding:1em 0 0 0.5em;}
.tab {margin:0 0 0 0.25em; padding:2px;}
.tabContents {padding:0.5em;}
.tabContents ul, .tabContents ol {margin:0; padding:0;}
.txtMainTab .tabContents li {list-style:none;}
.tabContents li.listLink { margin-left:.75em;}

#contentWrapper {display:block;}
#splashScreen {display:none;}

#displayArea {margin:1em 17em 0 14em;}

.toolbar {text-align:right; font-size:.9em;}

.tiddler {padding:1em 1em 0;}

.missing .viewer,.missing .title {font-style:italic;}

.title {font-size:1.6em; font-weight:bold;}

.missing .subtitle {display:none;}
.subtitle {font-size:1.1em;}

.tiddler .button {padding:0.2em 0.4em;}

.tagging {margin:0.5em 0.5em 0.5em 0; float:left; display:none;}
.isTag .tagging {display:block;}
.tagged {margin:0.5em; float:right;}
.tagging, .tagged {font-size:0.9em; padding:0.25em;}
.tagging ul, .tagged ul {list-style:none; margin:0.25em; padding:0;}
.tagClear {clear:both;}

.footer {font-size:.9em;}
.footer li {display:inline;}

.annotation {padding:0.5em; margin:0.5em;}

* html .viewer pre {width:99%; padding:0 0 1em 0;}
.viewer {line-height:1.4em; padding-top:0.5em;}
.viewer .button {margin:0 0.25em; padding:0 0.25em;}
.viewer blockquote {line-height:1.5em; padding-left:0.8em;margin-left:2.5em;}
.viewer ul, .viewer ol {margin-left:0.5em; padding-left:1.5em;}

.viewer table, table.twtable {border-collapse:collapse; margin:0.8em 1.0em;}
.viewer th, .viewer td, .viewer tr,.viewer caption,.twtable th, .twtable td, .twtable tr,.twtable caption {padding:3px;}
table.listView {font-size:0.85em; margin:0.8em 1.0em;}
table.listView th, table.listView td, table.listView tr {padding:0px 3px 0px 3px;}

.viewer pre {padding:0.5em; margin-left:0.5em; font-size:1.2em; line-height:1.4em; overflow:auto;}
.viewer code {font-size:1.2em; line-height:1.4em;}

.editor {font-size:1.1em;}
.editor input, .editor textarea {display:block; width:100%; font:inherit;}
.editorFooter {padding:0.25em 0; font-size:.9em;}
.editorFooter .button {padding-top:0px; padding-bottom:0px;}

.fieldsetFix {border:0; padding:0; margin:1px 0px;}

.sparkline {line-height:1em;}
.sparktick {outline:0;}

.zoomer {font-size:1.1em; position:absolute; overflow:hidden;}
.zoomer div {padding:1em;}

* html #backstage {width:99%;}
* html #backstageArea {width:99%;}
#backstageArea {display:none; position:relative; overflow: hidden; z-index:150; padding:0.3em 0.5em;}
#backstageToolbar {position:relative;}
#backstageArea a {font-weight:bold; margin-left:0.5em; padding:0.3em 0.5em;}
#backstageButton {display:none; position:absolute; z-index:175; top:0; right:0;}
#backstageButton a {padding:0.1em 0.4em; margin:0.1em;}
#backstage {position:relative; width:100%; z-index:50;}
#backstagePanel {display:none; z-index:100; position:absolute; width:90%; margin-left:3em; padding:1em;}
.backstagePanelFooter {padding-top:0.2em; float:right;}
.backstagePanelFooter a {padding:0.2em 0.4em;}
#backstageCloak {display:none; z-index:20; position:absolute; width:100%; height:100px;}

.whenBackstage {display:none;}
.backstageVisible .whenBackstage {display:block;}
StyleSheet for use when a translation requires any css style changes.
This StyleSheet can be used directly by languages such as Chinese, Japanese and Korean which need larger font sizes.
body {font-size:0.8em;}
#sidebarOptions {font-size:1.05em;}
#sidebarOptions a {font-style:normal;}
#sidebarOptions .sliderPanel {font-size:0.95em;}
.subtitle {font-size:0.8em;}
.viewer table.listView {font-size:0.95em;}
@media print {
#mainMenu, #sidebar, #messageArea, .toolbar, #backstageButton, #backstageArea {display: none !important;}
#displayArea {margin: 1em 1em 0em;}
noscript {display:none;} /* Fixes a feature in Firefox where print preview displays the noscript content */
<div class='header' macro='gradient vert [[ColorPalette::PrimaryLight]] [[ColorPalette::PrimaryMid]]'>
<div class='headerShadow'>
<span class='siteTitle' refresh='content' tiddler='SiteTitle'></span>&nbsp;
<span class='siteSubtitle' refresh='content' tiddler='SiteSubtitle'></span>
<div class='headerForeground'>
<span class='siteTitle' refresh='content' tiddler='SiteTitle'></span>&nbsp;
<span class='siteSubtitle' refresh='content' tiddler='SiteSubtitle'></span>
<div id='mainMenu' refresh='content' tiddler='MainMenu'></div>
<div id='sidebar'>
<div id='sidebarOptions' refresh='content' tiddler='SideBarOptions'></div>
<div id='sidebarTabs' refresh='content' force='true' tiddler='SideBarTabs'></div>
<div id='displayArea'>
<div id='messageArea'></div>
<div id='tiddlerDisplay'></div>
<div class='toolbar' macro='toolbar [[ToolbarCommands::ViewToolbar]]'></div>
<div class='title' macro='view title'></div>
<div class='subtitle'><span macro='view modifier link'></span>, <span macro='view modified date'></span> (<span macro='message views.wikified.createdPrompt'></span> <span macro='view created date'></span>)</div>
<div class='tagging' macro='tagging'></div>
<div class='tagged' macro='tags'></div>
<div class='viewer' macro='view text wikified'></div>
<div class='tagClear'></div>
<div class='toolbar' macro='toolbar [[ToolbarCommands::EditToolbar]]'></div>
<div class='title' macro='view title'></div>
<div class='editor' macro='edit title'></div>
<div macro='annotations'></div>
<div class='editor' macro='edit text'></div>
<div class='editor' macro='edit tags'></div><div class='editorFooter'><span macro='message views.editor.tagPrompt'></span><span macro='tagChooser excludeLists'></span></div>
To get started with this blank [[TiddlyWiki]], you'll need to modify the following tiddlers:
* [[SiteTitle]] & [[SiteSubtitle]]: The title and subtitle of the site, as shown above (after saving, they will also appear in the browser title bar)
* [[MainMenu]]: The menu (usually on the left)
* [[DefaultTiddlers]]: Contains the names of the tiddlers that you want to appear when the TiddlyWiki is opened
You'll also need to enter your username for signing your edits: <<option txtUserName>>
These [[InterfaceOptions]] for customising [[TiddlyWiki]] are saved in your browser

Your username for signing your edits. Write it as a [[WikiWord]] (eg [[JoeBloggs]])

<<option txtUserName>>
<<option chkSaveBackups>> [[SaveBackups]]
<<option chkAutoSave>> [[AutoSave]]
<<option chkRegExpSearch>> [[RegExpSearch]]
<<option chkCaseSensitiveSearch>> [[CaseSensitiveSearch]]
<<option chkAnimate>> [[EnableAnimations]]

Also see [[AdvancedOptions]]
premier second troisième
Anthèmes 2 requires 2 audio inputs and 6 audio outputs.
* the first input is the violin microphone, used for sound processing
* the second input is the violin microphone, used for the score follower
* The 6 outputs are the 6 surrounding channels (see the [[Technical rider]] part)

As an example, here is a Max5 audio set up with the audio card  Fireface Firewire 400


Clik the ~IOmapping button to set the input / Output mapping : 

[[Quick Start]]
See [[Performance Guidelines]]
[[Quick Start]]
[[Score Follower]]
[[iPad Lemur or BCF2000 Control]]
[[Levels & Deltas]]
[[MaxMsp patches]]
[[Audio Configuration]]
[[Technical rider]]
[[anthèmes 2 overview]]
[[Performance Guidelines]]
Here is the main patch overview with some of its subpatches : @@''~Anthèmes2_MMXI_53''@@ is the current version.
When preparing to play in a new hall care should be taken to @@first set the level of amplification for the violin@@.
The level should be @@such that the instrument’s color changes as a result of the amplification but no louder.@@ This is best done playing excerpts (without electronics) of section I – “Très lent”.
Next it is useful to play excerpts (without electronics) of section II – “Rapide, dynamique”, in order to take into account the effect of the pizzicatos. It may be useful to add some reverberation (not too much!) to the violin sound in order to give it more body.
As explained above, ''@@the amplification serves above all to balance the color one obtains through amplification with the color of the electronics.@@'' Once this phase has been completed, the same excerpts can be tried out with electronics.
If the hall is too dry, the sound of the amplified violin may be slightly reverberated, using an external reverb unit. In any case the reverb must be noticeable.  

''@@As a general rule, the level of the amplified violin should be the same as that of the electronics.@@'' 
The comments that follow will indicate any contradictions to this general rule or supply additional information with respect to balance and interpretation.

**''Introduction – “Libre”''    The level of the infinite reverberation (of the violin and samplers) at the end of the decrescendo should remain loud enough so that the cutoff at cue 11 by the violin be clearly heard. 

**''Harmonics (/I, I/II, II/III etc.)''   The infinite reverberation should be clearly audible for approximately five seconds after the violinist finishes the harmonic at the end, before the decrescendo starts. 

**''I – “Très lent”''    Particular attention should be given to balancing the sampler pizzicato dyads with the live violin, as of bar 2. 

**''II – “Rapide, dynamique”''   In this section @@the balance should be such that the listener is not able to distinguish the live violin from the electronic part.@@ The confusion between the two is deliberate. At the end of the section, wait until the sampler D5 "tenuto" sound in the background fades out before triggering the next harmonics part.

**''III – “Lent”''  During the “chaotic” processes the balance should be such that the listener is not able to distinguish the live violin from the electronic part. The “cloud” processes should be distinctly heard but remain in the background. Particular attention should be given to balancing the sampler dyads with the live violin as of bar 36.

**''IV “Agité, instable”''   @@The spatialization of the violin should be forceful. This needs that in this section the direct signal of the amplified violin fed to the loudspeakers system must be greatly reduced (see below "Sound Engineer tasks", in order to hear properly the spatialization processed by the computer. The sampler sequences starting at bars 1 and 25 as well as the “cloud” processes starting at bar 12 (cue 5) should be distinctly heard but remain in the background.@@  Moreover, in this section the violin should ideally interact and play together with the melody played by the electronics at the beginning and at the end, therefore the electronics should be well audible and present for the violinist himself.     

**''V – “Très lent”''   Same remarks apply as for III regarding the two processes. Particular attention should be given to balancing the sampler dyads with the live violin in bar 1, then as of the end of bar 20.

**''VI.1 – “Allant”''   @@The level of the spatialization at all the places marked “moitié-crins/moitié bois” (bars 6, 12, 17 etc.) should be such that the listener is not able to distinguish the live violin from the electronic part, which should be forceful.@@

**''VI.2''   @@Four different kinds of writing are present in this section@@. In order of appearance they are : @@''“Calme, régulier”'' : Light and not too aggressive. ''“Agité"'' : The harmonizer’s level should be such that the listener is not able to distinguish the live violin from the harmonizer. The sampler chords should be distinctly heard but remain in the background. ''“Brusque”'' : Both the solo violin and the sampler sequences should be forceful and aggressive. '“Calme, retenu” : The arpeggiatos should be clear but light. The sinus chords, RM2C (ring modulator to comb) and IR (infinite reverb) should be well blended. The RM2C’s resonance should be clearly heard but not overbearing.@@

**''VI.3 – “Calme”''   The two sampler clusters with infinite reverberation should be distinctly heard but remain in the background. At the end of the decrescendo starting the second half of bar 209, towards the end of the piece, the clusters should remain loud enough so that the cutoff at cue 31 by the violin be clearly heard. The last cue must be triggered in the exact moment when the violinist stops doing the last long trill and plays the final D. Arrangements may be taken with the violinist himself, in order to wait for a sign from the computer music performer. 

!Setting Levels for the electronics

@@While the patch contains level settings which are the result of playing the piece in many different places, it is always necessary to make adjustments, to fine tune the electronics with the hall and the sound system and configuration being used.@@
''@@Adjustements shall be made, for each section, during the rehearsal process, changing the values in the Relative Levels number boxes (delta levels, under the absolute levels - these latter ones NOT to be touched) and then storing the changes by mean of the pattrstorage interface named "deltas", located on the left of the patcher "DSP new".@@'' 


!Performance Tasks for the Sound Engineer

Apart following the overall balance of the amplified violin and live electronics, the Sound Engineer has some very important tasks to handle during the performance of Anthèmes 2.
* First of all, pizzicato passages should be well comprehensible, therefore they might need to be helped a little by amplification, while passages with “arco" should be not too loud. 
* In @@section ''IV''@@, from measure 1 to 11, and from measure 25 to 39, the @@''amplification for the violin should be reduced a lot''@@, in order to hear well the spatialised sound of the violin, processed by the computer. Amplification for the violin must come back again in the middle of the section, from measure 12 to 24.
* @@''Handling the external reverb unit for the violin amplified sound''@@ is also up to the sound engineer. In particular there's a specific need to use ''reverb on violin amplified sound'' @@in section ''VI.3'', to get a better balance between the electronics and the sound of the amplified violin@@. A starting "normally reverberated" and an ending "richly reverberated" presets must be found and stored during rehearsals. From the beginning of VI.3, the sound engineer should gradually increase the amount of reverb for the violin sound, arriving to the rich reverb maximum level towards the end of the section. This process may be done in four steps: from measure 164 in VI.3 to measure 169, the reverb level may gradually increase to half of the maximum, then stay like that until measure 188, and from 189 to 195 increase to the maximum level and stay like that until the end of the piece. 

!!Anthèmes 2
* Max4/Msp Electronic Design, by ''Andrew Gerzso'' (1997-2004)
* Score Following Design and Integration by ''Arshia Cont'' (2009) //arshia.cont@ircam.fr//
* Max5 Electronic Design, new Dsp Design by ''Gilbert Nouno'' (2010) //gilbert.nouno@ircam.fr//
* Control redesign for Max 6+ by ''Arshia Cont'' (2014) //arshia.cont@ircam.fr//
*//~TiddlyWiki// documentation by ''Gilbert Nouno'' (last update December 2014 by AC)

This page explains how to run, test and use the patch
!Running the patch
* run Max6.1+ and load the patch @@''Anthèmes2_~MMXI_53_6r.maxpat''@@ 
* you should see the [[MaxMsp patches]] window
* in the main @@''Anthèmes2_~MMX_47''@@ window click as shown below the message box ''@@dsp open@@'' that brings up the [[Audio Configuration]] window.
* You should do the audio setup once, if you quit the application or Max, it would retains the last audio setup next time you run the program
! The first reset (after the patch is loaded)
* in the main window click the ''@@bang@@'' at the right of the ''@@loadbang@@'' message, then click the ''@@loadbang@@'' message.
This reset should be done only one time.
before doing this first reset, choose your midi faders controller device in DSP_new patcher (see [[iPad Lemur or BCF2000 Control]]), in order to initialize it correctly. 
! Initialisation (takes place at the begining of the piece or each time you need to restart a section in rehearsal)
* in the main window click the big ''@@init button@@'' : in the ''@@~DSP_new@@''   patch, the ''@@violin_fx fader@@'' and the ''@@main fader@@'' should turn red :
* turn the ''@@DAC@@'' on (the loudspeaker icon)
The loudspeaker icon turns red to indicates that audio is on
! Check the adc 
* click the big ''@@init button@@''
* dac should be turned on
* the first two vu-meters on the left are displaying the signals, coming from the console, fed by the microphone of the violin (a DPA_4061). The most left vu-meter is the level of the violin to the sound processing, and the other one is the signal feeding the score follower.
As a general rule of thumb, first set the level for the score follower, looking at the calibration window (see below), so that it reaches nearly the maximum during strong attacks (compression must not be applied). 
Then set the level of the violin to sound processing. This signal might be slightly compressed (f.ex. ratio 3:1, threshold -15 dB, attack 2ms, release 100 ms, make-up maximum + 3dB), but in any case, to get a correct balance, the overall level should be equivalent to that one feeding the score follower.  

! Set the input level for the score follower
* click the big ''@@init button@@''
* open the ''@@Controls subpatch@@''
* check the Yellow button Audio on/off to antescofo button (should be on 1)
* turn the calibrate toggle on in the ''@@calibrate@@'' window
* if the violin plays, one should see the level in the ''@@calibrate@@'' window, an optimal level requires that strong attack should arrive nearly at the maximum

! Test the samples
* in the main window click the big ''@@init button@@''
* open the subpatch [img[images/ctl_new.png]]
** in the patch ''@@~CTL_new@@'' open the subpatch ''@@p test_samplers@@'' 
** click on the message box under "test ON"
** test the sounds with the 1, 2, 3, 4, 5, 6, 11, 12, 13, 14,15 message boxes, you should hear sound
** click on the message box under "test OFF"

! Running the patch with the recording
* in the main window click the big ''@@init button@@'' (the DAC should be on)
* in the patch [img[images/ctl_new.png]] click on the message box "simul 120 ..."
* in the patch [img[images/p_controls.png]] choose the a2_new_intro.score.txt
* the keyboard letter @@''S''@@ (s for the french "Suivi") toggles the score follower on and off, set it on  : the toggle appears with a cross in the [img[images/p_controls.png]]  window
* Press the @@"ascograph"@@ button, which will launch the standalone application as shown below visualizing the instrumental score (in piano roll) and electronics. A Cursor in real-time will show the progress into the score.
* the  [img[images/dsp_new.png]]  window should have changed as shown below [img[images/dsp_new_intro.png]]
* in the patch [img[images/ctl_new.png]] click on the  message box @@''intro''@@ (or the popup menu above it) : the piece should start with the electronic sounds and with the score follower engaged, please see the [[Score Follower]] menu to know where the score follower is used. Remember the ''@@Right Arrow key@@'' allows you to execute the //''next cue''// in the score (in case one automoatic cue is missed or if you have disengaged the score follower)
* The levels are pre-recorded within the score and the patch, nevertheless you will surely need to modulate them in real time durring the performance, you could do so with some midi faders remote control like ~BCF2000 or Lemur, please have a look at the [[iPad Lemur or BCF2000 Control]] section to setup your midi faders device. 
Regarding the score following in Anthèmes 2, this part is done by a module named ''Antescofo'', which uses an encoded  score of the piece.

Some parts of the piece are __not__ using ''Antescofo'' __intentionally__, because there is no need to! For example, section IV and VI are  enough to trigger by hand.
The movements where ''Antescofo'' is used are :
* Introduction (except for cue 3 and 4 that are triggered manually)
* Section I
* Section II
* Section III
* Section V
* Section VI-A can __optionally__ use Antescofo, but it really depends on your violinist as it is often too difficult.

All the harmonics parts (the transitions) are triggered by hand using the "@@Right Arrow Key@@".

In any circumstance, the patch and ''Antescofo'' have been designed so that at any point one can switch to hand triggering without any hassle: by pressing the @@s@@ key (s for french Suivi)  a message is sent to Antescofo that will globally turn off the following and then one can use the "@@Right Arrow Key@@"  key to move forward. One can also do this while ''Antescofo'' is on and it won't cause problems.

One  should separate the ''Antescofo'' signal on the console and boost its fader to get a good level for the following.

Please, be aware that there are extra cues in VI-A. They are marked by X.5 (like 142.5) and are systematic.

!! Use Ascograph

By pressing the Ascograph button in the @@Controls@@ patcher, you will launch the Standalone application Ascograph. Ascograph (see screenshot below) is designed to MONITOR the placement of in the score. This will help you to situate the performance at any time, using the follower or not.

You can resize the Ascograph window so that it fits your workspace. Additionally, you can disable the top panel from the @@View@@ menu for a more compact view.

"NOTE:" Ascograph is a standalone application. It communicates with Max using internal networks. Therefore, if for any reason AscoGraph quits, you don't need to panic! It won't affect the patch in any ways! Just relaunch it by double clicking on the ascograph button!

Electronics by Andrew Gerszo, Arshia Cont and Gilbert Nouno
Anthèmes 2 - Pierre Boulez
* Loudspeakers  (The amplifiers should be outside the hall or being silent)
** 2 Loudspeakers with amplifiers, controllers and speakers cables (L, R see map on page 2) (violin reinforcement)
** 6 Loudspeakers with amplifiers, controllers and speakers cables (1 to 6 see map) (electronics diffusion)

Loudspeakers L, R should be type C690, MTD 112 or equivalent
Loudspeakers 1 to 6  should be type D&B C690 or  ~MTD115 or equivalent 
The exact number of loudspeakers will have to be finalized according to the size and shape of the hall (balcony, etc.)

* Mixing Desk
** 1 mixing desk Yamaha ~DM1000 (with ~MY16-AT card if you use audio interface with adat in/out)
* Effects
** 1 digital reverb type Lexicon ~PCM91
*  Microphone
** 1 microphone DPA 4061 + string holder
** 1 UHF wireless system for the DPA 4061
* Computers
** 1 Apple Macbookpro 2,33Ghz minimum, with Max/MSP (4.6 minimum)
** 1 audio interface (2 in, 6 out) type RME Fireface 400 
* Cables
** 8 balanced audio lines from the mixer to the amps 


The sound control and the computers have to be  placed in the audience.

*	Lighting
** Focused and graduated lighting for the soloist
** Lighting Control

* [[DefaultTiddlers]]: Contains the names of the tiddlers that you want to appear when the ~TiddlyWiki is opened
You'll also need to enter your username for signing your edits: <<option txtUserName>>
Electronic Realization of Anthèmes 2 by Pierre Boulez

This document describes the procedure for concert realization and preparation of live electronics of Anthèmes 2 for violin and electronics by Pierre Boulez, with minimal human and institutional costs. It describes the procedures and roles of different parties as well as minimal technical and organization information needed to setup the process.

* Parties and Role Definitions

The parties involved in the procedure and their preliminary roles are described as follows:
**	Violinist: the person in change of executing and performing the violin section, and participating in programmed rehearsals.
**	Computer Music Performer: Is the person in charge of the real-time computer projection. He is responsible for:
***	Preliminary communications with the violinist regarding electronic performance in case the former has no prior experience with the piece.
***	Preparation of electronic acoustics with the sound engineer in the hall.
***	Execution of live electronics during concert and rehearsal
***	Communications with the Violinist; Musical preparation with the violinist

**	Sound Engineer: Is the person in charge of sound projection. He/She is responsible for:
***	Studying the venue acoustics remotely and negotiate the technical rider with the Venue Stage/Technical Director.
***	Preparing and adapting the electronic acoustics to the hall acoustics upon arrival.
***	Live mixing and general acoustics control of the speakers during rehearsals and performance.
***	Communications with Venue Technical Director

**	Venue Stage/Technical Director: is the person in charge of producing the piece in a venue (concert hall). She/He is responsible for:
***	Initiating communications with the computer music performer and sound engineer in charge of performance.
***	Discuss and negotiate the requested technical rider with third-parties or internal technical director for availability and installment of requested material as described by the computer music performer and sound engineer in charge.
***	Organize the logistics and scheduling of rehearsals for the piece with electronics as close as possible to the requested schedule by the violinist and computer music performers.

This document assumes that the existence of the violinist, the venue and its stage/technical director(s). The computer music performer and sound engineer are provided by Ircam or external to the concert venue. Note that the sound engineer’s role for this performance goes beyond conventional practices of sound engineering and is required to be provided by this party.

* Requirements for the venue

The venue is required to provide:
**	Arrangement for rehearsals and technical setup: As discussed during communications between the violinist and the computer realization crew. The piece requires atleast the following for each performance and in chronological order:
***	A technical setup (having speakers, cables and console set) for the sound engineer and calibrating the electronics to the hall (half-day)
***	A rehearsal with the violinist in the hall for live electronic calibration (2 hours service)
***	A dress rehearsal before the concert.

**	Arrangement for accommodations: For the violinist, computer music performer and the sound engineer, during the rehearsal and the concert.

**	Installations in the concert venue: Prior to the arrival of the technical party, the venue stage director and sound engineer would discuss acoustic issues and the sound engineer would issue a technical plan for equipment setup in the concert venue. The venue should then be equipped with discussed materials prior to the team’s arrival and ready for further assessments. Minimal technical material and coordination required by the venue include:
***	Loudspeakers as described in the technical rider. The exact number and placement of loudspeakers will be finalized during early communications between the venue stage director and the sound engineer.
***	Mixing Desk: As described in the technical rider with ADAT input and output.
***	Cables:  8 balanced audio lines from the mixer to the amps
***	Lighting:  Focused and graduated lighting for the violinist on the stage, and a light technical manager to discuss with during rehearsals.
***	Effect: 1 digital reverb similar to Lexicon ~PCM91

* Requirements for the Technical Party

The technical party (Ircam, including sound engineer & computer music performer) would/could provide the following materials:
**	Computers, as required for the performance and rehearsal
**	Microphones
**	Coordination with violinist: In the absence of prior experience in performing the piece.
**	Electronic Acoustic Adaptation
**	Rehearsal & performance

* Procedure

In chronological order:

**	The venue stage/technical director will contact the technical party (ex. Ircam’s Production director, see Contacts) and inform him of the dates of the concert, the program and the violinist. In the communication process, the hall plan would be transferred to the technical party, and a day planning would be established.
**	In the event that the violinist is new to this piece, he or she would contact the computer music designer to talk about the performance. This case would involve an additional rehearsal time (either at Ircam or at the venue before the concert), and discussions between the violinist and computer performers for details.
**	The sound engineers at Ircam will analyze the room acoustics and will send back a detailed plan for speaker setups to the venue technical director. Discussions will reveal details for installation of speakers before the crew arrival.
**	According to the established day-plan, accommodation and travel will be provided by the venue. Upon arrival, the day-planning will be executed.

* Appendix
Sample Day Planning

This is a sample day planning for the performance of Anthèmes 2 in January 2010 in the Chicago Symphony concert hall. 

There are two possible ways to remotely control levels in Anthemes 2, either by using a classical BCF2000 MIDI Controler or by using iPad's LEMUR.

!! iPad Lemur Control

You need @@iPad 2@@ or later with the @@Lemur Software@@ purchased and installed. Upload the @@Anthemes2.jzml@@ file to Lemur App on your iPad using iTunes.

Create a protected WIFI network on your Mac. Set your MAC WFI's TCP/IP (go to Preferences->Networks->Wifi->Advanced) to the following parameters, and Apply.
Open your iPad, connect to the home network created on your Mac. Click on (i) next to the connection and set to the following parameters.

!! BCF2000 midifaders

The midifaders are controlling the deltas (or relative levels) of the main useful faders.
* in the main @@''Anthèmes2_~MMX_47''@@ window click the following box 
which then opens the patch
In the center right menu, choose your midi device (and make sure the toggle on the right of the menu is checked). Under the menu the ctlin output should show some midi controllers activity when your device sends midi data.
Your midi device (with either faders ot knobs) should have the following controllers setup on midi channel 1 
** CTL 1 :: //main delta level//
** CTL 2 :: //sampler 1 delta level//
** CTL 3 :: //sampler 2 delta level//
** CTL 4 :: //general violin effects (fx) delta level//
** CTL 9 :: //Infinite Reverb 1 delta level//
** CTL 10 :: //Infinite Reverb 2 delta level//
** CTL 11 :: //Infinite Reverb 3 delta level//
** CTL 12 :: //Ring Modulation and Comb filter delta level//
** CTL 14 : //Frequency shifting + Delay delta level//
** CTL 15 :: //4 harmonizers delta level//

The controllers are updated during the piece by the automation from the cues, but you can of course modify their level manually whenever needed.