Studio Slate
A legit production slate card, no Photoshop involved
- thumbnail
- image
- slate_json
- slate_summary
The film-slate look has a practical point: every frame carries its identity - project, shot, take, version - so nobody has to guess what they're looking at. MKRStudioSlate renders that card as an image, straight from a form. Feed it your shot metadata and it draws a proper slate at any resolution, in one of four themes, and hands you the JSON too so the same metadata can flow into the rest of the pack's delivery chain.
This is the entry point of the MKRShift Studio pipeline. The pack's philosophy is that review boards, delivery sheets, and client notes should all agree on one set of shot facts - and this node is where you first type them. Everything downstream can consume what it produces.
What you set
- width / height - the canvas, default 1920×1080 (step 16, so it stays encoder-friendly).
- theme -
Carbon(dark, lime accent),Paper(light, warm),Signal(dark, orange),Blueprint(engineering-blue). Pick what your review culture reads as "serious." - The production block: project, sequence, shot, take, version_tag, department. Shot names like
A001and take numbers are what make the card readable at a glance. - The flavor block: director, artist, camera, lens, fps, aspect, date_text, notes, plus a badge if you want a status sticker on it.
- thumbnail (optional IMAGE) - drop a frame in and the slate becomes a title card with your actual render behind it. This is the output that makes it worth wiring into a video review pipeline.
What comes out
image (the slate), slate_json (structured metadata), slate_summary. Wire slate_json into MKRStudioDeliveryPlan and your filename and review title will pick the shot identity up automatically.
Installing it
Part of criskb/MKRShift_Nodes from Cris K B. ComfyUI Manager search "MKRShift_Nodes", or:
cd ComfyUI/custom_nodes
git clone https://github.com/criskb/MKRShift_Nodes
Restart. No pip requirements, no model downloads - rendering is plain image drawing, so this costs you nothing extra.
Where it gets good and where it doesn't
It's the node you'd actually reach for when you need consistent, branded headers for client dailies. The honest limits: it's a static card, not a video-safe template with moveable safe areas - that's MKRStudioReviewFrame's job - and the text fields are plain strings, so there's no auto-sequencing of shots. You type A001, A002, A003 or you wire them from elsewhere. If you're reviewing a whole batch, pair the slate with MKRStudioContactSheet so each frame in the sheet already knows what it is.
Inputs (20)
| Name | Type | Default | Description |
|---|---|---|---|
| width | INT | 1920256–4096 | — |
| height | INT | 1080256–4096 | — |
| theme | COMBO | Carbon | 4 options: Carbon, Paper, Signal, Blueprint |
| project | STRING | MKRShift Production | — |
| sequence | STRING | SEQ_01 | — |
| shot | STRING | A001 | — |
| take | STRING | 1 | — |
| version_tag | STRING | — | |
| department | STRING | — | |
| badge | STRING | — | |
| director | STRING | — | |
| artist | STRING | — | |
| camera | STRING | Virtual Camera | — |
| lens | STRING | 50mm | — |
| fps | STRING | 24 | — |
| aspect | STRING | 16:9 | — |
| date_text | STRING | — | |
| notes | STRING | — | |
| thumbnailopt | IMAGE | — | |
| delivery_plan_jsonopt | STRING | — |
Outputs (3)
| Name | Type | Description |
|---|---|---|
| image | IMAGE | — |
| slate_json | STRING | — |
| slate_summary | STRING | — |