Contact Us
When working with a system that receives files from PIXERA file distribution, those files will be placed in the RX-Cache folders by default.
While reliable, this mechanism can make it difficult to directly manage files on the receiving system’s disk — especially if that system is also being used for editing, such as when it serves as a Manager (typically a Director) in a multi-user session.
The custom asset root feature specifies a path that serves as the root of the cache on the receiving system. This affects both paths on the Director and paths on the Client.
In effect, this replicates the source file system structure under the custom root on the destination system. As a result, a user familiar with the source file layout can work on the destination in the same way, without needing to understand or navigate the RX-Cache’s internal subfile structure.
Benefits of Custom Asset Root
Using a Custom Asset Root is particularly beneficial when working in a multi-user setup without a shared NAS. In such cases, the assets can exist locally on both System A and System B simultaneously.
If your setup already includes a NAS, then this configuration is unnecessary and should be avoided.
Without a Custom Asset Root, assets transferred in a multi-user environment are stored in the RX cache. With a Custom Asset Root defined, they are instead stored in the specified Custom Asset Root path.
Without Custom Asset Root
This can quickly lead to confusion about where files are located, as they may appear under different path abstractions.
Warning
If a Custom Asset Root is set but files are imported from outside this path, they will still be transferred into the RX-Cache folder.
With Custom Asset Root
In this example, a Custom Asset Root is used and also configured on different drives.
Warning
If a Custom Asset Root is set but files are imported from outside this path, they will still be transferred into the RX-Cache folder.
Impact on the Client
On the client, if a custom root is set, the path changes as well, but the RX-cache drive is still treated as the root drive.
Example:
Setup
To enable this feature, please go to the settings, select ‘Resource Distribution’ and set a custom path under ‘Custom Asset Root’.
Warning
As the Custom Asset Root is a global setting, you should always work with a project-specific subfolder!
Content located directly in the root directory should be avoided.
Tip
Future versions of Pixera may require this project-related folder and won't allow content to sit directly in the Custom Asset Root folder.
Warning
You should not make any changes to the custom asset root whilst a multi-user session is in progress!
Future versions of Pixera may not allow this anymore
If you change the custom asset root at a later point in time, no files from the old file path will be transferred to the new one.
Known issues and current limitations
- Button in Live Systems “Delete files in cache which are unused in this project” does not work with custom asset root.
Pixera 26.1 R39 | 14. September 2026 | J.B