remove buffer limitation from README

README.md

@@ -23,8 +23,6 @@ At this early stage in the developement of this tool, there exist some known lim
 
 You can read more about each of the following topics in [our documentation](docs/README.md), including suggested current workarounds. 
 
-* At present, you will not be able to use or set a `DataRef` (buffer) inside of the node built from your RNBO export.
-
 * At present, `inport` and `outport` will only receive and transmit a `bang`, which is translated as a `Trigger` in MetaSounds. Float and list messages are [not currently implemented](docs/README.md#trigger).
 
 * See our [issues page](https://github.com/Cycling74/RNBOMetasound/issues) for more discussion.

docs/README.md

@@ -21,7 +21,7 @@ Your RNBO MetaSound node will be named by your top-level `[rnbo~]` object’s `@
 
 ## Generating Pin Types
 
-A RNBO patcher's `parameters` and message `inports` or `outports` can all become pins on the RNBO Metasound node, along with a pin for `MIDI` input/output and for connecting to a `Transport`. Those pins can be input pins, output pins, or both. 
+A RNBO patcher's `parameters`, message `inports` or `outports`, and `buffer~` objects can all become pins on the RNBO Metasound node, along with a pin for `MIDI` input/output and for connecting to a `Transport`. These objects can generate input pins, output pins, and in some cases, both. 
 
 ### Input and Output Parameters 
 
@@ -55,6 +55,10 @@ By default a pin for `[in~ 1]` or `[out~ 2]` will be named "in1" or "out2" but y
 
 Note that at present, the pin will only output a `Trigger` if the `outport` is set to output a `bang`.
 
+### WaveAsset
+
+A named buffer in a RNBO patch will generate an input pin of `WaveAsset` type.
+
 ## Utility Nodes
 
 This repository will build a few utility nodes that are designed to help you work with MIDI and RNBO's internal transport.