A typical Displayport to HDMI adaptor
Example of NVIDIA driver search for an A4000-based Windows 10 system
Drivers with a high "U-number" are considerably more stable then drivers with a low U-number
\[x] graphics driver
\[x] HD audiodriver
recommended driver installation parameters (custom install option)
Mosaic topologies
Example of using Mosaic on Display 1 & 2 (left image) to combine into a larger Display 1 (right image)
https://mosaic.vioso.com - online commandline generator for configureMosaic.exe
NVIDIA Control Panel Set Up Mosaic Page
Find this dialog in menu Options - Settings: Remote Control
Find this dialog in menu Options - Settings: Multi client
| Product | Resolution | Field of view HxV | operating distance |
|---|---|---|---|
| Logitech c930 | 1920x1080@30fps USB 2.0 | 78x46° | 5 - 15 meters |
| Logitech c920 | 1920x1080@30fps USB 2.0 | 70x40° | 5 - 15 meters |
| Logitech BRIO | 3840x2160@30fps USB 3.0 | 78x46° | 3 - 10 meters |
| Elgato Facecam | 1920x1080@60fps USB 3.0 | 70x40° | 3 - 10 meters |
CK\_W56-4
CK\_W76-4
CK\_W89-4
56,8° x 44,0°
76,0° x 60,8°
89,0° x 73,8°
16,10° x 12,10°
22,10° x 16,70°
31,50° x 23,90°
48,20° x 36,70°
60,00° x 46,90°
79,20° x 63,80°
CK\_WU120-4
CK\_WU135-4
135,0° x 119,0°
110,0° x 94,0°
CK\_T29-4
CK\_T44-4
28,9° x 21,9°
44,7° x 33,9°
CK\_FDN-4
CK\_FDN-4b
CK\_FDQ-4
Fisheye calibration kit
Fisheye calibration kit 1” sensor
HQ Fisheye calibration kit
2/3”
1”
1”
2448 x 2048
2592 x 2048
4508 x 4096
23 fps
20 fps
6 fps
CK\_FDY220-4
CK\_FDY250-4
CK\_FDY280-4
1/1.7”
1/1.7”
1/2.3”
4024 x 3036
4024 x 3036
3840×2748
9 pfs
9 fps
10 fps
365,00° x 220,00°
365,00° x 250,00°
365,00° x 280,00°
**(a) PoE (Power Over Ethernet)/DATA:**\
Connect the camera to this socket (this will power the camera and a small light will flicker).
**(b) DATA:**\
Connect the Ethernet cable to the PC/server or to a switch.
{% hint style="info" %}
The camera requires a stable 1Gb/s ethernet connection. 100MB/s won’t work!
{% endhint %}
{% hint style="info" %}
We strongly recommend running the camera directly to the PC. Therefore, VIOSO servers usually come with 2 dedicated Ethernet ports. Please note that during calibration the camera creates a large amount of data, occupying the whole network bandwidth and therefore should not be shared with other network based applications (e.g. remote access).
{% endhint %}
### 2. Installing the driver package “Galaxy DSK 2”
1. Download: [Galaxy\_Windows\_EN\_32bits-64bits\_2.0.2309.9181.exe](https://download.vioso.com/drivers/daheng/Galaxy_Windows_EN_32bits-64bits_2.0.2309.9181.exe)
2. Install driver:\
* Check GigE Vision
* Check DirectShow
* Check Enable Jumbo Frames
3. Reboot the system.
### 3. Network configuration
1. Make sure that the camera is connected and powered (PowerLED “blue”)
2. Run the application “GxGigEIPConfig”.\
* If the camera is connected, it shows within the “GigE” tree under the network adapter.
* If the network adapter is not active, the camera gets an address starting with “169.254…”. In this case it is required to reconfigure the network interface to a static IP. Right-Click the network adaptor and select “Network card configuration tool”:\
* Click the Button “Netcard Protocol Property” to access the Windows network settings. Change to static IP setting and enter an appropriate IP (e.g. 10.0.0.1 / 255.0.0.0 for a point-to-point connection). If the network already is set to a fixed IP, you can skip this step.\
\
Terminate everything with “OK” and “Apply”.
* The camera can be configured by clicking “Auto Configure IP”.\
* After this, the camera gets a fixed IP and is marked as available.
* Optional:\
Right-Click on the camera name and open the “Modify IP Address” dialog. Enter an IP of your choice that fits to the IP range entered for this ethernet connection (e.g. 10.0.0.12 according to the example above). You also can change the device name of the camera.\
* This way the camera has a fixed IP, that will make all subsequent tasks for calibration more transparent.
## Camera Configuration
All settings of the camera can be done in the “Galaxy Viewer” software.\
\
It is a complex tool, allowing a lot of settings to be made. But we recommend to stick to some very fundamental settings only, leaving as much as possible untreated. All settings that are done by the Galaxy software are temporary, unless you save them as a user set (see below).
Once the camera network configuration is complete, the camera icon gets green (1), indicating that the camera is ready to be operated. Launch the preview by double clicking the camera (1) and press the “Play” Button (2) in the top button bar to display a live camera image.
* **Exposure mode:** Timed
* **Exposure Auto:** always set to OFF!\
**Exposure time:** Set to a value that matches with the brightness of the filmed scene. By setting the exposure, the framerate automatically adapts accordingly. Please evaluate the exposure when projectors are displaying bright content, filling all the projection area.
* **Gain:** Set to 0.000 (dB)\
if the camera image is too dark, you can carefully increase the gain. Try to maintain a high contrast when setting a user defined gamma value.
* **GainAuto:** always set to OFF!
### Analog Control
In good conditions, where the camera get sufficient light, there is no need to make any changes, but in challenging environments, the analog control parameters of the camera can help to increase the sensitivity of the sensor. We recommend to leave these parameters unchanged as long as possible. If optimizations are required, start changing the **Blacklevel** parameters, then the **Gamma** parameters and use the **Gain** parameter only as a last resort.
Select the “Device” Tab and expand “Analog Control”:
* **Gain:** if the camera image is too dark, you can carefully increase the gain. Try to maintain a high contrast when setting a user defined gamma value.
* **GainAuto:** always set to OFF! Therefore, the values AutoGain are not used
* **GammaEnable:** this will enable the camera sensor gamma behaviour which results in a different sensitivity. Enable only if it is really hard to get a proper projector pattern detection and choose **GammaMode=SRGB**
* **Gamma:** Once enabled you can set the gamma value here.
* **Blacklevel:** This is a good parameter to have the projector patterns displayed properly while “hiding” darker parts. Start optimizing the camera behaviour by changing this value first, before trying Gain or Gamma.
### Image cropping for Fisheye calibration kits
fisheye lenses produce a sqare image, but the sensors aren’t square. For the use of 3D features in VIOSO (“MRD”), it is important to set the camera to a square pixel resolution. Therefore, a custom resolution based on the sensor height resolution should be set according to the sensor height resolution and with an offset to match the lens at the center.
1. To change the sensor resolution, STOP the current camera stream (1)
2. Set the parameters “Width” and “OffsetX” to get a square resolution, centered on the sensor (2) – see table below:89,0° x 73,8°
76,0° x 60,8°
56,8° x 44,0°
135,0° x 119,0°
110,0° x 94,0°
44,7° x 33,9°
28,9° x 21,9°
**(a) PoE (Power Over Ethernet)/DATA:**\
Connect the camera to this socket (this will power the camera and a small light will flicker).
**(b) DATA:**\
Connect the Ethernet cable to the PC/server or to a switch.
{% hint style="info" %}
The camera requires a stable 1Gb/s ethernet connection. 100MB/s won’t work!
{% endhint %}
{% hint style="info" %}
We strongly recommend running the camera directly to the PC. Therefore, VIOSO servers usually come with 2 dedicated Ethernet ports. Please note that during calibration the camera creates a large amount of data, occupying the whole network bandwidth and therefore should not be shared with other network based applications (e.g. remote access).
{% endhint %}
### 2. Install the driver package “MVS”
1. Download: [MVS\_STD\_3.3.1\_201207.exe](https://download.vioso.com/drivers/hik/MVS_STD_3.3.1_201207.exe)
2. Install driver:\
### 3. Install DirectShow Interface
Run as Admin:
```
C:\Program Files (x86)\MVS\Development\ThirdPartyPlatformAdapter\DirectShow\x64\MvDSS2\InstallDSSvc_x64.bat
```
{% hint style="info" %}
For x86 systems, run the same files from \x86 folder instead.
{% endhint %}
### 4. Network configuration
1. Make sure that the camera is connected and powered (PowerLED “blue”)
2. Run the application “MVS”.
* If the camera is connected, it shows within the “GigE” tree under the network adapter.
* If the network adapter is set to DHCP, the camera gets an address starting with “169.254…”. In this case it is required to reconfigure the network interface to a static IP. Right-Click the network adaptor and select “NIC Settings”\
* In the window “NIC Configurator” click “Internet protocol properties” to access the Windows network settings. Change to static IP setting and enter an appropriate IP (e.g. 10.0.0.1 / 255.0.0.0 for a point-to-point connection). If the network already is set to a fixed IP, you can skip this step.\
\
Terminate everything with “OK” and “Apply”.
## **Notes about Multi-Camera usage:**
* In MVS, when switching between cameras views, stop acquisition on the previous first or you will have bandwidth error warnings.
* In VIOSO MRD window (Model View Control) you might not see the camera full name in the dropdown menu. To check if it’s the right camera assigned, open the MRD file you created in a text editor. It is in XML format where `defCamName` parameter refers to the camera that calibrated the selected compound.
* Optional tip: It can be helpful to fix camera custom names in MVS (Right Click the camera > Rename User ID ). They will appear in VIOSO under “adjust camera > Options > Camera info”
# Configuring IDS Imaging Cameras
Legacy calibration kits, delivered until 2022
Legacy VIOSO Calibration comes with the camera body, a suitable lens, and a PoE-Injector for running the camera on any switch or directly from the PC/server.
## Overview about Calibration kits based on IDS cameras:
The following instructions apply to camera kits with a body from “IDS Imaging”:
| Calibration Kit | Description | Camera Body | Interface | Sensor size | Resolution | Lens |
| --------------- | -------------------------------- | ----------- | --------- | ----------- | ----------- | ---------------------------------------------- |
| CK\_FDU | Fulldome Calibration Kit USB | IDS uEye CP | USB 3.1 | 2/3” | 1920 x 1200 | 360° x 185° fisheye |
| CK\_FDY280 | Hyperfisheye Calibration Kit USB | IDS uEye CP | USB 3.1 | 1/2.3” | 4912 x 3684 | 360° x 280° fisheye |
| CK\_WQ95/XX | Super HQ Calibration Kit | IDS uEye CP | GigE | 1.1” | 4104 x 3006 | 95,70° x 78,70°
…
16,10° x 12,10°
**(a) PoE (Power Over Ethernet)/DATA:**\
Connect the camera to this socket (this will power the camera and a small light will flicker).
**(b) DATA:**\
Connect the Ethernet cable to the PC/server or to a switch.
{% hint style="info" %}
The camera requires a stable 1Gb/s ethernet connection. 100MB/s won’t work!
{% endhint %}
{% hint style="info" %}
We strongly recommend running the camera directly to the PC. Therefore, VIOSO servers usually come with 2 dedicated Ethernet ports. Please note that during calibration the camera creates a large amount of data, occupying the whole network bandwidth and therefore should not be shared with other network based applications (e.g. remote access).
{% endhint %}
### 2. Install IDS U-Eye Software
1. Download: [uEye 49610.zip](https://download.vioso.com/drivers/ids/uEye%2049610.zip)
2. Install driver
### 3. Network configuration
After installing and rebooting, you will be able to use the **IDS Camera Manager to co**ntrol the basic network settings of the camera.
#### IDS camera manager main window
If you see a yellow icon on the top of your window next to your camera, there has been an error (The error warning will be in red on the bottom of the window).
### uEye cockpit main window
Digital SLR cameras made by Nikon or Canon can be used for calibration, connected with a USB cable.
For this purpose, the camera has to operate in the *web-camera mode*.
While some cameras have this mode in their firmware, most cameras do not , so a different third-party software can be used for this conversion:
* 
These days, there are a lot of IP-cameras provided with the software that can stream a video using the Directshow framework, which is required for VIOSO Core.
In this case, this type of camera can be used for calibration (For example: AXIS ip-cameras and its AXIS Streaming Assistant).
If there is no such software provided by the camera manufacturer, you can use this converter:
optical blending mask in front of a projector lens
soft edge is physically achieved by blocking the light path, thus avoiding visible seams on dark contents
7. The activation key now is done and the license is locked on the PC.
8. Click “Finish” to close the the Activation Wizard.
9. The application automatically starts up. With such an activated license, the Licence Wizard is not shown anymore.\
[Learn here how to retrieve information about the current license state](https://helpdesk.vioso.com/knowledgebase/retieving-license-information-of-vioso-6-exaplay/).
## Common Errors
### License not matching
This error happens mainly of this reasons:
1. When using the webform 
VIOSO is actively developed and provide several releases per year. Your license is not restricted to a certain software version, but yields a certain maintenance period. During such an active maintenance period, you can install and use any update of the software, that is published.
Before you run an update, you should check if your license is eligible for an update.
### Find updates automatically
The most easiest way to retrieve an update for VIOSO is using the integrated License Wizard. Learn more about this procedure here: [#find-updates-automatically](#find-updates-automatically "mention")
### Get current maintenance status
If the computer running VIOSO is not online, you can retrieve the current status of the maintenance using our Licence Self-Help portal.
* Retrieve your activation key: [License information](/preparation/deployment/licensing/license-information#id-192933828-th9te6)
* Visit our License Self-Help: Requires a permanent or demo license;
The license must provide the total number of projectors (=sum of all projectors from all participating PCs)
Requires a permanent or demo license;
The license must provide the total number of projectors (=sum of all projectors from all participating PCs)
Your test pattern is ready to use!
Offers all advanced software features:
Limited functionality:
More complex operation:
VIOSO 6 in project Mode
VIOSO 6 in Free Mode
Main user interface of VIOSO 6.1
| Application | Location of SPSurDef.ini | Port |
|---|---|---|
| VIOSO | C:\ProgramData\VIOSO\VIOSO6\ | 8317 |
| VIOSO Pixera Module | C:\ProgramData\VIOSO\VIOSO6_AVStumpfl\ | 8317 |
| Digital Projectin Advanced Align | C:\ProgramData\VIOSO\VIOSO6_Digital Projection\SPSurDef.ini | 8317 |
| VIOSO Anyblend | C:\ProgramData\VIOSO\Anyblend5\ | 8080 |
| VIOSO Player | C:\ProgramData\VIOSO\VIOSOPlayer\ | 8080 |
| AV Stumpfl Autocal | C:\ProgramData\AutoCal\ | 8080 |
| Custom | select | 8080 |
### **1.2. Notes**
* You can click on an added display in the list and `Rename`, `Delete`, and `Split`.
* The `Reset` button re-initialize the configuration and starts over from scratch.
* Click `Apply` before exiting the Abstract Display Configurator to save this configuration.
* Restart VIOSO
## 2. Manual configuration
This is the most basic way and requires more time, but it’s suited to repair an existing Abstract Display configuration in case of failure.
Open the `SPSurDef.ini` file located in the software\`s main configuration folder. Contents of a “`SPSurDef.ini`” file:
```
* `posX posY sizeX sizeY` represent the display coordinates and resolution of the remote projector. You can type this data from your knowledge of the setup or retrieve them with this method:
* Open a browser and enter the following link using your corresponding client IP address :\
`http://192.x.x.x:8080/info.htm?displays&fmt`
* The result is shown below, you can use the Size (x,y) and Position (x,y) to fill out your `SPSurDef.ini` file parameters
Switch to project mode
drawing area of the Designer
If you use a control monitor, insert it and connect it to your graphics card's right output.
### **Projector**
All projectors to be calibrated must be inserted and the properties can be entered, although these do not initially affect the calibration.
### **Camera**
###
A network switch allows multiple cameras to be connected to a single server.
A switch node should also be created if a computer has multiple network cards, as it allows the active adapter to be selected.
Otherwise, it's not necessary to add a switch note to a design.
### **Projection surface**
The choice of surface determines the calibration process. You can choose between 2D, where the calibration must be manually adjusted to the screen, and 3D, where a 3D object is added to the calibration.
The 3D object compensates for any distortion of the screen in advance and then requires minimal correction.
The 3D object compensates for the distortion of the screen in advance and then requires only minimal manual warping afterwards, maintaining a good linearity.
For some basic geometrical surfaces a 3D object generator is available:
Flat surface
If you have selected a specific profile, these export settings will be pre-configured.
### **Eyepoint**
You can export views from a 3D calibration result. Each view represents a frustum calculated for the corresponding projector (Field of view, position and orientation). By default, the reference for this calculation is an eyepoint located in the origin of the 3D model representing the (0,0,0) point. If you would like to offset this position (e.g. for a driver's pose, co-pilot seat, high platform..etc) you can use the **eyepoint node** to set the offset values and connect it to the export node.
Note: This eyepoint node is only used for simulators with a static eyepoint integration (e.g. Prepar3D, DISI). For dynamic eyepoint plugins (e.g. Unreal, Unity, rFpro) the eyepoint position can be defined at runtime or in the VIOSOWarpBlend.ini of the host application
### Connecting Nodes
The nodes must be connected to each other. The connections must correspond to the actual conditions.
* Network Connections between: Computer Switch Camera
* Video connections between: Computer, Monitor, Projector
* View Connections between: Projector, Surface, Camera, Eyepoint
## Toolbar
A central toolbar helps with the navigation and view of the designer:
| 
## Multiclient Setup
It is possible to create multi-client setups in the Designer. To do this, all servers involved should first be prepared. This means that the same version of VIOSO is installed on all clients and set to run in "Client Mode". The network must be configured and all clients must be available withing the same network.
When everything is ready, you can start adding the first Client in the Designer. If everything is configured correctly, all the clients will now appear with their IP in a drop down menu where the appropriate devices can be selected. The software recognises the graphics card settings and creates the client in the Designer accordingly.
Once all the required Clients have been inserted, the projectors need to be added. All ports are then connected according to their use. The clients to the network and projectors, and the projectors to the surface.
## Finish Design
A typical setup may look like this:
System ready for calibration
Split setting examples
Grid/Arbitrary required, because because the outer lines of the projectors are part of the blend zone on all sided
Setup with horizontal blend only to increase blending quality
This camera (a Logitech C930e) has a best match of resultion and framerate when using 1920x1080 @30 fps
Adjust at Exposure and other settings. Do NOT check "Auto"!
Find settings that provide a bright, but constrast-rich overall image
Adjust the White Balance . Do NOT check "Auto"!
All parameters are available in a large parameter tree, that can be filtered by categories and complexity (“Guru”, “Beginner”…). Though all parameters seem accessible, it is not recommended to do much changes here, because of a bad user experience:
> Since the usability of these dialogs is challenging, we recommend to make these settings in the MVS application.
**Notes about Multi-Camera usage:**
* In MVS, when switching between cameras views, stop acquisition on the previous first or you will have bandwidth error warnings.
* In VIOSO MRD window (Model View Control) you might not see the camera full name in the dropdown menu. To check if it’s the right camera assigned, open the MRD file you created in a text editor. It is in XML format where `defCamName` parameter refers to the camera that calibrated the selected compound.
* Optional tip: It can be helpful to fix camera custom names in MVS (Right Click the camera > Rename User ID ). They will appear in VIOSO under “adjust camera > Options > Camera info”
# IDS Imaging
# Others
# Camera Masking (Region of interest)
For all types of cameras the procedure to define a Region of Interest by creating a mask is identical. The masking tools are integrated in the camera adjustment dialog
Whenever new projector masks are created or edited, the mask tool described below is used. It consists of a drawing area (A) , an area that contains mask layers (B) and a list of tools (C). It is possible to create multiple shapes and thus generate complex masks.
| Select drawing point | |
| Add point to shape | |
| Delete point from shape | |
| Toggle between linear and spline based shape drawing | |
| Insert rectangle shape (replacing existing shape - careful!) | |
| Insert round shape (replacing existing shape - careful) | |
| Display a helper grid | |
| Display a helper crosshair |
| Toggle layer visibility | |
| Toggle layer black/white | |
| Invert layer | |
| Delete layer |
projection without masking
projection with added digital mask on each projector
typical shape of such mask on a single projector
native projection
cropping masks applied to uniform the blending regions
Save each cropping mask for later use
After each projector scan, these cropping masks are then applied
Accessing the projector adjustment dialog
| Toggle layer visibility | |
| Toggle layer black/white | |
| Invert layer | |
| Delete layer |
most likely the noise filter threshold is wrong
Sample of a good scan using flat screen mmode
Bad scan - distortions visible
good scan
Example of a bad scan
| Purpose | |
|---|---|
| Detection of possibly invalid points | How strict the algorithm is in the decision of valid/rejected points (blue vs red) |
| Extrapolation method | The software is able to extrapolate to regions of the screen where the camera was not able to scan.
|
| Extrapolation distance | The more dots are chosen, the more the software tries to extrapolate. If you choose “Whole Display”, the software will try to extrapolate to the full display space. In case of a bad scan, the extrapolation might cause artifacts like swirls and deformed areas. The region of interest is an important aspect, if a projector is covering only a part of a screen, there is no need to extrapolate more than that area, therefore increment the extrapolation distance until you fully cover it |
| Surface curvature | If your surface has an extraordinary curve (slight or strong) you can get better results from switching between these options. |
| Intense overshooting of projector | Optimization of setups with an intense overshooting of the projectors |
| Optimization of Mesh | Pre-configured optimization of the texture distribution, enabled by default. Turn off if you notice strange patterns. |
| Crop Mask | An image file (.png or .bmp) that crops the geometry scanned and removes it entirely from the result. Example: you can load a projector mask with cropped borders to reduce the blending area size. Crop masks are created before scanning. Read more here: /pages/KrFmZbXOUwiAqYsYGqoH#creating-cropping-masks |
| Test image | Change the displayed test pattern with a custom image, e.g. load a 4k/6k grid to view higher details in the results and spot possible issues. |
| Save scan data | Save the result of this projector geometry scan in a file (.bdi). Use for backing up, comparing results or load during re-calibration. |
| Parameter | |
|---|---|
| Test image | Change the displayed test pattern with a custom image, e.g. load a 4k/6k grid to view higher details in the results and spot possible issues. |
| Save scan data | Save the result of this projector geometry scan in a file (.bdi). Use for backing up, comparing results or load during re-calibration. |
Typical example of a panoramic screen - projection warped in 2D to fit the outline
Typical example of 3D Mapping to ensure perfect linearity of the content
 | Select camera |
 | Switch the sensitivity for keyboard interaction (arrow keys) |
 | Move camera |
 | Rotate camera |
| Select camera |
 | Toggle arrow key mapping tool |
 | Pan view |
 | Rotate view |
 | Zoom view |
 | Reset view |
On the left are the axes for controlling rotation, on the right are the axes for movement.\
By selecting the axes, the arrows change the corresponding values. The axes are also displayed in the arrows.
#### Tools to adjust the camera
| Move camera |
| Rotate camera |
| Toggle arrow key mapping tool |
A screenshot of the camera taken at the start of the calibration can be found in the project folder under Content. Click `Browse` to select this file (`Camimg_[camera name]`) and `Open`.
Warping grid accessible behind the "3D Align" window
| Name | Select your 3D model from the list of created custom content spaces |
| Texture | If there is a custom texture that you would like to apply to your model, click ‘Select’ to browse an image from the disk. The default models created by VIOSO will have the texture file automatically created and filled in this field. |
| Quality | slider to increase/decrease the preview quality of the rendered texture |
| Name | Name of the camera. from V5.3+ it is automatically selected |
| Type | Type of the lens (Perspective or Fisheye) |
| Resolution | Resolution used by the camera during the calibration, if you did any cropping or ROI define here the final pixel space used. From V5.3+ it is automatically detected |
| FOV | Refer to the lens specifications, Values are usually for perspective (50-110) & fisheye (180-185) |
| Border px | If the camera has a lens that crops some areas of the sensor – fill out the dimension of the border of cropped pixels. It’s most frequently used with fish eye lenses – around 250px |
| Ratio | Resolution X/Y , usually automatically calculated |
| Origin: | Translation values: (Y up, X right, Z backward) |
| Rotation | Rotation values (X pitch, Y yaw, Z roll) |
Fisheye calibration camera view
| Tool | Description | Shortcut |
|---|---|---|
 | Undo (CTRL+Z) Undo an action. If you want to undo multiple actions, click multiple times | CTRL+ZCTRL+Y |
 | Toggle scaling / deformation mode Scale or deform one point or all points | |
 | Toggle pan / move mode Pan the entire working area or move the entire warping grid | INS |
 | Toggle line grippers Inserts a gripper between warping points moves a vertex between two points | F2 |
 | Toggle tangents Adds a tangent to the selected point. Tangents let you adjust the curvature in case of bicubic warping | F3 |
 | Keyboard fine or coarse points Use the arrow buttons on the keyboard to move a point, small or wider spaces | F4 |
 | More columns Adds a vertical column | F6 |
 | Less columns Erases a vertical column | F5 |
 | More rows Adds a horizontal row | F8 |
 | Less rows Erases a horizontal row | F7 |
 | Toggle linear/bicubic interpolation Linear: warping is based on straight lines between points Bicubic: warping is following a curved path between points | |
 | Show undo stack Displays a list of warping modifications, go back to a past point in your warp |
| Case 1
The sides of the projected image are different lengths, e.g. projectors are angled laterally. Drag the red corners to the smallest size of the projected image.
| | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | |  |Case 2
The upper and lower sides of the projected image are different lengths, e.g. projectors are tilted vertically. Drag the red corners with the mouse in order to straighten the sides.
| |  |Case 3
The projected image is larger than the projection surface, e.g. projectors are too far away from the surface. Drag the red corners to the size of the projection surface using the mouse.
| |  |Case 4
All 4 sides of the projected image are different lengths, e.g. projectors are tilted laterally and vertically. Drag the red corners as shown in the illustration.
| ## Arbitrary Warping In addition to the 4-point warping functionality, the warping feature supports nearly unlimited complexity of screen shaping and content mapping. By increasing the number of control points, complex warping grids can be established.
* **Interpolation method:** Here you switch between linear and cubic support point interpolation. Linear interpolation is suitable for corners, edges, etc., while cubic interpolation is suitable for rounded surfaces. Cubic interpolation is the default.
* **Load/Save:** Use thise features to save the current warping into a file (\*.vc). Such a saved warping can be applied any time on the same calibration or another calibration.
# Blending & Global Adjustments
## Overlap & Content Size
After completing the scan, VIOSO automatically calculates the overlap zones where projections from different projectors intersect. This calculation is crucial for eliminating visible seams or inconsistencies in the projected image.
The result of this calculation can be viewed after blending calculation (button `content info`) or when editing the result (button `More ...` and then `Calculate optimal content size`):
Overlaps for the blending is calculated automatically
Example of a bad blending result - mainly because of different projector color reproduction
Figure 1: Diagram showing relation between of pixels between projector 1 (smaller pixels) and projector 2 (bigger pixels)
Figure 2: Usage of texture based blacklevel uplift
Figure 3: Activating region based blacklevel before scanning
Figure 4: Conversion task for region based blacklevel (standard quality in camera space)
Figure 5: Adjustments for region based blacklevel compensation
Figure 6: Conversion task for region based blacklevel with highest quality (projector space)
Figure 7: Conversion task for manual blacklevel regions
Figure 9: access manual blacklevel region handling
Figure 10: manual blacklevel region handling
Figure 11: mouse and keyboard interaction for the manual overlap region handling
**1.3.1. Jump to first item:** Adds a contonl item that executes a jump to the first item on the playlist.
**1.3.2. Pause item:** Adds a contonl item that makes the playlist pause at this item.
**1.3.3. Stop item:** Adds a contonl item that stops the playlist and will start from the first item.
4. **Add model item:** Add an MRD item (Model Render Display) to use for 3D Mapping
### Media Item Options
Ricght-click a playlist item to access the context menu with options for this media item:
all export parameters in the "generic" profile in project mode
| Format | Description | Compatible with 3rd-party applications |
|---|---|---|
| VIOSO VWF | VIOSO’s export file definition | Exaplay AV Stumpfl Pixera 1 and 2, AV Stumpfl Wings and WingsRX, IOVERSAL Vertex, Derivative Touchdesigner, vvvv RSA Cosmos Sky Explorer Shira Player, Shira Universe |
| MPCDI | Vesa’s standardized Warp&Blend file definition | Dataton Watchout v6 and v7, 7th Sense Delta Green Hippo Bright Sign |
| DirectX .x-Files | Generic pixelmapping format of DirectX | Christie Pandora’s Box |
| Barco Pulse | Barcos warp & blend definition for Pulse-enabled devices | Barco projectors supporting Pulse |
| Barco MIPS | Barcos warp & blend definition for (legacy) warp&blend devices | Barco WB Boxes |
| SCISS/Zeiss SGC | Warp & Blend definition for SCISS Uniview | Uniview 3.0 and above |
| OpenWarp | Warp&Blend definition for eyevis OpenWARP2 devices | eyevis OPenWARP2 |
| Open EXR | ILM’s warping & blending definition |
{% hint style="info" %}
Only single client and single surface calibrations are supported to be embedded into the Windows Desktop via project mode.
{% endhint %}
### 3. Setup the project design nodes
You can setup the different nodes for the project: projectors, surface type, camera..etc
Make sure that the computer node shows a proper splitted Mosaic group. The split should be detected automatically by VIOSO - if not, this might indicate that something isn't properly set up and therefore will lead to issues.
In this preset, there are extra main options to customize:
| Option | Method | Parameters | Screenshot |
|---|---|---|---|
| Overlap type | Select the server node. Find the “Desktop Warp Parameters” section. |
| |
| Activate parameter | Click on the node from the layout to expand its parameters |
|  |
Example: Project Design for 2x projectors with Nvidia mosaic
| Logo | Engine | Version | Level of Integration | How it works |
|---|---|---|---|---|
 | Unreal Engine | v4.26+ |
| |
 | Unity 3D | SRP, HDRP, URP v2018+ |
| |
 | MiddleVR for Unity | v2.0+ |
| |
 | Techviz | v5.10+ |
|
5. `VIOSOWarpBlend.ini` Configuration:\
Open `Assets\Plugins\vioso\VIOSOWarpBlend.ini`Add the parameters for your cameras as shown below:
```ini
[default]
logLevel=2
base=[1000, 0, 0, 0; 0, 1000, 0, 0; 0, 0, -1000, 0; 0, 0, 0, 1]
eye=[0,0,0]
near=0.15000 ;the near plane clipping distance
far=10000.00000 ;the near plane clipping distance
bAutoView=1;
autoViewC=1.00000 ;
bTurnWithView=1
bBicubic=1
bDoNoBlack=0
;Path for the calibration file exported from VIOSO. Absolute or relative to the .dll path
calibFile=Export.vwf
;Camera name in Unity
[cam1]
calibIndex=2
[cam2]
calibIndex=1
[cam3]
;optionally you can assign here a different calibration file. e,g calibFile=export_2.vwf
calibIndex=0
```
* `calibFile=`: Name of .VWF file(s).
* `name`: Name of the **Camera GameObject** in Unity.
* `CalibIndex`: Assign the Index of the mapping inside the vwf (0,1,2..).
> Full list of .ini file parameters: [Broken mention](broken://pages/z7Wvgl5h0bKFU0e1G0ky)
Example of additional parameters:
* Add your **Pivot Point** coordinates for a moving platform by editing the highlighted X,Y,Z parameters of the **base** matrix as shown below:
* `Base = [1000, 0, 0,0; 0, 1000, 0, 0; 0, 0, -1000, 0; X, Y, Z, 1]`
* `(X,Y,Z)=(0,0,0)` being the center of the projection screen.
* Enable Dynamic Eyepoint by setting `eyePointProviderParam` to listen to a specific port using UDP protocol (i.e = port 999)
6\. The Integration is now complete. You can preview it by running the player and switching between displays (see note 2 below). If everything looks good, **Build** your project.
7\. Copy the `vioso3d.vwf` and `VIOSOWarpBlend.ini` files from Unity **Assets/plugin/vioso** to folder **\[your\_build\_path..]/\_data/plugin/** next to `ViosoWarpBlend.dll`.
8\. Launch your application and you should see your calibration active on the displays.
### In Unity3D (HDRP/URP)
Download the package from our Github and follow the instructions in the Readme.md
> **– HDRP**: 
The configuration parameters are detailed in the table below:
| Type | Parameter | Description |
|---|---|---|
| VIOSO | VIOSO type |
|
| VIOSO | file |
|
| VIOSO | Units in Meter | The units of the 3D model used in the VIOSO calibration. By default VIOSO’s own models are inmilliliters, so units in meter = 1000 |
| VIOSO | Calib index | Index of the mapping inside the calibration file, in case several projectors are exported to a single file |
| VIOSO | origin | The ID of a [scene_node] that defines the origin for the projection screen. This maps the frame of reference defined in the calibration to the virtual space in your Unreal Engine Level. Defaults to the origin of the 3D model used in the VIOSO calibration.You can use this node as an offset to position the projection screen in the 3D scene. |
| VIOSO | Enable Preview | Renders the VWF mesh in the editor viewport preview. |
| MPCDI | pfm | Geometry file exported in the VIOSO mpcdi folder |
| MPCDI | png | Blending file exported in the VIOSO mpcdi folder |
| VIOSO / MPCDI | View Origin | Origin of the viewing frustum. You can use this as an eyepoint node, to allow static/dynamic perspective correction. |
beta
x
available from v5.3.1+
2D
& 3D available from v5.3.1+
automatically masked from the warping result
adjustable in the nDisplay config file
Recommended=2
adjustable in the VIOSO export window
Recommended=2
[default]
logLevel=2
bLogClear=0 ;clear log file on start
base=[1000,0,0,0; 0,1000,0,0; 0,0,1000,0; 0,0,0,1] ; frontal cam left handed, row major, most DX
near=0.15 ; the minimum rendering distance, all faces closer than that are culled
far=20000 ; the maximum rendering disctance, all faces futher than that are culled
bTurnWithView=0 ; set to true, if moving platform alas world turns with view direction
bicubic=0 ; set to true to enhance sampling acuracy, will use up some extra GPU
calibFile=C:\Users\Public\Documents\VIOSO\VIOSOPlayer\Export\MyCalib.vwf
autoViewC=1 ;widen FoV to cover a range of autoViewC * screen
bAutoView=1 ;overwrites screen fov and dir
[Channel_1]
calibIndex=0
2. Enter the configuration file and channel name. You can find a template of a .ini file in `MiddleVR2/data/Vioso_MiddleVR_Template.ini`\
3. Assign the warper to a Camera\
4. Your VIOSO calibration is now integrated.
* Go back to the **APPS** tab and click on **RUN**.
### 3. Middle VR 2.0 (Legacy)
> For older versions of MVR, please follow our old helpdesk doc. Calibrate the projectors in either in:
[default]
;; Specify the full path to your VWF file
calibFile=C:\file.vwf
;; Specify the base matrix, that may vary depending on your display setup
base=[1000,0,0,0; 0,1000,0,0; 0,0,1000,0; 0,0,0,1]
;; Specify the channel indices, for as many channels as the VWF file contains
[A_left_eye]
calibIndex=0
[A_right_eye]
calibIndex=0
[B_left_eye]
calibIndex=1
[B_right_eye]
calibIndex=1
[C_left_eye]
calibIndex=2
[C_right_eye]
calibIndex=2
;; If you want debug logs:
; logLevel=3
; logFile=C:\file.log
3\. If you’re using an AMD threadripper CPU, you might encounter save issues. To solve this, go to Options / Settings / File Options and untick the checkbox “save compressed”
# Barco PULSE
VIOSO software can export warp and blend files in the Barco pulse format. It consists of an **XML file (warping grid)** and a **PNJ (blend image)** that are automatically generated for each calibrated projector.
## Project Mode
1. Create a new project with the “**Pulse**” template\
2. In the Design step, replace the name of each projector with its **IP address**\
3. Proceed with the regular calibration steps, and at the end your export button will automatically transfer the warp and blend files over network to the projectors.
## Free mode
#### Manual export – upload
From the main VIOSO window, go to `File > Export Mapping`\
Choose the format Barco Pulse from the list and export your file.
Next, you can upload the files using the Barco web interface or projector toolset.
#### Scripted export – upload
You can use VIOSO export scripts to automatically generate the files and transfer them on the network. Optionally you can also add conversion tasks and temporary files. Example:
```
3\. If you’re using an AMD threadripper CPU, you might encounter save issues. To solve this, go to Options / Settings / File Options and untick the checkbox “save compressed”
# Norxe
VIOSO software can export warp and blend files in the Norxe Unify format. It consists of an MPCDI file generated for each calibrated projector, which contains a **PFM file (Geometry), PNJ image(s) (blend + blacklevel maps )** and an **XML (parameter definition).**
## Project Mode
1. Create a new project with the “**Norxe**” template\
2. In the Design step, replace the name of each projector with its **IP address**\
3. Proceed with the regular calibration steps, and at the end your export button will automatically transfer the warp and blend files over network to the projectors.
## Free mode
### Manual export – upload
From the main VIOSO window, go to `File > Export Mapping`\
Choose the format **Norxe Unify** from the list and export.
Next, you can upload the files using the Unify interface.
### Scripted export – upload
You can use VIOSO export scripts to automatically generate the files and transfer them on the network. Optionally you can also add conversion tasks and temporary files. Example:
```
# VIOSO WarpBlend API
## Overview
VIOSO offers a library for integration in image generators and rendering/media engines. Its main features are:
* Warping: apply geometric correction and distortion compensation.
* Blending & masking: apply soft-edge gradients and black-out masks.
* Automatic view calculation: set the direction & field of view of each virtual camera based on the calibrated mesh.
* Perspective correction for static/dynamic eyepoint: supports dynamic views and warping per frame, for VR, tracking, motions platforms, etc.
The API takes as input a .vwf export file and a texture buffer to sample from. If no texture buffer is given, it uses a copy of the current back buffer. The output is rendered to the currently set back buffer.
The API is available on Github:
{% hint style="info" %}
integrated &
standalone workflow