vvopensource
|
An OSCBundle is a "container" for multiple OSC messages or bundles (bundles may also be nested) More...
#import <OSCBundle.h>
Inherits NSObject.
Instance Methods | |
(void) | - addElement: |
Adds the passed element to the bundle. | |
(void) | - addElementArray: |
Adds the array of passed elements to the bundle. | |
Class Methods | |
(id) | + create |
Creates and returns an auto-released bundle. | |
(id) | + createWithElement: |
Creates and returns an auto-released bundle with the single passed element. | |
(id) | + createWithElementArray: |
Creates and returns an auto-released bundle with the array of passed elements. | |
An OSCBundle is a "container" for multiple OSC messages or bundles (bundles may also be nested)
According to the OSC spec, an OSC bundle is basically a wrapper for multiple OSC messages (or other bundles). Instead of sending a bunch of individual messages, you can wrap them all into a bundle, and send the bundle (messages will still be sent to their individual address paths). OSCBundleÕs interface is correspondingly simple: you can create a bundle from some elements, or you can create a bundle and then add some elements (OSCMessages or OSCBundles) to it.
OSC bundles also have a time stamp- by default, this will be set to immediate execution (0s except for a single 1 in the LSB). while timetag execution isn't widely supported, you may specify non-immediate time tags in the hopes that the software on the receiving end will execute the bundle in time.