xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.

Opened 4 years ago

Closed 4 years ago

Last modified 16 months ago

#2044 closed enhancement (fixed)

use video encoders more aggressively - but not nvenc

Reported by: Antoine Martin Owned by: Antoine Martin
Priority: major Milestone: 2.5
Component: encodings Version: 2.4.x
Keywords: Cc:


See ticket:2029#comment:13 : using video encoders saves lots of bandwidth and isn't that much more expensive than "jpeg" or "webp".
The only exception is NVENC (see #2022): those encoder contexts are expensive, so we don't want to use them unless we are certain that this is going to last.

Attachments (1)

gradual-setup-cost.patch (4.1 KB) - added by Antoine Martin 4 years ago.
gradual decrease in setup cost

Download all attachments as: .zip

Change History (6)

comment:1 Changed 4 years ago by Antoine Martin

Status: newassigned

See also #2046

comment:2 Changed 4 years ago by Antoine Martin

#2043 would help so we could rely on the damage statistics.

Changed 4 years ago by Antoine Martin

Attachment: gradual-setup-cost.patch added

gradual decrease in setup cost

comment:3 Changed 4 years ago by Antoine Martin

With the patch above, nvenc doesn't get used for the first 20 or 30 frames.
But it doesn't take into account the number of frames per second, which is more important than the raw number of frames. But this would require #2043

comment:4 Changed 4 years ago by Antoine Martin

Resolution: fixed
Status: assignedclosed

r21057 does this but using the current fps value: encoders with a high setup cost (ie: nvenc) won't be chosen until the framerate is high enough (defaults to 5fps)

See also #2048 which would alleviate nvenc's slow start.

comment:5 Changed 16 months ago by migration script

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2044

Note: See TracTickets for help on using tickets.