ComfyUI Node: OCS MultiParam

OCS MultiParam:

The OCS MultiParam node is designed to streamline the process of setting multiple parameters simultaneously for overly complicated sampling tasks. This node is particularly useful for defining custom noise types and other intricate parameters that require specific inputs. By allowing you to set multiple parameters at once, it simplifies the workflow and enhances efficiency. The node is versatile and can be connected to other OCS Param or OCS MultiParam nodes, making it a flexible tool in your sampling toolkit. Its primary goal is to provide a comprehensive and user-friendly interface for managing complex sampling parameters, ensuring that you can achieve the desired results with minimal hassle.

OCS MultiParam Input Parameters:

key_1, key_2, key_3, key_4, key_5

These parameters are used to set the type of custom parameter. Each key corresponds to a specific parameter type, such as custom noise or merge sampler. The keys are indexed from 1 to 5, allowing you to define up to five different parameters simultaneously. The function of each key is to specify the type of value expected, ensuring that the correct type of input is provided. This helps in avoiding errors and ensures that the node functions as intended. There are no minimum or maximum values for these keys, but they must match the expected parameter types.

params_opt

This optional parameter allows you to connect the output from other OCS MultiParam or OCS Param nodes. By doing so, you can set multiple parameters in a more organized and efficient manner. This is particularly useful when dealing with complex workflows that require multiple parameter definitions. The tooltip for this parameter provides additional guidance on its usage.

parameters

This text parameter block allows you to set custom parameters using YAML (recommended) or JSON. It is optional and can be left blank if not needed. The default value is a template for additional YAML or JSON parameters, which should be an object with keys corresponding to the index of the input. This parameter is multiline and does not support dynamic prompts, making it ideal for detailed and structured parameter definitions.

value_opt_1, value_opt_2, value_opt_3, value_opt_4, value_opt_5

These optional parameters allow you to connect the type of value expected by the corresponding key. Each value_opt parameter corresponds to a key parameter, ensuring that the correct type of input is provided. This flexibility allows you to connect output from any type of node, but it is crucial to ensure that the input type matches the expected type to avoid errors during workflow execution. The tooltip for these parameters provides additional guidance on their usage.

OCS MultiParam Output Parameters:

OCS_PARAMS

The output parameter of the OCS MultiParam node is OCS_PARAMS. This output can be connected to another OCS Param or OCS MultiParam node, or any other OCS node that takes OCS_PARAMS as an input. The function of this output is to pass the defined parameters to the next node in the workflow, ensuring that the sampling process is configured correctly. This output is essential for maintaining the flow of parameter definitions and ensuring that all necessary parameters are set before the sampling process begins.

OCS MultiParam Usage Tips:

• When defining multiple parameters, ensure that each key corresponds to the correct type of value to avoid errors.
• Utilize the parameters text block for detailed and structured parameter definitions using YAML or JSON.
• Connect the params_opt input to other OCS Param or OCS MultiParam nodes to streamline complex workflows.
• Always check the tooltips for additional guidance on each parameter's usage.

OCS MultiParam Common Errors and Solutions:

"Invalid parameter type for key_X"

• Explanation: This error occurs when the type of value connected to a key parameter does not match the expected type.
• Solution: Ensure that the value connected to the key parameter matches the expected type as defined in the OCS_PARAM_TYPES.

"Missing required parameter key_X"

• Explanation: This error occurs when a required key parameter is not provided.
• Solution: Ensure that all required key parameters are defined and connected to the appropriate values.

"Invalid YAML/JSON format in parameters"

• Explanation: This error occurs when the parameters text block contains improperly formatted YAML or JSON.
• Solution: Verify that the YAML or JSON in the parameters text block is correctly formatted and adheres to the required structure.