Tutorials/JITLib | JITLib > Tutorials | Tutorials > JITLib


proxy space - basic concepts

external structure of the node proxy, referencing in proxyspace and environments.

This document covers:

a) normal environment lookup

further readings: Environment

b) a proxyspace as an environment

one can replace the current environment with a special type of environment, a ProxySpace. this environment represents processes that play audio on a server.

c) using the proxyspace to change processes on the fly

further readings: ProxySpace examples, Bus, AbstractFunction

d) when are the node proxies initialized?

By default, bus initialization of a node proxy happens as soon as it is used for the first time. Later inputs are adjusted to this bus, as far as it is possible.

This initialisation happens whenever the proxy is first used. Later, the proxy can be accessed with other rate/numChannels combinations as needed (rates are converted, numChannels are extended by wrapping, sources with too many channels are wrapped).

NOTE: In sc3.7, you can dynamically adjust the rate and numChannels using the NodeProxy: -mold message, and the proxy can also be set to dynamically adjust to the input (NodeProxy: -reshaping).

It can be useful to explicitly initialize proxies that use variable type inputs:

e) moving out of the proxy space

f) using ProxySpace together with other Environments

using proxy space as an access scheme for node proxies can get in the way of the normal use of environments as pseudo variables. Here are some ways to cope with this.

previous: jitlib_basic_concepts_01 next: jitlib_basic_concepts_03