This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
beyond:osc_commands [2020/01/21 11:00] Bob Varkevisser [OSC Message] |
beyond:osc_commands [2021/04/16 11:10] Bob Varkevisser |
||
---|---|---|---|
Line 17: | Line 17: | ||
===== OSC in Object tree ===== | ===== OSC in Object tree ===== | ||
- | To find OSC commands/ | + | To find OSC commands/ |
Open up the tools menu and click object tree to make it visible. | Open up the tools menu and click object tree to make it visible. | ||
Line 42: | Line 42: | ||
A known issue is that TouchOSC is not able to process OSC commands to use the | A known issue is that TouchOSC is not able to process OSC commands to use the | ||
cue grid to its full potential. | cue grid to its full potential. | ||
- | | ||
+ | ===== OSC to PangoScript GATEWAY ===== | ||
+ | Server transform the OSC message to the command first and then the command goes to execution. The command appear in the system in the same way as it could be from the keyboard, or the mouse. This kind of servers also has fixed address and corresponding set of arguments. Actually, the address of such OSC server is a way to describe BEYOND command. And it was main intention - to give OSC the ability to do the same what the Script can do. Both parts (OSC and Script) produce a Command at the end, and why not to mix both worlds. | ||
+ | Address of message and number of arguments should correspond to the PangoScript command. Available following addressing: | ||
- | ===== Supported Argument types ===== | + | / |
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | |||
+ | " | ||
+ | |||
+ | The " | ||
+ | |||
+ | |Address|Type|Commentary| | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |/ | ||
+ | |||
+ | |||
+ | |||
+ | ==== Supported Argument types ==== | ||
BEYOND support integer number (i), float point number (f), and string (s). Other data types ignored. You need to ensure that OSC client send correct type of argument to BEYOND. | BEYOND support integer number (i), float point number (f), and string (s). Other data types ignored. You need to ensure that OSC client send correct type of argument to BEYOND. | ||
Line 78: | Line 225: | ||
/ | / | ||
- | ===== Direct servers | + | ===== Other OSC Servers ===== |
+ | ==== Direct servers ==== | ||
This kind of server provide a direct access to internal object of BEYOND. No extra layers, or something in between. BEYOND receive the OSC packet, analyze the address and if the address point on direct server, the BEYOND execute it right after the address parsing. Such servers has fixed address part and number of arguments. | This kind of server provide a direct access to internal object of BEYOND. No extra layers, or something in between. BEYOND receive the OSC packet, analyze the address and if the address point on direct server, the BEYOND execute it right after the address parsing. Such servers has fixed address part and number of arguments. | ||
Line 221: | Line 369: | ||
" | " | ||
- | ===== OSC to PangoScript GATEWAY ===== | ||
- | |||
- | Server transform the OSC message to the command first and then the command goes to execution. The command appear in the system in the same way as it could be from the keyboard, or the mouse. This kind of servers also has fixed address and corresponding set of arguments. Actually, the address of such OSC server is a way to describe BEYOND command. And it was main intention - to give OSC the ability to do the same what the Script can do. Both parts (OSC and Script) produce a Command at the end, and why not to mix both worlds. | ||
- | |||
- | Address of message and number of arguments should correspond to the PangoScript command. Available following addressing: | ||
- | |||
- | / | ||
- | / | ||
- | / | ||
- | / | ||
- | / | ||
- | / | ||
- | |||
- | " | ||
- | |||
- | The " | ||
- | |||
- | |Address|Type|Commentary| | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
- | |/ | ||
Line 487: | Line 486: | ||
What commands can be served by /cue/ server? The most definitely is the Live Control group commands, and FX. The command like cue start, or cue stop, is an area of /general/ server | What commands can be served by /cue/ server? The most definitely is the Live Control group commands, and FX. The command like cue start, or cue stop, is an area of /general/ server | ||
- | |||
- | ==== OSC to Object server ==== | ||
- | |||
- | |||
- | Address of server start from prefix /object . After this follow name of object and finally the name of property. As example, we have object Main Graphics (projection zone) and it has property SizeX. The address for access is | ||
- | / | ||
- | The message must comes with one value (argument). It could be string or number. | ||