Studio Review Frame

Here's the review-frame problem nobody warns you about: you drop a title and version on a frame for a client, then iterate, then the client's note is "which one is this?" MKRStudioReviewFrame is the cure - a full presentation frame with header, footer, version tag, safe-area guides, and your image sitting centered with a shadow. It's the "this is v003, look at the boxed region" frame.

Mechanically it's simple and that's the point: take an IMAGE, composite it onto a themed canvas (Carbon, Paper, Signal, Blueprint) with margins, draw a header band with title/subtitle/badge, a footer with left and right labels, and optional safe-area overlays. show_safe_area draws the classic action/title-safe guides, which is genuinely useful when you're reviewing frames that will be broadcast or projected. show_frame_index tags each frame in a batch with its index, so a 30-frame review doesn't turn into "frame... uh, the third one."

The inputs that matter

• title, subtitle, badge, version_tag - the identity block. version_tag defaults to v001, and the badge defaults to "IN REVIEW". If you wire in a delivery plan, these can be driven from the plan.
• theme - same four options as the other Studio nodes, so your whole review package stays on-brand.
• show_safe_area / show_frame_index - the two booleans that separate "pretty frame" from "review frame."
• margin_px, header_px, footer_px - control how much breathing room the image gets. Defaults are sane for 1080p.

What comes out

image (the framed shot) and review_frame_info - a JSON string with everything this frame claims about itself. Feed review_frame_info into MKRStudioDeliveryPlan and the review title, filenames, and handoff sheet pick it up.

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.

The trade-off

It's heavier than MKRStudioReviewBurnIn - more chrome, bigger header, safe-area overlays. That's the right look for client review decks, but it's overkill if you just need a quick version stamp on a frame going to a Slack thread. For that, the burn-in node is the lighter option. The trap to watch: it renders every frame in a batch with the same title, so if your batch is "different shots," you want one frame per shot or you'll stamp the whole batch with one identity.