Quote:
Originally Posted by goldenarpharazon
Introduces...
|
goldenarpharazon. if you are entitled to do so, you might want to enhance the “OSCII-bot code reference” website →
https://www.cockos.com/oscii-bot/oscii-bot-doc.html similar to this suggestion (in case my guessing of how OSCII-bot 0.4 works is correct).
@input : specifies a device to open for input. Usage:
@input devicehandle MIDI "substring devicename match" [skip_count]
@input devicehandle OSC "1.2.3.4 : port"
>>> the IP address given denotes the interface in the system OSCII-bot runs in, the port given is the port OSCII-bot opens to listen on. Hence the sending site needs to be configured to use this address and port to send OSC messages to OSCII-bot. <<<
@input devicehandle OSC "* : port"
>>> use any IP interface in the system OSCII-bot runs in <<<
>>> if an OSC message is detected at a port defined by “@input devicehandle OSC ...”, or automatically assigned by “@output devicehandle OSC ...”, the @oscmsg event handler EEL code is executed, and oscstr and oscparm() will provide the content received, msgdev will provide the devicehandle. <<<
>>> if oscsend() is used with a devicehandle defined by “@input devicehandle OSC ...”, the OSC message will be sent to the last IP-address and port number an OSC messages has been received from via this device. This is useful to have OSCII-bot act as a server-like OSC instance, doing bidirectional communication. <<<
@input devicehandle OMNI-MIDI -- receives all MIDI received by other scripts
@input devicehandle OMNI-OSC -- receives all OSC received by other scripts
@input devicehandle OMNI-MIDI-OUTPUT -- receives all MIDI sent by other scripts
@input devicehandle OMNI-OSC-OUTPUT -- receives all OSC sent by other scripts
@output : specifies a device to open for output. Usage:
@output devicehandle OSC "host : port" [maxpacketsize (def=1024)] [sleepinMS (def=10)]
>>> the host IP address and port number define the target site to receive OSC messages sent by OSCII-bot via this device. The sending IP address for such messages will be the IP address of the interface in the system OSCII-bot runs in. The sending port number of the messages will be a random number that is chosen when OSCII-bot starts the script. <<<
>>> The port number acquired by “@output devicehandle OSC "host : port" ...“ will also be opened to listen to received OSC messages on. For incomming OSC messages to this port, the @oscmsg event handler EEL code is executed, and msgdev will provide the devicehandle. This is useful to have OSCII-bot attach to a server-like OSC instance (such as a hardware based digital mixer), doing bidirectional communication.
@output devicehandle MIDI "substring match" [skip]