Add Omnidream interactive upsampler client#350
Draft
gtong-nv 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.
Summary
Adds an optional async FlashVSR uplift stream for the OmniDreams interactive-drive world-model backend.
When
upsampling_enabledis set in the world-model manifest, generated chunks are queued to a FlashVSR gRPC server without blocking the interactive rendering loop. The client defaults todisplay_only, so the FlashVSR HTTP viewer owns presentation while interactive-drive continues to show the original model output plus an on-screen uplift status message.Changes
UpliftStreamClientandUpliftStreamConfigfor best-effort chunk streaming to FlashVSR.WorldModelRenderBackend:upliftoptional dependency extra forflashdreams-flashvsr, which provides the FlashVSR gRPC protos/client surface only when upsampling is enabled.Notes
The PR does not yet route upsampled frames back into interactive-drive.
upsampling_return_framesis present as a future hook, but the default path drains responses only to observe server errors/backpressure.The uplift queue is intentionally bounded. If the remote server falls behind, chunks are dropped and the status message reports the drop count instead of stalling rendering.
Normal interactive-drive usage does not require FlashVSR. To run with
upsampling_enabled=true, sync/run with both extras:Installing the
upliftextra installs the FlashVSR Python package surface needed by the gRPC client. It does not download FlashVSR checkpoints; those are fetched only when the FlashVSR server/pipeline is instantiated.