[hlky]

What does this PR do?

Adds TripoSplat image-to-3D Gaussian generation through both TripoSplatPipeline and modular pipeline blocks.

The integration includes:

• The flow transformer and Gaussian decoder, reusing DINOv3 and AutoencoderKLFlux2 for image conditioning.
• Optional BiRefNet foreground segmentation, implemented within the TripoSplat pipeline package.
• Foreground image preparation, configurable Gaussian densities, callbacks, generator support, and Gaussian PLY/splat export.
• Checkpoint conversion and native single-file loading for the transformer, decoder, and BiRefNet using shared weight mappings.
• Model, pipeline, modular-block, processor, and loading tests, plus API documentation and examples.

Known limitations

• Updated modular from_config processor settings do not persist across reloads. A strict xfail records the shared framework limitation, and documentation explains how to reapply the processor.
• Adaptive octree decoding prevents whole-decoder static compilation; repeated transformer blocks expose regional compilation.
• Single-file loading requires an explicit component config until a converted Hub repository is available. Tiny pretrained Hub fixtures remain follow-up work.

Example

Image	Splat
	butterfly.mp4

Fixes #15005.

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

cc @yiyixuxu @dg845 @asomoza (Pipelines and models)

[github-actions]

Hi @hlky, thanks for the PR! It does not appear to link an issue it fixes. If this PR addresses an existing issue, please add a closing keyword (e.g. Fixes #1234) to the PR description so the issue is linked. See the contribution guide for more details. If this PR intentionally does not fix a tracked issue, a maintainer can add the no-issue-needed label to silence this reminder.

Please note that PRs without a linked issue are likely to be automatically closed 10 days after this notice.

Once the PR links an issue (or gets the no-issue-needed label), you can ignore this message — it stays here as a comment, but it no longer applies.

[hlky]

Gentle ping.

cc @sayakpaul @linoytsaban

[sayakpaul]

Maybe we could host it as a community modular pipeline first like the Krea one since there's a few customizations happening? @yiyixuxu thoughts?

[hlky]

@sayakpaul

1. Which customisations are actually the concern?
2. Is the proposed community modular pipeline intended as an initial staging step toward upstream integration, or do you consider TripoSplat unsuitable for first-class support?

Personally, I'd prefer not to undertake the adaptation to a Hub-hosted community modular pipeline, given the work already invested in this PR. However, I have no objection to someone else adapting it for that purpose.

If there's no interest in upstream integration, feel free to close this PR.