Nodes/ComfyUI-RTX-Remix/RTX Remix Mute Layer
ComfyUI Node

RTX Remix Mute Layer

Mute (or unmute) an RTX Remix layer without touching the Toolkit UI

By NVIDIAGameWorks·Created 2 years ago·Updated 6 days ago· 71
RTX Remix Mute Layer
  • context
  • context
  • layer_id
mutetrue
layer_id
enable_this_nodetrue

Muting a layer is how you take it out of the picture without deleting it - hide the capture layer while you judge your replacement, or silence a workfile you're done with. In the Toolkit you'd click the eyeball. In a ComfyUI-driven REST API workflow, you'd reach for RTX Remix Mute Layer, which flips that state programmatically with a single boolean.

It's a small node with a clear job: PUT /stagecraft/layers/{layer_id}/mute with a value payload. The mute input is literally the switch - default true, labeled mute vs unmute on the widget. Set it true and the layer goes dark; set it false and it comes back.

Inputs:

  • mute (BOOLEAN) - true mutes, false unmutes. Default true.
  • layer_id (STRING) - which layer. Build it with RTX Remix Define Layer Id or pull it from RTX Remix Get Layers rather than hand-typing paths.
  • context (RTXRemixContext) - the standard connection thread.
  • enable_this_node (BOOLEAN) - the standard bypass; off returns an empty string.

Outputs:

  • context - passed through.
  • layer_id (STRING) - echoed back, so you can chain e.g. mute → save without re-wiring the ID.

Where it earns its keep is sequencing. Because the context chain enforces order, you can build "unmute the base layer → mute the old replacement → save" as a deterministic sequence, and it'll run the same way every time. That's the whole point of driving the Toolkit from ComfyUI rather than clicking around: repeatable, branchable, auditable state changes.

Install: part of NVIDIAGameWorks/ComfyUI-RTX-Remix, NVIDIA's official pack. ComfyUI Manager (search "RTX Remix") or:

cd ComfyUI/custom_nodes
git clone https://github.com/NVIDIAGameWorks/ComfyUI-RTX-Remix
# restart ComfyUI

Needs ComfyUI v0.3.48+ (V3 schema) and a running Toolkit with a project open - this is a live API call.

Where people get burned: a typo'd layer_id produces a "layer not found" style error from the Toolkit, and since the node's default mute is true, forgetting to set it means you silently mute a layer you meant to unmute. Also worth noting: muting is not removing - the layer still exists, still occupies its place in the stage, and will still show up in Get Layers. If you actually want it gone, that's RTX Remix Remove Layer's job.

CategoryRTXRemix/layers

Inputs (4)

NameTypeDefaultDescription
muteBOOLEANtrue
layer_idSTRING
contextRTXRemixContext
enable_this_nodeBOOLEANtrue

Outputs (2)

NameTypeDescription
contextRTXRemixContext
layer_idSTRING