TBG ETUR ColorMatch Debug Gates

ETUR's refiner doesn't correct color once - it corrects color at a dozen points in the pipeline: after PiD VAE decode, after segment sampling, before the final rebuild, after the final stitch. That's how you get seamless, tile-consistent output, and it's also why a color artifact can be maddening to chase. You see a green cast in the final image and you have no idea which of the dozen passes put it there.

ColorMatch Debug Gates exists to answer that. It's a wall of boolean switches, one per color stage, and its single output - a tbg_colormatch_debug pipe - plugs into the Labs for Refiner node's optional ColorMatch_Debug input. Flip a stage off, rerun, and you've bisected the problem. It's the diagnostic node you connect when something looks wrong, not the one you leave in a happy workflow.

The gates

The numbering tells you where each stage sits in the pipeline:

• 03_Flux2_PID_NormalVAE_Reference - builds a normal-VAE reference from the sampled latent (Flux2 PiD tiles, reference path only).
• 04_Flux2_PID_AfterPiDVAE_ColorMatch - the RGB/luma correction applied right after PiD VAE decode.
• 05_Flux2_PID_PostTone_ColorMatch - post-tone/seam low-frequency stabilization, also after PiD decode.
• 08_Segment_PostVAE_ColorMatch - the correction applied to generated segments after their PiD/VAE decode.
• 10_Final_TileOnly_ColorCorrection - after normal tiles are stitched, before segment rebuild; matches against the original/upscaled input.
• 11_Final_SegmentAware_ColorBase - builds the final reference, optionally swapping in PiD segment crops.
• 12_PID_Final_ColorMatch_4x - the near-final PiD rebuild container.
• 13_Final_PerArea_SegmentOverrides - the per-area path for protected tiles/segments.
• 14_Final_Global_ColorMode - the final global RGB/luma pass.

Each defaults to on. Turning one off disables that stage - but only if normal ETUR settings had activated it in the first place. That's the Override_Normal_Gates switch's job: with it off, your toggles only disable stages that were already running; with it on, the switches force stages on or off, including over tile/segment color gates. The tooltip is also upfront that some tile-aware behavior requires API member access and Neuro Generative Tile Fusion - the debug gates can only switch what your account is allowed to run.

How to actually use it

Isolation, one gate at a time. See a tint that only shows up on PiD-decoded Flux2 tiles? Kill gate 04, rerun, compare. See a cast that appears only around generated segments? That's gate 08. The pattern is the same as every debugging rule in the book: change one thing, keep the seed fixed, compare. The output of this node isn't an image - it's the config pipe - so connect it to Labs for Refiner and look at the refined output, not at this node.

Installing it

Ships in the TBG ETUR pack:

cd ComfyUI/custom_nodes
git clone https://github.com/Ltamann/ComfyUI-TBG-ETUR
cd ComfyUI-TBG-ETUR
pip install -r requirements.txt

Or ComfyUI Manager → search "TBG" → TBG_Enhanced Tiled Upscaler & Refiner FLUX PRO, restart.

Notes

This is a developer tool and it wears the label proudly - don't feel obliged to understand every gate before touching the pack. The pragmatic workflow: leave the node disconnected until a color problem appears, then wire it in, flip one switch, and let the evidence point. The one genuinely useful habit: if a stage doesn't seem to do anything when you disable it, the stage probably wasn't active in your configuration in the first place - check Override_Normal_Gates before you conclude the gate is broken.