ComfyUI Node: 💾 Save Splat Scene (SPZ + Camera)

💾 Save Splat Scene (SPZ + Camera):

The ArchAi3D_SaveSplatScene node is designed to facilitate the saving of 3D Gaussian Splat data along with camera information, making it particularly useful for web applications that require detailed 3D scene representations. This node supports multiple output formats, including PLY, SPZ (compressed), and JSON for camera data, providing flexibility in how the data is stored and utilized. By compressing the data into SPZ format, it significantly reduces file size, which is beneficial for storage and transmission efficiency. The node also captures essential camera parameters, ensuring that the 3D scene can be accurately reconstructed or visualized in different environments. This functionality is crucial for AI artists and developers working with 3D data, as it streamlines the process of preparing and exporting complex scenes for various applications.

💾 Save Splat Scene (SPZ + Camera) Input Parameters:

ply_path

The ply_path parameter specifies the path to the input PLY file, which is a common format for storing 3D data. This file serves as the source of the 3D Gaussian Splat data that will be processed and saved by the node. It is a required parameter, meaning you must provide a valid path to a PLY file for the node to function correctly. The PLY file should be generated from tools like SharpPredict or similar applications that produce compatible 3D data.

output_name

The output_name parameter determines the base name for the output files generated by the node. By default, this is set to "scene," resulting in output files named scene.spz and scene_camera.json. This parameter allows you to customize the naming of your output files, which can be helpful for organizing and identifying different scenes or versions. It is important to choose a meaningful name that reflects the content or purpose of the scene being saved.

💾 Save Splat Scene (SPZ + Camera) Output Parameters:

final_splat_path

The final_splat_path output provides the path to the saved splat file, which could be in SPZ or PLY format depending on the chosen output format. This path is essential for accessing the compressed or uncompressed 3D data, which can then be used in web applications or further processing.

json_path

The json_path output gives the path to the JSON file containing the camera data and scene metadata. This file is crucial for understanding the context and configuration of the 3D scene, as it includes information about the camera parameters and the source of the data.

scene_info

The scene_info output is a summary string that lists the files saved by the node. It provides a quick overview of the output, indicating which files were successfully generated and saved, which can be useful for logging and verification purposes.

💾 Save Splat Scene (SPZ + Camera) Usage Tips:

• Ensure that the ply_path points to a valid and correctly formatted PLY file to avoid errors during processing.
• Use descriptive names for the output_name parameter to easily identify and manage your output files, especially when working with multiple scenes.
• Consider using the SPZ format for output if file size is a concern, as it offers significant compression benefits without losing essential data.

💾 Save Splat Scene (SPZ + Camera) Common Errors and Solutions:

Niantic SPZ not installed

• Explanation: This error occurs when the SPZ library, required for handling SPZ files, is not installed in your environment.
• Solution: Install the SPZ library by following the installation instructions provided by the library's documentation or contact your system administrator for assistance.

Niantic SPZ save failed

• Explanation: This error indicates that the node was unable to save the SPZ file, possibly due to incorrect file paths or insufficient permissions.
• Solution: Verify that the output directory is writable and that the file paths are correct. Ensure that you have the necessary permissions to write to the specified location.

Input PLY: <size> MB

• Explanation: This message is informational, indicating the size of the input PLY file being processed.
• Solution: No action is required. However, if the file size is unexpectedly large, consider optimizing your PLY file to reduce processing time and resource usage.