Skip to content

Conversation

@digaobarbosa
Copy link
Contributor

@digaobarbosa digaobarbosa commented Dec 10, 2025

Description

Right now video tracks do not work when we send video files to inference.
The idea is to solve this in a way that both approaches work, without any changes to the API.

Solved that with a few new configurations on the client side, and moving the video track creation early in the process.

  1. Supporting two output modes for video files (client-side):
  • Datachannel mode (default): Frames received as base64 JSON - higher bandwidth but guaranteed delivery
  • Video track mode: Frames via video codec - lower bandwidth with hardware acceleration, but can drop frames/drop quality
  1. Adding realtime processing control: Choose between batch mode (process all frames ASAP) or realtime mode (match original FPS). Depends on user use case.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature

How has this change been tested, please provide a testcase or example of how you tested the change?

locally

Any specific deployment considerations

none

Docs

  • Docs updated? What were the changes:

@digaobarbosa digaobarbosa self-assigned this Dec 10, 2025
@digaobarbosa digaobarbosa merged commit b80d102 into main Dec 12, 2025
51 checks passed
@digaobarbosa digaobarbosa deleted the rodrigo/dep-233-python-sdk-video-file-with-video-track-output branch December 12, 2025 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants