xpra icon
Bug tracker and wiki

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


Changes between Version 12 and Version 13 of Encodings


Ignore:
Timestamp:
07/05/13 09:36:58 (8 years ago)
Author:
Antoine Martin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Encodings

    v12 v13  
    5454This option, shown as "latency" via the tray menu, controls how hard the encoder is going to work at compressing the picture. Working harder means lower bandwidth, but also higher latency.
    5555x264 supports the following speed settings: {{{ultrafast}}}, {{{superfast}}}, {{{veryfast}}}, {{{faster}}}, {{{fast}}}, {{{medium}}}, {{{slow}}}, {{{slower}}}, {{{veryslow}}} and {{{placebo}}}.
    56 xpra maps the 100% to 0% speed option from {{{superfast}}} to {{{slower}}} only.
     56xpra maps the 100% to 0% speed option from {{{ultrafast}}} to {{{slower}}} only.
    5757{{{veryslow}}} and {{{placebo}}} are not particularly useful (diminishing returns: much much slower and without sufficient savings for real-time use).
    58 {{{ultrafast}}} is not available because setting the encoder to this setting has side-effects which prevents other settings from behaving as they should if the option is later changed. And in theory, {{{superfast}}} is almost as good.
    59 To test {{{ultrafast}}}, try [/attachment/wiki/Encodings/x264-allow-ultrafast.patch x264-allow-ultrafast.patch]
     58{{{ultrafast}}} is only available when setting the encoder speed to 100% manually (via the command line or UI) - note that this setting has side-effects which prevents other settings from behaving as they should if the option is later changed.
    6059
    6160
     
    6665Though you may find some [http://alax.info/blog/1394 good illustrations] online to give you an idea of the trade offs.
    6766(ie: [http://blog.malayter.com/2010/12/presets-versus-quality-in-x264-encoding.html fps vs noise], [http://blogs.motokado.com/yoshi/2011/06/25/comparison-of-x264-presets/ fps vs size])
    68 Be aware that the lossless auto-refresh will trigger a new frame at 95% quality, which often means re-initializing the whole codec, and this is expensive so increasing this delay may help.
     67Be aware that the lossless auto-refresh will trigger a lossless frame encoded using png or webp. If the delay is too low, it may negate the benefits of using efficient compression.
    6968
    7069