xpra icon
Bug tracker and wiki

Changes between Version 36 and Version 37 of Encodings


Ignore:
Timestamp:
01/16/14 08:36:04 (6 years ago)
Author:
Antoine Martin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Encodings

    v36 v37  
    3333* otherwise, choose h264 and tune the speed/quality to suit your needs (see below)
    3434The other encodings are somewhat less useful:
    35 * [/wiki/Encodings/vpx vpx] is similar to x264 but it does not support speed and quality tuning
     35* [/wiki/Encodings/vpx vpx] is similar to h264 but it does not support speed and quality tuning
    3636* jpeg gives lower size/quality than other lossy encodings, use this if the video encodings are not available and you need better compression than png can give you
    3737* webp (lossy mode) is a single image subset of vpx, and therefore lacks [http://en.wikipedia.org/wiki/Intra-frame intra-frame] compression - but latency is decent, though it is leaking memory at present and should therefore be avoided
     
    5252Though you may find some [http://alax.info/blog/1394 good illustrations] online to give you an idea of the trade offs.
    5353(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])
    54 Be 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.
     54Be aware that the lossless auto-refresh will trigger a lossless frame encoded using png or rgb. If the delay is too low, it may negate the benefits of using efficient compression.
    5555
    5656