Mir's default DisplayBuffer clone mode forces all outputs to the rate of the slowest one (and increases latency too)
Bug #1395416 reported by
Daniel van Vugt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Triaged
|
Medium
|
Unassigned | ||
mir (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Clone mode forces all outputs to render at the rate of the slowest one.
This is unnecessary. If you're cloning between say a 24Hz TV and a 60Hz laptop then Mir should be smart enough to give them separate compositors so as to keep the laptop screen rendering at 60Hz.
tags: | added: multimonitor |
summary: |
- [regression] Multimonitor frame sync is running very slow + Clone mode forces all outputs to render at the rate of the slowest one |
Changed in mir: | |
status: | Invalid → Triaged |
tags: | removed: regression |
description: | updated |
To post a comment you must log in.
Oops, forgot it's defaulting to clone mode so the compositing rate is indeed throttled to the slowest output (24Hz).
Setting the outputs side-by-side forces Mir to create separate compositors: mir_demo_ server_ shell --display- config= sidebyside
bin/
so now they're independent and the laptop display renders smoothly at 60Hz.