Xpra: Ticket #178: vpx/x264: offer the user the choice of sacrificing picture quality or fps - sometimes we can't do both

Our heuristics sit somewhere in the middle at present, but some users may prefer lower fps with near pixel-perfect quality, or maybe just high fps with lower quality.

This would require:

--switchname=0...100
something in the UI to change at runtime
said value in the server used to weigh on the heuristics

Also, it seems that we should be less aggressive with colourspace conversion sub-sampling as this is more noticeable with applications like terminals..

Thu, 27 Sep 2012 15:24:11 GMT - Antoine Martin: status, milestone changed

status changed from new to accepted
milestone changed from 0.6 to 0.7

Wed, 10 Oct 2012 06:13:33 GMT - Antoine Martin: milestone changed

milestone changed from 0.7 to 0.8

Wed, 10 Oct 2012 06:14:53 GMT - Antoine Martin: description changed

description modified (diff)

Fri, 08 Feb 2013 04:38:12 GMT - Antoine Martin: status changed; resolution set

status changed from accepted to closed
resolution set to fixed

done in r2592 and r2603, with further fixes/changes in r2601, r2604, r2610, r2612, r2614 (ui), r2631 (ui), r2640, r2663 (osx), r2679 (ui)

We now have command line options:

--quality=
--min-quality=
--speed=
--min-speed=

And UI to control "Min Quality" and "Speed".

Sat, 23 Jan 2021 04:47:39 GMT - migration script:

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