diff --git a/README.md b/README.md index eb169c49059195407eb5e5c4f851b2adf48bf70c..9ea440df86b47d680f2c95c6ef1c397f80610f5b 100644 --- a/README.md +++ b/README.md @@ -9,9 +9,11 @@ Bf-pd is a library built in PureData (Pd) which enables communication and cooper The design of bf-pd is based on the BOEUF conceptual framework which consists of a classification of modes of collaboration used in collective music performance, and a set of components which affords them. More details on the BOEUF conceptual framework can be found [on this page](doc/boeuf.md). +For more information on the BOEUF project, please visit [https://bf-collab.net/](https://bf-collab.net/). + ## Installing bf-pd -- Download and install Pure Data (>=0.51) for your operating system from https://puredata.info/downloads/pure-data +- Download and install Pure Data (>=0.51) for your operating system from [https://puredata.info/downloads/pure-data](https://puredata.info/downloads/pure-data) - Install the **mrpeach** library using Deken (PD -> Help -> Find Externals) - Install **bf-pd** using Deken @@ -96,6 +98,8 @@ Documentation for each of the user objects in bf-pd can be found in [objects.md] The *BOEUF conceptual framework* describes the *modes of collaboration* used in musical collaboration and describes a set of *components* for realizing these modes in a software framework. Bf-pd is based on this framework. More info can be found in [boeuf.md](doc/boeuf.md). +For more information on the BOEUF project, please visit [https://bf-collab.net/](https://bf-collab.net/). + ## Authors * Luke Dahl, University of Virginia diff --git a/bf-ask-help.pd b/bf-ask-help.pd deleted file mode 100644 index 96807f3afc109e7c64d88a3507a0a4621e5fe117..0000000000000000000000000000000000000000 Binary files a/bf-ask-help.pd and /dev/null differ diff --git a/bf-ask.pd b/bf-ask.pd deleted file mode 100644 index 303bfd906bc9df2a8ff5cfc3cb3c8ef31f1908bd..0000000000000000000000000000000000000000 Binary files a/bf-ask.pd and /dev/null differ diff --git a/bf-instrument-help.pd b/bf-instrument-help.pd index cd43641b6d01a151724c4d35d30792ce6e2df6c7..fe5a1d8aeff4374d6c62afb5a40de9ae7cd64536 100644 Binary files a/bf-instrument-help.pd and b/bf-instrument-help.pd differ diff --git a/bf-module.pd b/bf-module.pd deleted file mode 100644 index 89d8f76553302b8ba00f18f19349d591c97ce4f7..0000000000000000000000000000000000000000 Binary files a/bf-module.pd and /dev/null differ diff --git a/bf-output-help.pd b/bf-output-help.pd new file mode 100644 index 0000000000000000000000000000000000000000..10901ee60a01521865dcd482bdeb82c35979bb13 Binary files /dev/null and b/bf-output-help.pd differ diff --git a/bf-session-help.pd b/bf-session-help.pd deleted file mode 100644 index a8a0a822b0f94bfd49c92c5dc30c5fb24217e798..0000000000000000000000000000000000000000 Binary files a/bf-session-help.pd and /dev/null differ diff --git a/bf-session-web.pd b/bf-session-web.pd deleted file mode 100644 index b131e929fb65dab8da5538f6a26bb9800085c43a..0000000000000000000000000000000000000000 Binary files a/bf-session-web.pd and /dev/null differ diff --git a/bf-session.pd b/bf-session.pd deleted file mode 100644 index f4a26b9d7b3c17b5e679db6e055f3588c8ae723b..0000000000000000000000000000000000000000 Binary files a/bf-session.pd and /dev/null differ diff --git a/bf-watch-help.pd b/bf-watch-help.pd deleted file mode 100644 index 736b54d7e1e4b2915646c0912befc24298bb494e..0000000000000000000000000000000000000000 Binary files a/bf-watch-help.pd and /dev/null differ diff --git a/bf-watch.pd b/bf-watch.pd deleted file mode 100644 index 5c118079cad3dafd102ab58548609e6d67a194c3..0000000000000000000000000000000000000000 Binary files a/bf-watch.pd and /dev/null differ diff --git a/boeuf-help.pd b/boeuf-help.pd index c105de70338ab94c0d3cf3e094a6f70014a8e679..2a0fb3865ad39065da2b2f11268e477b54ad951a 100644 Binary files a/boeuf-help.pd and b/boeuf-help.pd differ diff --git a/doc/boeuf.html b/doc/boeuf.html index e27097568dd35b1edcf32ba16bcff967dc045ce6..ad981b3addbcdd0fa0b328b34d0206a048a0ab41 100644 --- a/doc/boeuf.html +++ b/doc/boeuf.html @@ -44,16 +44,54 @@ <h3 id="organisation-modes">Organisation Modes</h3> <p><em>Organisation</em> describes the relationships between musicians. Organisation does not directly affect the sound production, but it impacts how the communication and cooperation modes operate.</p> <ul> -<li><p><strong>Nomination: </strong> Nomination is that act of de fining the roles of musicians within the group. For example one musician might be the conductor, another might be a soloist.</p></li> +<li><p><strong>Nomination:</strong> Nomination is that act of defining the roles of musicians within the group. For example one musician might be the conductor, another might be a soloist.</p></li> <li><p><strong>Grouping</strong> The act of grouping de fines a hierarchy of groups of instruments. For example a musician might be in the group “viola players†as well as in the group “string section.â€</p></li> <li><p><strong>Selection</strong> Selection is the act of choosing a group or instrument for cooperation or communication. For example, a conductor might gesture to the wind section (thereby selecting them) before cueing their entrance (indication.)</p></li> </ul> -<h2 id="the-boeuf-components">The Boeuf components</h2> -<p>[TODO]</p> -<h2 id="navigate">Navigate</h2> +<h2 id="the-boeuf-components">The Boeuf Components</h2> +<p>The Boeuf Components are intended as a generic set of components that would be needed to implement the Cooperation and Communication modes described above. Most, but not all, of these are implemented as objects in the bf-pd library. And there are some differences between these conceptual components and their actual implementation in bf-pd.</p> <ul> -<li>The BOEUF project: <a href="https://bf-collab.net/bf/"></a></li> -<li>The Bf-Pd library: <a href="https://gitlab.cristal.univ-lille.fr/boeuf/bf-pd/blob/master/README.html"></a></li> +<li><strong>Session:</strong> A session represents an instance of a group interaction. A session contains a set of instruments and the network of possible interactions between instruments.</li> +</ul> +<p>In <em>bf-pd</em> the bf-session object is used to join a session.</p> +<ul> +<li><strong>Instrument:</strong> An instrument represents a bounded set of music-generating processes (i.e. modules) along with a user interface. In instrument may contain parameters, outputs, meters and it can receive and send messages. We presume that each musician in the ensemble is in control of at least one instrument. Thus, in our modeling an instrument often acts as a proxy for the musician.</li> +</ul> +<p>In <em>bf-pd</em> the bf-instrument object is used to instantiate an instrument.</p> +<ul> +<li><strong>Parameter:</strong> A parameter is an attribute of an instrument or module that influences its musical production. Parameters can be of various types such as MIDI events, float or integer values, input audio streams, and so on. Parameters can be:</li> +<li><em>Set:</em> where the parameter is set to a new value.</li> +<li><em>Retrieved:</em> where the current value of the parameter is returned.</li> +<li><em>Watched:</em> where the value of the parameter is sent every time the parameter value changes (until the parameter is no longer being watched.)</li> +<li><em>Grabbed:</em> where the parameter can only be set by the instrument that has grabbed it.</li> +<li><em>Indicated:</em> where a new value may be proposed for the parameter, but the value is not set.</li> +</ul> +<p>These actions are always accessible to the instrument that owns the parameter, but permission may be needed for other instruments to access another instrument’s parameter. Concurrent access can be managed in different ways. For example, by grabbing a parameter so that only one instrument can access it at a time.</p> +<p>In <em>bf-pd</em> the bf-param object is used to instantiate a parameter. bf-param enables most of these actions, however grabbing is not currently possible.</p> +<ul> +<li><em>Output:</em> An output is a musical attribute that is produced by a module or instrument. Outputs can be of the same types as parameters. Outputs can be retrieved and watched by another instrument.</li> +</ul> +<p>In <em>bf-pd</em> the bf-output object can be used.</p> +<ul> +<li><em>Meter:</em> A meter is a component of an instrument that is not used in the actual sound production, but rather gives an indication on the activity of the instrument, which can help enable <em>awareness</em>. For example a meter might display the spectrum or loudness of an instrument’s audio output.</li> +</ul> +<p>In <em>bf-pd</em> each instrument has an activity monitor that displays a simplified spectrum of the instrument’s output. In the collab window a musician can see this meter for all other instruments in the session. (Note: In bf-pd’s <em>collab window</em>, the view of other instruments’ parameters can effectively function as meters.)</p> +<ul> +<li><strong>Group:</strong> A group is a set of instruments or other groups. Instantiating a group is an act of <em>grouping</em>. Parameters common to all instruments in a group can be grabbed and set simultaneously. Similarly, messages sent to a group should be sent to all members. For example in a poly-instrument orchestra, a group might be all the musicians with the same instrument. A default group of all instruments is always defined, thereby giving access to parameters common to all instruments in the session e.g. tempo or scale.</li> +</ul> +<p><em>Note:</em> Groups are not explicitly enabled in the current version of the bf-pd library.</p> +<ul> +<li><strong>Module:</strong> A module is a component that produces musical data, of audio or control type. It may be composed of several parameters and outputs. Modules have a type, where each instance of the type has the same predefined parameters. This allows modules of the same type to easily exchange parameter settings. For example, a module of type <em>LowPassFilter</em> might have Cutoff Frequency and Q as parameters, whereas a module of type *MidiPattern** would hold an array of MIDI events.</li> +</ul> +<p><em>Note:</em> Modules are not explicitly implemented in the current version of the bf-pd library.</p> +<ul> +<li><em>Message:</em> A message can be some text, image, or video sent from one instrument to another instrument or group. Messages can be generic (e.g. Start, Stop, Fade Out), defined per session, or dynamically created.</li> +</ul> +<p><em>Note:</em> While many messages are sent between objects in bf-pd, bf-pd does not currently enable arbitrary or user-defined messages.</p> +<p>For more information :</p> +<ul> +<li><a href="https://bf-collab.net/bf/">The BOEUF project</a></li> +<li><a href="https://hal.archives-ouvertes.fr/hal-01380373/file/Boeuf.pdf">Paper presenting the framework</a></li> </ul> </main> </body> diff --git a/doc/boeuf.md b/doc/boeuf.md index af29ddfed3f699e65f99f5e22fd43730681ec672..170dee959c9524d1c0d95868786fd16c6794f712 100644 --- a/doc/boeuf.md +++ b/doc/boeuf.md @@ -79,8 +79,7 @@ In *bf-pd* each instrument has an activity monitor that displays a simplified sp *Note:* While many messages are sent between objects in bf-pd, bf-pd does not currently enable arbitrary or user-defined messages. -[TODO: add a link to the BOEUF framework paper!] +For more information : -## Navigate -* The BOEUF project: [](https://bf-collab.net/bf/) -* The Bf-Pd library: [](https://gitlab.cristal.univ-lille.fr/boeuf/bf-pd/blob/master/README.md) \ No newline at end of file +* [The BOEUF project](https://bf-collab.net/bf/) +* [Paper presenting the framework](https://hal.archives-ouvertes.fr/hal-01380373/file/Boeuf.pdf) diff --git a/doc/index.html b/doc/index.html index 3bc590bee1b298cdbc8b3464d344db10d4000bf2..e7642e73a6b11325d6e93cd7d251cf2c1651d711 100644 --- a/doc/index.html +++ b/doc/index.html @@ -27,9 +27,10 @@ <p>Digital instruments allow us to do things that were not possible with purely acoustic instruments. For example musicians can share data between instruments in real-time, in effect creating distributed multi-musician super-instruments. Musicians such as The Hub have been doing this since at least the 1970s. Contemporary digital musicians often write their own software instruments to re-create these functionalities.</p> <p>Bf-pd is a library built in PureData (Pd) which enables communication and cooperation between digital instruments. Bf-pd can be integrated into any instrument built in Pd. It provides a <em>collaboration window</em> from which musicians can view each others’ activity and share control of instrument parameters and other musical data.</p> <p>The design of bf-pd is based on the BOEUF conceptual framework which consists of a classification of modes of collaboration used in collective music performance, and a set of components which affords them. More details on the BOEUF conceptual framework can be found <a href="boeuf.html">on this page</a>.</p> +<p>For more information on the BOEUF project, please visit <a href="https://bf-collab.net/">https://bf-collab.net/</a>.</p> <h2 id="installing-bf-pd">Installing bf-pd</h2> <ul> -<li>Download and install Pure Data (>=0.51) for your operating system from https://puredata.info/downloads/pure-data</li> +<li>Download and install Pure Data (>=0.51) for your operating system from <a href="https://puredata.info/downloads/pure-data">https://puredata.info/downloads/pure-data</a></li> <li>Install the <strong>mrpeach</strong> library using Deken (PD -> Help -> Find Externals)</li> <li>Install <strong>bf-pd</strong> using Deken</li> </ul> @@ -95,6 +96,7 @@ <h2 id="more-resources">More resources</h2> <p>Documentation for each of the user objects in bf-pd can be found in <a href="objects.html">objects.md</a> and on help patches directly in PureData (right-click an object -> Help)</p> <p>The <em>BOEUF conceptual framework</em> describes the <em>modes of collaboration</em> used in musical collaboration and describes a set of <em>components</em> for realizing these modes in a software framework. Bf-pd is based on this framework. More info can be found in <a href="boeuf.html">boeuf.md</a>.</p> +<p>For more information on the BOEUF project, please visit <a href="https://bf-collab.net/">https://bf-collab.net/</a>.</p> <h2 id="authors">Authors</h2> <ul> <li>Luke Dahl, University of Virginia</li> diff --git a/doc/objects.html b/doc/objects.html index c811d0d8b503d2b3fb1fefcbb502aa2119dd1375..73afab84fde9111976de8a85bc756d2f90cc8365 100644 --- a/doc/objects.html +++ b/doc/objects.html @@ -22,42 +22,35 @@ <li><a href="objects.html">Objects</a></li> </nav> <main> -<p>Bf-pd is a library of pd objects for enabling real-time collaboration. This page describes each of the objects in bf-pd, their arguments, inlets and outlets.</p> -<h2 id="bf-session">bf-session</h2> -<p>A bf-session represents a group of musicians (as represented by their bf-instruments) making music together. Within the bf-pd system a bf-session works “behind the scenes†to coordinate the data exchanged between bf-instruments.</p> -<p>To participate in a bf-session there must be at least one instance of bf-session instantiated somewhere. A bf-session has a name, e.g. “technoJam1â€, and this session would be instantiated as [bf-session technoJam1].</p> -<p>There can be more than one bf-session object with the same name within the patches running in Pd. So you can add the same bf-session to each bf-instrument. (However if you instantiate two different bf-sessions within pd, the second one will not work.)</p> -<h6 id="arguments">Arguments:</h6> -<ol type="1"> -<li>The name of the session.</li> -</ol> -<h6 id="outlets">Outlets:</h6> -<ol type="1"> -<li>Outlet 1 sends all the session messages which are used “behind the scenes†by the bf-pd objects.</li> -</ol> +<p>Bf-pd is a library of pd objects for enabling real-time collaboration. This page describes each of the objects in bf-pd, their arguments, inlets and outlets. (Note, there is also a help file for each of the bf-pd objects</p> <h2 id="bf-instrument">bf-instrument</h2> <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.</p> -<h6 id="arguments-1">Arguments:</h6> +<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> <ol type="1"> <li>The name of the instrument.</li> </ol> <h6 id="inlets">Inlets:</h6> <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 : +<ul> +<li>the session name [session-name mySession(</li> +</ul></li> </ol> <h2 id="bf-param">bf-param</h2> -<p>A bf-param creates a user parameter within the bf-pd system. A bf-param can be controlled by the user of the bf-instrument it belongs to, and the bf-param will also be accessible to other instruments within the bf-session via the collaboration window, if the owner of the bf-instrument grants access.</p> +<p>A bf-param creates a user parameter within the bf-pd system. A bf-param can be controlled by the user of the bf-instrument it belongs to, and the bf-param will also be accessible to other instruments within the bf-session via the collaboration window (if the owner of the bf-instrument has granted access.)</p> <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-2">Arguments:</h6> +<h6 id="arguments-1">Arguments:</h6> <ol type="1"> <li>The name of the instrument, e.g. “myDrumMachineâ€.</li> <li>The name of the parameter, e.g. “kickOnOffâ€</li> <li>The dimensionality of the parameter, e.g. “8â€</li> <li>The type of the parameter, e.g. “boolâ€</li> +<li>The order you want the parameter to appear in the Collab Window.</li> </ol> <p>So a bf-param with 8 drum machine note triggers would be: <code>[bf-param myDrumMachine kickOnOff 8 bool]</code> and creates this object within your patch:</p> <figure> @@ -70,35 +63,62 @@ <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-1">Outlets:</h6> +<h6 id="outlets">Outlets:</h6> <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 of the parameter value of the most recent change, and the index of the parameter that was changed.</li> +<li>A list with the parameter value of the most recent change, and the index of the parameter that was changed.</li> <li>The parameter value for the index that was sent to <em>Inlet 3</em>.</li> </ol> <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>Each bf-output in your bf-instrument will appear [TODO continue]</p> -<p>is a musical attribute that is produced by a module or instrument. They can have the same types as parameters. Outputs can be retrieved and watched by other instruments, and function as a means for both awareness and exchange.</p> -<h6 id="arguments-3">Arguments:</h6> +<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> <ol type="1"> -<li>arg1</li> +<li>The name of your instrument, e.g. “myDrumMachineâ€</li> +<li>The name of your output, e.g. “triggersâ€</li> +<li>The dimensionality of the parameter, e.g. “4â€</li> +<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> +<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> <ol type="1"> -<li>blah</li> +<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> +<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> +<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> +<li>A number sets the meter, i.e. the number of beats in a measure, e.g. “4†for 4/4 time.</li> +<li>A number sets the first beat subdivision. E.g. “2†will create eighth notes (or quavers).</li> +<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> <ol type="1"> -<li>blah</li> +<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> +<li>Outputs a bang on each subdivision1. E.g. if sub1 is “2â€, then the bangs can be thought of as eighth notes (quavers).</li> +<li>Outputs a bang on each subdivision1. E.g. if sub2 is “3â€, then the bangs can be thought of as eighth note triplets (quavertriplets).</li> +<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-3">Inlets:</h6> +<h6 id="inlets-4">Inlets:</h6> <ol type="1"> <li>blah</li> </ol> @@ -112,7 +132,7 @@ <ol type="1"> <li>arg1</li> </ol> -<h6 id="inlets-4">Inlets:</h6> +<h6 id="inlets-5">Inlets:</h6> <ol type="1"> <li>blah</li> </ol> diff --git a/doc/objects.md b/doc/objects.md index 99dd13e82da2d83920da290be69711667be865f8..4ba2be35762998a31ad5f097b7ec8d907c48fbeb 100644 --- a/doc/objects.md +++ b/doc/objects.md @@ -1,19 +1,5 @@ Bf-pd is a library of pd objects for enabling real-time collaboration. This page describes each of the objects in bf-pd, their arguments, inlets and outlets. (Note, there is also a help file for each of the bf-pd objects -## bf-session -A bf-session represents a group of musicians (as represented by their bf-instruments) making music together. Within the bf-pd system a bf-session works "behind the scenes" to coordinate the data exchanged between bf-instruments. - -To participate in a bf-session there must be at least one instance of bf-session instantiated somewhere. A bf-session has a name, e.g. "technoJam1", and this session would be instantiated as [bf-session technoJam1]. - -There can be more than one bf-session object with the same name within the patches running in Pd. So you can add the same bf-session to each bf-instrument. (However if you instantiate two different bf-sessions within pd, the second one will not work.) - -###### Arguments: -1. The name of the session. - -###### Outlets: -1. Outlet 1 sends all the session messages which are used "behind the scenes" by the bf-pd objects. - - ## bf-instrument 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]. @@ -26,6 +12,8 @@ The *collaboration window* can be opened with the toggle in the bf-instrument ob ###### 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( ## bf-param