Idea:
- adding "/report/commands/entry/argument, [cmd_index], [arg_index], [minval], [maxval], [warp], [step], [default], [units]"
But perhaps wise to simplify and not leverage every possible item…
we have mono polls for in/out, but wondering if those should be reserved for user scripts and a system-level poll (array returned) would be better for vu displays. the data could be publicly available…
we need a system to get feedback from the engine. for example:
- sound output levels (for a VU display)
- sample playback position (for building an mlr-like thing)
i'm figuring this is a matter…