🔧 Advanced Tile Splitter:
The CustomTileSplitter is a specialized node designed to divide an image or latent space into smaller, manageable tiles. This functionality is particularly beneficial for processing large images or datasets that exceed the capacity of your hardware or software limitations. By splitting the image into tiles, you can apply various processing techniques to each tile individually, which can then be recombined to form the complete image. This approach not only optimizes resource usage but also enhances processing efficiency and flexibility. The node allows for customization of tile size, overlap, and the number of rows and columns, providing you with control over how the image is divided. This is especially useful in scenarios where specific regions of an image require different processing techniques or when working with high-resolution images that need to be processed in parts.
🔧 Advanced Tile Splitter Input Parameters:
tile_size
The tile_size parameter determines the dimensions of each tile in pixels. It defines both the height and width of the tiles, ensuring they are square. The default value is 512 pixels, which is a common size that balances detail and processing efficiency. Adjusting this value can impact the granularity of the processing; smaller tiles may allow for more detailed processing but can increase the number of tiles and processing time.
overlap
The overlap parameter specifies the number of pixels that adjacent tiles will share. This overlap is crucial for seamless blending when tiles are recombined, preventing visible seams or artifacts. The default overlap is 64 pixels. Increasing the overlap can improve blending quality but may also increase processing time and resource usage.
rows
The rows parameter allows you to specify the number of rows into which the image should be divided. If set to a value greater than zero, it overrides the automatic calculation based on tile size and overlap. This parameter provides control over the vertical division of the image, which can be useful for specific processing needs.
columns
The columns parameter functions similarly to rows, but it controls the horizontal division of the image. By setting this parameter, you can dictate the number of columns, overriding automatic calculations. This is useful for tailoring the horizontal division to suit particular processing requirements.
normalize
The normalize parameter is a boolean that determines whether the tiles should be normalized during the splitting process. Normalization can help in standardizing the tile data, making it easier to apply consistent processing techniques across all tiles. The default setting is True, which ensures that tiles are prepared uniformly for subsequent processing.
image
The image parameter is the input image that you wish to split into tiles. This parameter accepts the image data that will be processed, and it is essential for the node's operation. The image should be in a compatible format for the node to function correctly.
latent
The latent parameter is an optional input that allows you to provide latent space data instead of an image. This is useful in scenarios where you are working with latent representations of images, such as in generative models. Providing latent data enables the node to split this data into tiles for further processing.
🔧 Advanced Tile Splitter Output Parameters:
splits
The splits output parameter provides a list of dictionaries, each containing the coordinates and dimensions of the tiles generated by the node. This information is crucial for tracking the position and size of each tile, enabling you to process and later recombine them accurately. The splits include details such as the x and y coordinates, as well as the height and width of each tile.
🔧 Advanced Tile Splitter Usage Tips:
- To achieve seamless blending when recombining tiles, ensure that the
overlapparameter is set appropriately. A larger overlap can help reduce visible seams. - When working with high-resolution images, consider adjusting the
tile_sizeto balance between processing time and detail. Smaller tiles may provide more detail but can increase the number of tiles and processing time.
🔧 Advanced Tile Splitter Common Errors and Solutions:
"Tile count mismatch. Config: X, Input: Y"
- Explanation: This error occurs when the number of tiles generated does not match the expected configuration, possibly due to incorrect input dimensions or parameter settings.
- Solution: Verify that the input image dimensions and the
tile_size,rows, andcolumnsparameters are set correctly. Adjust these parameters to ensure they align with the expected output configuration.
"Invalid image or latent input"
- Explanation: This error indicates that the provided image or latent data is not in a compatible format or is missing.
- Solution: Ensure that the input image or latent data is correctly formatted and provided to the node. Check for any issues with the data source or format.
