<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title type="text">Rémi Denis-Courmont</title>
  <subtitle type="html">
    Rémi Denis-Courmont website feed
  </subtitle>
  <updated>2012-03-26T19:37:00Z</updated>
  <author>
    <name>Rémi Denis-Courmont</name>
    <uri>http://www.remlab.net/</uri>
  </author>
  <id>tag:remlab.net,2009:main</id>
  <link rel="alternate" type="text/html" hreflang="en"
   href="http://www.remlab.net"/>
  <link rel="self" type="application/atom+xml"
   href="http://www.remlab.net/feed.xml"/>
  <rights>Copyright © 2009-2012 Rémi Denis-Courmont</rights>

  <entry>
    <title>Why (not) to relicense VLC under LGPL?</title>
    <id>tag:remlab.net,2012:vlc-lgpl</id>
    <link href="http://www.remlab.net/op/vlc-lgpl.shtml"/>
    <updated>2012-11-30T22:10:00Z</updated>
    <summary>The tedious and intricate process of relicensing
      has been documented.
      However a number of curious have asked not how but why
      was that was done in the first place. 
    </summary>
  </entry>

  <entry>
    <title>AVC-encoding camera with VLC and Video4Linux</title>
    <id>tag:remlab.net,2012:vlc-v4l2-h264</id>
    <link href="http://git.videolan.org/?p=vlc/vlc-2.0.git;a=commit;h=2.0.1-38-g4561899"/>
    <updated>2012-03-26T19:37:00Z</updated>
    <content type="xhtml" xml:lang="en">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><a href="http://www.videolan.org/vlc/">VLC media player</a>
          version 2.0.2 for <a href="http://www.kernel.org/">Linux</a>
          will gain support for AVC-encoding
          (a.k.a. ITU-T H.264 a.k.a. MPEG-4 Part 10)
          video cameras.
          This include the -currently- higher-end standard
          <a href="http://www.usb.org/">USB</a> Video Class webcams
          boasting <em>H.264</em>.
        </p>
        <p>At this time, those devices are a bit expensive,
          with prices starting at about a 100€.
          But they can encode high-definition video in real-time
          at acceptable quality.
        </p>
        <p>With adequate <a href="http://linuxtv.org/">Video4Linux</a>
          device drivers found in kernel version 3.1 or later, you can capture
          H.264 video with the magic VLC media location, e.g.:
          <kbd>v4l2://:chroma=h264</kbd> (video device number 0) or
          <kbd>v4l2:///dev/video1:chroma=h264</kbd> (device number 1).
        </p>
      </div>
    </content>
  </entry>

  <entry>
    <title>VLC 1.2 on Linux</title>
    <id>tag:remlab.net,2011:vlc-1.2-linux</id>
    <link href="http://www.remlab.net/op/vlc-1.2-linux.shtml"/>
    <updated>2011-10-20T17:06:00Z</updated>
    <summary>VLC media player version 1.2.0 is getting ready.
      The code freeze has been ongoing for a few weeks,
      and the first test version should be out in a matter of days.
       I would like to use this as an opportunity to review
       the Linux port news...
    </summary>
  </entry>

  <entry>
    <title>VLC 1.1.11 to address security issues</title>
    <id>tag:remlab.net,2011:vlc-1.1.11-security</id>
    <updated>2011-07-14T12:44:00Z</updated>
    <link href="http://www.videolan.net/security/"/>
    <content type="xhtml" xml:lang="en">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>As a <a href="http://www.remlab.net/">security contact</a>
          I used to announce VideoLAN security advisories
          on the <a href="http://www.videolan.org/">main VideoLAN website</a>.
          But most users are not literate in open-source development
          and do not understand the difference
          between source code releases and availability of binaries.
          So lets try another slightly less visible venue to announce
          the two advisories for the security fixes in upcoming VLC
          version 1.1.11:
          <a href="http://www.videolan.org/security/sa1105.html"
           >CVE-2011-2587</a> and
          <a href="http://www.videolan.org/security/sa1106.html"
           >CVE-2011-2588</a>.
        </p>
        <p><strong>Update: VLC 1.1.11 is now officially released.</strong>
        </p>
       </div>
    </content>
  </entry>
</feed>
