gradio-sync3dcompare 0.0.14

Synchronized side-by-side 3D comparison viewer for Gradio — supports PLY and GLB files with shared camera control.

gradio_sync3dcompare

Synchronized side-by-side 3D comparison viewer for Gradio — supports PLY and GLB files with shared camera control.

Installation

pip install gradio_sync3dcompare

Usage

import gradio as gr
from gradio_sync3dcompare import Sync3DCompare


with gr.Blocks(title="Sync3DCompare Demo") as demo:
    gr.Markdown("# Sync3DCompare — Synchronized 3D Comparison Viewer")
    gr.Markdown(
        "Compare two 3D assets side-by-side with synchronized orbit, pan, and zoom. "
        "Rotate one view and all others follow."
    )
    gr.Markdown(
        "### Two synchronized viewports. Upload `.ply` or `.glb` files manually into each pane."
    )
    Sync3DCompare(
        label="Two-Viewport 3D Comparison",
        value=[],
        render_mode="points",
        sync_camera=True,
        point_size=2.0,
        height=540,
        max_views=2,
    )


if __name__ == "__main__":
    demo.launch()

Sync3DCompare

Initialization

name	type	default	description
value	list[dict]| None	value = None	None
label	str| None	value = "3D Comparison"	None
render_mode	"points"| "native"	value = "points"	None
sync_camera	bool	value = True	None
point_size	float	value = 2.0	None
max_point_size	float	value = 10.0	None
default_zoom	float	value = 1.0	None
min_zoom	float	value = 0.5	None
max_zoom	float	value = 16.0	None
height	int	value = 500	None
max_views	int	value = 4	None
num_views	int| None	value = None	None
interactive	bool	value = True	None
visible	bool	value = True	None
elem_id	str| None	value = None	None
elem_classes	list[str]| str| None	value = None	None
render	bool	value = True	None

Events

name	description
change

User function

The impact on the users predict function varies depending on whether the component is used as an input or output for an event (or both).

• When used as an Input, the component only impacts the input signature of the user function.
• When used as an output, the component only impacts the return signature of the user function.

The code snippet below is accurate in cases where the component is used as both an input and an output.

• As input: Should return, the output data received by the component from the user's function in the backend.

def predict(
    value: Unknown
) -> list[dict]| None:
    return value