Spout Sender & Receiver
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 171
Description
## What problem does this solve or what need does it fill?
Ability to send Bevy's video frames in real time to another software for further processing.
Ability to receive video frames in real time from another software and include it in Bevy's renderings.
## What solution would you like?
Spout (https://spout.zeal.co/) is the non-network solution implemented in Openframeworks, Processing, TouchDesigner, OBS and others, see https://leadedge.github.io/spout-projects.html
## What alternative(s) have you considered?
On windows it seems there are no other alternatives to Spout.
NDI (or any other network based solution) forces codec settings and is less efficient.
## Additional context
I would like to migrate a real-time off-screen 3D project developed in Scala and use Bevy/Rust instead.
I searched for the keyword "spout" in the Bevy project and did not find any results.
Contributor guide
Research direction
The issue names no Bevy files, tests, or entry points. Start by reviewing the linked Spout project and Bevy's rendering context to determine how Windows frame sending and receiving could fit; done would mean real-time frame transfer in both directions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100