ComfyUI Node: CreativeCode Code2Vid

CreativeCode Code2Vid:

CreativeCodeRender is a powerful node designed to transform shader code into dynamic video content, offering a seamless way to convert creative coding into visual animations. This node is particularly beneficial for AI artists and creative coders who wish to leverage the power of shaders to produce intricate and visually appealing animations. By utilizing this node, you can input shader code and configure various parameters to render animations with specific dimensions, frame rates, and other custom settings. The node's primary goal is to facilitate the rendering of shader-based animations, providing a bridge between creative coding and visual output. It supports both GLSL and P5.js code types, allowing for a wide range of creative possibilities. The node also includes a preview UI, enabling you to visualize your animations before finalizing them, thus enhancing the creative process by providing immediate feedback.

CreativeCode Code2Vid Input Parameters:

shader_code

The shader_code parameter is the core input for the CreativeCodeRender node, where you provide the actual shader code that defines the visual effects and animations you wish to render. This code can be written in GLSL or P5.js, depending on your preference and the complexity of the visual effects you aim to achieve. The shader code dictates how each pixel is rendered, allowing for intricate designs and animations. There are no strict minimum or maximum values for this parameter, but the complexity of the code can impact rendering performance.

width

The width parameter specifies the width of the output video in pixels. It determines the horizontal resolution of the rendered animation, affecting the level of detail and clarity. A higher width value results in a more detailed image but may require more processing power. There is no explicit minimum or maximum value provided, but typical values range from 640 to 1920 pixels, with 1280 being a common default for HD resolution.

height

The height parameter defines the vertical resolution of the output video in pixels. Similar to the width, it affects the level of detail and clarity of the animation. A higher height value increases the vertical resolution, enhancing the visual quality but also demanding more computational resources. Typical values range from 480 to 1080 pixels, with 720 being a common default for HD resolution.

frames

The frames parameter indicates the total number of frames to be rendered in the animation. It determines the duration of the video, with more frames resulting in a longer animation. The number of frames, combined with the frames per second (fps) setting, defines the total playback time. There is no explicit minimum or maximum value, but common values range from 30 to 300 frames, depending on the desired length and complexity of the animation.

fps

The fps (frames per second) parameter controls the playback speed of the animation. It defines how many frames are displayed per second, influencing the smoothness and fluidity of the motion. A higher fps value results in smoother animations but requires more frames to maintain the same duration. Typical values range from 24 to 60 fps, with 30 fps being a common default for standard animations.

time_start

The time_start parameter sets the initial time offset for the animation, allowing you to start rendering from a specific point in time. This can be useful for synchronizing animations with other media or for creating looping effects. The value is typically a floating-point number representing seconds, with a default value of 0.0 to start from the beginning.

custom_uniforms

The custom_uniforms parameter allows you to pass additional data to the shader code in the form of a JSON string. These uniforms can be used to control various aspects of the shader, such as colors, positions, or other dynamic properties. This parameter provides flexibility and customization, enabling you to create more interactive and responsive animations. The default value is an empty JSON object ({}).

version_mode

The version_mode parameter determines the version of the shader language to be used, with options such as "auto" to automatically detect the appropriate version based on the code provided. This ensures compatibility with different shader syntaxes and helps prevent errors related to version mismatches. The default value is "auto".

code_type

The code_type parameter specifies the type of shader code being used, such as "glsl" for OpenGL Shading Language or "p5js" for P5.js. This parameter ensures that the node processes the code correctly, applying the appropriate rendering techniques for each type. The default value is "glsl".

settings

The settings parameter is an optional input that allows you to provide additional configuration settings for the rendering process. These settings can include various rendering options and optimizations, tailored to your specific needs. The default value is None, indicating that no additional settings are applied.

channels

The channels parameter is a list of optional input textures or data channels that can be used by the shader code. These channels provide additional data for the shader to process, enabling more complex and dynamic visual effects. The default value is a list of four None values, indicating that no additional channels are used.

CreativeCode Code2Vid Output Parameters:

output

The output parameter is the primary result of the CreativeCodeRender node, providing the rendered animation as a tensor. This output represents the visual content generated by the shader code, ready for further processing or display. The tensor format allows for efficient handling and manipulation of the animation data, making it suitable for integration into larger workflows or projects.

shader_code

The shader_code output parameter returns the original shader code provided as input. This allows you to verify and review the code used for rendering, ensuring that the correct version was processed and enabling easy adjustments or iterations if needed.

CreativeCode Code2Vid Usage Tips:

• Ensure your shader code is compatible with the specified code_type to avoid syntax errors and rendering issues.
• Use the custom_uniforms parameter to introduce dynamic elements into your animations, allowing for greater interactivity and customization.
• Experiment with different fps and frames settings to achieve the desired animation length and smoothness, balancing performance and visual quality.

CreativeCode Code2Vid Common Errors and Solutions:

[CreativeCode] P5.js Render Error: Cannot render P5.js directly on backend.

• Explanation: This error occurs when attempting to render P5.js code directly on the backend, which is not supported.
• Solution: Use the "BAKE ANIMATION" button in the node UI to capture frames from your browser and send them to the node before queuing.

[CreativeCode] Shader compilation failed:

• Explanation: This error indicates a failure in compiling the shader code, often due to syntax differences between WebGL2 and ModernGL.
• Solution: Review your shader code for compatibility issues, especially if using features specific to WebGL2. Adjust the code to align with ModernGL syntax.

Invalid custom_uniforms JSON:

• Explanation: This error arises when the custom_uniforms parameter contains improperly formatted JSON data.
• Solution: Ensure that the JSON string is correctly formatted, with proper syntax and structure, before passing it to the node.

[CreativeCode] OpenGL Error:

• Explanation: This error signifies a general issue with the OpenGL rendering process, potentially due to resource limitations or incorrect settings.
• Solution: Check your system's GPU capabilities and ensure that all input parameters are correctly configured. Adjust settings to optimize performance if necessary.