Studio Workflow

Uncanny's production workflow covering naming conventions, versioning, file formats, folder structures, DCC specifics, and archiving. Based on uncanny-workflow v2.1 (work in progress).

Pre-Production Checklist

Before a project starts, confirm the following with the client:

Production must always deliver:

Naming Conventions

File Names

Format: client-project_specifics_length_language_aspectratio_version.extension

Examples:

Abbreviated versions for readability:

3D renders and compositing files: version in the folder name, not the filename (makes relinking easier).

Project Folders

Format: client-project_comment

Examples: berlin-olvarit_rework, berlin-isms_2025

Avoid abbreviating project folder names unless specified.

Naming in Other Tools

GitHub

Our GitHub is github.com/UncannyBE. It hosts internal tooling and shared code the team needs to read, review, or contribute to. Client deliverables stay on Z:/, not here.

What belongs on UncannyBE:

Repos are private by default. Open them up only when there's a reason.

Naming:

Inside DCCs

Same methodology applies to sequences in Premiere, comps in After Effects, write nodes in Nuke: client-project_shot_scene_version.

Versioning

Client-Facing Files

v01 on the client side must be v01 on the studio side. Additional granularity:

Example: berlin-callebaut_hotchocolate_precut_v01_r01_m01_altpanc.mp4

Intermediary Files

Date renders after the scene/comp name: scene_001 > MMDD

Inside DCC

Version names inside the DCC must match the filename in explorer.

File Formats

Preview Files

Upload to Frame.io or transfer via fromSmash.

Intermediary Files

Delivery Files

Always check/ask for technical specifications.

MXF 8 Channels -23 LUFS

Use the -23 LUFS mix with 8 channels in Media Encoder. Check in Premiere with Loudness Radar. Create sequence manually using 25i 8 mono discrete preset, pan track 1 and 2 to left and right.

Folder Structure (Windows Explorer)

Project folders are generated by the UC_Project_Builder tool, launched from W:\UC_Project_Builder\uc-project-builder.bat. The tool replaces the older Post Haste preset. On submission it:

  1. Copies the scaffolded folder tree from app/example/ to the NAS destination and renames any template_v1.{aep,prproj,xlsx} files to {client}-{project}_v1.{ext}.
  2. Optionally creates a #{client}-{project} Slack channel, invites the team, posts a welcome message, and appends a row to the Slack Project Status list.
  3. Optionally creates a Teamleader deal

Two checkboxes on the form ("Slack channel + project status list" and "Teamleader deal") let accounts opt out per project; both are on by default.

Frame.io integration is parked — the account runs on Adobe's V4 platform (next.frame.io) and needs an Adobe OAuth link before the V4 endpoint will respond. Wiring is in the code but disabled in the UI.

Windows-only (PowerShell). Mac users Parsec into UC_12 to run it.

00-production

01-projects

The builder pre-creates named DCC subfolders and drops in a template_v1 file where relevant (renamed to {client}-{project}_v1.{ext} on creation).

PureRef no longer has a dedicated subfolder. Houdini / Animate / Fusion files don't have dedicated subfolders either, add them inside the relevant DCC parent when needed.

02-assets

03-renders

04-exports

Note: the builder renumbered this section. Older projects on tape may still use 0401-delivery / 0402-finals.

DCC App Folder Structures

After Effects

Template: W:\AfterEffects\uncanny-template.aet

Premiere

Template: W:\Premiere\uncanny-template.prproj

DCC Specifics

Resolve

Blender

Template: W:\Blender\_blender45lts\startup.blend

Compositing setup uses Node Wrangler's "Lazy Connect" (ALT+RMB). Render paths are relative: //../../../../../04-Renders/0401_3D/render/exr/...

Render passes (lnh, 16-bit half float): rgba, alpha, mist, diffuse, glossy, transmission, volume, emit, env, ao, shadowcatcher, noisyimage, noisyshadowcatcher, greasepencil.

Data passes (ncf, 32-bit full float): depth, depth-denoise-normal, position, normal, vector, uv, crypto (object/material/asset), noisy, denoising.

Finalizing and Archiving

  1. Kitchen review: everyone responsible for the project reviews positives and negatives.
  2. File finalization and archiving:
    • Account managers confirm final files are in 0401-finals. Delivery folders (0400-delivery) deleted. Socials content moved to 0206-socials. Status changed to Tape?
    • Studio cleans folders and renders to keep only used rush/renders.
    • Final exports placed on W:\Uncanny\exports and social posts saved.
    • Final exports added to Eagle library with correct tags.
    • Cleaned folders stored on tape. Status changed to Y?
    • Project folders moved to Y: server for storage (1 year).
  3. Closing: Slack channel, project status, Teamleader deal, and Teamleader project all closed.

Safe Zones

Templates at W:\Uncanny\safezones\png. Available formats: 1:1 Instagram, 1:1 TikTok, 4:5 Instagram, 16:9 broadcast, 16:9 online, 16:9 online Meta, 16:9 online YouTube, 9:16 online LinkedIn, 9:16 online TikTok, 9:16 online Meta, 9:16 online YouTube.