NOTE: if you are receiving this message but you aren't on the [turbo|tiger]-devel mailing lists, it's because I BCC'ed you. Don't panic. :)
The following article provides details of low-level tests I performed this week to assess the feasibility of using x264 (probably the most popular H.264 open source codec) as a replacement or a supplement for the TurboVNC encoder: http://www.turbovnc.org/About/H264 In short, at the moment, I find H.264 to be somewhat less than compelling. As predicted, the full-frame nature of the codec makes it a poor fit for VNC, it can only be shown to provide better compression on a very limited set of workloads, and despite SIMD acceleration, x264 is still really slow compared to the TurboVNC encoder (H.264 seems to be somewhat less symmetric, compared to JPEG, in terms of its CPU usage on the encoder and decoder side.) The codec is currently so slow that it would be CPU-bound, even on very slow broadband or satellite connections, so what's the point? Feedback is, as always, welcome. DRC ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
