ComfyUI > Nodes > Chaosaiart-Nodes > ๐Ÿ”ถ Load Checkpoint by Frame

ComfyUI Node: ๐Ÿ”ถ Load Checkpoint by Frame

Class Name

chaosaiart_CheckpointLoader

Category
๐Ÿ”ถChaosaiart/checkpoint
Author
chaosaiart (Account age: 355days)
Extension
Chaosaiart-Nodes
Latest Updated
2024-05-27
Github Stars
0.05K

How to Install Chaosaiart-Nodes

Install this extension via the ComfyUI Manager by searching for Chaosaiart-Nodes
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter Chaosaiart-Nodes 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

๐Ÿ”ถ Load Checkpoint by Frame Description

Dynamically load AI art model checkpoints based on frame number for seamless style transitions.

๐Ÿ”ถ Load Checkpoint by Frame:

The chaosaiart_CheckpointLoader node is designed to dynamically load checkpoints based on the frame number during the execution of an AI art generation process. This node is particularly useful for artists who want to apply different model checkpoints at various stages of their animation or frame sequence, allowing for a seamless transition between different styles or model capabilities. By leveraging this node, you can automate the process of switching checkpoints, ensuring that the appropriate model is loaded at the right time, thus enhancing the creative possibilities and efficiency of your workflow.

๐Ÿ”ถ Load Checkpoint by Frame Input Parameters:

ckpt_1

This parameter specifies the initial checkpoint to be used. It is a required parameter and serves as the default checkpoint if no other conditions are met. The value should be a valid checkpoint file from the list of available checkpoints.

ckpt_2

This parameter allows you to specify a second checkpoint to be used starting from a particular frame. It is optional and can be set along with ckpt_2_Frame_start to define when this checkpoint should be activated. The value should be a valid checkpoint file from the list of available checkpoints.

ckpt_2_Frame_start

This integer parameter defines the frame number at which ckpt_2 should be activated. The default value is 0, with a minimum of 0 and a maximum of 150000. Adjusting this value allows you to control precisely when the second checkpoint is loaded.

ckpt_3

Similar to ckpt_2, this parameter specifies a third checkpoint to be used from a certain frame. It is optional and should be used in conjunction with ckpt_3_Frame_start. The value should be a valid checkpoint file from the list of available checkpoints.

ckpt_3_Frame_start

This integer parameter sets the frame number at which ckpt_3 should be activated. The default value is 0, with a minimum of 0 and a maximum of 150000. This allows for precise control over when the third checkpoint is loaded.

ckpt_4

This parameter specifies a fourth checkpoint to be used from a certain frame. It is optional and should be used in conjunction with ckpt_4_Frame_start. The value should be a valid checkpoint file from the list of available checkpoints.

ckpt_4_Frame_start

This integer parameter sets the frame number at which ckpt_4 should be activated. The default value is 0, with a minimum of 0 and a maximum of 150000. This allows for precise control over when the fourth checkpoint is loaded.

ckpt_5

This parameter specifies a fifth checkpoint to be used from a certain frame. It is optional and should be used in conjunction with ckpt_5_Frame_start. The value should be a valid checkpoint file from the list of available checkpoints.

ckpt_5_Frame_start

This integer parameter sets the frame number at which ckpt_5 should be activated. The default value is 0, with a minimum of 0 and a maximum of 150000. This allows for precise control over when the fifth checkpoint is loaded.

ckpt_6

This parameter specifies a sixth checkpoint to be used from a certain frame. It is optional and should be used in conjunction with ckpt_6_Frame_start. The value should be a valid checkpoint file from the list of available checkpoints.

ckpt_6_Frame_start

This integer parameter sets the frame number at which ckpt_6 should be activated. The default value is 0, with a minimum of 0 and a maximum of 150000. This allows for precise control over when the sixth checkpoint is loaded.

ckpt_7

This parameter specifies a seventh checkpoint to be used from a certain frame. It is optional and should be used in conjunction with ckpt_7_Frame_start. The value should be a valid checkpoint file from the list of available checkpoints.

ckpt_7_Frame_start

This integer parameter sets the frame number at which ckpt_7 should be activated. The default value is 0, with a minimum of 0 and a maximum of 150000. This allows for precise control over when the seventh checkpoint is loaded.

ckpt_8

This parameter specifies an eighth checkpoint to be used from a certain frame. It is optional and should be used in conjunction with ckpt_8_Frame_start. The value should be a valid checkpoint file from the list of available checkpoints.

ckpt_8_Frame_start

This integer parameter sets the frame number at which ckpt_8 should be activated. The default value is 0, with a minimum of 0 and a maximum of 150000. This allows for precise control over when the eighth checkpoint is loaded.

ckpt_9

This parameter specifies a ninth checkpoint to be used from a certain frame. It is optional and should be used in conjunction with ckpt_9_Frame_start. The value should be a valid checkpoint file from the list of available checkpoints.

ckpt_9_Frame_start

This integer parameter sets the frame number at which ckpt_9 should be activated. The default value is 0, with a minimum of 0 and a maximum of 150000. This allows for precise control over when the ninth checkpoint is loaded.

๐Ÿ”ถ Load Checkpoint by Frame Output Parameters:

info

This output parameter provides detailed information about the currently active checkpoint, including the frame number, checkpoint name, and the positive and negative prompts being used. This information is useful for debugging and understanding the current state of the node.

MODEL

This output parameter represents the loaded model from the active checkpoint. It is essential for generating the AI art and is used in conjunction with other components like CLIP and VAE.

PositivOut

This output parameter contains the encoded positive prompt, which is used to guide the AI model in generating the desired output. It is derived from the positive text prompt provided and encoded using the CLIP model.

NegativOut

This output parameter contains the encoded negative prompt, which is used to guide the AI model in avoiding certain features or styles in the generated output. It is derived from the negative text prompt provided and encoded using the CLIP model.

VAE

This output parameter represents the Variational Autoencoder (VAE) component of the loaded model. It is used in the generation process to decode latent representations into the final image output.

๐Ÿ”ถ Load Checkpoint by Frame Usage Tips:

  • Ensure that all checkpoints specified are valid and available in the list of checkpoints to avoid loading errors.
  • Use the frame start parameters to precisely control when each checkpoint should be activated, allowing for smooth transitions between different models.
  • Regularly check the info output to verify that the correct checkpoint and prompts are being used at each frame.

๐Ÿ”ถ Load Checkpoint by Frame Common Errors and Solutions:

Checkpoint not found

  • Explanation: The specified checkpoint file could not be located in the list of available checkpoints.
  • Solution: Verify that the checkpoint file exists and is correctly named in the list of available checkpoints.

Frame start value out of range

  • Explanation: The frame start value specified is outside the allowable range (0 to 150000).
  • Solution: Adjust the frame start value to be within the valid range.

Model loading failed

  • Explanation: The model could not be loaded from the specified checkpoint.
  • Solution: Ensure that the checkpoint file is not corrupted and is compatible with the node's requirements.

๐Ÿ”ถ Load Checkpoint by Frame Related Nodes

Go back to the extension to check out more related nodes.
Chaosaiart-Nodes
RunComfy

ยฉ Copyright 2024 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals.