Always
in motion.

With the Project Download tool, you can download your cloud projects to your local machine and choose exactly which files and versions to include.

Here's how:
1. Select the folders you want to download.
2. Choose the Review and WIP versions.
3. Configure additional files.
4. Connect to Kraken Server.
5. Scan the project and start downloading!

A new version of Kraken has been released today. This is the changelog details included in this new release:

- DCC plugins have been separated from the main Kraken package. Plugins are now installed and updated as an independent package, while still maintaining their location within Kraken's folder structure. The plugin package can be updated using any of the following methods:
> From the application, using the new New Plugins Version Available button on the main page.
> Using the Update Plugins button in the Settings window.
> During Kraken startup: if an update is available, the plugins are automatically updated when the application starts and the main interface is loaded.
> Along with a Kraken update: when Kraken is updated, the plugins are also automatically updated when the main interface is launched.
- A new interface has been added to display the progress of plugin updates.
- The plugin installation process has been automated after an update. Adobe CEP plugins (After Effects and Premiere) are excluded from this process and require a manual update due to an Administrator permission requirement in Windows. In these cases, the plugin must be updated manually from Settings using the corresponding orange Update Plugin button for the installed plugin.

Following our previos post about how to manage mockups with PipelinePro and create new assets from selected geometry on a scene, our Replace tool lets you swap multiple objects in your scene for assets from the platform in just a few clicks.

Getting started is easy:
1. Select the objects you want to replace.
2. Open Pipeline > Assets > Replace.
3. Choose the asset you want to use.
4. Decide whether to keep or delete the original objects.
5. Click Replace and you're done!

Click the link below if you want to know more about this feature.

Our Maya integration lets you send assets straight to the platform without leaving your scene, making it easier to build and update your mockups with assets from different departments.

Getting started is easy:
1. Open Pipeline > Assets > Export.
2. Choose whether to import the asset as a reference.
3. Set its category and destination.
4. Click OK and you're done.

Check the link at the bottom of this post for more information.

Download your projects, tasks, and deliveries directly to your Mac. Kraken automatically converts Windows file paths to Mac-compatible paths, so you can get straight to work.

Getting started is easy:
- Install Kraken and connect your account.
- Choose your destination folder.
- Download your files and get to work!

You can download files directly through Kraken, the Pipeline Pro platform, or Delivery.

A new version of Kraken has been released today. This is the changelog details included in this new release:

- Added support for Kraken on macOS.
- Added the *Open Task Detail* button, which opens the platform page corresponding to the selected task in the browser.
- Added a new *Render Output* section to the Render panels in Maya, Blender, and Nuke, displaying information about the render output format and settings.
- Added new configuration options in Kraken Server: 
- Selector for the number of files that can be downloaded simultaneously.
- Option to choose whether existing files are overwritten or skipped.
- Added compatibility between Kraken Server and the commands of the new *Download Project* system.
- Various adjustments to the Kraken interface.
- Reorganized the sections of the After Effects Render panel: the *Options* section has been moved below the publishing section to make it easier to select the version type and access the corresponding options.
- Fixed an issue with logging in using an *API Key*: when subsequently logging in with a username and password, Kraken incorrectly started downloads in Kraken Server mode.
- Fixed the Blender playblast format, replacing AVI_RAW with FFMPEG to ensure compatibility with Blender versions later than 3.1.
- Fixed bugs in the *Export Asset* and *Duplicate Asset* tools for Maya and Blender.

Major fixes and improvements have been applied to the BuildTrack and ingest workflow, especially concerning timeline frame range publication. The in/out values of the SHOT are now correctly published during ingest, ensuring accurate clip positioning in the timeline.

Clip import now links properly with track items and bins, and deleted episodes no longer appear in the selection menu. The default color interpretation for .mov files has also been adjusted to reflect proper project settings.

A new backend-level async trigger system is now in place to execute custom logic whenever key pipeline entities are created—such as episodes, sequences, scenes, shots, or tasks. This allows for automated actions like folder setup, structure initialization, or low-level sync with external systems.

A new shortcut is now available in DCC menus to launch Kraken directly. When triggered, Kraken opens and takes the user to the appropriate context-based path.

This default behavior can be customized, allowing teams to define specific destination routes depending on the environment or task type.

The centralized Publish tool is now fully integrated across the pipeline menu. When selected, it opens a modal that allows users to set the status to “published,” add comments, and log time spent on the task.

The new Publish tool is now available in Blender through the pipeline menu. When selected, it opens a modal that allows users to set the version status to “published,” add comments, and log time spent on the task.

A new Publish tool is now available in Nuke, integrated into the pipeline menu. It allows users to publish the current scene by opening a modal where they can change the status to “published,” add comments, and log work time.

A new “Publish” button has been added to the pipeline panel, allowing users to finalize a version with just a few clicks. The modal lets you set the version to “published”, add a descriptive comment, and include a time log—for example, marking time spent on rendering.

A dual-preview system is now active across all entities, supporting both image and video formats. Whether through import or manual upload, content is automatically converted to generate static and dynamic previews.

Any newly uploaded material replaces the existing preview, ensuring updated visibility while preserving access to previous versions.

A new color management checker is now available in Nuke to ensure that the scene's active color settings match the officially published configuration from Hiero. The tool, named Check Nuke Color, compares each parameter and highlights any mismatches, showing both the current and expected values.

If a discrepancy is found, users can apply a fix directly through the interface, automatically updating the color settings in Nuke to match the published version. If no configuration has been published from Hiero, the checker passes by default.

A new tool called "Publish Runner" has been introduced in Blender, allowing users to configure and execute multiple publishing actions sequentially from a single interface. This feature is particularly useful for automating validation steps, preparing deliverables, or running chained scripts.

The panel provides real-time feedback, showing which action is currently being executed. Optional time delays can be added to simulate processing time and better visualize execution flow during testing or review.

Openers are now fully functional in Blender tasks, allowing predefined actions to run automatically whenever a scene is opened. The system includes the RunChecks feature, which launches checkers in the background.

One of the integrated checkers is Check Sort From Range, designed to identify issues related to frame range ordering. When triggered, users can apply a fix directly from the interface. These checks currently run in a secondary thread, though due to Blender API limitations, execution may be moved to the main thread if stability issues arise.

The panel now allows users to search by name or episode and displays each asset with a preview image, category, asset type, associated episode, and task.

The last task linked to the asset is selected by default, but users can easily change it before confirming. Once imported, the asset appears with all relevant preview and file data ready to use.

A new update improves the traceability of ingest-related tasks within Kraken. Tasks automatically generated during the ingest process for refedits and plates now use clear, descriptive names.

Refedit tasks are named “Refedit Ingest – [SHOT]”, while plate copy tasks are named “Plate Ingest – [SHOT] – [PLATE]”. This makes it much easier to visually identify what is being processed and to monitor the task status—whether it’s pending, in progress, or completed.

Clips no longer need to include the plate name—it's enough for the clip name to match the shot name. The system automatically assigns the role of each clip (refedit, main plate, or additional plate) based on the track's name. Only one track can be set as refedit and one as main plate per shot. When a new assignment is made, any previous assignment of the same type is automatically deactivated.

The panel now includes a resolution selector, allowing users to define whether the shot resolution should come from the main plate, the Hiero sequence, or the project’s technical specifications. Additionally, a color publishing fix ensures that the .mov files now reflect the correct color settings configured within Hiero.