<p align="center">
<img src="assets/readme/mkrshift-nodes-banner.svg" alt="MKRShift Nodes banner" width="920" />
MKRShift_Nodes Introduction
MKRShift_Nodes is a collection of custom nodes for ComfyUI. It brings creative direction, image finishing, masking, material work, review, and output tools into one pack. It also includes nodes for exchanging information with other creative applications and for planning certain 3D-print workflows.
In ComfyUI, a node is a step in a visual workflow. You connect nodes to pass images, masks, settings, or other information from one step to the next. MKRShift_Nodes helps you build more of that workflow in one place: you can explore a character, refine the look of an image, compare results, and prepare work for review or delivery without assembling every task from unrelated node packs.
You do not need to use the whole pack. Choose the nodes that suit your project, whether that means adding bloom to a finished image, making a contact sheet from several variations, or preparing texture maps for a material.
How MKRShift_Nodes Works
Think of a ComfyUI workflow as a production line for an artwork. One node may supply an image, another changes its color, and a third prepares the result for review. MKRShift_Nodes provides steps for several parts of that line:
- Shape the idea: Explore character details, outfits, poses, camera angles, and framing.
- Develop the look: Adjust color, contrast, texture, lighting effects, and materials.
- Inspect the result: Compare alternatives or arrange a batch of images on a labeled sheet.
- Prepare the handoff: Create review frames, delivery plans, manifests, or other output materials.
For example, you might use MKRPoseStudio to block out a pose, make several image variations, compare them with AxBCompare, refine a favorite with x1ColorWheels, and place the result in MKRStudioReviewFrame. These are possible workflow steps, not a required sequence.
Some nodes work directly with images or masks. Others create plans or metadata: structured information describing a shot, an endpoint, an export, or a handoff. A planning node does not necessarily perform the action it describes. Check its outputs before assuming that it has transferred a file, started a stream, or completed an export.
MKRShift_Nodes Features
Creative Direction and Characters
| Nodes | What they help you do |
|---|---|
MKRCharacterCustomizer, MKRCharacterState | Set up character details and carry identity-related state through a workflow. These are useful when exploring variations of the same character. |
MKROutfitSet | Work with outfit variations during character development. |
MKRPoseStudio | Block out a 3D pose before developing an image. |
AngleShift | Explore changes in viewing angle. |
Aspect1X | Work with framing and aspect ratio. |
AxBCompare | Inspect two alternatives side by side, such as different poses, crops, or looks. |
A practical approach is to keep the character setup consistent while changing one creative choice at a time. Comparing two outfit or angle options is easier when the rest of the workflow stays the same.
Color, Look Development, and Image Finishing
The color nodes include x1ColorWheels, x1Curves, x1ColorWarpHueSat, x1ColorWarpChromaLuma, x1PaletteMap, xLUT, and xLUTOutput. They support grading, palette work, color matching, and LUT-related workflows. For example, you might use color wheels for a broad mood change, curves for contrast, or palette mapping when you want several images to share a more consistent color direction.
Finishing nodes include x1Bloom, x1Film, x1Stylize, x1LocalContrast, x1SharpenPro, x1LightWrapComposite, and x1EdgeAberration. They cover effects and adjustments such as glow, film-like texture, detail, compositing, and edge treatment. Small changes may be enough for a subtle polish; stronger changes can make a look more pronounced. Compare the result against the original to make sure important image details still read clearly.
Masks, Resizing, and Image Utilities
x1MaskGen helps generate masks, which identify the parts of an image you want to treat differently. A mask can help you focus a later adjustment on a subject or region instead of changing the entire image.
Other utilities include AdvResize for resize work; MKRImageSplitGrid and MKRImageCombineGrid for tiled-image workflows; MKRPixelPaletteReduce for reducing colors in pixel-art work; MKRSpriteSheetExtract for extracting sprites; and xShader and x1DenoiseDetail for shader-related work and cleanup.
Surfaces and Materials
For material-focused work, the pack includes x1PreviewMaterial, x1PBRPack, x1ClearcoatMap, x1ClearcoatRoughnessMap, x1EdgeWearMask, and x1TextureDetileBlend.
These nodes support material previews, preparation and packing of physically based rendering (PBR) maps, clearcoat-related maps, wear masks, and reducing obvious repetition in tiled textures. For example, an edge-wear mask can help distinguish a used surface from a pristine one, while anti-tiling work can make a repeated texture less visibly repetitive.
Inspection, Review, and Delivery
When you have several promising outputs, review nodes can make decisions easier:
AxBCompareplaces alternatives in a compare view.MKRBatchCollagePreviewandMKRStudioContactSheetorganize multiple images for inspection.MKRStudioReviewFrame,MKRStudioCompareBoard,MKRStudioSlate, andMKRStudioReviewBurnInsupport review-ready presentation.MKRStudioDeliveryPlanhelps plan naming and handoff.
Publish and output nodes include MKRPublishPromoFrame, MKRPublishEndCard, MKRPublishAssetManifest, MKRPublishManifestAtIndex, MKRPublishCopyDeck, and MKRPublishCopyAtIndex. These help prepare promotional framing, end cards, asset lists, and copy for delivery. The AtIndex nodes are useful when you need a particular item from a collection rather than the whole collection.
For preview-first media output, the pack also provides MKRPreSave, MKRPresaveVideo, and MKRPresaveAudio. MKRMuxVideoAudio combines video and audio work, while MKRTrimVideoByTime supports time-based video trimming. Video and audio export or muxing workflows may require ffmpeg to be available.
Creative-App Handoffs
The Blender bridge includes nodes such as MKRBlenderSceneImport, MKRBlenderCameraShot, MKRBlenderImageImport, MKRBlenderMaterialImport, and the corresponding image, material, and return-plan nodes. These are intended for workflows that bring Blender scene or image information into ComfyUI and prepare a route back.
The wider host-addon area covers TouchDesigner, TiXL, Nuke, Photoshop, After Effects, Premiere Pro, Affinity, Fusion 360, and Maya. The provided documentation describes these integrations as packet-first: their nodes work with application payloads and handoff plans. The 3D-host area also includes image or texture handoff routes. The Affinity route is based on Photoshop-plugin compatibility.
Network transport nodes, including MKRAddonEndpointPlan, MKROSCMessagePlan, MKRNDIStreamPlan, MKRSpoutSenderPlan, MKRSyphonSenderPlan, MKRTCPBridgePlan, MKRHTTPWebhookPlan, MKRWatchFolderPlan, and MKRWebSocketBridgePlan, help describe different ways applications might exchange information. Choose a transport that matches the applications and workflow you are using; a transport plan should not be mistaken for a confirmed live connection.
G-code and 3D Printing
The G-code area is for preparing and examining 3D-print instructions. It includes printer and preset nodes (MKRGCodePrinterProfile, MKRGCodeOrcaProfileLoader), model and generator nodes (MKRGCodeLoadMeshModel, MKRGCodeHeightmapPlate, MKRGCodeSpiralVase), analysis and adjustment nodes, a preview node, an external slicer node, and MKRGCodeExport for .gcode output.
If you use MKRGCodeExternalSlicer, the source documentation names OrcaSlicer, PrusaSlicer, and CuraEngine as supported external slicer options. Its dry_run mode can validate command and configuration text without an installed slicer command-line tool. When you intend to apply calibration or conditional processing later in a graph, keep include_comments enabled on MKRGCodeExport: those later nodes work best when exported layer comments are present.
Custom Node Interfaces
Some nodes have custom on-screen interfaces intended to make visual work easier. These include the character and pose nodes, AngleShift, AxBCompare, the PreSave nodes, MKRPublishPromoFrame, color and LUT nodes, and x1MaskGen. Their help pages are in web/docs/.
What's New with MKRShift_Nodes
The supplied project notes describe additions and current areas of work, but do not provide version numbers or a dated change history. The following is therefore a summary of documented changes, not a version-by-version changelog:
- Broader creative and delivery coverage: The pack brings direction, surface work, finishing, inspection, studio review, and publishing tools together. This can help you keep more of an artwork’s journey in one ComfyUI workflow.
- Expanded creative-app integration: Host-addon scaffolds and matching ComfyUI nodes cover several creative applications, with image and texture handoff routes for 3D hosts.
- Reusable network plans: Endpoint, streaming, messaging, and watch-folder planning nodes provide options for designing application handoffs.
- Extension-builder workflow:
MKRNodeExtensionBuilderAdvanced,MKRNodeExtensionBuilderPlan, andMKRNodeExtensionPyprojectPlansupport planning a ComfyUI extension and drafting its package metadata. This is primarily relevant if you create extensions, rather than only use nodes for artwork. - Initial V3 schema companion: The project notes identify a newer schema lane focused on addon and network transport nodes. It is described as an initial lane, not a replacement for every node in the pack.
Troubleshooting MKRShift_Nodes
The supplied documentation does not include issue-specific screenshots or videos. The checks below follow the documented node areas and requirements.
A video or audio output step does not work
- Identify whether the failing node is a video, audio, muxing, or trimming node.
- Check that
ffmpegis available in the environment running ComfyUI; the project notes identify it as a requirement for video/audio export and muxing work. - Check that the expected media inputs reach the node, then try the step again.
An external G-code slicing step cannot run
- Confirm that you are using
MKRGCodeExternalSlicer. - Check that the selected slicer command-line tool is available to the ComfyUI environment. The documented options are OrcaSlicer, PrusaSlicer, and CuraEngine.
- Use
dry_runto check the command and configuration text before attempting a full slicing run.
A later G-code processing node lacks the layer information it needs
- Find the
MKRGCodeExportnode feeding the later step. - Enable
include_comments. - Export again and check the later calibration or conditional-processing step. The project notes say these nodes give the strongest results when exported layer comments are present.
A host-integration or transport node produced a plan, but nothing appeared in the other application
- Check the node’s output name and contents to see whether it produced a plan, metadata, or an actual media output.
- Confirm that the corresponding application-side workflow is in place. The documented host integrations use application add-on scaffolds as well as ComfyUI nodes.
- Check the intended handoff route and endpoint settings in the relevant nodes. A plan alone does not confirm that another application received an image or message.
Frequently Asked Questions
Do I need every node in the pack?
No. You can use only the nodes relevant to your current artwork or delivery task.
Does MKRShift_Nodes include different AI image-generation models?
The supplied documentation describes nodes and workflows, but does not list bundled AI models. Nodes such as x1PreviewMaterial are tools for a task, not a documented list of selectable AI models.
Where can I find help for nodes with custom interfaces?
See the Markdown help pages in web/docs/.
Is the G-code area only for making artwork previews?
No. Its documented scope includes printer profiles, generators, analysis, preview, external slicing, and direct .gcode export. Review printer-specific output before using it on a physical machine.
Learn More about MKRShift_Nodes
web/docs/contains help pages for nodes with custom interfaces.web/docs/Home.mdis the documented landing page for a GitHub wiki.web/docs/_Sidebar.mdprovides wiki navigation organized around the pack’s node areas.
Start with the help page for the node you are using, then explore related nodes in the same area. For instance, if you are building a look, the color and finishing nodes are a more useful starting point than the host-handoff or G-code tools.
