Communicate with a remote rnbo device Remotely set and receive information on a Remote RNBO Device. This Information includes information and changes with parameters , messages, MIDI, external clock , and RNBO presets on the remote device.



Cycling '74 TEXT_HERE Messages and MIDI input The Message and Midi inlet on the rnbo.remote receive midi formatted messages and messages to set attributes of the exported rnbo code on the remote device. Messages and MIDI bytes The Message and Midi inlet on the rnbo.remote receive midi formatted messages and messages to set attributes of the exported rnbo code on the RNBO remote device. MIDI messages sent to the left inlet of the rnbo.remote are sent to midiin objects on the remote device. Messages can be set to named inport objects in the left inlet to target named param objects and attributes of the rnbo.remote object. Outport messages The leftmost outlet reports the state of outport objects exported rnbo code on the RNBO remote device. To report the state of the outport objects, reference the object by namespace using an object such as route. MIDI bytes The middle outlet outputs the status of midiformatted messages that are sent to midiout objects in the exported RNBO code on the remote device. Status messages The right outlet reports the status of the RNBO code on the remote device.



The "host names" message retrieves a list of discovered remote rnbo devices. This is essentially all of the RNBO Device names that appear on the shared networks address.



The "connectivity" message reveals the connectivity status between the Remote and the RNBO device. An output value of '1' means that the devices are connected for remote control and retrieval of information from the devicE, AND '0'means there are no connected devices.



The "instance_info" message retrieves and lists the values of the named parameters, inports, outports, and data references running on the RNBO device. TEXT_HERE TEXT_HERE Midi bytes MIDI formatted messages sent to the left inlet of the rnbo.remote are sent to midiin objects on the remote device. Inport messages To change the value of a named inport object , the word message is prepended to the inport @name, followed by a value.

message 'inport @name' $ Status output triggering From the rightmost outlet, the status of the RNBO code on the remote device is reported.



The "host names" message retrieves a list of discovered remote rnbo devices. This is essentially all of the RNBO Device names that appear on the shared networks address.



The "connectivity" message reveals the connectivity status between the Remote and the RNBO device. An output value of '1' means that the devices are connected for remote control and retrieval of information from the devicE, AND '0'means there are no connected devices.



The "instance_info" message retrieves and lists the values of the named parameters, inports, outports, and data_refs Remove a patcher from the list of patches on the runner Remove a named patcher that has been exported to the pi from the runner's cache.



If an instance of the patcher is loaded when a "patcherdestroy" is set for it, the instance will remain loaded until a different patcher is loaded. Initialize, load, save, and delete presets. Load, save, and delete presets on the RNBO device remotely.



To load a preset from the RNBO devices preset index, append the preset message with the load argument, followed by the name of the preset so that it looks like this : preset load $1 .



To save a preset from the RNBO devices preset index, append the preset message with the saveargument, followed by the name of the preset so that it looks like this : preset save $1.



To delete a preset from the RNBO devices preset index, append the preset message with the delete argument, followed by the name of the preset so that it looks like this : preset delete $1.



To set a preset to load first when the device intially boots, append the preset message with the initial argument,followed by the name of the preset so that it looks like this : preset initial $1 . If this is not set, then by default, the first preset saved to the rnbo.device will load on reboot.



The address of the host to communicate with Setting the address of the device host running the RNBO code will point the rnbo.remote device to communicate with that device. The address is the IPV4 address of the RNBO remote device. The number of milliseconds to ignore incoming parameter updates after a local update for feedback suppression. The number of milliseconds to ignore incoming parameter updates after a local update for feedback suppression. The numbered instance of the patcher to load and communicate with. The numbered instance of the patcher to load and communicate with. This is associated alpabetically with the patchername that has been exported to your Pi (f.e. if you have two patches on your pi,@inst 0 will reference @patchername delay and@inst 1 will reference @patchername reverb). The name of the host to communicate with. The name of the RNBO device host to communicate with. This is the name set for your RNBO device determined in the configuration settings at the time of export. The name of the patcher to load and communicate with. The name of the patcher to load and communicate with. This is the name set for your patcher determined under Patch Name in the target sidebar at the the time of export. The port on the host to communicate on Communicate on a specific port of the RNBO device shared IPv4 network. This can be specifically useful for instances where you would like to utilize port forwarding for the rnbo.remote's communication. Provided that both the RNBO device and the remote are connected to the same network, setting the port will allow messaging to be forwarded specifically to that port. The default port is 5678. The MIDI channel to use for changing presets via MIDI Program messages. Use MIDI channels for changing RNBO presets via MIDI program messages. This is helpful for setting presets from MIDI hardware connected to the RNBO device. The MIDI program number will load the preset by it's number represented in the preset index.



By default, this setting is set to omni, which allows any midichannel to set program changes to the rnbo devices presets



Setting a integer value between 1and16 will allow programs from a specific Midi channel, f.e. presets/midichannel 1 will only allow program changes via MIDI channel1.



Setting presets/midichannel nonewill not allow program changes to be made to any MIDI channels. Remote control and visualization of the transport tempo (beats per minute) Remote control the transport tempo (beats per minute) of the RNBO code running locally on the RNBO remote device. Enable to allow the rnbo.remote to control the rnbo.devices local transport tempo. The RNBO code running on the remote device has it's own transport tempo. Enabling transport/rolling allows us the ability to remotely control and visualize the transport tempo running on the RNBO runner from the rnbo.remote object. rnbo~ The left outlet reports the state of outport objects exported rnbo code on the RNBO remote device. To report the state of the outport objects, reference the object by namespace using an object such as route. The middle outlet outputs the status of midiformatted messages that are sent to midiout objects in the exported RNBO code on the remote device. The right outlet reports the status of the RNBO code on the remote device.



The "host names" message retrieves a list of discovered remote rnbo devices. This is essentially all of the RNBO Device names that appear on the shared networks address.



The "connectivity" message reveals the connectivity status between the Remote and the RNBO device. An output value of '1' means that the devices are connected for remote control and retrieval of information from the device, and '0'means there are no connected devices.



The "instance_info" message retrieves and lists the values of the named parameters, inports, outports, and data_refs