Starting with PIXERA 25.2, you can now use a single server to act as a backup for either a Manager or Client machine. Before this feature, you would typically need a dedicated server to back up your Manager and another dedicated server to back up your Client. 

However, while this new feature makes it possible to perform this workflow with just one backup server, you should already be extremely comfortable with Manager/Client workflows, Multi-User workflows, and Backup scenarios before attempting this, as it is only recommended for advanced users, and combines all three of these methodologies.

Methodology

Hybrid Mode combines the concepts of Manager Backup and Client Backup scenarios into a single workflow.

Remember, PIXERA is not just a media server software but a suite of softwares, including PIXERA, Presence, RX, and Control. Behind PIXERA's powerful GUI is PIXERA's powerful Render Engine (RX). Whether you are launching PIXERA or Presence, each of these softwares access the PIXERA Render Engine as a background process to offer you stunning visuals and sophisticated programming.

What that usually means is, either PIXERA is accessing the Render Engine OR Presence is. Now, within Hybrid Mode, PIXERA and Presence can run simultaneously on a single machine so that the PIXERA instance can access RX via Presence - like a Manager/Client workflow, just localized.

System Setup

Before we can set up our Backup scenarios properly, we first need a system in place in which to build off of. For this scenario we will use 3 servers - a Manager, a Client, and a Hybrid server to back up either the Manager or Client in the case of failure.

Using this article as a foundation, we will first build a basic Manager/Client system using two of the servers, ensuring we also have implemented the steps below. 

• Ensure both servers are on a dedicated PIXERA network (confirm the two servers can ping each other)
• Launch Presence on the Client machine (ensuring the Adapter IP is set to the network in the above step, which should match the Manager's Discovery Adapter)
• Create a new PIXERA project on the Manager machine
  • Set the Discovery Adapter to the network adapter used above (may require restart)
  • Add two Displays
    • Name one “Manager” and the other “Client”
• “Start” the Client machine via the Mapping tab
  • Now, you should see two systems with green icons - "Local" and your Client (Here, PX2-21049)
• Assign one of your Local (Manager) outputs to the Manager screen and one of the Client's outputs to the Client screen
  • Then, Activate both outputs
• Add at least two pieces of content to a Timeline
  • Assign one piece of content to the Manager display and the other to the Client display
  • Ensure you are seeing content play out from each machine before moving forward

Manager Backup

On the third machine (soon-to-be Hybrid machine), using the same PIXERA version as the other machines, join the Manager in a Multi-User session. We will refer to this third machine, for now, as the Backup Manager and the other as the Main Manager. Once properly setup, this Backup Manager will be called the Hybrid Backup.

Referring to this article as a foundation, ensure the Backup Manager's Multi-User and Backup settings are as follows:

• Treat Closed Members As Lost
•  Automatically Activate Local Outputs When Member Lost
•  Automatically Take Over Clients From Lost Members

Treat Closed Members As Lost means that when the Backup Manager notices another server in the Multi-User session disappear (either by closing PIXERA's engine or due to loss of communication), it will consider this as a Multi-User Member failing or becoming lost. In this case, when the Main Manager disconnects, it will be registered as the Lost Member.

Automatically Activate Local Outputs When Member Lost means when the Backup Manager registers a Lost Member (as noted above), it will assume responsibility for outputting that Lost Member's local outputs. So if the Main Manager was outputting content via it's GPU, now the Backup Manager will output that same content from it's local GPU.

Automatically Take Over Clients From Lost Members means when the Backup Manager registers a Lost Member (again, as noted above), it will also assume responsibility for controlling playback of that Lost Member's Clients. In this scenario, where the Main Manager disconnects, the Backup Manager would takeover playback control of the Client machine that was once controlled by the Main Manager.

Client Backup

Now, here's where the Backup Manager becomes the Hybrid Backup.

Remember, instead of PIXERA accessing the Render Engine directly, for Hybrid to work, PIXERA needs to access the Render Engine via a local instance of Presence. To do this, on the Backup Manager, navigate to Settings > Discovery and turn on “Use Presence For Local Live System.” Then, restart PIXERA.

Once PIXERA has restarted on the Backup Manager, open Hub on that same machine and click the cog icon next to the PIXERA version you are using. Select “Start Presence.” 

To confirm this machine is available as a potential Hybrid Backup, on your Main Manager, check to see that the Backup Manager is listed as a Live System under the Mapping tab. Select that System and start it's Engine.

To officially make our Backup Manager the Hybrid Backup, we need to follow a Backup scenario, assigning the Backup Manager/Hybrid Backup as a Backup for the Client machine. For this scenario, we will keep it as simple as possible but the article linked above can be followed for more advanced options.

To make this assignment, either from the Main Manager or Backup Manager, select the Client machine under Mapping > Live.

Then, in the Inspector window on the right, find the entry box titled “Usage” and give this Client machine a Usage Preset by typing in a name and then selecting “Update.” This stores the Client's Live System configuration as a Usage Preset, which will be set up in the next step to transfer to the Hybrid Backup in case of Client Engine/communication loss.

Continuing downward in the Client's Inspector, find the “Backup” menu and twirl down it's options.

Populate the “Backup IP” entry box with the IP address of the Backup Manager/Hybrid Backup. Then, set the Usage Transfer Mode to “Copy,” and then select “Configure Transfer.” Doing so will copy the Client's Usage Preset over to the Hybrid Backup in the event of the Backup being triggered.

The Backup Manager has now officially become the Hybrid Backup!

Testing

The most important part of using PIXERA's Backup features is ensuring they work as intended! Please always test your backup system before relying on it for a production.

To test that the Hybrid Backup takes over for the Main Manager, close the Main Manager's PIXERA GUI or “Close” the Main Manager's Engine. If setup properly, the following will happen:

• Hybrid Backup machine will takeover playback of the content from the “Manager” screen, which was outputting locally from the Main Manager, now outputting locally from the Hybrid Backup's outputs
• The Client machine will continue outputting content from the “Client” screen, which was receiving playback commands from the Main Manager, but is now receiving playback commands from the Hybrid Backup. Pause the Timeline from the Hybrid Backup and ensure the content on the Client pauses as well

Once successfully tested, re-open the PIXERA project on the Main Manager and reconnect to the Multi-User session. 

You will notice that the Hybrid Backup still has priority over playback control of the project. To regain control on the Main Manager, you can start, or restart, the Hybrid Backup's Engine and Client's Engine via the Mapping Tab > Live systems tab from the Main Manager. You will be prompted with a pop-up informing you that you are “taking the engine” from the Hybrid Backup/other Manager and asking if you'd like to continue - select “Yes.”  Doing so will give the Main Manager playback control again. Now we are back to normal and can test our Client backup.

To test that the Hybrid Backup takes over for the Client, we can perform the same “mock” failure of the Client as we did for the Main Manager - closing it's Engine, disconnecting the Client from the network, or selecting “Trigger Backup.” In doing so:

• The Hybrid Backup machine will takeover playback of the content from the “Client” screen and will output this content from the Hybrid Backup's local outputs. Playback control will still be coming from the Main Manager

Congratulations! You have successfully setup a PIXERA Hybrid Backup system.

Going Further

If you are interested in taking this a step further, or configuring a larger network of servers, please have a look at these articles:

• Resource Distribution
• Custom Asset Root
• Dry Client Programming

PIXERA 25.2  | 15. September 2025 | R.J.

Inner Loop is a new feature to 25.2 that allows users to program a clip to have a specific section of the clip (set by Free Loop Inpoint and Free Loop Outpoint) repeat, while still having unique sections before and/or after the clip.

Activating Inner Loop-Timeline Based

In order to activate the Inner Loop feature, you first must set your clip play mode to: Free Loop

From there you can set your Loop points under the Clip Timing Properties in the Inspector:

Inpoint: When the nowpointer enters the clip, this will be the starting time of the resource that is playing

Free Loop Inpoint: The “Inner Loop” in point, where the resource will loop back to once it hits the Free Loop Outpoint

Free Loop Outpoint: The “Inner Loop” out point, where the resource will loop back to the Free Loop Inpoint

Outpoint: Where the resource will end once you “exit” the inner loop
 

Exiting the inner loop-Timeline Based

To exit the Inner loop on the Timeline you can use a Pause cue that has “Trigger Inner Loop Outro on Leave” checked

PIXERA 25.2  | 14. August 2025 | MB

Layer Groups is a new feature in version 25.2 that allows the user to group layers together in order to more easily manage their timeline organization.

Create a Layer Group

To create a layer group, right click in the layer heading and then select ‘Add Group’, or click on the ‘Add Layer’ Icon in the Timeline Tool bar and select ‘Add Group’

Add Layers to Group

You can add a layer to the group in a couple of ways:

1- Click and drag a layer (or layers) into the created Group

2- Right click into the Group in the Layer header and ‘Add Layer to Group’

Group Multiple Layers

You can Group Multiple Layers together by shift or control selecting layers in the Layer Header, then right clicking in the header and selecting ‘Group Layers’

Group Inspector

You can rename a group by selecting the group and renaming it in the Inspector. You can also change the color of the group here

Moving Groups on the Timeline

You can select the group in the timeline to move all the clips in the group together. If you select a Clip within the group and move it, it will separate out the Group selection in the Timeline.

PIXERA 25.2  | 24. July 2025 | MB

Quick Overview

Create Mask

Via the context menu, you can go to “Add Resource" and select “Mask”

this will create a new mask resource in you selected directory,

This can be used like any other Resource in PIXERA, as default it contains a square Mask element.

This mask resource can now directly be used in a container on a timeline or in the Mask effect, See → Mask RGB Effect 

To use this mask element and to behave with the expected behavior of a mask, you need to set the clip or layer where it is assigned to, to Blending→Mode→Multiply
 

possible alternative of this is to set the background color to alpha:
 

Modify Mask

Resource Resolution

After the mask is defined in a resource, it must also include a resolution.
 

The size defined here specifies the dimensions of the element on the layer and is used for scaling in cases where different aspect ratios are applied. Subsequently, all layer parameters refer to the rectangular dimensions defined by this resource resolution.

Mask Element

A Mask Resource can contain multiple Mask Elements
These can be edited within the inner compositing.

After selecting the resource, the Mask points can be edited.
 

Background Color

Specifies the background color of the mask. By default, it is white, but an alpha value (transparency) can also be configured.

Mask Color

Allows adjustment of the mask color. When 'multiply' is selected as the blending mode, this enables easy creation of a colored highlight over the area.

Invert Mask

To invert the Mask, you can set the Background Color to Black, and the Mask Color to White.
 

Use Mask in Sampler

The mask generated in Pixera can be loaded directly into the sampler in FX.
 

Limitations

Currently, it is not possible to animate the mask points, but It is possible to animate the movement of the Mask Resource.
Export and Transfer of the Mask resource is currently not possible.

PIXERA 25.2 INTER 30  | 22. July 2025 | J.B.

Projectors, Displays and LED's can have color correction applied via a LUT. It is also possible to update a Screen's color correction in real time, this includes having a brightness value be changeable per display. 

The feature can be found in the Mapping tab by clicking on the Displays and LED's in the workspace. To color correct Projection Screens, you need to instead select the Projectors being used.

In the Inspector's Setup tab, you can find the Color Correction Real Time folder.

Adjust the settings as needed. The Eye will mute and unmute the settings applied from a Parameter. The Reset icon will bring back that Parameter to its default state.

Below the Color Correction Real Time settings, you can find the DMX Patch settings for the real time color correction.

Auto patch will patch all the Parameters to the next available Universe/Channel. Patch Screen will open the DMX Patch window, as described in detail in this article.

API/Control

New API calls are available starting from 25.2 R 3 allowing the Color Correction Real Time values to be changed from outside calls or from Control.

These calls include:

• Pixera.Screens.Screen.resetAllColorCorrections()

• Pixera.Screens.Screen.setColorCorrectionWithPath(string path,float value)

• Pixera.Screens.Screen.getColorCorrectionWithPath(string path)

• Pixera.Screens.Screen.setColorCorrectionAsJsonString(string colorCorrection)

• Pixera.Screens.Screen.getColorCorrectionAsJsonString()

• Pixera.Projectors.Projector.resetAllColorCorrections()

• Pixera.Projectors.Projector.setColorCorrectionWithPath(string path,float value)

• Pixera.Projectors.Projector.getColorCorrectionWithPath(string path)

• Pixera.Projectors.Projector.setColorCorrectionAsJsonString(string colorCorrection)

• Pixera.Projectors.Projector.getColorCorrectionAsJsonString()

If setting the color correction, the path calls are aimed for easier programming usage, although they are less flexible being able to only change one Parameter at a time. The JSON calls are more complicated to program, however they are able to change as many Parameters as desired at once.

RealTimeColorCorrection is an example Module that can be downloaded to see how the set with path call works from Control, it can also be used in itself to Control the settings as a working Module with a UI of Sliders to change the values.

Troubleshooting

• Color correction is not available/Color correction real time is not available.

If real-time color correction is displayed as unavailable, then the Display/Projector must first be assigned an Output.

Pixera 25.2 R 3 | 20 October 2025 | O.K./C.L

How to import/export cues via CSV

Import/Export all cues from a timeline

Create and edit cue lists in Excel, Google Sheets and Reaper. 

Timeline Inspector

The inspector > Cues setting has been extended with two buttons: Import Cues and Export Cues.
 

Export Cues

If you click the Export Cues button, you will get asked which Cue Values you want to export. “Basic” and “All” is available. The "All" setting will export every parameter of the cues while "Basic" holds a limited set of parameters:

Basic File

All File

Basic:

Cue Number

Time (ss:ms)

Label

Note

Color

Operation

Is Active

Timeline Name

Timeline ID

All:

Cue Number

Time (ss:ms)

Label

Note

Color

Operation

Is Active

Wait Duration (ss:ms)

Spontaneous

Triggers Inner Loop Outro On Leave

Exclude From Cue Lists And Countdown

Jump Mode

Jump Goal (ss:ms)

Jump Fade Duration

Timeline To Trigger

Timeline To Trigger ID

Timeline Trigger TriggerMode

Timeline Trigger TimeMode

Timeline Trigger Goal

Timeline Trigger Fade Duration

Timeline Trigger Show

Network Cmd Api Output

Network Cmd Data

Timeline Name

Timeline ID
 

Import Cues

A pop-up will appear on clicking the import cues button. 

Mode asks you if you want to merge the CSV with your current cues on the timeline. 
Replace will remove all existing cues first. 
Merge will add the imported cues to all existing cues.

Destination lets you choose the destination timeline. 

Current Timeline: the one you have currently selected and pressed import cues in the inspector 
Original Timeline (skip if not existent): the timeline that is specified inside the CSV. WIll be skipped if it is non-existent.
Original Timeline 

Workflows/tips:

Google or your favorite AI will gladly create a breakdown of the best possible way to open and convert CSV files in Google Sheets, Excel or Apple Numbers.
Great prompts:
how to open a CSV with Google sheets
how to open and convert a CSV with Excel

Besides the usual suspects, there are countless other CSV Viewers/Editors that can be found online.
 

Reaper Setup (Generated with AI)

To export markers from Reaper, navigate to the Marker/Region Manager, export the markers to a file (e.g., CSV), and then import the file into the desired application. Specifically, set the timeline to HH:MM:SS:FF, open the Marker/Region Manager, right-click inside the window, select "Export regions/markers...", choose a file format (like CSV), and save the file. 
Here's a more detailed breakdown:
 

Set Reaper Timeline to HH:MM:SS:FF

Do this on the top of the Reaper Timeline. Right-click on the top of the ruler area.
The Markers must reflect the HH:MM:SS:FF structure.

Setting the Reaper Timeline FPS 

Go to “File”, select “Project settings”.
In the pop-up window, select “Video”. Now choose your frame rate.

 

PIXERA 25.2 INTER 47 | 04 September 2025 | OK

Disclaimer

Virtual Production is a complex topic. It is mandatory to understand the basic setup to be able to advance to the advanced techniques (For example, Set Extension and Multi-Pos warp).
Furthermore, it is mandatory to understand all the basic principles of PIXERA.

Here is a list of the essential VP related documentation in chronological order:

XR System Design 

Unreal Engine (5.2.1) Setup 

Unreal Engine PIXERA Setup 

Unreal 5.2.1 Tips and Tricks (Performance and Testing) 

PIXERA Connect, an Unreal Plugin - General Usage 

PIXERA Texture Sharing to Unreal 

Studio Camera (Virtual Production) 

Set Extension (Virtual Production) 

Multi-Pos Warp 

Introduction

Starting with PIXERA 2.0, Unreal Engine 5.2.1 can be used as a resource in the compositing tab. 

Prior to starting the setup, please check the following prerequisites:

• Unreal Engine (compositing resource) only works with a Server License or official PIXERA Servers
   
• Unreal Engine 4.27 is NOT working with PIXERA 2.0.
  • In case you are currently working with an Unreal 4.27 Setup please follow the official Epic migration guide:
  • Unreal Engine 5 Migration Guide | Unreal Engine 5.0 Documentation 
     
• Unreal is extremely demanding. We recommend using a dedicated powerful director as well as a playout server (e.g. PIXERA 4RS. In case of a homebrew, we recommend using a RTX A6000)
   
• Download Unreal from the EPIC Games store from this URL: Epic Games Store DOWNLOAD
   
• Install the .NET 4.8 SDK. .NET is a Microsoft platform used to build and run applications. It is open-source, free, secure, reliable, and high-performance. .NET is required when installing and using Unreal. 
   
• Optional for Packaged Projects:
  • Install Visual Studio including following Options (only necessary if you want to package a project):
    • Add Game development with C++ (under Workloads) and following options:
      • C++ profiling tools
      • C++ Address Sanitizer
  • Windows 10 SDK (10.0.18362 or newer)

Unreal Engine Installation Guide

Create an account or log in with an existing account. Navigate to the Unreal Tab and install the correct build version, 5.2.1:

Uninstall unwanted versions by choosing remove. 

Warning

Install Epic Games and Unreal Engine on the D - Drive. When installed on the C - Drive, PIXERA might not be able to access certain files. Furthermore, after a reimage of the system, the installed files will still be accessible.

 

Go to options and change the install options:

 

Unreal Engine Setup

New Project

Start Unreal Engine via the Epic Games launcher. In the welcome menu, select Film / Video & Live Events and open the default nDisplay project:

1: Select Film / Video Live Events

2: Select the nDisplay project

3: Warning: define the correct project location. We recommend choosing the same drive as the installation path.

4: Create project

Warning

Start once and compile shaders:

 

Created Project

If you already have a project and want to make it work inside PIXERA, you will need to manually set up the following for nDisplay.

You must first enable the nDisplay plugin by going to “Edit\Plugins” and activating nDisplay in the “Built-in” section.

nDisplay must now be turned on in the project itself. This can be done by going to “Edit\Project Settings” in the “Plugins\nDisplay” section and checking the Enabled box on.

Lastly, some Unreal Projects, such as the ones downloaded from the Marketplace, may not have a “Windows\WindowsEngine.ini” Directory in their Config folder. If this file is not available, then PIXERA will be unable to open the project. This folder and file can be copied from an Unreal Project that does contain it, such as the nDisplay template project.

Unreal Executable Setup

The “Unreal_Engine_5-2-1” zip contains the engine and should be extracted to wherever desired, usually in the initial C or D directory.

Navigating to “Unreal_Engine_5-2-1\Engine\Windows\Engine\Binaries\Win64” you will find a file which in the same location as other Unreal Engine builds being the “UnrealEditor.exe”. Use this executable to run the engine.

After selecting and opening the project, an Unreal popup will explain that the project should be copied as the Unreal Engine being used is different from what the project was first created it. It is recommended to copy the project and keep this copy available for any rebuilds you may need. Also, this copied project will not open immediately in the vanilla Unreal Engine version, it will instead also ask to copy.

Once the project is open, you can package by going to “Platforms\Windows\Package Project”. The editor will then ask for a location to place the executable. Once selected, the project will begin to be packaged and finish, depending on how large the project being packaged is.

Unreal Multi-User Setup

To run Unreal in Multi-User mode, you must first enable the Multi-User plugin.

After saving and restarting your Unreal scene, navigate to “Project Settings/Plugins/Multi-User Editing “.

“Enable Multi-User Toolbar Button“ and “Auto Connect“ have to be enabled.

Further, please enter the Windows computer name of your Unreal Server in “Default Server URL“ and assign a name for “Default Session Name“.

Save your project and re-open it.

Click on the arrow next to “Join“ in the toolbar and select “Launch Multi-User Server”.

A new window pops up, afterward close Unreal again, and you are all set to bring the project into PIXERA!

PIXERA Interop Setup

The Interop is an important part of Unreal Integration. Without the correct Interop version, Unreal setups can't be achieved. There are three different Unreal modes in PIXERA. Each mode requires the Interop to be in a different root directory:

• Dash Game: 
  • Interop must be placed beside the Unreal Editor (as seen in the screenshots below). Whilst installing the Interop the root install directory can be chosen. Please keep in mind that for multiclient setups, the interop can be transferred directly via PIXERA. If Unreal was installed on the C drive, PIXERA won't be able to copy the Interop because of windows.
• MultiUser:
  • Interop must be placed at the Unreal Editor which will be doing the editing work. Depending on the setup, the Control Instance could be placed on a different server in the network.
• Packaged:
  • Interop must be placed beside the EXE file. 

Download the PIXERA Interop from here: Downloads (pixera.one)

Select correct root path. This is the same path as the Unreal Engine installation.

As soon as the installation setups have been completed, unreal projects can be imported into PIXERA as a compositing resource.

Interop is installed into the PIXERA install path:

Furthermore, the Interop installer exchanges the available nDisplay DLL´s in the Unreal Engine root install path. The original DLL´s are being placed inside the “PIXERABackup” Folder.

The Interop is then either installed or copied via PIXERA to the root folder of the Unreal Engine:

Triggering the “Copy RXInterop.dll To Configured Nodes” button in PIXERA will take the interop from the PIXERA install path and copy it into the Unreal Engine root path.

The Unreal Editor path can be found in the PIXERA project:

PIXERA 2.0.65 | 09. July 2024 | CL

To better understand the mechanisms explained below, it is advisable to read this article first:
Output Mapping  

In some situations, it is necessary to map content pixel by pixel to the output. An example of this would be a display on a façade equipped with individual pixels or tubes.

With standard pixel mapping using feeds (normal LED mapping), you would have to create a separate feed for each pixel in order to then position it at the desired location on the output.

This quickly results in hundreds or even thousands of feeds, which are no longer manageable.

If LED panels are used as screens in PIXERA, it is possible to load this mapping into PIXERA using .csv or .pfm files.
This creates a single feed that contains the entire remapping.

Before doing that, it is necessary to set the “Selective Target Rendering” of that LED to “Texture per Screen”. This setting can be found by selecting the LED in the Screens Tab -Render Settings - Inspector.

The .csv file can be loaded in the Inspector of the selected mapping under ‘Warp’.

The 'war'p' is only visible on the output but not in the warp window on the right hand side.

Before loading the .csv file

After loading the .csv file

The .csv file only contains coordinates for the source position of the pixels and the destination position of the pixels. the example .csv file which was used in the example above, can be found below as well.

Download sample .csv

After importing the .csv file, PIXERA automatically changes the file type to .pfm. Alternatively .pfm files can be loaded directly as well.

If the source is larger than the destination (i.e. the resolution of the created LED is larger than the resolution of the output), pixels that are outside the output resolution can still be mapped so that they are within the output resolution.

PIXERA 25.2 RC 1 | 17 September 2025 | FE

PIXERA offers a powerful API that enables creative professionals to build custom workflows and integrations. Designed for artistic and media-rich environments, PIXERA gives users the flexibility to shape immersive experiences with precision and creativity by providing direct access to powerful functionality. To ensure secure operation in these contexts, we strongly recommend deploying PIXERA in an isolated network, separate from general IT infrastructure.

At the same time, we increasingly see PIXERA being used in enviroments where managing external access through network configuration alone is challenging. To give you control over the exposed API in these use cases 25.2, introduces an allowlist feature. Specific API commands can now be blocked or allowed based on fine-grained configuration in the settings. This lays the groundwork for a wide range of deployment scenarios that involve external access points, unlocking even more creative potential and integration possibilities.
 

When enabled, this allowlist will only permit all API commands/control actions in the Action Allowlist. This also affects the Web UI controls when used from an external Browser, the internal Control inside the PIXERA GUI will still allow the complete use.

Gui representation

If the allowlist is enabled and access to the API is restricted or blocked, this status is visually indicated by the corresponding icon in the GUI.

Right-clicking the icon opens a context menu where you can manage access settings — either to activate the allowlist globally or to include or exclude all API access points.

Left-clicking on this icon takes you directly to the settings, where this option can be found.

Settings

To deactivate this restriction, please deactivate “Restrict Web Access to Actions That Match Allowlist”

This checkbox affects all commands sent from an external web UI, as well as API commands sent to one of the API access points.
The API access points can also be activated and deactivated separately.
If the “Restrict Web Access to Actions That Match Allowlist” checkbox is unchecked, this also disables API access restriction even if “Use Control Action Allowlist To Restrict API Access” is checked.

The behavior in the Control Web UI when commands and/or control functions are not enabled can be seen in the upper right corner.
Here, the user is informed that they are not authorized.
 

The web UI editor within PIXERA Control is exempt from this restriction, it always has full access rights.

Allowlist Options and Syntax

To restore full access to the API, please uncheck the box “Restrict Web Access To Actions That Match Allowlist.”

The allowlist provides an editor that allows you to set commands. It also has an export and import function.

Syntax

• NewModule.test →Only allow the action “test” in “NewModule”
• NewModule.Folder.* → Allows everything in the Folder “Folder” of Module “NewModule”
• NewModule.* → Allows Everything in “NewModule”
• * → Allow all and use other commands to Deny actions (Invert Allowlist to Blocklist)

The “Deny” Button allows inverting that to only deny those commands

Action strings can use an asterisk () as a wildcard for any part of the action path. This means it matches all action paths that share the remaining parts. For example, ".act1" matches any action named "act1" in any module.

Export

The Export button allows you to export the list in JSON format.

{
 "entries": [
  {
   "command": "NewModule.test",
   "isBlack": false
  },
  {
   "command": "NewModule.Folder.*",
   "isBlack": false
  },
  {
   "command": "NewModule.*",
   "isBlack": false
  }
 ]
}

Import

The Import button allows you to import the list as JSON using the syntax described above.

Recommendation

This is a summary list of recommended commands to block.

{
 "entries": [
  {
   "command": "pixcGetAddressDescriptions",
   "isDeny": false
  },
  {
   "command": "*.Utils.Filesystem",
   "isDeny": true
  },
  {
   "command": "*.Utils.System",
   "isDeny": true
  },
  {
   "command": "*.Utility.Filesystem",
   "isDeny": true
  },
  {
   "command": "*.Utility.System",
   "isDeny": true
  },
  {
   "command": "*.Utility.runJsScript",
   "isDeny": true
  },
  {
   "command": "*.Utility.dynamicRebuildFromJsonDescription",
   "isDeny": true
  },
  {
   "command": "*.dynamicRebuild",
   "isDeny": true
  },
  {
   "command": "*.dynamicRebuildFromDescription",
   "isDeny": true
  },
  {
   "command": "*.dynamicRebuildFromJsonDescription",
   "isDeny": true
  },
  {
   "command": "*.WebViews.setFuncBodyState",
   "isDeny": true
  },
  {
   "command": "*.WebViews.setTag",
   "isDeny": true
  },
  {
   "command": "*.WebViews.setEditorIsUsingBlocks",
   "isDeny": true
  },
  {
   "command": "*",
   "isDeny": false
  }
 ]
}

allowlist_v2

PIXERA 25.2 R 3  | 14. October 2025 | J.B.