These objects can be used
\nto process a large amount of
\ndevice explorer nodes at once.
\n
They all allow using the pattern matching language
supported by score:
- * means all the nodes at a level of the tree,
- foo{0..9} means foo0, foo1, foo.. up to foo9, etc.
- /{foo,bar} means /foo and /bar
See https://ossia.io/score-docs/in-depth/pattern-matching.html
Note that addresses are always processed in lexicographical order.
Pattern applier takes a list as input and applies each value to a
successive OSC address. Here:
- 0 goes to /pattern_applier/0,
- 10 goes to /pattern_applier/1
etc.
Pattern combiner takes a list of addresses and turns the result in a set of values.
There are multiple useful modes for instance when one wants to read the average
value of an array of sensors, etc.
Spammer is a bit special: it's the only object that doesn't actually
goes through the device tree: it spawns a separate thread dedicated
to sending OSC messages with the highest possible regularity.
In this example, it sends ten OSC messages at 1khZ,
so 10k messages per second since there's ten addresses.
Measured by
nc -l -u 10002 | fold -w 16 | pv -lr > /dev/null
If the input rate is too slow, one can apply smoothing to match the receiver's
expectation
Sweeper sweeps its input across the addresses
it matches, switching at a regular rate.
Useful for fun effects.
Note that the pattern matching expressions
\ncan always be used as input or output of a port,
\nwith the semantic of:
- take any value from these addresses (for inputs)
- write the value to all these addresses (for outputs).
Finally