Disguise

ncam reality configuration it's recommended to use the reflective marker tracking mode for led installations the environment should have the retro reflective markers added to it using the marker calculator and marker setup wizard (available from the the webui actions tab) some circular markers may be obscured by top mounted walls or monitors, etc a minimum of one fiducial anchor instant recovery marker printed to the correct size for the space, remember if you’re using multiple markers, they must be different id’s as a general rule on sizing 2 4 meters from mk2 camera bar to ceiling a3 4 6 meters from mk2 camera bar to ceiling a2 6 10 meters from mk2 camera bar to ceiling a1 the fiducial anchor chart may need additional lighting depending on where it can be mounted in the volume and this should be taken into account mounting the camera bar should be pointed 90 degrees upwards using a rigid mount such as this and this the mk2 external encoders can be mounted using the zoom bar attachment the ir emitter will be required and plugged into either the mk2 server or connection box integration this process is built on the assumption that the led wall parameters have already been input into the disguise software and the disguise operator is able to complete the led wall observations once the data stream is established lens calibration disguise creates its own calibration and world transformation using observations, therefore, only one point of calibration is technically required (z 0, f 0 5) to be able to perform the witness to main calibration as disguise will calculate its own translation offsets during the observation process, our zero point does not have to be lined up to a real life object or the screen, such as is the case with ndisplay it just has to have its axis in the correct orientation setting the zero point to the instant recovery fiducial marker on the ceiling is recommended having a point that can be recovered consistently is vital because once the disguise led wall observations have been completed if the zero point is moved or reset somewhere else the disguise led observations then become redundant and have to be re done from scratch supported format disguise is compatible with both the ncamsdk and freed data streams using a network connection between the two devices ensuring a consistent zero point to streamline the use of ncam and disguise software it is strongly recommended to use the saving and loading of projects/alignments inside the ncam software in combination with the use of a fiducial anchor, this will allow for consis tent and reproducible tracking and ensure that t he absolute positionin g of the tracked camera is not changing between multiple operating sessions suggested settings and workflow are provided below, using the full ui is required to configure some of the parameters create a project/alignment tracking cores circular & fiducial density 24 key positions 0 4 ncam sdk or freed enabled exposure checked and set manually on air enabled delete the point cloud, refresh the tracking with the fiducial marker(s) being detected, and move around the whole volume decide on the position of the zero point and position it save the project project/alignment recovery as mentioned above, pixel perfect project recovery is required for a seamless integration enable the ‘load the last project on start up’ option to make the solution headless and autonomous the saving and automatic recovery of the project, zero point, and settings is vital and should always be tested with full system reboots, shutdowns, and power downs before starting the observation process in disguise locking the pointcloud once an alignment has been saved we recommend "locking the point cloud" see the locking the pointcloud docid\ epdhurqtxymrfin0ss6qn section for details on this receiving tracking data in disguise confirm that the network connection between the ncam reality server and the disguise server is correctly configured confirm that either the ncamsdk or freed protocols are activated and sending tracking data from ncam reality confirm the tracking is correctly configured and that a zero point has been set it is important that a consistent zero point will be used and can be easily recovered as the disguise calibration requires the tracking remains consistent over multiple sessions inside the disguise software home screen, select the "+" icon from the devices tab choose a identifiable name for the new device and then select " position receiver " from the provided list depending on the tracking protocol being sent from ncam reality, choose either ncamdriver or freeddriver from the list of position receivers a subsequent window will ask for the ncam server ip address and the port number that has been selected the port number is 38860 to engage tracking data, in the disguise software, right click on the director status tab and switch from disengaged to engaged to view the raw tracking data, right click on the automotion tab at the top of the software and then select ‘ monitor ’ next to the driver you have previously named