ComfyOnline
CR-Pipe-Switch

Table of Content

ComfyUI Node: 🔀️ CR Pipe Switch

Class Name

CR Pipe Switch

Category 🧩 Comfyroll Studio/✨ Essential/🎷 Pipe

Author Suzie1 (Account age: 2158days)Extension Comfyroll StudioLatest Updated 2024-06-05Github Stars 0.49K

Github Ask Suzie1 Questions Current Questions Past Questions

How to Install Comfyroll Studio

Install this extension via the ComfyUI Manager by searching for Comfyroll Studio

    1. Click the Manager button in the main menu
    1. Select Custom Nodes Manager button
    1. Enter Comfyroll Studio in the search bar

After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • High-speed GPU machines
  • 200+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 50+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

🔀️ CR Pipe Switch Description

Facilitates dynamic selection between two pipelines based on input for conditional data routing and workflow control.

🔀️ CR Pipe Switch:

The CR Pipe Switch node is designed to facilitate the dynamic selection between two different pipelines based on a specified input. This node is particularly useful when you need to conditionally route data through one of two possible paths, allowing for greater flexibility and control in your workflow. By leveraging this node, you can streamline complex processes and ensure that the appropriate pipeline is utilized based on the given conditions. This can be especially beneficial in scenarios where different processing steps or modules need to be applied under varying circumstances.

🔀️ CR Pipe Switch Input Parameters:

Input

The Input parameter determines which pipeline will be selected. It accepts an integer value with a default of 1, a minimum of 1, and a maximum of 2. When set to 1, the first pipeline (pipe1) is chosen; when set to 2, the second pipeline (pipe2) is selected. This parameter is crucial for directing the flow of data through the desired pipeline based on your specific requirements.

pipe1

The pipe1 parameter represents the first pipeline option. It is of type PIPE_LINE and serves as one of the two possible routes that data can be directed through. This pipeline will be selected if the Input parameter is set to 1.

pipe2

The pipe2 parameter represents the second pipeline option. It is also of type PIPE_LINE and serves as the alternative route that data can be directed through. This pipeline will be selected if the Input parameter is set to 2.

🔀️ CR Pipe Switch Output Parameters:

PIPE_LINE

The PIPE_LINE output is the selected pipeline based on the Input parameter. It will be either pipe1 or pipe2, depending on the value of Input. This output is essential as it determines the subsequent path that the data will follow in your workflow.

show_help

The show_help output provides a URL string that links to the documentation for the CR Pipe Switch node. This is useful for users who need additional information or guidance on how to effectively use the node. The URL is: https://github.com/Suzie1/ComfyUI_Comfyroll_CustomNodes/wiki/Pipe-Nodes#cr-pipe-switch.

🔀️ CR Pipe Switch Usage Tips:

  • Ensure that the Input parameter is correctly set to either 1 or 2 to select the appropriate pipeline.
  • Use the show_help output to access detailed documentation and examples on how to use the CR Pipe Switch node effectively.
  • Combine the CR Pipe Switch node with other nodes to create complex, conditional workflows that can adapt to different scenarios.

🔀️ CR Pipe Switch Common Errors and Solutions:

Invalid Input Value

  • Explanation : The Input parameter must be set to either 1 or 2. - Solution : Verify that the Input parameter is within the valid range (1 or 2) and adjust it accordingly.

Missing Pipeline

  • Explanation : One or both of the pipeline parameters (pipe1 or pipe2) are not provided.
  • Solution : Ensure that both pipe1 and pipe2 parameters are correctly connected to valid pipelines before executing the node.

related extension: