feat(video): support typed input references - #13706
Draft
furionw wants to merge 1 commit into
Draft
Conversation
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.
Based on #13705.
Why
The video API exposes only one untyped image reference, while vLLM-Omni pipelines can condition generation on image, video, and audio inputs. Dynamo needs a typed contract that preserves per-modality order, materializes remote media within request-level limits, and adapts singleton values to existing pipeline ABIs. Backends without this capability must reject the field instead of silently producing unconditioned video.
What Change
classDiagram NvCreateVideoRequest --> VideoReferenceMaterializer : supplies typed references VideoReferenceMaterializer --> OmniHandler : returns pipeline-ready paths OmniHandler --> OmniTextPrompt : attaches multimodal data note for VideoReferenceMaterializer "Bounds, stages, groups, and cleans request media" note for OmniHandler "Adapts references to the selected pipeline ABI"Test Plan