Data pools are almost exactly like Patterns that don't contain notes. Instead, they contain values that can be accessed exclusively from the DataGrab Evaluator. If nothing reads from them, they just sit there, but if patterns or transforms ask for data, they serve it up on request.
Data pools can be shared among any track that wishes to draw from them, and they do move in terms of set directions, just like patterns.
A basic data pool looks a lot like a Pattern, but instead of Slots, it contains DataSlots. It also takes a lot less arguments than Pattern
api.data_pools.add(name='sourceData', direction='random', slots=[ DataSlot(value=1), DataSlot(value=2), DataSlot(value=3), DataSlot(value=4), DataSlot(value=5), DataSlot(value=6), DataSlot(value=7) ])
A scene has the following properties:
|name||string||A symbolic name for the data pool, as referenced from DataGrab|
|direction||string||A direction, just as described in Patterns|
- Use a data pool with a random direction, such as serialized instead of a RandomChoice or RandomRange
- Use a data pool to interleave a melodic sequence or motif across multiple different scenes
other API demos. If you're done with that, it's time to kick out the jams.