insglobal — An opcode which can be used to implement a remote orchestra. This opcode will send note events from a source machine to many destinations.


With the insremot and insglobal opcodes you are able to perform instruments on remote machines and control them from a master machine. The remote opcodes are implemented using the master/client model. All the machines involved contain the same orchestra but only the master machine contains the information of the score. During the performance the master machine sends the note events to the clients. The insglobal opcode sends the events to all the machines involved in the remote concert. These machines are determined by the insremot definitions made above the insglobal command. To send events to only one machine use insremot.


insglobal isource, instrnum [,instrnum...] 


isource -- a string that is the intended server computer (e.g. This is the source host which generates the events of the given instrument(s) and sends it to all the machines involved in the remote concert.

instrnum -- a list of instrument numbers which will be played on the destination machines


[Note] Note
If is essential the computers using this opcode have the same byte-order, data size (double or float) and pointer size. One cannot use it with mixed 32 and 64 computers for instance.
[Note] Note
Internally this opcode makes use of the gethostname and gethostbyname functions to determine the client's and server's IP address for checking which messages are for which machine. If a computer has more than one IP address there is no way to control which IP address is found.
[Note] Note
The remote operation does not allow the sending of strings at all.


See the entry for insremot for an example of usage.

See also

insremot, midglobal, midremot, remoteport


Author: Simon Schampijer

New in version 5.03