MediaHub

Files

Browsing Media Files

Importing media files from Remote Wiretap Gateway servers has been deprecated.

It is no longer possible to browse files from remote Flame Family products workstations on your network using Wiretap Gateway servers. To access files from a remote workstation, configure NFS and export the folders you want to access.

If a legacy project on your workstation references media on a remote Wiretap Gateway server, the application will try to read the media path directly from file systems mounted on your workstation.

When restoring a legacy archive referencing media on a remote Wiretap Gateway server, configure the required mount points or use Path Translation before restoring the archive with the Use Archive Option Convert To Local Path option enabled.


File Colour Space Information (Preview panel)

The Colour Space information of the selected media file has been added to the MediaHub's Preview panel, in addition to the Input and Clip Colour Space information. This information is useful when using any Colour Management settings to perform a colour space conversion.



Projects

Copying Content Between Projects

The content of a project can be copied to another project using the Projects tab in the MediaHub. Copying content from projects created in legacy versions of the application duplicates the content.



Archives

Archiving Project with Custom OCIO Config

When archiving a project using an external OCIO config, it is possible to include a copy of the config and its external LUT files as an OCIO archive (OCIOZ). This is a very useful option if the facility restoring the archive does not have access to the custom OCIO config.

Enable Generate OCIOZ in the Colour Management section of the Archive Options to include a copy of the OCIO config.

Note: This option is not available if the project's OCIO config is one of the presets installed with the application.

When the project archive is restored, the application uses the original location of the config. If this location is not available, modify the OCIO config of the project and use the copy of the original OCIO config, which is located in the colour_mgmt folder of the project.

Warning: The application cannot create an OCIO archive if the OCIO config of the project contains context variables to solve external files like LUT or CDL. The following error message is displayed in the console when archiving the project: "OCIO: Failed archiving config as OCIOZ: Config is not archivable". If the policy of the project is from an OCIO Config Archive format (OCIOZ), the Generate OCIOZ option will not be available.

The flame_archive command line tool can archive the OCIO config of the project as an OCIOZ file. The option is enabled by default for projects using an external config and it is possible to disable this option with the --O / -omit option. Refer to the flame_archive help for more details.


Archiving from the Command Line for Pre-2026 Projects

The flame_archive command line tool can only be used to archive 2026 projects and can restore projects of any version. To archive projects from legacy versions, use a legacy flame_archive command line tool included with a previous version.


Restoring a Project Archive

The following project attributes can be configured when restoring a Project Archive:

Note: By default, the Cache and Renders media format of the original project is used for the restored project, but a new format can be defined.

See Working with Projects from Previous Versions for more details.


Linked Archive Option

Convert To Local Path Archive is the default and only value for the Linked Archive option. In previous versions, Use Archived Path was the default value.

When the original location of content is not available on the workstation, use Path Translation to automatically reconnect media files or mount the file system at the matching location.