PRG Mbox Remote Manual 3.9 - Manual (Page 73)

MBOX ® REMOTE USER MANUAL 67
Fixtures Out of Bounds
It is possible for a fixture to have some or all of its pixels outside the boundaries of its context, or even the entire
source. Pixels that are outside the boundary of their context will not output any pixel mapping level data. Pixels can
end up outside the context’s boundary:
+ If the fixture is positioned such that some of its pixels end up outside the boundary.
+ If the context or source is resized to be smaller after the fixture has been added to the configuration.
Fixtures that have pixels outside their context show this in two ways:
+ Pixels that are outside the boundary are outlined in red.
+ Fixtures that have pixels outside the boundary will have a red dot shown in the Fixtures table.
Addressing Fixtures
As fixtures are added to a context, they are automatically assigned an output protocol, then a universe, device, or
device.port within that protocol, and finally an address for the first pixel in the fixture. Subsequent pixels in the same
fixture receive an address that is offset from the first pixel by a set amount. The amount is typically based on the
number of channels (addresses) that the previous pixel uses.
+ Art-Net = universe & address
+ sACN = universe & address
+ KiNET Portout = device.port & address
+ KiNET DMXout = device & address
The protocol is based on the protocol of the context that it is placed upon, while the address is based on the universe/
device and address shown in the sequencing box at the lower right of the window.
Fixture out of bounds
Universe for next fixture placement
Address for next fixture placement
Find Next Universe/Address
Allow Conflicts Checkbox