On 9/4/2017 2:40 PM, Michael Niedermayer wrote:
> On Sat, Sep 02, 2017 at 11:21:35PM +0100, Mark Thompson wrote:
>> ---
>> The idea here is to be able to capture the screen with little CPU
>> interaction by encoding KMS scanout planes. Given X running on KMS, it can
>> capture both X and virtual
On 9/4/2017 2:46 PM, wm4 wrote:
> On Mon, 4 Sep 2017 19:40:25 +0200
> Michael Niedermayer wrote:
>
>> My thought, if its less energy intensive than what we have then its
>> worth having.
>> A tiny contribution to reducing carbon emissions ...
>
> Removing some fringe codecs/filters and FATE test
On Mon, 4 Sep 2017 19:40:25 +0200
Michael Niedermayer wrote:
> My thought, if its less energy intensive than what we have then its
> worth having.
> A tiny contribution to reducing carbon emissions ...
Removing some fringe codecs/filters and FATE test would contribute a
LOT to this. Currently, L
On Sat, Sep 02, 2017 at 11:21:35PM +0100, Mark Thompson wrote:
> ---
> The idea here is to be able to capture the screen with little CPU interaction
> by encoding KMS scanout planes. Given X running on KMS, it can capture both
> X and virtual consoles, including transitions between them while re
---
The idea here is to be able to capture the screen with little CPU interaction
by encoding KMS scanout planes. Given X running on KMS, it can capture both X
and virtual consoles, including transitions between them while recording.
Unfortunately, it's rather inconvenient to use: the KMS API d
