Offline
Value members
Abstract methods
Logically closes the offline server and returns a list of all the bundles collected so far. Note: Calling this method will clear the bundles held by the server.
Logically closes the offline server and returns a list of all the bundles collected so far. Note: Calling this method will clear the bundles held by the server.
- Value Params
- addDefaultGroup
if
true
, prepends a/g_new
message for the standard default group (node id 1) to the returned bundles
Inherited methods
Sends out a packet immediately without synchronization
Sends out a packet immediately without synchronization
- Inherited from
- Server
Sends out a packet with an added sync message. The returned future is completed with the sync message's reply having arrived.
Sends out a packet with an added sync message. The returned future is completed with the sync message's reply having arrived.
- Inherited from
- Server
Acquires a synth def to be used in this transaction on the server.
If the ugen graph was already sent to the server, it returns the
corresponding synth def, and no recv()
is necessary. The internal
use counter is increment. Otherwise produces a fresh synth def and
stores it in the cache.
Acquires a synth def to be used in this transaction on the server.
If the ugen graph was already sent to the server, it returns the
corresponding synth def, and no recv()
is necessary. The internal
use counter is increment. Otherwise produces a fresh synth def and
stores it in the cache.
If the number of synth definitions on the server would exceed the maximum, a number of synth-def disposals are issued for those that have a use count of zero.
- Inherited from
- Server
Signalizes that no more messages are sent from the currently committing transaction. The offline server collects these futures, in order to allow an outside process to eventually wait for these to be completed, before closing the OSC file and carrying on. The realtime server just ignores these futures.
Signalizes that no more messages are sent from the currently committing transaction. The offline server collects these futures, in order to allow an outside process to eventually wait for these to be completed, before closing the OSC file and carrying on. The realtime server just ignores these futures.
- Inherited from
- Server
Abstract fields
The current frame position in the OSC file. The user should increment this according to a reference transport, so that messages are queued in the correct position.
The current frame position in the OSC file. The user should increment this according to a reference transport, so that messages are queued in the correct position.