Repository navigation
Conversation
added 11 commits
November 17, 2026 14:51
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
The official PAN2 T2V example was used:
704x1248,241frames,24 FPS, seed123, swimmer prompt frominference/prompts/examples.json, and the PAN2 scheduler. BF16 could not fit on the 24 GiB RTX 5090. A real one-step NVFP4 run completed with 241 frames, 229.54 s end-to-end latency, 14.36 GiB peak allocated / 20.71 GiB reserved, and 1.05 generated FPS (0.044x realtime). The one-step output is attached below; it is a capacity/path validation, not a quality claim. A 50-step run was started and measured at roughly 83-92 s per denoise step, so the single-card block-offload profile is not realtime.pan2-official-nvfp4-one-step.mp4
Model feasibility
MiniMax-H3-Image and LightX2V H3 were evaluated before adding a misleading integration: both use the same 33.1B H3-Image DiT. Official H3-Image lists 66.28 GB BF16 DiT weights, a 66.7 GB BF16 Qwen3-VL text encoder, and a 2.34 GB VAE. NVFP4 can reduce the DiT to roughly 17-19 GB, but the complete pipeline still cannot reside in a 24 GiB RTX 5090. LightX2V's official single-GPU profile therefore enables model-level CPU offload; its four-GPU profiles disable offload.
Generated reports and media are PR attachments only; no model output is committed to the repository.
5090 Feasibility Report
The detailed Chinese report is available locally at
reports/pan2_5090_nvfp4_feasibility.mdand summarized here:This distinguishes measured PAN2 data from H3 estimates; no H3 estimate is presented as a local benchmark.