Export to any application
Last updated
Last updated
While VIOSO’s proprietary file format *.sps holds all calibration information, the data required to embed warping and blending into the Windows operating system or GPU must be handled differently.
Therefore, a secondary file format exists: the “VIOSO Warp File” format *.vwf. We use this file format, not only to address the embedding services of VIOSO Anyblend, but also to export to third party applications using the VIOSO API.
OEM builds of VIOSO 6 (e.g. for Pixera or Ioversal) produce VWF files that are only readable by the OEM application.
To do an export, finish the calibration.
Whenever you create a project, there is an export node in the project designer. Depending on the profie, the values for the export are pre-populated accordingly and parameters are filtered for easier handling.
The "generic" profile provides access to all export parameters. It's the choice of the operator to make use of them.
To run the export, you have to complete a calibration. Once this is done, the step Export is available. Clicking Export will immediately initiate the export sequence and run the export using the values and parameters specified in the Design step.
In free mode, the export can be done anytime by calling Menu > File > Export Mapping:
The operator decides about the appropriate moment to export, as well as to do the appropriate export settings:
Exporting is heavily depending on the target system. There are numerous ways to create export files, and it is part of VIOSO's ongoing effort to export to as many target systems as possible. We describe the main export formats and parameters in this documentation.
For target systems that are not listed here, please refer to our support - we are happy to analyze and adjust to every possible configuraion
| 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 |
As the export is the last step in a calibration procedure, we provide a recalibration script generator at the export dialog:
With a few parameters specified it creates a script that re-runs the calibration procedure without interaction and performs the export as specified before.
Parameters to specify for a recalibration script:
Script file: the location where the script is saved. We recommend to stick to the VIOSO 6 default path Documents\VIOSO6\Scripting as this will make running the script very easy (see below)
sps file: Select the SPS file where the currently used calibration is saved
Close application: when checked, the script will close VIOSO 6 after running the recalibration script. This is useful if you do not want to expose VIOSO 6 to the end user
With Export: Keep always checked, as this setting will enable the export according to the current settings
Create Batch file: When checked, after performing the calibration, a Windows Batch file *.bat is created at a user-specific location (you're prompted) that runs the recal script.
There are numerous ways to shape a calibration export. This is handled by a “scripting-like” method, where parameters are collected and stored in an XML-File. We call this the “export definition file”.
An Export definition file is created as soon as you check the box use settings from file and click edit. After that the system default text editor oens with a skeleton of such an export definition file.
Learn here how to handle export definitions and available functions and parameters: Export Automation Reference
