Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pipewire pipewire
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 650
    • Issues 650
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 17
    • Merge requests 17
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWirePipeWire
  • pipewirepipewire
  • Issues
  • #1484
Closed
Open
Issue created Aug 05, 2021 by Jonas Ådahl@jadahlContributor

Consumer driven streams

Sometimes it's better if the consumer is the entity that drives the generation of new buffers in a stream.

An example of this is a screen cast where the consumer is a headless compositor that doesn't have any monitor to v-sync to. This is generally currently handled by applying an arbitrary refresh rate.

By letting the consumer being in control of when new buffer/frames are to be produced, one could effectively v-sync the producer (e.g. a headless compositor) to the monitor of the consumer (e.g. across a network barrier or in a local viewer setup).

Related: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1949

Assignee
Assign to
Time tracking