5. Nodes reference table

Node URIs
OSs	Mode	Value	Query keys [1]	Description
Data Redirection
LWX	I	in[.<encoding>]<InputDevice>		listen and decode data from an input device
LWX	O	out[.<encoding>]<OutputDevice>		encode and forward the data to a target destination
Record/Replay
LWX	I	play[.<encoding>]:<filepath>	loop, speed, interval	replay a log file (default encoding pickle)
LWX	O	log[.<encoding>]:<filepath>		record data to log file (default encoding pickle)
LWX	O	rec:	request, timelimit, sizelimit, oversizecut, fps, timewarping	data recorder with GUI
LWX	I	player[.<encoding>]:	interval, open	log files player with GUI (default encoding pickle)
Data Debug
LWX	O	dump[.<encoding>]<OutputDevice>	request, mode, separator, src, dest, depth	dump products to an output device
LWX	O	stat[.<encoding>]<OutputDevice>	request, fps	print products statistics to an output device
LWX	O	viz:	antialiasing, fps	display multi-touch contacts
Data Processing
LWX	W	nop:		no operation node
LWX	W	edit:	merge, copy, result, **dict	apply to all the received products **dict
LWX	W	calib:	matrix, screen, attr, request, merge, copy, result	apply a 4x4 transformation matrix
LWX	W	filtering:[<filter-path>]	attr, request, merge, copy, result, <filter-attr> [2]	filter product data
LWX	W	timekeeper:	merge, copy, result	mark each received product with a timetag
LWX	W	lag:[<msec>]		add a lag to each received product
Utils
LWX	[3]	conf:<filepath>		composite node containing the pipeline defined into the specified configuration file.

5.1. Encodings

Encodings [4]
OSs	Mode	Value	Query keys	Description
LWX	IO	slip		bytestream from/to SLIP
LWX	I	pickle	noslip	pickle to products
LWX	O	pickle	protocol, request, noslip	Products to pickle
LWX	I	json	noslip	JSON to products
LWX	O	json	request, noslip	products to JSON
LWX	IO	osc	rt, noslip	bytestream from/to OSC
LWX	IO	tuio[.osc]	rawsource	Multi-touch events from/to TUIO

5.2. Input/Output devices

Input/Output devices
OSs	Mode	Value	Query keys	Description
LX	I	:[stdin]		read from standard input
LWX	I	:[stdout]		write to standard output
LWX	I	[.file]:<filepath>	uncompress, postend	read from file
LWX	O	[.file]:<filepath>		write to file
LWX	I	[.udp]://<host>:<port>		read from UDP socket
LWX	O	[.udp]://<host>:<port>	writeend	write to UDP socket
LWX	IO	.tcp://<host>:<port>	writeend	read/write on TCP socket

5.3. Hosts

Hosts
OSs	Mode	Value	Description
LWX	I	empty	same as IPv4 any address
LWX	I	0.0.0.0	IPv4 any address
LWX	I	[::]	IPv6 any address
LWX	IO	127.0.0.1	IPv4 loopback
LWX	IO	[::1]	IPv6 loopback
LWX	IO	x.x.x.x	specific IPv4 address
LWX	IO	[x:x:x:x:x:x:x:x]	specific IPv6 address
LWX	IO	<hostname>	specific hostname

5.4. Modes

Modes
Value	Description
I	Input
O	Output
W	Worker

See also

Section The pipeline architecture

5.5. OS support

OS support
Value	Description
L	Linux
W	Windows 7 [5]
X	OS X

Footnotes

[1]

The available query keys are obtained from the union of the available query keys of all the uri components. As an example, the URI out.json://[::1]:7777 is by default translated to out.json.udp://[::1]:7777, so it owns the query keys of the JSON encoder (request and filter) and of the udp socket node (writeend).

[2]	<filter-attr> dependes on the requested filter.

[3]	The mode depends on the pipeline defined into the configuration file. It is important to note that pipelines may have a closed configuration, which means they do not behave neither as input nor output, nor worker. This happens when all the inputs are connected in series to the outputs.

[4]	Some encodings have default input/output devices (e.g. in.tuio: is by default translated into in.tuio.udp://[::]:3333).

[5]	On Windows, in order to define a file using the scheme file: it is necessary to place the character ‘/’ (slash) before the drive letter (e.g. file:///C:/Windows/explorer.exe).