lom_batch
Execute multiple raw LOM get, set, or call operations in one round trip to reduce latency. Use when you need several Live Object Model reads or writes at once.
Instructions
Execute multiple raw LOM operations (get, set, call) in a single round trip.
One trip instead of many, which is what makes a wide read affordable at roughly
450 ms per round trip.
Returns:
Dictionary containing ordered results for each operation.
Note:
A batch runs inside one handler call, so nothing Live recomputes between
operations is visible to a later operation in the same batch. A read that follows
a transport jump in the same batch still reports the position from before the
move. Four jumps interleaved with four reads returned four identical pre-jump
values and no error at all. That is the failure shape to expect here. It does not
raise. It returns a clean set of numbers that look like a measurement of a
parameter which never changes, and the conclusion drawn from them is wrong. Sample
a moving transport with one call per position, never inside a batch.
``atomic`` is a stop switch and not a transaction: nothing is undone. After a
partial failure, read the state back rather than assuming either all or none
of the batch landed.
Prefer a dedicated tool for anything it covers. get_session, get_track and
get_devices already batch their own reads, and set_mix writes a whole mixer
in one trip, each with verification this does not perform.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ops | Yes | The operations to run, in order. Each one declares its own op, path and payload; the item schema carries the field meanings. | |
| atomic | No | True stops at the first error, leaving the operations before it applied and the ones after it untried. False runs every operation and reports each result. Neither rolls anything back. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||