fix(connector): resolve server render paths on the workstation
Deploy / deploy (push) Successful in 6m4s
Deploy / deploy (push) Successful in 6m4s
QC's Open Render used the server's outputDir verbatim. The server
addresses renders from its own root (render.outputRoot, e.g. //SAN),
which the render worker translates via its own pathMappings because it
runs as a service account — the panel had no equivalent, so Open Render
failed on any machine that could not resolve that root.
Resolution now tries, in order: an optional Path Mappings setting, the
server path as given, then re-basing on Export Root. The last one is why
this usually needs no configuration at all: both sides lay renders out as
{root}/{showId}/{episode}/{shot}/{version}, so the tail can simply be
re-attached. A failure names every candidate it tried rather than
reporting one path that was never going to work.
Diagnostics gained the same check against a real folder from the QC
queue, since "Export Root exists" and "this machine can reach a render
the server wrote" are different questions and only the second one breaks
QC.
Verified against the live V: drive: a //SAN path, a backslash variant and
an explicitly-mapped path all resolve to the real render folder, while an
unknown root and a different show correctly resolve to nothing.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -17,6 +17,28 @@ Settings are stored per-machine via the **⚙ Settings** button in the panel (pe
|
||||
| **Banner Path** | Path to the panel banner image |
|
||||
| **Artist Email** | Used for render attribution in the pipeline |
|
||||
| **Handle Frames** | Plate handle frames prepended before the shot's source TC in-point (default: 8) |
|
||||
| **Path Mappings** | *Optional.* Rewrites paths the **server** supplies — see below |
|
||||
|
||||
### Server paths vs. this machine
|
||||
|
||||
The server addresses render folders from its own root (`render.outputRoot`,
|
||||
e.g. `//SAN`), which a workstation may not resolve — the render worker
|
||||
translates them with its own `pathMappings` because it runs as a service
|
||||
account. The panel needs the same translation to open a render for QC.
|
||||
|
||||
It resolves this itself in most cases, trying in order:
|
||||
|
||||
1. **Path Mappings**, if configured — format `//SAN/=V:/_EXPORTS/`, several
|
||||
separated by `;`.
|
||||
2. **The server path as given** — correct when `render.outputRoot` is already
|
||||
a path this machine can reach.
|
||||
3. **Re-based on Export Root** — the server's export layout mirrors the panel's
|
||||
from the show folder down (`{root}/{showId}/{episode}/{shot}/{version}`), so
|
||||
the tail is simply re-attached to Export Root.
|
||||
|
||||
Step 3 is why this usually needs no configuration. Set Path Mappings only when
|
||||
the two layouts genuinely differ. **Diagnostics** checks this against a real
|
||||
render folder from the QC queue and names every path it tried when it fails.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user