Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add --control-pipe option #32

Open
fasterthanlime opened this issue Mar 24, 2017 · 0 comments
Open

Add --control-pipe option #32

fasterthanlime opened this issue Mar 24, 2017 · 0 comments

Comments

@fasterthanlime
Copy link
Collaborator

In a native game setup there's three actors:

  • the launcher + overlay-renderer (itch)
  • the encoder (capsulerun)
  • the game

The current --pipe handles the encoder <-> game communication: it mostly concerns itself with synchronizing the video frame buffer (and capture start/stop).

We need a --control-pipe for launcher <-> encoder, so that the launcher is aware of some metrics (fps, recorded length, etc.) some events (recording start/stop, encoding finished with file path, etc.) and so on. It will also be useful for when we're able to capture mouse/keyboard events from the game, to relay them back to the overlay renderer.

TL:DR we need another pair of fifos/named pipes. Luckily both capsulerun and itch have classes that encapsulate that functionality now, so it should be rather easy. We might however have to change MainLoop to work off an event queue instead of reading directly from a connection, since we'll have several connections to deal with.

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

No branches or pull requests

1 participant