From 99ec164886a940c745a4a2194bfe55c5b163d81d Mon Sep 17 00:00:00 2001
From: BERTHAUT Florent <florent.berthaut@univ-lille1.fr>
Date: Fri, 30 Jul 2021 23:44:09 +0200
Subject: [PATCH] Fixed header levels

---
 bf-scowden.pd    | Bin 3186 -> 3472 bytes
 doc/objects.html |  50 +++++++++++------------------------------------
 doc/objects.md   |  22 ++++++++++-----------
 3 files changed, 22 insertions(+), 50 deletions(-)

diff --git a/bf-scowden.pd b/bf-scowden.pd
index 00d7681a0848f087798cacb2dfec90fa5b188b44..821d933c0254fbcf05ebbe56b80cd88fb74b6f71 100644
GIT binary patch
delta 322
zcmew)F+o~T*-s%kF|RDKSi#cFNWsj|Y@)yeMuUwXe{j{8q*jzD7@8><nwu*)rRf$Y
z=a;9X<|!oS=jEj)mlP|M<SQg9IQhGVx+xT=78hsc=P4xSr6?4oCg&HW6e}d=<Zz`V
zmLw`9=jUeTr7NTr<>xAtWTYx&<`tI|mFA}Al@wcZDMu(k?6FiZHZxHONGvK*$WK#9
zO4F?`NKuH<QAo^F$jmLsNd>7-ECE@Pp9VGtVslziVs2`Aeo;18Ql)}VX?CiDOJYV2
z*dcB?`9-ODB??ZdMI{-Dr6qa_zWGI|3Mr{2iJ3XY3i){o86_nJ#a8<I>6s-tiAj3N
zMVZAVi8*?ud6{LpIZ~N9IjMSSMfyqksikT9Nol$TDO@@VX$q#Mlk+%LCv);-0sv*I
BZL9zQ

delta 38
ucmbOr{YgSV*-s%kF|RDKSi#cFNWs!{qTmBY!;PPQa7`}ZRG6&Jn+X8*ZVcN1

diff --git a/doc/objects.html b/doc/objects.html
index 73afab8..71df148 100644
--- a/doc/objects.html
+++ b/doc/objects.html
@@ -27,11 +27,11 @@
 <p>A bf-instrument represents a musical instrument within the bf-pd system. Each instrument joins a bf-session and can contain bf-params and bf-outputs. To create an instrument you should instantiate a bf-instrument with the name of your instrument, e.g. [bf-instrument myDrumMachine].</p>
 <p>The audio output of your instrument should be connected to the first inlet of bf-instrument object. The interface has an <em>activity monitor</em> which shows a simple representation of the changing spectrum of the instrument’s sound, and the activity for each bf-instrument in the bf-session appears in the <em>collaboration window</em>. (Note: you must also send your audio to [dac~] in order to hear it!)</p>
 <p>The <em>collaboration window</em> can be opened with the toggle in the bf-instrument object. If musicians enter or leave the session you may need to close and re-open the collaboration window to update the collab window.</p>
-<h6 id="arguments">Arguments:</h6>
+<h3 id="arguments">Arguments:</h3>
 <ol type="1">
 <li>The name of the instrument.</li>
 </ol>
-<h6 id="inlets">Inlets:</h6>
+<h3 id="inlets">Inlets:</h3>
 <ol type="1">
 <li>The audio output of your instrument should be sent here. (It must also be sent to [dac~].)</li>
 <li>Messages can be sent to set :
@@ -44,7 +44,7 @@
 <p>A bf-param object has a user interface within the instrument patch itself, and it also creates a user interface in the collaboration window of each musician in the session.</p>
 <p>A bf-param can be one of four <em>types</em>: * <em>cont</em> are numbers between 0.0 and 1.0. * <em>midi</em> are numbers between 0.0 and 127.0. * <em>bool</em> can take values of 0 or 1. * <em>bang</em> are bang messages which are used to trigger actions.</p>
 <p>A bf-param can be a single instance of its type or it can be a multiple, which creates an array of values within a single bf-param object. For example, a bf-param “8 bool” creates an interface with 8 toggles, and might be used to represent 8 on/off values in a drum machine sequencer.</p>
-<h6 id="arguments-1">Arguments:</h6>
+<h3 id="arguments-1">Arguments:</h3>
 <ol type="1">
 <li>The name of the instrument, e.g. “myDrumMachine”.</li>
 <li>The name of the parameter, e.g. “kickOnOff”</li>
@@ -56,14 +56,14 @@
 <figure>
 <img src="img/bf-param_example.png" alt="" /><figcaption>bf-param_example</figcaption>
 </figure>
-<h6 id="inlets-1">Inlets:</h6>
+<h3 id="inlets-1">Inlets:</h3>
 <ol type="1">
 <li>Sets the value of the parameter. If the parameter is a multiple, then <em>Inlet 1</em> sets the parameter at the index last received on <em>Inlet 2</em>.</li>
 <li>Sets the index of the parameter which will be changed by sending values to <em>Inlet 1</em>.</li>
 <li>An integer in <em>Inlet 3</em> will send the value of the parameter at that index to <em>Outlet 3</em>.</li>
 </ol>
 <p>(The first two inlets for bf-param operate similar to the first two inlets for [array set] in Pd.)</p>
-<h6 id="outlets">Outlets:</h6>
+<h3 id="outlets">Outlets:</h3>
 <ol type="1">
 <li>The parameter value of the most recent change to the bf-param (whether that change came from the inlets, the UI, or via the collaboration window.)</li>
 <li>A list with the parameter value of the most recent change, and the index of the parameter that was changed.</li>
@@ -72,7 +72,7 @@
 <h2 id="bf-output">bf-output</h2>
 <p>An bf-output can be used to send some musical data from your bf-instrument to another instrument in the same bf-session. A bf-output can have the same types and multiplicity as a bf-param.</p>
 <p>When you open the collab window (by clicking on the ‘collab’ toggle in your bf-instrument) Each bf-output in your bf-instrument will appear on the left of the column for your instrument. You will also see three default outputs which are computed from your instrument’s audio: one detects onsets in your instrument’s audio, one outputs a pitch estimate, and one which outputs a loudness estimate.</p>
-<h6 id="arguments-2">Arguments:</h6>
+<h3 id="arguments-2">Arguments:</h3>
 <ol type="1">
 <li>The name of your instrument, e.g. “myDrumMachine”</li>
 <li>The name of your output, e.g. “triggers”</li>
@@ -80,21 +80,21 @@
 <li>The type of the parameter, e.g. “bang”</li>
 <li>The order you want the outlet to appear in the Collab Window (after the three default outputs).</li>
 </ol>
-<h6 id="inlets-2">Inlets:</h6>
+<h3 id="inlets-2">Inlets:</h3>
 <p>The inlets are similar to the first two inlets of bf-param 1. Sets the value of the output. If the output is a multiple, then <em>Inlet 1</em> sets the parameter at the index last received on <em>Inlet 2</em>. 2. Sets the index of the output which will be changed by sending values to <em>Inlet 1</em>.</p>
-<h6 id="outlets-1">Outlets:</h6>
+<h3 id="outlets-1">Outlets:</h3>
 <ol type="1">
 <li>The bf-output object in your patch does not have any outlets.</li>
 </ol>
 <h2 id="bf-clock">bf-clock</h2>
 <p>A bf-clock can be used for generating and sharing tempi and rhythmic events. You can use a bf-clock to create rhythmic events in your instrument, and you can synchronise instruments by sharing tempi between instruments via the collab window.</p>
-<h6 id="arguments-3">Arguments:</h6>
+<h3 id="arguments-3">Arguments:</h3>
 <ol type="1">
 <li>The name of your instrument, e.g. “myDrumMachine”</li>
 <li>The name of your bf-clock, e.g. “leadClock”</li>
 <li>The order you want the clock to appear (amongst the other bf-params) in the Collab Window.</li>
 </ol>
-<h6 id="inlets-3">Inlets:</h6>
+<h3 id="inlets-3">Inlets:</h3>
 <ol type="1">
 <li>A ‘1’ or ‘0’ turns the clock on and off</li>
 <li>A number sets the tempo in beats-per-minute (BPM), e.g. “120”</li>
@@ -103,7 +103,7 @@
 <li>A number sets the second beat subdivision. E.g. “3” will create eighth note triplets (or quaver triplets).</li>
 <li>This inlet can take a variety of messages for controlling a bf-clock. (See bf-clock-help.pd for details.)</li>
 </ol>
-<h6 id="outlets-2">Outlets:</h6>
+<h3 id="outlets-2">Outlets:</h3>
 <ol type="1">
 <li>Outputs a bang on each downbeat. E.g. if meter is set to ‘4’, the downbeat will occur every four beats. You can think of this as the first beat in a measure.</li>
 <li>Outputs a bang on each beat. E.g. if BPM is set to ‘120’, then there will be two beats per second.</li>
@@ -112,34 +112,6 @@
 <li>This outlet sends various messages about the state of the bf-clock, which allows one bf-clock to control the bpm of, and synchronize with, another bf-clock within the same patch.</li>
 </ol>
 <p>See bf-clock-help.pd to see more details about using bf-clock.</p>
-<h2 id="bf-watch">bf-watch</h2>
-<p>Bf-watch is used to get data from another bf-instrument into your bf-instrument.</p>
-<h6 id="arguments-4">Arguments:</h6>
-<ol type="1">
-<li>arg1</li>
-</ol>
-<h6 id="inlets-4">Inlets:</h6>
-<ol type="1">
-<li>blah</li>
-</ol>
-<h6 id="outlets-3">Outlets:</h6>
-<ol type="1">
-<li>blah</li>
-</ol>
-<h2 id="bf-ask">bf-ask</h2>
-<p>Description blah blah</p>
-<h6 id="arguments-5">Arguments:</h6>
-<ol type="1">
-<li>arg1</li>
-</ol>
-<h6 id="inlets-5">Inlets:</h6>
-<ol type="1">
-<li>blah</li>
-</ol>
-<h6 id="outlets-4">Outlets:</h6>
-<ol type="1">
-<li>blah</li>
-</ol>
 </main>
 </body>
 </html>
diff --git a/doc/objects.md b/doc/objects.md
index 963d105..8d99c7d 100644
--- a/doc/objects.md
+++ b/doc/objects.md
@@ -7,10 +7,10 @@ The audio output of your instrument should be connected to the first inlet of bf
  
 The *collaboration window* can be opened with the toggle in the bf-instrument object. If musicians enter or leave the session you may need to close and re-open the collaboration window to update the collab window.
 
-###### Arguments:
+### Arguments:
 1. The name of the instrument.
 
-###### Inlets:
+### Inlets:
 1. The audio output of your instrument should be sent here. (It must also be sent to [dac~].) 
 2. Messages can be sent to set :
 	* the session name [session-name mySession(
@@ -29,7 +29,7 @@ A bf-param can be one of four *types*:
 
 A bf-param can be a single instance of its type or it can be a multiple, which creates an array of values within a single bf-param object. For example, a bf-param "8 bool" creates an interface with 8 toggles, and might be used to represent 8 on/off values in a drum machine sequencer.
 
-###### Arguments:
+### Arguments:
 1. The name of the instrument, e.g. "myDrumMachine".
 2. The name of the parameter, e.g. "kickOnOff"
 3. The dimensionality of the parameter, e.g. "8"
@@ -41,14 +41,14 @@ So a bf-param with 8 drum machine note triggers would be:
 
 ![bf-param_example](img/bf-param_example.png)
 
-###### Inlets:
+### Inlets:
 1. Sets the value of the parameter. If the parameter is a multiple, then *Inlet 1* sets the parameter at the index last received on *Inlet 2*.
 2. Sets the index of the parameter which will be changed by sending values to *Inlet 1*.
 3. An integer in *Inlet 3* will send the value of the parameter at that index to *Outlet 3*.
 
 (The first two inlets for bf-param operate similar to the first two inlets for [array set] in Pd.)
 
-###### Outlets:
+### Outlets:
 1. The parameter value of the most recent change to the bf-param (whether that change came from the inlets, the UI, or via the collaboration window.)
 2. A list with the parameter value of the most recent change, and the index of the parameter that was changed.
 3. The parameter value for the index that was sent to *Inlet 3*.
@@ -62,31 +62,31 @@ When you open the collab window (by clicking on the 'collab' toggle in your bf-i
 Each bf-output in your bf-instrument will appear on the left of the column for your instrument. You will also see three default outputs which are computed from your instrument's audio: one detects onsets in your instrument's audio, one outputs a pitch estimate, and one which outputs a loudness estimate. 
 
 
-###### Arguments:
+### Arguments:
 1. The name of your instrument, e.g. "myDrumMachine" 
 2. The name of your output, e.g. "triggers"
 3. The dimensionality of the parameter, e.g. "4"
 4. The type of the parameter, e.g. "bang"
 5. The order you want the outlet to appear in the Collab Window (after the three default outputs).
 
-###### Inlets:
+### Inlets:
 The inlets are similar to the first two inlets of bf-param
 1. Sets the value of the output. If the output is a multiple, then *Inlet 1* sets the parameter at the index last received on *Inlet 2*.
 2. Sets the index of the output which will be changed by sending values to *Inlet 1*.
 
-###### Outlets:
+### Outlets:
 1. The bf-output object in your patch does not have any outlets.
 
 
 ## bf-clock
 A bf-clock can be used for generating and sharing tempi and rhythmic events. You can use a bf-clock to create rhythmic events in your instrument, and you can synchronise instruments by sharing tempi between instruments via the collab window. 
 
-###### Arguments:
+### Arguments:
 1. The name of your instrument, e.g. "myDrumMachine" 
 2. The name of your bf-clock, e.g. "leadClock"
 3. The order you want the clock to appear (amongst the other bf-params) in the Collab Window.
 
-###### Inlets:
+### Inlets:
 1. A '1' or '0' turns the clock on and off
 2. A number sets the tempo in beats-per-minute (BPM), e.g. "120"
 3. A number sets the meter, i.e. the number of beats in a measure, e.g. "4" for 4/4  time.
@@ -94,7 +94,7 @@ A bf-clock can be used for generating and sharing tempi and rhythmic events. You
 5. A number sets the second beat subdivision. E.g. "3" will create eighth note triplets (or quaver triplets).
 6. This inlet can take a variety of messages for controlling a bf-clock. (See bf-clock-help.pd for details.)
 
-###### Outlets:
+### Outlets:
 1. Outputs a bang on each downbeat. E.g. if meter is set to '4', the downbeat will occur every four beats. You can think of this as the first beat in a measure.
 2. Outputs a bang on each beat. E.g. if BPM is set to '120', then there will be two beats per second. 
 3. Outputs a bang on each subdivision1. E.g. if sub1 is "2", then the bangs can be thought of as eighth notes (quavers).
-- 
GitLab