#1951 closed enhancement (fixed)
video-scaling should be set to auto
Reported by: | Antoine Martin | Owned by: | J. Max Mena |
---|---|---|---|
Priority: | major | Milestone: | 2.4 |
Component: | encodings | Version: | 2.3.x |
Keywords: | Cc: |
Description
We already have speed and quality settings.
Those alone should be enough to drive the amount of video scaling applied.
We can keep the existing heuristics for when video scaling is set to a value.
We may want to expose this via the system tray menu and html5 advanced connection options.
Change History (5)
comment:1 Changed 4 years ago by
Status: | new → assigned |
---|
comment:2 Changed 4 years ago by
Owner: | changed from Antoine Martin to J. Max Mena |
---|---|
Status: | assigned → new |
Not going to update the UI (we have too many controls already), and not going to use fullscreen or maximized flags (not sure which way they should favour).
@maxmylyn: FYI, the new heuristics should be easier to use (automatic) and will honour the dynamic quality and speed tuning more accurately.
comment:5 Changed 17 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1951
Note: See
TracTickets for help on using
tickets.
New heuristics mostly done in r20366 - see commit message for details. Updates in r20367 + r20368.
Rather than choosing the downscaling using the old opaque heuristics, the new code will choose the downscaling required to fit within a target budget. This target can come from:
XPRA_SCALING_MIN_PPS=1000000
(ie: 1 megapixels per second), defaults to 240p25: 25*320*240XPRA_SCALING_PPS_TARGET=16000000
(ie: 16 megapixels per second) defaults to 1080p25: 25*1920*1080--video-scaling=VALUE
(withVALUE=1
) instead ofvideo-scaling=auto
.Tweaks:
Still TODO: