Xpra: Ticket #2044: use video encoders more aggressively - but not nvenc

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.

Mon, 19 Nov 2018 05:05:34 GMT - Antoine Martin: status changed

status changed from new to assigned

Mon, 19 Nov 2018 08:32:37 GMT - Antoine Martin:

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

Mon, 19 Nov 2018 14:10:01 GMT - Antoine Martin: attachment set

attachment set to gradual-setup-cost.patch

gradual decrease in setup cost

Mon, 19 Nov 2018 14:37:04 GMT - 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

Tue, 20 Nov 2018 17:18:41 GMT - Antoine Martin: status changed; resolution set

status changed from assigned to closed
resolution set to fixed

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.

Sat, 23 Jan 2021 05:40:39 GMT - migration script:

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