Contact Us
You may encounter some issues when updating from version 1.8. If you need assistance during the process, you can contact our support team.
This guide describes potential problems that may occur when updating from version 1.8. It also highlights several important points to consider during the update process.
Warning
This process cannot be completed using only the project file. It must be performed on the system where the project is running.
Potential Issues to Watch Out For
When opening or migrating a project, several things can go wrong:
- Mappings lost – These can usually be restored by following a specific workflow (see below).
- Screen groups changed – This may lead to incorrect distribution or reduced performance. Screen Groups
- Audio settings lost – Audio configuration may need to be redone manually.
- Control license changes – Certain modules may become deactivated or blocked from external connections. PIXERA Control New License Structure
- Art-Net pixel mapping outputs lost – These can be recovered by recreating the mapping with exactly the same name as before.
- Control Project name - This needs to be a valid Lua expression starting from 2.0, if not than it will break the lua core.
- Tracking inside Control - Due to a change on handling API paths there is the risk that API commands used inside Tracking Modules do not work anymore and throw strange errors. This can be corrected with a tweakconfig file and "controlUseAbsolutePathInRefs": false
- Input card driver and compatibility to PIXERA Deltacast Update Guide
Restoring Mappings After an Update
Before proceeding, always create a backup of your original v1.8 show file.
Steps
1. Open the project in version 1.8
○ Take a screenshot of the hardware naming and Art-Net streams.
○ Note down the graphics card names.
§ In v1.8, they should appear with their actual hardware names (e.g., “NVIDIA RTX 3080”).
§ Once opened in v2.0, these names will automatically change to generic labels such as “Graphics Card 1”.
2. Open the project in version 2.0
○ Manually rename the graphics cards back to their original hardware names.
○ Do not save the project at this stage.
3. Reload the same project file
○ Go to File → Open Recent and select the same file.
○ When Pixera asks whether to save changes, choose “No”.
4. Verify mappings
○ After reopening, your outputs and mappings should be restored.
Compatibility
This workflow has been tested and confirmed to work for Pixera v2.0 and v25.1.
It is expected to function similarly for more recent versions as well.
PIXERA 25.2 R 4 | 15. October 2025 | J.B.