Studio Review Burn-In

Some frames need the whole presentation treatment - header, footer, safe areas. Most frames just need to not be anonymous. MKRStudioReviewBurnIn is the second kind: a slim band across the top of your image carrying title, subtitle, and a badge, plus a footer strip, with an accent bar so the band reads as intentional design rather than a watermark. It's the "throw a version on it and get it to the client" node.

The distinction from MKRStudioReviewFrame matters, and it's the reason you'd pick this one: where the review frame re-composites your image onto a big canvas with margins and safe-area overlays, the burn-in draws on top of the image itself with an adjustable inset. The image keeps its size and position; the chrome is an overlay. That makes it far better for video review, because every frame gets stamped identically without re-laying out.

What you set

• title, subtitle, badge - the identity. No version field here; if you want version tags, put v003 in the title or drive it from a delivery plan.
• theme - Carbon/Paper/Signal/Blueprint, matching the rest of the Studio family.
• band_height_px (default 96) and accent_width_px (default 12) - the band's thickness and the accent stripe. This is where you tune the look from "subtle" to "broadcast".
• opacity - how solid the band is, 0.1 to 1.0, default 0.9.
• inset_px - how far the band sits from the frame edges.
• show_frame_index - stamps each frame with its index in the batch.

What comes out

image (the stamped frame) and burnin_info (JSON describing what got burned in). Wire burnin_info into MKRStudioDeliveryPlan if you want the delivery sheet to know what each stamped frame is.

Installing it

In 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 models.

When to reach for it

This is the one you'd actually use day-to-day for internal review - batch a set of renders, stamp them, drop them in a shared folder. The band covers a little of your image on the top edge, so if the important detail lives up there, nudge band_height_px down or use opacity around 0.5 so the frame stays readable. And remember the honest limits: no safe-area guides (that's the review frame's party trick) and no automatic version sequencing - you provide the version, this node just wears it.