diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000000000000000000000000000000000000..a5999df5eac54baaadc5d48f3f76c3c7a80483b3
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,339 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc., <http://fsf.org/>
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ bf-pd
+ Copyright (C) 2019 BOEUF
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License along
+ with this program; if not, write to the Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ {signature of Ty Coon}, 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.
diff --git a/README.md b/README.md
index e70086f9334acbf7e6b1f05e79af92402ab272b6..eb169c49059195407eb5e5c4f851b2adf48bf70c 100644
--- a/README.md
+++ b/README.md
@@ -1,19 +1,103 @@
-# bf-pd
+# bf-pd : a PureData external for building Digital Orchestras
-## Description
+## Introduction: What is bf-pd and why do you need it?
-bf-pd is an implementation for PureData of the BOEUF framework, which enables advanced collaboration modes in spontaneous digital orchestras.
+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.
-Help and tutorials can be found in the [documentation folder.](doc/README.md)
+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 *collaboration window* from which musicians can view each others’ activity and share control of instrument parameters and other musical data.
-## Requires the following puredata libraries (Help->Find Externals)
+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).
-* mrpeach
+## Installing bf-pd
+
+- Download and install Pure Data (>=0.51) for your operating system from https://puredata.info/downloads/pure-data
+- Install the **mrpeach** library using Deken (PD -> Help -> Find Externals)
+- Install **bf-pd** using Deken
+
+## Getting started: Building your instrument
+
+
+
+Starting from an existing instrument made in PureData :
+
+1. Create a declare object with -path bf-pd
+2. Create a bf-instrument object with your instrument name as argument
+3. Connect the sound output of your instrument to its inlet
+4. Create a bf-param object for each control you want to share with the others and insert it into your instrument
+5. Create a bf-session object with the name of the session you want to connect to
+
+### Parameters and outputs
+
+**Parameters** correspond to controls you have over your instrument and that you want to share with others.
+
+
+
+
+**Outputs** have the same properties but correspond to musical content produced by your instruments (notes, onsets, envelopes ...). They can be used to control others parameters.
+Three default outputs are automatically created by bf-pd and extracted from the audio you send to bf-instrument : pitch, onsets, loudness.
+
+
+
+
+Parameters and outputs have the same **arguments** :
+
+1. instrument name
+2. parameter / output namenumberOfValues valuesType parameterIndex ]
+3. number of values
+4. type of values : cont (0 to 1), midi (0 to 127), bool (0 or 1), bang
+5. index : position in the collaboration window
+
+## Performance: Making music together using bf-pd
+
+### The collaboration window
+
+The collaboration window is a collaboration interface that comes with bf-pd and provides a way to connect your instrument with other instruments in the session.
+
+To open the collaboration window, simply check the *collab* toggle in the bf-instrument object.
+
+The leftmost green column shows your instrument with its outputs and parameters. The grey columns show the other instruments in the session with their respective activity, outputs and parameters.
+
+
+
+### Sharing / granting access to your parameters
+
+By default, all your parameters are in the *granted* mode, which means that all the other musicians can change your parameter values. You can of course change this by clicking the red *grant* toggle for each parameter, or the *grant all* toggle at the top of your column.
+When your parameter is not granted, values *asked* by others are only displayed on the gray widgets. You can accept their *ask* by using the *1x* bang.
+
+
+
+### Using others parameters and outputs to change your parameters
+
+A *watch* bus selector is placed below each parameter and output of the other instruments. By choosing a bus other than 0, the values are sent to the corresponding bus and can be sent to your parameters connected to the same bus using the *watching* selector.
+
+
+
+### Controlling others parameters with your parameters and outputs
+
+Symmetrically, you can control others parameters by choosing a non-zero bus on the *ask* selector and the same *asking* bus below one of your outputs or parameters. This requires however that the parameter that you want to controlled is *granted* (i.e. that the green *granted* toggle is checked).
+
+
+
+
+### Directly asking / controlling others parameters
+
+You can also ask another instrument's parameter to be set to a specific value by interacting with the white sliders/toggles/bangs. It the access is granted, the value will be directly set.
+
+
+
+## Demo Video
+
+<a href="https://pod.univ-lille.fr/video/19614-bf-pd-collaboration-window/"><img src="doc/img/video.png" height="300px"/><br/>Video demoing the collab window for bf-pd</a>.
+
+## More resources
+
+Documentation for each of the user objects in bf-pd can be found in [objects.md](doc/objects.md) and on help patches directly in PureData (right-click an object -> Help)
+
+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).
## Authors
* Luke Dahl, University of Virginia
* Florent Berthaut, University of Lille
-
-
diff --git a/doc/README.md b/doc/README.md
index 95fd395ba8e2526292b08a7d871802b00d522691..12918a28c46c9f542367df571f5097462ed8fb50 100644
--- a/doc/README.md
+++ b/doc/README.md
@@ -1,45 +1,5 @@
+# bf-pd documentation
-# Introduction: What is bf-pd and why do you need it?
-
-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.
-
-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 *collaboration window* from which musicians can view each others’ activity and share control of instrument parameters and other musical data.
-
-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 wiki page](boeuf.md).
-
-# Installing bf-pd
-
-- Download and install Pure Data for your operating system from https://puredata.info/downloads/pure-data
-- Install the **mrpeach** library using Deken (PD -> Help -> Find Externals)
-- Install **bf-pd** using Deken
-
-# Getting started: Building your instrument
-
-
-
-- Create a declare object with -path bf-pd
-- Create a bf-instrument object with your instrument name as argument
-- Connect the sound output of your instrument to its inlet
-- Create a bf-param object for each control you want to share with the others and insert it into your instrument
-- Create a bf-session object with the name of the session you want to connect to
-
-# Performance: Making music together using bf-pd
-### The collaboration window
-
-### Sharing parameters
-
-### Connecting parameters using ask and watch
-
-
-### Video example
-
-<a href="https://vimeo.com/214380530">Video showing a simple session</a>
-
-
-# More resources
-
-Documentation for each of the user objects in bf-pd can be found in [objects.md](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](boeuf.md).
+* Explanations on the BOEUF framework for collaboration modes in orchestras [on this page](boeuf.md).
+* List of bf-pd [objects](objects.md)
diff --git a/doc/bf-pd_start.gif b/doc/bf-pd_start.gif
deleted file mode 100644
index 4890a66df6e01238f591293328acc11ea42a2b7b..0000000000000000000000000000000000000000
Binary files a/doc/bf-pd_start.gif and /dev/null differ
diff --git a/doc/boeuf.html b/doc/boeuf.html
new file mode 100644
index 0000000000000000000000000000000000000000..e27097568dd35b1edcf32ba16bcff967dc045ce6
--- /dev/null
+++ b/doc/boeuf.html
@@ -0,0 +1,60 @@
+<!DOCTYPE html>
+<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
+<head>
+ <meta charset="utf-8" />
+ <meta name="generator" content="pandoc" />
+ <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
+ <title>bf-pd : the BOEUF framework</title>
+ <style>
+ code{white-space: pre-wrap;}
+ span.smallcaps{font-variant: small-caps;}
+ span.underline{text-decoration: underline;}
+ div.column{display: inline-block; vertical-align: top; width: 50%;}
+ div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+ ul.task-list{list-style: none;}
+ </style>
+ <link rel="stylesheet" href="img/style.css" />
+</head>
+<body>
+<nav>
+ <li><a href="index.html">Home</a></li>
+ <li><a href="boeuf.html">BOEUF</a></li>
+ <li><a href="objects.html">Objects</a></li>
+</nav>
+<main>
+<h1 id="the-boeuf-conceptual-framework">The BOEUF conceptual framework</h1>
+<p>BOEUF is a conceptual framework for modeling and building orchestras of digital musical instruments. It consists of a classification of <em>modes of collaboration</em>, and a set of <em>components</em> which can be used to enable these modes in digital instruments. We developed this classification after conducting interviews with digital musicians who work in ensembles, as well as literature review of work on digital ensembles and collaborative instruments. The word “boeuf” is french slang for a jam session.</p>
+<h2 id="modes-of-collaboration">Modes of Collaboration</h2>
+<p>The <em>modes of collaboration</em> are a categorization which is intended to describe all the ways that musicians collaborate and communicate during performance. This includes interactions which are <em>mediated</em> (i.e. take place through some technology) as well as <em>unmediated</em> interactions (which can occur through being in the same space together.)</p>
+<p>We propose that there are three modes of collaboration: <em>Cooperation</em>, <em>Communication</em>, and <em>Organisation</em></p>
+<h3 id="cooperation-modes">Cooperation Modes</h3>
+<p><em>Cooperation</em> describes the ways that musicians coordinate their actions with respect to their instruments. This cooperation can be:</p>
+<ul>
+<li><p><strong>Independent:</strong> Each musician controls their own instrument. For example, when two musicians begin to play their instruments at the same time this is <em>independent cooperation</em>. They are cooperating because they coordinated their musical gestures, but they act only on their own instrument.</p></li>
+<li><p><strong>Complementary:</strong> Multiple musicians can affect different aspects of the same musical process. For example, when one musician adds effects to a sound generated by another musician.</p></li>
+<li><p><strong>Concurrent:</strong> Multiple musicians can control the same aspect of the same musical musical process. For example, when two musicians can both control some parameter (e.g. filter cutoff frequency) on the same instrument.</p></li>
+</ul>
+<h3 id="communication-modes">Communication Modes</h3>
+<p><em>Communication</em> describes how musicians exchange information which may then influence their actions.</p>
+<ul>
+<li><p><strong>Awareness:</strong> Awareness describes all non-intentional communication. For example being able to see the movements of other musicians.</p></li>
+<li><p><strong>Indication:</strong> Indications are intentional communicative acts. For example, cueing an entrance. Deliberate nods and glances between musicians may be indications.</p></li>
+<li><p><strong>Exchanges:</strong> Exchange is the transfer of musical data between musicians. For example, in a digital ensemble on musician might send a sequence of notes to another’s instrument. Or in a jazz ensemble a soloist might use a motif from the previous soloist.</p></li>
+</ul>
+<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>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>
+<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>
+</ul>
+</main>
+</body>
+</html>
diff --git a/doc/boeuf.md b/doc/boeuf.md
index 4cc7eaaddb5c4b00c762e9cc19cde106659b8048..14469cf8b666e910237ed95cd897ca432a626817 100644
--- a/doc/boeuf.md
+++ b/doc/boeuf.md
@@ -37,4 +37,8 @@ We propose that there are three modes of collaboration: *Cooperation*, *Communic
* **Selection** 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.)
## The Boeuf components
-[TODO]
\ No newline at end of file
+[TODO]
+
+## 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
diff --git a/doc/build.sh b/doc/build.sh
new file mode 100755
index 0000000000000000000000000000000000000000..2641f2dd8233f3b828aa4b3ddc0857dabc8a9f20
--- /dev/null
+++ b/doc/build.sh
@@ -0,0 +1,3 @@
+pandoc ../README.md -o index.html -s --lua-filter=img/md_to_html.lua -c img/style.css --template=img/template.html --metadata title="bf-pd : index"
+pandoc boeuf.md -o boeuf.html -s --lua-filter=img/md_to_html.lua -c img/style.css --template=img/template.html --metadata title="bf-pd : the BOEUF framework"
+pandoc objects.md -o objects.html -s --lua-filter=img/md_to_html.lua -c img/style.css --template=img/template.html --metadata title="bf-pd : objects"
diff --git a/doc/img/asking.gif b/doc/img/asking.gif
new file mode 100644
index 0000000000000000000000000000000000000000..90f3c7da2a032af62465380e5d1786564a8dcb23
Binary files /dev/null and b/doc/img/asking.gif differ
diff --git a/doc/img/bf-output.gif b/doc/img/bf-output.gif
new file mode 100644
index 0000000000000000000000000000000000000000..14d7ec9430906b24a00e3f576a9cf068b729001c
Binary files /dev/null and b/doc/img/bf-output.gif differ
diff --git a/doc/img/bf-param.gif b/doc/img/bf-param.gif
new file mode 100644
index 0000000000000000000000000000000000000000..f946c1064c5ccf023891f4f131705746b0dbe442
Binary files /dev/null and b/doc/img/bf-param.gif differ
diff --git a/doc/img/bf-param_example.png b/doc/img/bf-param_example.png
new file mode 100644
index 0000000000000000000000000000000000000000..c6c3a53ab5f0d65f87b2fed69116a8aa2e7a2b6a
Binary files /dev/null and b/doc/img/bf-param_example.png differ
diff --git a/doc/img/collabwin.png b/doc/img/collabwin.png
new file mode 100644
index 0000000000000000000000000000000000000000..59615db35d7877b8ca47fc56145dbda7420dfc87
Binary files /dev/null and b/doc/img/collabwin.png differ
diff --git a/doc/img/direct_asking.gif b/doc/img/direct_asking.gif
new file mode 100644
index 0000000000000000000000000000000000000000..5f737c3ce2f21c53d29041ec8a0d2c7ea852bf55
Binary files /dev/null and b/doc/img/direct_asking.gif differ
diff --git a/doc/img/md_to_html.lua b/doc/img/md_to_html.lua
new file mode 100644
index 0000000000000000000000000000000000000000..f68f9364e6924f66fedd4cbae995f011cdf1f365
--- /dev/null
+++ b/doc/img/md_to_html.lua
@@ -0,0 +1,17 @@
+function Link(el)
+ el.target = string.gsub(el.target, "%.md", ".html")
+ el.target = string.gsub(el.target, "doc/", "")
+ return el
+end
+
+function Image(el)
+ el.src = string.gsub(el.src, "doc/", "")
+ return el
+end
+
+function RawInline (raw)
+ if raw.format == 'html' then
+ return pandoc.RawInline('html', string.gsub(raw.text, "doc/img", "img"))
+ end
+end
+
diff --git a/doc/img/param.gif b/doc/img/param.gif
new file mode 100644
index 0000000000000000000000000000000000000000..ab9b18078eee2130346ebc583f97b0ad726e1b3f
Binary files /dev/null and b/doc/img/param.gif differ
diff --git a/doc/img/sharing.gif b/doc/img/sharing.gif
new file mode 100644
index 0000000000000000000000000000000000000000..58c319dfc8dd3db20170cfb116f6ccd2d1016916
Binary files /dev/null and b/doc/img/sharing.gif differ
diff --git a/doc/img/start.gif b/doc/img/start.gif
index e96a5db8a01ec820e188e5fa3e776c202de77ac5..b1d04927d70f78480e5192b66adb57eaed6a8db4 100644
Binary files a/doc/img/start.gif and b/doc/img/start.gif differ
diff --git a/doc/img/style.css b/doc/img/style.css
new file mode 100644
index 0000000000000000000000000000000000000000..1df084ea8fbdf8790b39c02a7c0530e9f0c54827
--- /dev/null
+++ b/doc/img/style.css
@@ -0,0 +1,68 @@
+body {
+ display:grid;
+ grid:"nav main" auto
+ / 100px 1fr;
+ grid-gap:10px;
+ padding:0px 5% 50px 5%;
+ font-family:sans-serif;
+}
+
+main {
+ grid-area:main;
+ background-color:#DDD;
+ padding:0px 5px;
+}
+
+nav {
+ grid-area:nav;
+ font-size:1.2em;
+ position:sticky;
+ top:5px;
+ background-color:#333;
+ align-self:start;
+}
+
+nav li {
+ list-style-type:none;
+ width:100%;
+}
+
+nav a {
+ color:white;
+ background-color:#333;
+ width:100%;
+ font-weight:bold;
+}
+
+nav a:hover {
+ color:#333;
+ background-color:white;
+}
+
+a {
+ color:#333;
+}
+
+a:hover {
+ color:white;
+ background-color:#333;
+}
+
+h1 {
+ margin-top:0px;
+}
+
+h1, h2 {
+ color:white;
+ background-color: #333;
+}
+
+img {
+ max-width:100%;
+ border:2px black solid;
+}
+
+figcaption {
+ display:none;
+}
+
diff --git a/doc/img/template.html b/doc/img/template.html
new file mode 100644
index 0000000000000000000000000000000000000000..36142fc7d40b6d6dd4999ca2b819e07ed64afe00
--- /dev/null
+++ b/doc/img/template.html
@@ -0,0 +1,46 @@
+<!DOCTYPE html>
+<html xmlns="http://www.w3.org/1999/xhtml" lang="$lang$" xml:lang="$lang$"$if(dir)$ dir="$dir$"$endif$>
+<head>
+ <meta charset="utf-8" />
+ <meta name="generator" content="pandoc" />
+ <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
+$for(author-meta)$
+ <meta name="author" content="$author-meta$" />
+$endfor$
+$if(date-meta)$
+ <meta name="dcterms.date" content="$date-meta$" />
+$endif$
+$if(keywords)$
+ <meta name="keywords" content="$for(keywords)$$keywords$$sep$, $endfor$" />
+$endif$
+ <title>$if(title-prefix)$$title-prefix$ – $endif$$pagetitle$</title>
+ <style>
+ $styles.html()$
+ </style>
+$for(css)$
+ <link rel="stylesheet" href="$css$" />
+$endfor$
+$if(math)$
+ $math$
+$endif$
+$for(header-includes)$
+ $header-includes$
+$endfor$
+</head>
+<body>
+$for(include-before)$
+$include-before$
+$endfor$
+<nav>
+ <li><a href="index.html">Home</a></li>
+ <li><a href="boeuf.html">BOEUF</a></li>
+ <li><a href="objects.html">Objects</a></li>
+</nav>
+<main>
+$body$
+</main>
+$for(include-after)$
+$include-after$
+$endfor$
+</body>
+</html>
diff --git a/doc/img/video.png b/doc/img/video.png
new file mode 100644
index 0000000000000000000000000000000000000000..ae3aca88b1381abc40b86fb62bf5f4e8050d81a9
Binary files /dev/null and b/doc/img/video.png differ
diff --git a/doc/img/watching.gif b/doc/img/watching.gif
new file mode 100644
index 0000000000000000000000000000000000000000..1d05c9e48b59548d468620d9a895ab7b0309ca4f
Binary files /dev/null and b/doc/img/watching.gif differ
diff --git a/doc/index.html b/doc/index.html
new file mode 100644
index 0000000000000000000000000000000000000000..3bc590bee1b298cdbc8b3464d344db10d4000bf2
--- /dev/null
+++ b/doc/index.html
@@ -0,0 +1,105 @@
+<!DOCTYPE html>
+<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
+<head>
+ <meta charset="utf-8" />
+ <meta name="generator" content="pandoc" />
+ <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
+ <title>bf-pd : index</title>
+ <style>
+ code{white-space: pre-wrap;}
+ span.smallcaps{font-variant: small-caps;}
+ span.underline{text-decoration: underline;}
+ div.column{display: inline-block; vertical-align: top; width: 50%;}
+ div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+ ul.task-list{list-style: none;}
+ </style>
+ <link rel="stylesheet" href="img/style.css" />
+</head>
+<body>
+<nav>
+ <li><a href="index.html">Home</a></li>
+ <li><a href="boeuf.html">BOEUF</a></li>
+ <li><a href="objects.html">Objects</a></li>
+</nav>
+<main>
+<h1 id="bf-pd-a-puredata-external-for-building-digital-orchestras">bf-pd : a PureData external for building Digital Orchestras</h1>
+<h2 id="introduction-what-is-bf-pd-and-why-do-you-need-it">Introduction: What is bf-pd and why do you need it?</h2>
+<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>
+<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>Install the <strong>mrpeach</strong> library using Deken (PD -> Help -> Find Externals)</li>
+<li>Install <strong>bf-pd</strong> using Deken</li>
+</ul>
+<h2 id="getting-started-building-your-instrument">Getting started: Building your instrument</h2>
+<figure>
+<img src="img/start.gif" alt="" /><figcaption>doc/img/start.gif</figcaption>
+</figure>
+<p>Starting from an existing instrument made in PureData :</p>
+<ol type="1">
+<li>Create a declare object with -path bf-pd</li>
+<li>Create a bf-instrument object with your instrument name as argument</li>
+<li>Connect the sound output of your instrument to its inlet</li>
+<li>Create a bf-param object for each control you want to share with the others and insert it into your instrument</li>
+<li>Create a bf-session object with the name of the session you want to connect to</li>
+</ol>
+<h3 id="parameters-and-outputs">Parameters and outputs</h3>
+<p><strong>Parameters</strong> correspond to controls you have over your instrument and that you want to share with others.</p>
+<figure>
+<img src="img/bf-param.gif" alt="" /><figcaption>doc/img/bf-param.gif</figcaption>
+</figure>
+<p><strong>Outputs</strong> have the same properties but correspond to musical content produced by your instruments (notes, onsets, envelopes …). They can be used to control others parameters. Three default outputs are automatically created by bf-pd and extracted from the audio you send to bf-instrument : pitch, onsets, loudness.</p>
+<figure>
+<img src="img/bf-output.gif" alt="" /><figcaption>doc/img/bf-output.gif</figcaption>
+</figure>
+<p>Parameters and outputs have the same <strong>arguments</strong> :</p>
+<ol type="1">
+<li>instrument name</li>
+<li>parameter / output namenumberOfValues valuesType parameterIndex ]</li>
+<li>number of values</li>
+<li>type of values : cont (0 to 1), midi (0 to 127), bool (0 or 1), bang</li>
+<li>index : position in the collaboration window</li>
+</ol>
+<h2 id="performance-making-music-together-using-bf-pd">Performance: Making music together using bf-pd</h2>
+<h3 id="the-collaboration-window">The collaboration window</h3>
+<p>The collaboration window is a collaboration interface that comes with bf-pd and provides a way to connect your instrument with other instruments in the session.</p>
+<p>To open the collaboration window, simply check the <em>collab</em> toggle in the bf-instrument object.</p>
+<p>The leftmost green column shows your instrument with its outputs and parameters. The grey columns show the other instruments in the session with their respective activity, outputs and parameters.</p>
+<figure>
+<img src="img/collabwin.png" alt="" /><figcaption>doc/img/collabwin.png</figcaption>
+</figure>
+<h3 id="sharing-granting-access-to-your-parameters">Sharing / granting access to your parameters</h3>
+<p>By default, all your parameters are in the <em>granted</em> mode, which means that all the other musicians can change your parameter values. You can of course change this by clicking the red <em>grant</em> toggle for each parameter, or the <em>grant all</em> toggle at the top of your column. When your parameter is not granted, values <em>asked</em> by others are only displayed on the gray widgets. You can accept their <em>ask</em> by using the <em>1x</em> bang.</p>
+<figure>
+<img src="img/sharing.gif" alt="" /><figcaption>doc/img/sharing.gif</figcaption>
+</figure>
+<h3 id="using-others-parameters-and-outputs-to-change-your-parameters">Using others parameters and outputs to change your parameters</h3>
+<p>A <em>watch</em> bus selector is placed below each parameter and output of the other instruments. By choosing a bus other than 0, the values are sent to the corresponding bus and can be sent to your parameters connected to the same bus using the <em>watching</em> selector.</p>
+<figure>
+<img src="img/watching.gif" alt="" /><figcaption>doc/img/watching.gif</figcaption>
+</figure>
+<h3 id="controlling-others-parameters-with-your-parameters-and-outputs">Controlling others parameters with your parameters and outputs</h3>
+<p>Symmetrically, you can control others parameters by choosing a non-zero bus on the <em>ask</em> selector and the same <em>asking</em> bus below one of your outputs or parameters. This requires however that the parameter that you want to controlled is <em>granted</em> (i.e. that the green <em>granted</em> toggle is checked).</p>
+<figure>
+<img src="img/asking.gif" alt="" /><figcaption>doc/img/asking.gif</figcaption>
+</figure>
+<h3 id="directly-asking-controlling-others-parameters">Directly asking / controlling others parameters</h3>
+<p>You can also ask another instrument’s parameter to be set to a specific value by interacting with the white sliders/toggles/bangs. It the access is granted, the value will be directly set.</p>
+<figure>
+<img src="img/direct_asking.gif" alt="" /><figcaption>doc/img/direct_asking.gif</figcaption>
+</figure>
+<h2 id="demo-video">Demo Video</h2>
+<p><a href="https://pod.univ-lille.fr/video/19614-bf-pd-collaboration-window/"><img src="img/video.png" height="300px"/><br/>Video demoing the collab window for bf-pd</a>.</p>
+<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>
+<h2 id="authors">Authors</h2>
+<ul>
+<li>Luke Dahl, University of Virginia</li>
+<li>Florent Berthaut, University of Lille</li>
+</ul>
+</main>
+</body>
+</html>
diff --git a/doc/objects.html b/doc/objects.html
new file mode 100644
index 0000000000000000000000000000000000000000..c811d0d8b503d2b3fb1fefcbb502aa2119dd1375
--- /dev/null
+++ b/doc/objects.html
@@ -0,0 +1,125 @@
+<!DOCTYPE html>
+<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
+<head>
+ <meta charset="utf-8" />
+ <meta name="generator" content="pandoc" />
+ <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
+ <title>bf-pd : objects</title>
+ <style>
+ code{white-space: pre-wrap;}
+ span.smallcaps{font-variant: small-caps;}
+ span.underline{text-decoration: underline;}
+ div.column{display: inline-block; vertical-align: top; width: 50%;}
+ div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+ ul.task-list{list-style: none;}
+ </style>
+ <link rel="stylesheet" href="img/style.css" />
+</head>
+<body>
+<nav>
+ <li><a href="index.html">Home</a></li>
+ <li><a href="boeuf.html">BOEUF</a></li>
+ <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>
+<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>
+<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>
+</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 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>
+<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>
+</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>
+<img src="img/bf-param_example.png" alt="" /><figcaption>bf-param_example</figcaption>
+</figure>
+<h6 id="inlets-1">Inlets:</h6>
+<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-1">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>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>
+<ol type="1">
+<li>arg1</li>
+</ol>
+<h6 id="inlets-2">Inlets:</h6>
+<ol type="1">
+<li>blah</li>
+</ol>
+<h6 id="outlets-2">Outlets:</h6>
+<ol type="1">
+<li>blah</li>
+</ol>
+<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>
+<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-4">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 20575c20d9819b0190b0cfa843b7ea07539480d5..bb826f864f7ca4605ea2284d6ea959840424c337 100644
--- a/doc/objects.md
+++ b/doc/objects.md
@@ -17,7 +17,7 @@ There can be more than one bf-session object with the same name within the patch
## 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].
-The audio output of your instrument should be connected to the first inlet of bf-instrument object. The interface for has an *activity monitor* 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 *collaboration window*. (Note: you must also send your audio to [dac~] in order to hear it!)
+The audio output of your instrument should be connected to the first inlet of bf-instrument object. The interface has an *activity monitor* 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 *collaboration window*. (Note: you must also send your audio to [dac~] in order to hear it!)
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.
@@ -29,9 +29,9 @@ The *collaboration window* can be opened with the toggle in the bf-instrument ob
## bf-param
-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 user of the bf-instrument grants access.
+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.
-A bf-param object has a user interface within the instrument patch itself, and it creates a user interface in the collaboration window of each musician in the session.
+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.
A bf-param can be one of four *types*:
* *cont* are numbers between 0.0 and 1.0.
@@ -39,7 +39,7 @@ A bf-param can be one of four *types*:
* *bool* can take values of 0 or 1.
* *bang* are bang messages which are used to trigger actions.
-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 sequencers.
+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:
1. The name of the instrument, e.g. "myDrumMachine".
@@ -47,10 +47,10 @@ A bf-param can be a single instance of its type or it can be a multiple, which c
3. The dimensionality of the parameter, e.g. "8"
4. The type of the parameter, e.g. "bool"
-So a parameter to store 8 drum machine note triggers would be:
+So a bf-param with 8 drum machine note triggers would be:
`[bf-param myDrumMachine kickOnOff 8 bool]` and creates this object within your patch:
-
+
###### 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*.