> For the complete documentation index, see [llms.txt](https://docs.vioso.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vioso.com/integration/projectors/barco-pulse.md).

# 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 <a href="#id-1209060696-ij3wej" id="id-1209060696-ij3wej"></a>

1. Create a new project with the “**Pulse**” template\
   ![](https://helpdesk.vioso.com/wp-content/uploads/2023/09/barcopulse-1024x443.jpg)
2. In the Design step, replace the name of each projector with its **IP address**\
   ![](https://helpdesk.vioso.com/wp-content/uploads/2023/09/BarcoPulse2-1024x804.jpg)
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 <a href="#id-2092867227-ajz5n2" id="id-2092867227-ajz5n2"></a>

#### Manual export – upload <a href="#id-1241176298-ww7y3u" id="id-1241176298-ww7y3u"></a>

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 <a href="#id-1305654058-2qv71y" id="id-1305654058-2qv71y"></a>

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:

```
<?xml version="1.0"?>
<VIOSO>
<File version="1.0.0" />

<CalibCommerceTask Typ="export" Format="vwf" >
<CommonParam bSilent="0" bNoVC="0" bNoGeomCorr="0" bNoBlending="0" bNoMask="0" bSeparatedSplitDisp="1" bAllToMaster="1" bBlankUnusedSplitDispParts="0" bExactFileName="0"
FileName="tempFile" />
<SpecialParam qGridDimX="21" qGridDimY="21" />

<Task Typ="convert" Format="observer conversion">
<SpecialParam customCntSpaceName="*" />
</Task>

<TransferTask Format="PULSE" Device="D5 FL40-WU MKII (BPS0E0B)" Core="192.168.1.100" >
<Destination Core="192.168.1.130" />
</TransferTask>

<TransferTask Format="PULSE" Device="D7 FL40-WU MKII (BPS0E0B)" Core="192.168.1.100" >
<Destination Core="192.168.1.131" />
</TransferTask>

<TransferTask Format="PULSE" Device="D6 FL40-WU MKII (BPS0E0B)" Core="192.168.1.100" >
<Destination Core="192.168.1.132" />
</TransferTask>

</CalibCommerceTask>
</VIOSO>
```

## Troubleshooting <a href="#id-807027858-oit5k6" id="id-807027858-oit5k6"></a>

1\. If you have issues with the automatic transfer of the files, check the network connection of the calibration machine to the projectors in the browser. e.g: `http://192.168.1.132:9999`

2\. You can debug the exported geometry from the XML file with the SplineTestTool. You can find it in your install folder `\VIOSO6\Shared tools\SplineTestTool.exe`

<img src="https://helpdesk.vioso.com/wp-content/uploads/2023/09/barcoSpline-1024x536.jpg" alt="" height="366" width="700">

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”


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vioso.com/integration/projectors/barco-pulse.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
