blog/tags/multimedia/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen: Entries Tagged multimedia</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="multimedia.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21     <h3>Entries tagged "multimedia".</h3>
  22
  23     <div class="entry">
  24       <div class="title">
  25         <a href="http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html">New lsdvd release version 0.17 is ready</a>
  26       </div>
  27       <div class="date">
  28          4th October 2014
  29       </div>
  30       <div class="body">
  31         <p>The <a href="https://sourceforge.net/p/lsdvd/">lsdvd project</a>
  32 got a new set of developers a few weeks ago, after the original
  33 developer decided to step down and pass the project to fresh blood.
  34 This project is now maintained by Petter Reinholdtsen and Steve
  35 Dibb.</p>
  36
  37 <p>I just wrapped up
  38 <a href="https://sourceforge.net/p/lsdvd/mailman/message/32896061/">a
  39 new lsdvd release</a>, available in git or from
  40 <a href="https://sourceforge.net/projects/lsdvd/files/lsdvd/">the
  41 download page</a>.  This is the changelog dated 2014-10-03 for version
  42 0.17.</p>
  43
  44 <ul>
  45
  46  <li>Ignore 'phantom' audio, subtitle tracks</li>
  47  <li>Check for garbage in the program chains, which indicate that a track is
  48    non-existant, to work around additional copy protection</li>
  49  <li>Fix displaying content type for audio tracks, subtitles</li>
  50  <li>Fix pallete display of first entry</li>
  51  <li>Fix include orders</li>
  52  <li>Ignore read errors in titles that would not be displayed anyway</li>
  53  <li>Fix the chapter count</li>
  54  <li>Make sure the array size and the array limit used when initialising
  55    the palette size is the same.</li>
  56  <li>Fix array printing.</li>
  57  <li>Correct subsecond calculations.</li>
  58  <li>Add sector information to the output format.</li>
  59  <li>Clean up code to be closer to ANSI C and compile without warnings
  60    with more GCC compiler warnings.</li>
  61
  62 </ul>
  63
  64 <p>This change bring together patches for lsdvd in use in various
  65 Linux and Unix distributions, as well as patches submitted to the
  66 project the last nine years.  Please check it out. :)</p>
  67
  68       </div>
  69       <div class="tags">
  70
  71
  72         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>.
  73
  74
  75       </div>
  76     </div>
  77     <div class="padding"></div>
  78
  79     <div class="entry">
  80       <div class="title">
  81         <a href="http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html">Suddenly I am the new upstream of the lsdvd command line tool</a>
  82       </div>
  83       <div class="date">
  84         25th September 2014
  85       </div>
  86       <div class="body">
  87         <p>I use the <a href="https://sourceforge.net/p/lsdvd/">lsdvd tool</a>
  88 to handle my fairly large DVD collection.  It is a nice command line
  89 tool to get details about a DVD, like title, tracks, track length,
  90 etc, in XML, Perl or human readable format.  But lsdvd have not seen
  91 any new development since 2006 and had a few irritating bugs affecting
  92 its use with some DVDs.  Upstream seemed to be dead, and in January I
  93 sent a small probe asking for a version control repository for the
  94 project, without any reply.  But I use it regularly and would like to
  95 get <a href="https://packages.qa.debian.org/lsdvd">an updated version
  96 into Debian</a>.  So two weeks ago I tried harder to get in touch with
  97 the project admin, and after getting a reply from him explaining that
  98 he was no longer interested in the project, I asked if I could take
  99 over.  And yesterday, I became project admin.</p>
 100
 101 <p>I've been in touch with a Gentoo developer and the Debian
 102 maintainer interested in joining forces to maintain the upstream
 103 project, and I hope we can get a new release out fairly quickly,
 104 collecting the patches spread around on the internet into on place.
 105 I've added the relevant Debian patches to the freshly created git
 106 repository, and expect the Gentoo patches to make it too.  If you got
 107 a DVD collection and care about command line tools, check out
 108 <a href="https://sourceforge.net/p/lsdvd/git/ci/master/tree/">the git source</a> and join
 109 <a href="https://sourceforge.net/p/lsdvd/mailman/">the project mailing
 110 list</a>. :)</p>
 111
 112       </div>
 113       <div class="tags">
 114
 115
 116         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>.
 117
 118
 119       </div>
 120     </div>
 121     <div class="padding"></div>
 122
 123     <div class="entry">
 124       <div class="title">
 125         <a href="http://people.skolelinux.org/pere/blog/Do_you_need_an_agreement_with_MPEG_LA_to_publish_and_broadcast_H_264_video_in_Norway_.html">Do you need an agreement with MPEG-LA to publish and broadcast H.264 video in Norway?</a>
 126       </div>
 127       <div class="date">
 128         25th August 2014
 129       </div>
 130       <div class="body">
 131         <p>Two years later, I am still not sure if it is legal here in Norway
 132 to use or publish a video in H.264 or MPEG4 format edited by the
 133 commercially licensed video editors, without limiting the use to
 134 create "personal" or "non-commercial" videos or get a license
 135 agreement with <a href="http://www.mpegla.com">MPEG LA</a>.  If one
 136 want to publish and broadcast video in a non-personal or commercial
 137 setting, it might be that those tools can not be used, or that video
 138 format can not be used, without breaking their copyright license.  I
 139 am not sure.
 140 <a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">Back
 141 then</a>, I found that the copyright license terms for Adobe Premiere
 142 and Apple Final Cut Pro both specified that one could not use the
 143 program to produce anything else without a patent license from MPEG
 144 LA.  The issue is not limited to those two products, though.  Other
 145 much used products like those from Avid and Sorenson Media have terms
 146 of use are similar to those from Adobe and Apple.  The complicating
 147 factor making me unsure if those terms have effect in Norway or not is
 148 that the patents in question are not valid in Norway, but copyright
 149 licenses are.</p>
 150
 151 <p>These are the terms for Avid Artist Suite, according to their
 152 <a href="http://www.avid.com/US/about-avid/legal-notices/legal-enduserlicense2">published
 153 end user</a>
 154 <a href="http://www.avid.com/static/resources/common/documents/corporate/LICENSE.pdf">license
 155 text</a> (converted to lower case text for easier reading):</p>
 156
 157 <p><blockquote>
 158 <p>18.2. MPEG-4. MPEG-4 technology may be included with the
 159 software. MPEG LA, L.L.C. requires this notice: </p>
 160
 161 <p>This product is licensed under the MPEG-4 visual patent portfolio
 162 license for the personal and non-commercial use of a consumer for (i)
 163 encoding video in compliance with the MPEG-4 visual standard (“MPEG-4
 164 video”) and/or (ii) decoding MPEG-4 video that was encoded by a
 165 consumer engaged in a personal and non-commercial activity and/or was
 166 obtained from a video provider licensed by MPEG LA to provide MPEG-4
 167 video.  No license is granted or shall be implied for any other
 168 use. Additional information including that relating to promotional,
 169 internal and commercial uses and licensing may be obtained from MPEG
 170 LA, LLC.  See http://www.mpegla.com. This product is licensed under
 171 the MPEG-4 systems patent portfolio license for encoding in compliance
 172 with the MPEG-4 systems standard, except that an additional license
 173 and payment of royalties are necessary for encoding in connection with
 174 (i) data stored or replicated in physical media which is paid for on a
 175 title by title basis and/or (ii) data which is paid for on a title by
 176 title basis and is transmitted to an end user for permanent storage
 177 and/or use, such additional license may be obtained from MPEG LA,
 178 LLC. See http://www.mpegla.com for additional details.</p>
 179
 180 <p>18.3. H.264/AVC. H.264/AVC technology may be included with the
 181 software.  MPEG LA, L.L.C. requires this notice:</p>
 182
 183 <p>This product is licensed under the AVC patent portfolio license for
 184 the personal use of a consumer or other uses in which it does not
 185 receive remuneration to (i) encode video in compliance with the AVC
 186 standard (“AVC video”) and/or (ii) decode AVC video that was encoded
 187 by a consumer engaged in a personal activity and/or was obtained from
 188 a video provider licensed to provide AVC video. No license is granted
 189 or shall be implied for any other use. Additional information may be
 190 obtained from MPEG LA, L.L.C. See http://www.mpegla.com.</p>
 191 </blockquote></p>
 192
 193 <p>Note the requirement that the videos created can only be used for
 194 personal or non-commercial purposes.</p>
 195
 196 <p>The Sorenson Media software have
 197 <a href="http://www.sorensonmedia.com/terms/">similar terms</a>:</p>
 198
 199 <p><blockquote>
 200
 201 <p>With respect to a license from Sorenson pertaining to MPEG-4 Video
 202 Decoders and/or Encoders: Any such product is licensed under the
 203 MPEG-4 visual patent portfolio license for the personal and
 204 non-commercial use of a consumer for (i) encoding video in compliance
 205 with the MPEG-4 visual standard (“MPEG-4 video”) and/or (ii) decoding
 206 MPEG-4 video that was encoded by a consumer engaged in a personal and
 207 non-commercial activity and/or was obtained from a video provider
 208 licensed by MPEG LA to provide MPEG-4 video. No license is granted or
 209 shall be implied for any other use. Additional information including
 210 that relating to promotional, internal and commercial uses and
 211 licensing may be obtained from MPEG LA, LLC. See
 212 http://www.mpegla.com.</p>
 213
 214 <p>With respect to a license from Sorenson pertaining to MPEG-4
 215 Consumer Recorded Data Encoder, MPEG-4 Systems Internet Data Encoder,
 216 MPEG-4 Mobile Data Encoder, and/or MPEG-4 Unique Use Encoder: Any such
 217 product is licensed under the MPEG-4 systems patent portfolio license
 218 for encoding in compliance with the MPEG-4 systems standard, except
 219 that an additional license and payment of royalties are necessary for
 220 encoding in connection with (i) data stored or replicated in physical
 221 media which is paid for on a title by title basis and/or (ii) data
 222 which is paid for on a title by title basis and is transmitted to an
 223 end user for permanent storage and/or use. Such additional license may
 224 be obtained from MPEG LA, LLC. See http://www.mpegla.com for
 225 additional details.</p>
 226
 227 </blockquote></p>
 228
 229 <p>Some free software like
 230 <a href="https://handbrake.fr/">Handbrake</A> and
 231 <a href="http://ffmpeg.org/">FFMPEG</a> uses GPL/LGPL licenses and do
 232 not have any such terms included, so for those, there is no
 233 requirement to limit the use to personal and non-commercial.</p>
 234
 235       </div>
 236       <div class="tags">
 237
 238
 239         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 240
 241
 242       </div>
 243     </div>
 244     <div class="padding"></div>
 245
 246     <div class="entry">
 247       <div class="title">
 248         <a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html">Hvordan enkelt laste ned filmer fra NRK med den "nye" løsningen</a>
 249       </div>
 250       <div class="date">
 251         16th June 2014
 252       </div>
 253       <div class="body">
 254         <p>Jeg har fortsatt behov for å kunne laste ned innslag fra NRKs
 255 nettsted av og til for å se senere når jeg ikke er på nett, men
 256 <a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html">min
 257 oppskrift fra 2011</a> sluttet å fungere da NRK byttet
 258 avspillermetode.  I dag fikk jeg endelig lett etter oppdatert løsning,
 259 og jeg er veldig glad for å fortelle at den enkleste måten å laste ned
 260 innslag er å bruke siste versjon 2014.06.07 av
 261 <a href="http://rg3.github.io/youtube-dl/">youtube-dl</a>.  Støtten i
 262 youtube-dl <a href="https://github.com/rg3/youtube-dl/issues/2980">kom
 263 inn for 23 dager siden</a> og
 264 <a href="http://packages.qa.debian.org/y/youtube-dl.html">versjonen i
 265 Debian</a> fungerer fint også som backport til Debian Wheezy.  Det er
 266 et lite problem, det håndterer kun URLer med små bokstaver, men hvis
 267 en har en URL med store bokstaver kan en bare gjøre alle store om til
 268 små bokstaver for å få youtube-dl til å laste ned.  Rapporterte
 269 nettopp
 270 <a href="https://github.com/rg3/youtube-dl/issues/2980">problemet til
 271 utviklerne</a>, og antar de får fikset det snart.</p>
 272
 273 <p>Dermed er alt klart til å laste ned dokumentarene om
 274 <a href="http://tv.nrk.no/program/KOID23005014/usas-hemmelige-avlytting">USAs
 275 hemmelige avlytting</a> og
 276 <a href="http://tv.nrk.no/program/KOID23005114/selskapene-bak-usas-avlytting">Selskapene
 277 bak USAs avlytting</a>, i tillegg til
 278 <a href="http://tv.nrk.no/program/KOID20005814/et-moete-med-edward-snowden">intervjuet
 279 med Edward Snowden gjort av den tyske tv-kanalen ARD</a>.  Anbefaler
 280 alle å se disse, sammen med
 281 <a href="http://media.ccc.de/browse/congress/2013/30C3_-_5713_-_en_-_saal_2_-_201312301130_-_to_protect_and_infect_part_2_-_jacob.html">foredraget
 282 til Jacob Appelbaum på siste CCC-konferanse</a>, for å forstå mer om
 283 hvordan overvåkningen av borgerne brer om seg.</p>
 284
 285 <p>Takk til gode venner på foreningen NUUGs IRC-kanal
 286 <a href="irc://irc.freenode.net/%23nuug">#nuug på irc.freenode.net</a>
 287 for tipsene som fikk meg i mål</a>.</p>
 288
 289 <p><strong>Oppdatering 2014-06-17</strong>: Etter at jeg publiserte
 290 denne, ble jeg tipset om bloggposten
 291 "<a href="http://ingvar.blog.redpill-linpro.com/2012/05/31/downloading-hd-content-from-tv-nrk-no/">Downloading
 292 HD content from tv.nrk.no</a>" av Ingvar Hagelund, som har alternativ
 293 implementasjon og tips for å lage mkv-fil med undertekstene inkludert.
 294 Kanskje den passer bedre for deg?  I tillegg ble feilen i youtube-dl
 295 ble fikset litt senere ut på dagen i går, samt at youtube-dl fikk
 296 støtte for å laste ned undertitler.  Takk til Anders Einar Hilden for
 297 god innsats og youtube-dl-utviklerne for rask respons.</p>
 298
 299       </div>
 300       <div class="tags">
 301
 302
 303         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 304
 305
 306       </div>
 307     </div>
 308     <div class="padding"></div>
 309
 310     <div class="entry">
 311       <div class="title">
 312         <a href="http://people.skolelinux.org/pere/blog/Half_the_Coverity_issues_in_Gnash_fixed_in_the_next_release.html">Half the Coverity issues in Gnash fixed in the next release</a>
 313       </div>
 314       <div class="date">
 315         29th April 2014
 316       </div>
 317       <div class="body">
 318         <p>I've been following <a href="http://www.getgnash.org/">the Gnash
 319 project</a> for quite a while now.  It is a free software
 320 implementation of Adobe Flash, both a standalone player and a browser
 321 plugin.  Gnash implement support for the AVM1 format (and not the
 322 newer AVM2 format - see
 323 <a href="http://lightspark.github.io/">Lightspark</a> for that one),
 324 allowing several flash based sites to work.  Thanks to the friendly
 325 developers at Youtube, it also work with Youtube videos, because the
 326 Javascript code at Youtube detect Gnash and serve a AVM1 player to
 327 those users. :) Would be great if someone found time to implement AVM2
 328 support, but it has not happened yet.  If you install both Lightspark
 329 and Gnash, Lightspark will invoke Gnash if it find a AVM1 flash file,
 330 so you can get both handled as free software.  Unfortunately,
 331 Lightspark so far only implement a small subset of AVM2, and many
 332 sites do not work yet.</p>
 333
 334 <p>A few months ago, I started looking at
 335 <a href="http://scan.coverity.com/">Coverity</a>, the static source
 336 checker used to find heaps and heaps of bugs in free software (thanks
 337 to the donation of a scanning service to free software projects by the
 338 company developing this non-free code checker), and Gnash was one of
 339 the projects I decided to check out.  Coverity is able to find lock
 340 errors, memory errors, dead code and more.  A few days ago they even
 341 extended it to also be able to find the heartbleed bug in OpenSSL.
 342 There are heaps of checks being done on the instrumented code, and the
 343 amount of bogus warnings is quite low compared to the other static
 344 code checkers I have tested over the years.</p>
 345
 346 <p>Since a few weeks ago, I've been working with the other Gnash
 347 developers squashing bugs discovered by Coverity.  I was quite happy
 348 today when I checked the current status and saw that of the 777 issues
 349 detected so far, 374 are marked as fixed.  This make me confident that
 350 the next Gnash release will be more stable and more dependable than
 351 the previous one.  Most of the reported issues were and are in the
 352 test suite, but it also found a few in the rest of the code.</p>
 353
 354 <p>If you want to help out, you find us on
 355 <a href="https://lists.gnu.org/mailman/listinfo/gnash-dev">the
 356 gnash-dev mailing list</a> and on
 357 <a href="irc://irc.freenode.net/#gnash">the #gnash channel on
 358 irc.freenode.net IRC server</a>.</p>
 359
 360       </div>
 361       <div class="tags">
 362
 363
 364         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 365
 366
 367       </div>
 368     </div>
 369     <div class="padding"></div>
 370
 371     <div class="entry">
 372       <div class="title">
 373         <a href="http://people.skolelinux.org/pere/blog/Video_DVD_reader_library___python_dvdvideo___nice_free_software.html">Video DVD reader library / python-dvdvideo - nice free software</a>
 374       </div>
 375       <div class="date">
 376         21st March 2014
 377       </div>
 378       <div class="body">
 379         <p>Keeping your DVD collection safe from scratches and curious
 380 children fingers while still having it available when you want to see a
 381 movie is not straight forward.  My preferred method at the moment is
 382 to store a full copy of the ISO on a hard drive, and use VLC, Popcorn
 383 Hour or other useful players to view the resulting file.  This way the
 384 subtitles and bonus material are still available and using the ISO is
 385 just like inserting the original DVD record in the DVD player.</p>
 386
 387 <p>Earlier I used dd for taking security copies, but it do not handle
 388 DVDs giving read errors (which are quite a few of them).  I've also
 389 tried using
 390 <a href="http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html">dvdbackup
 391 and genisoimage</a>, but these days I use the marvellous python library
 392 and program
 393 <a href="http://bblank.thinkmo.de/blog/new-software-python-dvdvideo">python-dvdvideo</a>
 394 written by Bastian Blank.  It is
 395 <a href="http://packages.qa.debian.org/p/python-dvdvideo.html">in Debian
 396 already</a> and the binary package name is python3-dvdvideo. Instead
 397 of trying to read every block from the DVD, it parses the file
 398 structure and figure out which block on the DVD is actually in used,
 399 and only read those blocks from the DVD.  This work surprisingly well,
 400 and I have been able to almost backup my entire DVD collection using
 401 this method.</p>
 402
 403 <p>So far, python-dvdvideo have failed on between 10 and
 404 20 DVDs, which is a small fraction of my collection.  The most common
 405 problem is
 406 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720831">DVDs
 407 using UTF-16 instead of UTF-8 characters</a>, which according to
 408 Bastian is against the DVD specification (and seem to cause some
 409 players to fail too).  A rarer problem is what seem to be inconsistent
 410 DVD structures, as the python library
 411 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723079">claim
 412 there is a overlap between objects</a>.  An equally rare problem claim
 413 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741878">some
 414 value is out of range</a>.  No idea what is going on there.  I wish I
 415 knew enough about the DVD format to fix these, to ensure my movie
 416 collection will stay with me in the future.</p>
 417
 418 <p>So, if you need to keep your DVDs safe, back them up using
 419 python-dvdvideo. :)</p>
 420
 421       </div>
 422       <div class="tags">
 423
 424
 425         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 426
 427
 428       </div>
 429     </div>
 430     <div class="padding"></div>
 431
 432     <div class="entry">
 433       <div class="title">
 434         <a href="http://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html">IETF activity to standardise video codec</a>
 435       </div>
 436       <div class="date">
 437         15th September 2012
 438       </div>
 439       <div class="body">
 440         <p>After the
 441 <a href="http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html">Opus
 442 codec made</a> it into <a href="http://www.ietf.org/">IETF</a> as
 443 <a href="http://tools.ietf.org/html/rfc6716">RFC 6716</a>, I had a look
 444 to see if there is any activity in IETF to standardise a video codec
 445 too, and I was happy to discover that there is some activity in this
 446 area.  A non-"working group" mailing list
 447 <a href="https://www.ietf.org/mailman/listinfo/video-codec">video-codec</a>
 448 was
 449 <a href="http://ietf.10.n7.nabble.com/New-Non-WG-Mailing-List-video-codec-Video-codec-BoF-discussion-list-td119548.html">created 2012-08-20</a>.  It is intended to discuss the topic and if a
 450 formal working group should be formed.</p>
 451
 452 <p>I look forward to see how this plays out.  There is already
 453 <a href="http://www.ietf.org/mail-archive/web/video-codec/current/msg00003.html">an
 454 email from someone</a> in the MPEG group at ISO asking people to
 455 participate in the ISO group.  Given how ISO failed with OOXML and given
 456 that it so far (as far as I can remember) only have produced
 457 multimedia formats requiring royalty payments, I suspect
 458 joining the ISO group would be a complete waste of time, but I am not
 459 involved in any codec work and my opinion will not matter much.</p>
 460
 461 <p>If one of my readers is involved with codec work, I hope she will
 462 join this work to standardise a royalty free video codec within
 463 IETF.</p>
 464
 465       </div>
 466       <div class="tags">
 467
 468
 469         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 470
 471
 472       </div>
 473     </div>
 474     <div class="padding"></div>
 475
 476     <div class="entry">
 477       <div class="title">
 478         <a href="http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html">IETF standardize its first multimedia codec: Opus</a>
 479       </div>
 480       <div class="date">
 481         12th September 2012
 482       </div>
 483       <div class="body">
 484         <p>Yesterday, <a href="http://www.ietf.org/">IETF</a> announced the
 485 publication of of
 486 <a href="http://tools.ietf.org/html/rfc6716">RFC 6716, the Definition
 487 of the Opus Audio Codec</a>, a low latency, variable bandwidth, codec
 488 intended for both VoIP, film and music.  This is the first time, as
 489 far as I know, that IETF have standardized a multimedia codec.  In
 490 <a href="http://tools.ietf.org/html/rfc3533">RFC 3533</a>, IETF
 491 standardized the OGG container format, and it has proven to be a great
 492 royalty free container for audio, video and movies.  I hope IETF will
 493 continue to standardize more royalty free codeces, after ISO and MPEG
 494 have proven incapable of securing everyone equal rights to publish
 495 multimedia content on the Internet.</p>
 496
 497 <p>IETF require two interoperating independent implementations to
 498 ratify a standard, and have so far ensured to only standardize royalty
 499 free specifications.  Both are key factors to allow everyone (rich and
 500 poor), to compete on equal terms on the Internet.</p>
 501
 502 <p>Visit the <a href="http://opus-codec.org/">Opus project page</a> if
 503 you want to learn more about the solution.</p>
 504
 505       </div>
 506       <div class="tags">
 507
 508
 509         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 510
 511
 512       </div>
 513     </div>
 514     <div class="padding"></div>
 515
 516     <div class="entry">
 517       <div class="title">
 518         <a href="http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html">Git repository for song book for Computer Scientists</a>
 519       </div>
 520       <div class="date">
 521          7th September 2012
 522       </div>
 523       <div class="body">
 524         <p>As I
 525 <a href="http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html">mentioned
 526 this summer</a>, I have created a Computer Science song book a few
 527 years ago, and today I finally found time to create a public
 528 <a href="https://gitorious.org/pere-cs-songbook/pere-cs-songbook">Gitorious
 529 repository for the project</a>.</p>
 530
 531 <p>If you want to help out, please clone the source and submit patches
 532 to the HTML version.  To generate the PDF and PostScript version,
 533 please use prince XML, or let me know about a useful free software
 534 processor capable of creating a good looking PDF from the HTML.</p>
 535
 536 <p>Want to sing?  You can still find the song book in HTML, PDF and
 537 PostScript formats at
 538 <a href="http://www.hungry.com/~pere/cs-songbook/">Petter's Computer
 539 Science Songbook</a>.</p>
 540
 541       </div>
 542       <div class="tags">
 543
 544
 545         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>.
 546
 547
 548       </div>
 549     </div>
 550     <div class="padding"></div>
 551
 552     <div class="entry">
 553       <div class="title">
 554         <a href="http://people.skolelinux.org/pere/blog/Mer_oppf_lging_fra_MPEG_LA_om_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html">Mer oppfølging fra MPEG-LA om avtale med dem for å kringkaste og publisere H.264-video</a>
 555       </div>
 556       <div class="date">
 557          5th July 2012
 558       </div>
 559       <div class="body">
 560         <p>I føljetongen om H.264
 561 <a href="http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html">forlot
 562 jeg leserne i undring</a> om hvor pakken fra MPEG-LA tok veien, og om
 563 hvilke selskaper i Norge som har avtale med MPEG-LA.  Da Ryan hos
 564 MPEG-LA dro på ferie sendte jeg min melding videre til hans kollega,
 565 og dagen etter fikk jeg følgende svar derfra:</p>
 566
 567 <p><blockquote>
 568 <p>Date: Fri, 29 Jun 2012 18:32:34 +0000
 569 <br>From: Sidney Wolf &lt;SWolf (at) mpegla.com&gt;
 570 <br>To: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
 571 <br>Cc: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
 572 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
 573
 574 <p>Dear Mr. Reinholdtsen,</p>
 575
 576 <p>Thank you for your message. As you know, Ryan is currently our of the
 577 office, so it will be my pleasure to assist you.</p>
 578
 579 <p>Per your request, attached please find an electronic copy of the
 580 AVC Patent Portfolio License. Please note that the electronic copy of
 581 the License is provided as a convenience and for informational
 582 purposes only. When concluding the Licenses, only the hard copies
 583 provided by MPEG LA may be used.</p>
 584
 585 <p>To your question, MPEG LA lists our Licensees on our website
 586 according to each program.  The lists are in alphabetical order, so it
 587 is very easy to search.</p>
 588
 589 <p>I hope that this was helpful. If we can be of additional
 590 assistance, please let me know.</p>
 591
 592 <p>Kind regards,</p>
 593
 594 <p>Sidney A. Wolf
 595 <br>Manager, Global Licensing
 596 <br>MPEG LA</p>
 597 </blockquote></p>
 598
 599 <p>Selv om et epostvedlegg er nyttig for mottakeren, så håpet jeg å få
 600 et dokument jeg kunne dele med alle leserne av bloggen min, og ikke et
 601 som må deles på individuell basis.  Opphavsretten krever godkjenning
 602 fra rettighetsinnehaver før en kan gjøre slikt, så dermed fulgte jeg
 603 opp med et spørsmål om dette var greit.</p>
 604
 605 <p><blockquote>
 606 <p>Date: Wed, 4 Jul 2012 20:25:06 +0200
 607 <br>From: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
 608 <br>To: Sidney Wolf &lt;SWolf (at) mpegla.com&gt;
 609 <br>Cc: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
 610 <br>Subject: Re: Do NRK have a license agreement with MPEG-LA?</p>
 611
 612 <p>Thank you for your reply.</p>
 613
 614 <p>[Sidney Wolf]
 615 <br>&gt; Per your request, attached please find an electronic copy of the AVC
 616 <br>&gt; Patent Portfolio License. Please note that the electronic copy of
 617 <br>&gt; the License is provided as a convenience and for informational
 618 <br>&gt; purposes only. When concluding the Licenses, only the hard copies
 619 <br>&gt; provided by MPEG LA may be used.</p>
 620
 621 <p>This is useful for me to learn, but the reason I asked for the
 622 Internet address of the licensing document was to ensure I could
 623 publish a link to it when I discuss the topic of H.264 licensing here
 624 in Norway, and allow others to verify my observations.  I can not do
 625 the same with an email attachment.  Thus I would like to ask you if it
 626 is OK with MPEG LA that I publish this document on the Internet for
 627 others to read?</p>
 628
 629 <p>&gt; To your question, MPEG LA lists our Licensees on our website
 630 <br>&gt; according to each program. The lists are in alphabetical order, so
 631 <br>&gt; it is very easy to search.</p>
 632
 633 <p>I am afraid this do not help me locate Norwegian companies in the
 634 list of Licensees.  I do not know the name of all companies and
 635 organisations in Norway, and thus do not know how to locate the
 636 Norwegian ones on that list.</p>
 637
 638 <p>&gt; I hope that this was helpful. If we can be of additional assistance,
 639 <br>&gt; please let me know.</p>
 640
 641 <p>Absoutely helpful to learn more about how MPEG LA handle licensing.</p>
 642
 643 <p>--
 644 <br>Happy hacking
 645 <br>Petter Reinholdtsen</p>
 646 </blockquote></p>
 647
 648 <p>Jeg håpet også at det skulle være mulig å få vite hvilke av de
 649 mange hundre som har avtale med MPEG-LA om bruk av H.264 som holdt til
 650 i Norge.  Begge mine håp falt i grus med svaret fra MPEG-LA.
 651
 652 <p><blockquote>
 653 <p>Date: Thu, 5 Jul 2012 17:42:39 +0000
 654 <br>From: Sidney Wolf &lt;SWolf (at) mpegla.com&gt;
 655 <br>To: 'Petter Reinholdtsen' &lt;pere (at) hungry.com&gt;
 656 <br>Cc: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
 657 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
 658
 659 <p>Dear Mr. Reinholdtsen,</p>
 660
 661 <p>Thank you for your reply.</p>
 662
 663 <p>We appreciate the additional explanation you have provided and for
 664 asking our permission to publish the electronic copy of the License in
 665 advance of doing so.  Typically, MPEG LA prefers to distribute the
 666 electronic copies of our Licenses to interested parties. Therefore,
 667 please feel free to send interested parties to the AVC portion of our
 668 website, http://www.mpegla.com/main/programs/AVC/Pages/Intro.aspx for
 669 their further reference.</p>
 670
 671 <p>As previously mentioned, MPEG LA maintains a list of Licensees in good
 672 standing on our website according to each program. Due to the large
 673 volume of Licensees, it would be administratively impractical to
 674 provide this level of detail to interested parties.  Therefore, I am
 675 afraid we are not in a position to assist you with your request.</p>
 676
 677 <p>Kind regards,</p>
 678
 679 <p>Sidney A. Wolf
 680 <br>Manager, Global Licensing
 681 <br>MPEG LA</p>
 682 </blockquote></p>
 683
 684 <p>Men takket være epostvedlegget kunne jeg søke på Google etter
 685 setningen "WHEREAS, a video standard commonly referred to as AVC has
 686 been defined and is referred to in this Agreement as the “AVC
 687 Standard” (as more fully defined herein below)" som finnes i avtalen,
 688 og lokalisere en kopi fra 2007 av
 689 <a href="http://www.sec.gov/Archives/edgar/data/1342960/000119312509050004/dex1024.htm">lisensavtalen
 690 mellom MPEG-LA og DivX, Inc.</a>, slik at mine lesere kan se hvordan
 691 avtalen så ut da.  Jeg har ikke sammenlignet tekstene for å se om noe
 692 har endret seg siden den tid, men satser på at teksten er representativ.</p>
 693
 694 <p>Jeg aner fortsatt ikke hvor FedEx tok veien med pakken fra
 695 MPEG-LA.</p>
 696
 697 <p>Update 2012-07-06: Jeg er visst ikke den første som forsøker å få
 698 klarhet i problemstillinger rundt H.264, og kom nettopp over en veldig
 699 interessant bloggpost fra 2010 hos LibreVideo med tittelen
 700 "<a href="http://www.librevideo.org/blog/2010/06/14/mpeg-la-answers-some-questions-about-avch-264-licensing/">MPEG-LA
 701 answers some questions about AVC/H.264 licensing</a>.  Anbefales!</p>
 702
 703       </div>
 704       <div class="tags">
 705
 706
 707         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 708
 709
 710       </div>
 711     </div>
 712     <div class="padding"></div>
 713
 714     <div class="entry">
 715       <div class="title">
 716         <a href="http://people.skolelinux.org/pere/blog/Departementenes_servicesenter_har_ingen_avtale_om_bruk_av_H_264_med_MPEG_LA.html">Departementenes servicesenter har ingen avtale om bruk av H.264 med MPEG-LA</a>
 717       </div>
 718       <div class="date">
 719         29th June 2012
 720       </div>
 721       <div class="body">
 722         <p>Da fikk jeg nettopp svar fra
 723 <a href="http://www.dss.dep.no/">Departementenes servicesenter</a>
 724 (DSS) på
 725 <a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">mitt
 726 spørsmål om avtale rundt bruk av H.264</a>.  De har ingen avtale med
 727 MPEG LA eller dets representanter.  Her er svaret.
 728
 729 <p><blockquote>
 730
 731 <p>Date: Fri, 29 Jun 2012 07:04:42 +0000
 732 <br>From: Nielsen Mette Haga &lt;Mette-Haga.Nielsen (at) dss.dep.no&gt;
 733 <br>To: Petter Reinholdtsen &lt;petter.reinholdtsen (at) ...&gt;
 734 <br>CC: Postmottak &lt;Postmottak (at) dss.dep.no&gt;
 735 <br>Subject: SV: Innsynsbegjæring om MPEG/H.264-relaterte avtaler</p>
 736
 737 <p>DSS har ikke inngått noen egen lisensavtale med MPEG-LA eller noen som
 738 representerer MPEG-LA i Norge. Videoløsningen på regjeringen.no er
 739 levert av Smartcom:tv. Lisensforholdet rundt H.264 er ikke omtalt i
 740 vår avtale med Smartcom.</p>
 741
 742 <p>Vennlig hilsen</p>
 743
 744 <p>Mette Haga Nielsen
 745 <br>Fung. seksjonssjef</p>
 746
 747 <p>Departementenes servicesenter</p>
 748
 749 <p>Informasjonsforvaltning
 750
 751 <p>Mobil 93 09 83 51
 752 <br>E-post mette-haga.nielsen (at) dss.dep.no</p>
 753 </blockquote></p>
 754
 755 <p>Hvis den norske regjeringen representert ved DSS ikke har slik
 756 avtale, så kan en kanskje konkludere med at det ikke trengs?  Jeg er
 757 ikke trygg på at det er god juridisk grunn å stå på, men det er i det
 758 minste interessant å vite at hverken NRK eller DSS har funnet det
 759 nødvendig å ha avtale om bruk av H.264.</p>
 760
 761 <p>Det forklarer ikke hvordan de kan ignorere bruksvilkårene knyttet
 762 til bruk av opphavsrettsbeskyttet materiale de bruker til
 763 videoproduksjon, med mindre slike vilkår kan ignoreres av selskaper og
 764 privatpersoner i Norge.  Har de lov til å bryte vilkårene, eller har
 765 de brutt dem og så langt sluppet unna med det?  Jeg aner ikke.</p>
 766
 767       </div>
 768       <div class="tags">
 769
 770
 771         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 772
 773
 774       </div>
 775     </div>
 776     <div class="padding"></div>
 777
 778     <div class="entry">
 779       <div class="title">
 780         <a href="http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html">MPEG-LA mener NRK må ha avtale med dem for å kringkaste og publisere H.264-video</a>
 781       </div>
 782       <div class="date">
 783         28th June 2012
 784       </div>
 785       <div class="body">
 786         <p>Etter at NRK
 787 <a href="http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html">nektet
 788 å spore opp eventuell avtale med MPEG-LA</a> eller andre om bruk av
 789 MPEG/H.264-video etter at jeg <a
 790 href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">ba
 791 om innsyn i slike avtaler</a>, tenkte jeg at i stedet for å forsøke å
 792 få NRK til å finne en slik avtale, så burde det være like enkelt å
 793 spørre MPEG-LA om de hadde avtale med NRK.  Spørsmålet ble sendt før
 794 jeg fikk tips fra Kieran Kunhya om hvor listen over lisensinnehavere
 795 "in Good Standing" befant seg.  MPEG-LA svarte meg i dag, og kan
 796 fortelle at NRK ikke har noen avtale med dem, så da er i det minste det
 797 slått fast.  Ikke overraskende mener MPEG-LA at det trengs en avtale
 798 med MPEG-LA for å streame H.264, men deres rammer er jo
 799 rettstilstanden i USA og ikke Norge.  Jeg tar dermed den delen av
 800 svaret med en klype salt.  Jeg er dermed fortsatt ikke klok på om det
 801 trengs en avtale, og hvis det trengs en avtale her i Norge, heller
 802 ikke sikker på om NRK har en avtale med noen andre enn MPEG-LA som
 803 gjør at de ikke trenger avtale direkte med MPEG-LA.  Jeg håper NRKs
 804 jurister har vurdert dette, og at det er mulig å få tilgang til
 805 vurderingen uansett om de trenger en avtale eller ikke.</p>
 806
 807 <p>Her er epostutvekslingen med MPEG-LA så langt.  Håper ikke
 808 utvekslingen fører til NRK plutselig får en litt uventet pakke fra
 809 MPEG-LA.</p>
 810
 811 <p><blockquote>
 812 <p>Date: Mon, 25 Jun 2012 15:29:37 +0200
 813 <br>From: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
 814 <br>To: licensing-web (at) mpegla.com
 815 <br>Subject: Do NRK have a license agreement with MPEG-LA?</p>
 816
 817 <p>Hi.  I have a small question for you, that I hope it is OK that I
 818 ask.</p>
 819
 820 <p>Is there any license agreements between MPEG-LA and NRK, &lt;URL:
 821 <a href="http://www.nrk.no/">http://www.nrk.no/</a> &gt;, the
 822 Norwegian national broadcasting cooperation?  I am not sure if they
 823 need one, and am just curious if such agreeement exist.</p>
 824
 825 <p>The postal address is</p>
 826
 827 <p><blockquote>
 828   NRK
 829   <br>Postbox 8500, Majorstuen
 830   <br>0340 Oslo
 831   <br>Norway
 832 </blockquote></p>
 833
 834 <p>if it make it easier for you to locate such agreement.</p>
 835
 836 <p>Can you tell me how many entities in Norway have an agreement with
 837 MPEG-LA, and the name of these entities?</p>
 838
 839 <p>--
 840 <br>Happy hacking
 841 <br>Petter Reinholdtsen
 842 </blockquote></p>
 843
 844 <p>I dag, to dager senere, fikk jeg følgende svar:</p>
 845
 846 <p><blockquote>
 847 <p>Date: Thu, 28 Jun 2012 14:11:17 +0000
 848 <br>From: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com>
 849 <br>To: Petter Reinholdtsen &lt;pere (at) hungry.com>
 850 <br>CC: MD Administration &lt;MDAdministration (at) mpegla.com>
 851 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
 852
 853 <p>Dear Mr. Reinholdtsen,</p>
 854
 855 <p>Thank you for your message and for your interest in MPEG LA. We
 856 appreciate hearing from you and I will be happy to assist you.</p>
 857
 858 <p>To begin, I will assume that you are referring to AVC/H.264
 859 technology in your message below, as this technology is commonly used
 860 in the transmission of video content.  In that case, please allow me
 861 to briefly summarize the coverage provided by our AVC Patent Portfolio
 862 License.</p>
 863
 864 <P>Our AVC License provides coverage for end products and video
 865 services that make use of AVC/H.264 technology.  Accordingly, the
 866 party offering such end products and video to End Users concludes the
 867 AVC License and is responsible for paying the applicable royalties
 868 associated with the end products/video they offer.</p>
 869
 870 <p>While the Norwegian Broadcast Corporation (NRK) is not currently a
 871 Licensee to MPEG LA's AVC License (or any other Portfolio License
 872 offered by MPEG LA), if NRK offers AVC Video to End Users for
 873 remuneration (for example, Title-by-Title, Subscription, Free
 874 Television, or Internet Broadcast AVC Video), then NRK will need to
 875 conclude the AVC License and may be responsible for paying applicable
 876 royalties associated with the AVC Video it distributes.</p>
 877
 878 <p>Today I will send you a FedEx package containing a copy of our AVC
 879 License for your review.  You should receive the License document
 880 within the next few days.</p>
 881
 882 <p>Meanwhile, MPEG LA currently has several Norwegian Licensees that
 883 can be found under the "Licensees" header within the respective
 884 portion of our website.  For example, you may find our list of
 885 Licensees in Good Standing to our AVC License in the AVC portion of
 886 our website,
 887 <a href="http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx">http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx</a></p>
 888
 889 <p>I hope the above information is helpful.  If you have additional
 890 questions or need further assistance with the AVC License, please feel
 891 free to contact me directly.  I look forward to hearing from you again
 892 soon.</p>
 893
 894 <p>Best regards,</p>
 895
 896 <p>Ryan</p>
 897
 898 <p>Ryan M. Rodriguez
 899 <br>Licensing Associate
 900 <br>MPEG LA
 901 <br>5425 Wisconsin Avenue
 902 <br>Suite 801
 903 <br>Chevy Chase, MD 20815
 904 <br>U.S.A.
 905 <br>Phone:  +1 (301) 986-6660 x211
 906 <br>Fax:    +1 (301) 986-8575
 907 <br>Email: rrodriguez (at) mpegla.com</p>
 908
 909 </blockquote></p>
 910
 911 <p>Meldingen om utsendt FedEx-pakke var så merkelig at jeg
 912 øyeblikkelig sendte svar tilbake og spurte hva i alle dager han mente,
 913 da han jo ikke hadde fått noen postadresse som nådde meg.</p>
 914
 915 <p><blockquote>
 916
 917 <p>Date: Thu, 28 Jun 2012 16:36:15 +0200
 918 <br>From: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
 919 <br>To: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
 920 <br>Cc: MD Administration &lt;MDAdministration (at) mpegla.com&gt;
 921 <br>Subject: Re: Do NRK have a license agreement with MPEG-LA?</p>
 922
 923 <p>[Ryan Rodriguez]
 924 <br>&gt; Dear Mr. Reinholdtsen,</p>
 925
 926 <p>Thank you for your quick reply.</p>
 927
 928 <p>&gt; Today I will send you a FedEx package containing a copy of our AVC
 929 <br>&gt; License for your review.  You should receive the License document
 930 <br>&gt; within the next few days.</p>
 931
 932 <p>The part about sending a FedEx package confused me, though.  I did not
 933 <br>give you my address, nor am I associated with NRK in any way, so I hope
 934 <br>you did not try to send me a package using the address of NRK.  If you
 935 <br>would send me the Internet address of to the document, it would be more
 936 <br>useful to me to be able to download it as an electronic document.</p>
 937
 938 <p>&gt; Meanwhile, MPEG LA currently has several Norwegian Licensees that can
 939 <br>&gt; be found under the "Licensees" header within the respective portion
 940 <br>&gt; of our website.  For example, you may find our list of Licensees in
 941 <br>&gt; Good Standing to our AVC License in the AVC portion of our website,
 942 <br>&gt; http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx</p>
 943
 944 <p>How can I recognize the Norwegian licensees?</p>
 945
 946 <p>--
 947 <br>Happy hacking
 948 <br>Petter Reinholdtsen</p>
 949 </blockquote></p>
 950
 951 <p>Selv om jeg svarte kun noen minutter etter at jeg fikk eposten fra
 952 MPEG-LA, fikk jeg eposten under som automatisk var beskjed på min
 953 siste epost.  Får håpe noen likevel følger opp "FedEx-pakken".  For å
 954 øke sjansen for at noen revurderer utsending av pakke uten mottaker,
 955 videresendte jeg min epost til swolf (at) mpegla.com, så får vi se.
 956 Har ikke hørt noe mer 3 timer senere, så jeg mistenker at ingen leste
 957 min epost tidsnok.</p>
 958
 959 <p><blockquote>
 960
 961 <p>Date: Thu, 28 Jun 2012 14:36:20 +0000
 962 <br>From: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
 963 <br>To: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
 964 <br>Subject: Automatic reply: Do NRK have a license agreement with MPEG-LA?</p>
 965
 966 <p>Thank you for your message.</p>
 967
 968 <p>I will be out of the office until Thursday, July 5 and will respond
 969 to all messages upon my return.  If this is a matter that requires
 970 immediate attention, please contact Sidney Wolf (swolf (at)
 971 mpegla.com)</p>
 972
 973 <p>Best regards,</p>
 974
 975 <p>Ryan</p>
 976
 977 <p>Ryan M. Rodriguez
 978 <br>Licensing Associate
 979 <br>MPEG LA</p>
 980
 981 </blockquote></p>
 982
 983 <p>Litt klokere, men fortsatt ikke klok på mitt opprinnelige spørsmål,
 984 som er om en trenger avtale med MPEG-LA for å publisere eller
 985 kringkaste H.264-video i Norge.</p>
 986
 987       </div>
 988       <div class="tags">
 989
 990
 991         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 992
 993
 994       </div>
 995     </div>
 996     <div class="padding"></div>
 997
 998     <div class="entry">
 999       <div class="title">
1000         <a href="http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html">NRK nekter å finne og utlevere eventuell avtale med MPEG-LA</a>
1001       </div>
1002       <div class="date">
1003         25th June 2012
1004       </div>
1005       <div class="body">
1006         <p>Jeg fikk nettopp svar fra NRK på
1007 <a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">min
1008 forespørsel om kopi av avtale</a> med MPEG-LA eller andre om bruk av
1009 MPEG og/eller H.264.  Svaret har fått saksreferanse 2011/371 (mon tro
1010 hva slags sak fra 2011 dette er?) hos NRK og lyder som følger:</p>
1011
1012 <p><blockquote>
1013
1014 <p><strong>Svar på innsynsbegjæring i MPEG / H.264-relaterte
1015 avtaler</strong></p>
1016
1017 <p>Viser til innsynsbegjæring av 19. juni 2012. Kravet om innsyn
1018 gjelder avtale som gjør at NRK «ikke er begrenset av de generelle
1019 bruksvilkårene som gjelder for utstyr som bruker MPEG og/eller
1020 H.264».</p>
1021
1022 <p>I henhold til offentleglova § 28 annet ledd må innsynskravet gjelde
1023 en bestemt sak eller i rimelig utstrekning saker av en bestemt
1024 sak. Det er på det rene at det aktuelle innsynskravet ikke gjelder en
1025 bestemt sak. Spørsmålet som reiser seg er om identifiseringsgraden er
1026 tilstrekkelig. I Justisdepartementets «Rettleiar til offentleglova»
1027 står følgende:</p>
1028
1029 <p>«Kravet om at innsynskravet må gjelde ei bestemt sak er til hinder
1030 for at eit innsynskrav kan gjelde alle saker av ein bestemt art, utan
1031 at den enkelte saka blir identifisert.  Ein kan med andre ord i
1032 utgangspunktet ikkje krevje innsyn i til dømes alle saker om
1033 utsleppsløyve hos Statens forureiningstilsyn frå dei siste tre åra,
1034 med mindre ein identifiserer kvar enkelt sak, til dømes med tilvising
1035 til dato, partar eller liknande.»</p>
1036
1037 <p>Vedrørende denne begrensningen har Justisdepartementet uttalt
1038 følgende (Lovavdelingens uttalelser JDLOV-2010-3295):</p>
1039
1040 <p><em>«Bakgrunnen for avgrensinga av kva innsynskravet kan gjelde,
1041 er fyrst og fremst at meir generelle innsynskrav, utan noka form for
1042 identifikasjon av kva ein eigentleg ynskjer, ville vere svært
1043 vanskelege å handsame for forvaltninga.»</em></p>
1044
1045 <p>I samme sak uttaler Lovavdelingen følgende:</p>
1046
1047 <p><em>«Det følgjer vidare av offentleglova § 28 andre ledd at det `i
1048 rimeleg utstrekning' kan krevjast innsyn i `saker av ein bestemt
1049 art'. Vilkåret om at eit innsynskrav berre `i rimeleg utstrekning' kan
1050 gjelde saker av ein bestemt art, er i hovudsak knytt til kor
1051 arbeidskrevjande det vil vere å finne fram til dei aktuelle
1052 dokumenta. I tillegg reknar vi med at vilkåret kan gje grunnlag for å
1053 nekte innsyn i tilfelle der innsynskravet er så omfattande (gjeld så
1054 mange dokument) at arbeidsmengda som ville gått med til å handsame
1055 det, er større enn det ein `i rimeleg utstrekning' kan krevje (sjølv
1056 om det nok skal mykje til).»</em></p>
1057
1058 <p>NRK har ikke noen egen sammenstilling over avtaler innenfor
1059 bestemte områder som omtales i innsynsbegjæringen. De måtte søkes på
1060 vanlig måte. I tillegg finnes ikke noen automatisert måte å finne
1061 avtaler som «ikke er begrenset av de generelle bruksvilkårene som
1062 gjelder for utstyr som bruker MPEG og/eller H.264». En slik
1063 gjennomgang av avtaler måtte gjøres manuelt av en person med
1064 spesialistkunnskap. Dette vil kreve at NRK avsetter omfattende
1065 ressurser for å finne frem relevante avtaler og for deretter å vurdere
1066 om de dekkes av det innsynsbegjæringen omfattes.</p>
1067
1068 <p>På bakgrunn av dette nekter NRK innsyn, med den begrunnelsen at
1069 innsynskravet er så omfattende at arbeidsmengden for å håndtere kravet
1070 vil være langt større enn det som i rimelig utstrekning kan kreves i
1071 henhold til offentleglova § 28 annet ledd.</p>
1072
1073 <p>Avslag på deres innsynsbegjæring kan påklages til Kultur- og
1074 kirkedepartementet innen tre uker fra det tidspunkt avslaget kommer
1075 frem til mottakeren, i henhold til reglene i offentleglova § 32,
1076 jf. forvaltningsloven kapittel VI. Klagen skal stiles til Kultur- og
1077 kirkedepartementet, og sendes til NRK.</p>
1078
1079 <p>NRK er imidlertid etter Offentleglova forpliktet å gi ut journaler,
1080 slik at en eventuell søknad om innsyn kan tydeligere identifisere
1081 hvilke dokumenter som det ønskes innsyn i. NRKs offentlige journaler
1082 for inneværende og forrige måned ligger ute på
1083 NRK.no/innsyn. Journaler som går lengre tilbake i tid, kan sendes ut
1084 på forespørsel til innsyn (at) nrk.no.</p>
1085
1086 <p>Med hilsen
1087 <br>Dokumentarkivet i NRK
1088 <br>v/ Elin Brandsrud
1089 <br>Tel. direkte: 23 04 29 29
1090 <br>Post: RBM3, Postboks 8500 Majorstuen, 0340 Oslo
1091 <br>innsyn (at) nrk.no</p>
1092
1093 </blockquote></p>
1094
1095 <p>Svaret kom
1096 <a href="http://people.skolelinux.org/pere/blog/images/2012-06-25-video-mpegla-nrk.pdf">i
1097 PDF-form som vedlegg på epost</a>.  Jeg er litt usikker på hvordan jeg
1098 best går videre for å bli klok, men jeg har jo i hvert fall tre uker
1099 på å vurdere om jeg skal klage.  Enten må nok forespørselen
1100 reformuleres eller så må jeg vel klage.  Synes jo det er merkelig at
1101 NRK ikke har bedre kontroll med hvilke avtaler de har inngått.  Det
1102 burde jo være noen i ledelsen som vet om de har signert en avtale med
1103 MPEG-LA eller ikke...</p>
1104
1105 <p>Oppdatering 2012-06-25 20:20: Et google-søk på "2011/371 nrk"
1106 sendte meg til postjournalen for
1107 <a href="http://nrk.no/contentfile/file/1.8212365!offentligjournal19062012.pdf">2012-06-19</a>
1108 og
1109 <a href="http://nrk.no/contentfile/file/1.8214156!offentligjournal20062012.pdf">2012-06-20</a>
1110 hos NRK som viser mine forespørsler og viser at sakens tittel hos NRK
1111 er "Graphic Systems Regions MA 2378/10E".  Videre søk etter "Graphic
1112 Systems Regions" viser at dette er saken til et anbud om
1113 "<a href="http://no.mercell.com/m/mts/Tender/27179412.aspx">a graphics
1114 system for 12 or 13 sites broadcasting regional news</a>" hos Mercell
1115 Sourcing Service, også omtalt på
1116 <a href="http://www.publictenders.net/tender/595705">Public
1117 Tenders</a> og
1118 <a href="http://www.doffin.no/search/show/search_view.aspx?ID=JAN155521">Doffin</a>.
1119 Jeg er dog usikker på hvordan dette er relatert til min
1120 forespørsel.</p>
1121
1122 <p>Oppdatering 2012-06-25 22:40: Ble tipset av Kieran Kunhya, fra
1123 miljøet rundt
1124 <a href="http://code.google.com/p/open-broadcast-encoder/">Open
1125 Broadcast Encoder</a>, at listen over de som har lisensavtale med
1126 MPEG-LA er
1127 <a href="http://www.mpeg-la.com/main/programs/AVC/Pages/Licensees.aspx">tilgjengelig
1128 på web</a>.  Veldig fint å oppdage hvor den finnes, da jeg må ha lett
1129 etter feil ting da jeg forsøke å finne den.  Der står ikke NRK, men
1130 flere andre "Broadcasting Company"-oppføringer.  Lurer på om det betyr
1131 at NRK ikke trenger avtale, eller noe helt annet?</p>
1132
1133       </div>
1134       <div class="tags">
1135
1136
1137         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1138
1139
1140       </div>
1141     </div>
1142     <div class="padding"></div>
1143
1144     <div class="entry">
1145       <div class="title">
1146         <a href="http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html">Song book for Computer Scientists</a>
1147       </div>
1148       <div class="date">
1149         24th June 2012
1150       </div>
1151       <div class="body">
1152         <p>Many years ago, while studying Computer Science at the
1153 <a href="http://www.uit.no/">University of Tromsø</a>, I started
1154 collecting computer related songs for use at parties.  The original
1155 version was written in LaTeX, but a few years ago I got help from
1156 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
1157 while keeping the ability to create a nice book in PDF format.  I have
1158 not had time to maintain the book for a while now, and guess I should
1159 put it up on some public version control repository where others can
1160 help me extend and update the book.  If anyone is volunteering to help
1161 me with this, send me an email.  Also let me know if there are songs
1162 missing in my book.</p>
1163
1164 <p>I have not mentioned the book on my blog so far, and it occured to
1165 me today that I really should let all my readers share the joys of
1166 singing out load about programming, computers and computer networks.
1167 Especially now that <a href="http://debconf12.debconf.org/">Debconf
1168 12</a> is about to start (and I am not going).  Want to sing?  Check
1169 out <a href="http://www.hungry.com/~pere/cs-songbook/">Petter's
1170 Computer Science Songbook</a>.
1171
1172       </div>
1173       <div class="tags">
1174
1175
1176         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>.
1177
1178
1179       </div>
1180     </div>
1181     <div class="padding"></div>
1182
1183     <div class="entry">
1184       <div class="title">
1185         <a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">Trenger en avtale med MPEG-LA for å publisere og kringkaste H.264-video?</a>
1186       </div>
1187       <div class="date">
1188         21st June 2012
1189       </div>
1190       <div class="body">
1191         <p>Trengs det avtale med MPEG-LA for å ha lovlig rett til å
1192 distribuere og kringkaste video i MPEG4 eller med videokodingen H.264?
1193 <a href="http://webmink.com/essays/h-264/">H.264 og MPEG4 er jo ikke en
1194 fri og åpen standard</a> i henhold til
1195 <a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">definisjonen
1196 til Digistan</a>, så i enkelte land er det ingen tvil om at du må ha
1197 en slik avtale, men jeg må innrømme at jeg ikke vet om det også
1198 gjelder Norge.  Det ser uansett ut til å være en juridisk interessant
1199 problemstilling.  Men jeg tenkte her om dagen som så, at hvis det er
1200 nødvendig, så har store aktører som
1201 <a href="http://www.nrk.no/">NRK</a> og
1202 <a href="http://www.regjeringen.no/">regjeringen</a> skaffet seg en
1203 slik avtale.  Jeg har derfor sendt forespørsel til begge (for
1204 regjeringen sin del er det Departementenes Servicesenter som gjør
1205 jobben), og bedt om kopi av eventuelle avtaler de har om bruk av MPEG
1206 og/eller H.264 med MPEG-LA eller andre aktører som opererer på vegne
1207 av MPEG-LA.  Her er kopi av eposten jeg har sendt til
1208 <a href="http://www.dss.dep.no/">Departementenes Servicesenter</a>.
1209 Forespørselen til NRK er veldig lik.</p>
1210
1211 <p><blockquote>
1212
1213 <p>Date: Tue, 19 Jun 2012 15:18:33 +0200
1214 <br>From: Petter Reinholdtsen
1215 <br>To: postmottak@dss.dep.no
1216 <br>Subject: Innsynsbegjæring om MPEG/H.264-relaterte avtaler
1217
1218 <p>Hei.  Jeg ber herved om innsyn og kopi av dokumenter i DSS relatert
1219 til avtaler rundt bruk av videoformatene MPEG og H.264.  Jeg er
1220 spesielt interessert i å vite om DSS har lisensavtale med MPEG-LA
1221 eller noen som representerer MPEG-LA i Norge.</p>
1222
1223 <p>MPEG og H.264 er videoformater som brukes både til kringkasting
1224 (f.eks. i bakkenett og kabel-TV) og videopublisering på web, deriblant
1225 via Adobe Flash.  MPEG-LA, &lt;URL:
1226 <a href="http://www.mpeg-la.com/">http://www.mpeg-la.com/</a> &gt;, er
1227 en organisasjon som har fått oppgaven, av de kjente rettighetshavere
1228 av immaterielle rettigheter knyttet til MPEG og H.264, å selge
1229 bruksrett for MPEG og H.264.</p>
1230
1231 <p>Via regjeringen.no kringkastes med MPEG og H.264-baserte
1232 videoformater, og dette ser ut til å være organisert av DSS.  Jeg
1233 antar dermed at DSS har avtale med en eller annen aktør om dette.</p>
1234
1235 <p>F.eks. har Adobe Premiere Pro har følgende klausul i følge &lt;URL:
1236 <a href="http://news.cnet.com/8301-30685_3-20000101-264.html">http://news.cnet.com/8301-30685_3-20000101-264.html</a>
1237 &gt;:</p>
1238
1239 <p><blockquote>
1240
1241   <p>6.17. AVC DISTRIBUTION. The following notice applies to software
1242   containing AVC import and export functionality: THIS PRODUCT IS
1243   LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND
1244   NON-COMMERCIAL USE OF A CONSUMER TO (a) ENCODE VIDEO IN COMPLIANCE
1245   WITH THE AVC STANDARD ("AVC VIDEO") AND/OR (b) DECODE AVC VIDEO THAT
1246   WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL
1247   ACTIVITY AND/OR AVC VIDEO THAT WAS OBTAINED FROM A VIDEO PROVIDER
1248   LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
1249   IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED
1250   FROM MPEG LA L.L.C. SEE
1251   <a href="http://www.mpegla.com">http://www.mpegla.com</a>.</p>
1252
1253 </blockquote></p>
1254
1255 <p>Her er det kun "non-commercial" og "personal and non-commercial"
1256 aktivitet som er tillatt uten ekstra avtale med MPEG-LA.</p>
1257
1258 <p>Et annet tilsvarende eksempel er Apple Final Cut Pro, som har
1259 følgende klausul i følge &lt;URL:
1260 <a href="http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf">http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf</a>
1261 &gt;:</p>
1262
1263 <p><blockquote>
1264
1265   <p>15. Merknad om H.264/AVC. Hvis Apple-programvaren inneholder
1266   funksjonalitet for AVC-koding og/eller AVC-dekoding, krever
1267   kommersiell bruk ekstra lisensiering og følgende gjelder:
1268   AVC-FUNKSJONALITETEN I DETTE PRODUKTET KAN KUN ANVENDES AV
1269   FORBRUKERE OG KUN FOR PERSONLIG OG IKKE- KOMMERSIELL BRUK TIL (i)
1270   KODING AV VIDEO I OVERENSSTEMMELSE MED AVC-STANDARDEN ("AVC-VIDEO")
1271   OG/ELLER (ii) DEKODING AV AVC-VIDEO SOM ER KODET AV EN FORBRUKER TIL
1272   PERSONLIG OG IKKE-KOMMERSIELL BRUK OG/ELLER DEKODING AV AVC-VIDEO
1273   FRA EN VIDEOLEVERANDØR SOM HAR LISENS TIL Å TILBY
1274   AVC-VIDEO. INFORMASJON OM ANNEN BRUK OG LISENSIERING KAN INNHENTES
1275   FRA MPEG LA L.L.C. SE HTTP://WWW.MPEGLA.COM.</p>
1276 </blockquote></p>
1277
1278 <p>Tilsvarende gjelder for andre programvarepakker, kamera, etc som
1279 bruker MPEG og H.264, at en må ha en avtale med MPEG-LA for å ha lov
1280 til å bruke programmet/utstyret hvis en skal lage noe annet enn
1281 private filmer og i ikke-kommersiell virksomhet.</p>
1282
1283 <p>Jeg er altså interessert i kopi av avtaler DSS har som gjør at en
1284 ikke er begrenset av de generelle bruksvilkårene som gjelder for
1285 utstyr som bruker MPEG og/eller H.264.</p>
1286 </blockquote></p>
1287
1288 <p>Nå venter jeg spent på svaret.  Jeg planlegger å blogge om svaret
1289 her.</p>
1290
1291       </div>
1292       <div class="tags">
1293
1294
1295         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1296
1297
1298       </div>
1299     </div>
1300     <div class="padding"></div>
1301
1302     <div class="entry">
1303       <div class="title">
1304         <a href="http://people.skolelinux.org/pere/blog/HTC_One_X___Your_video___What_do_you_mean_.html">HTC One X - Your video?  What do you mean?</a>
1305       </div>
1306       <div class="date">
1307         26th April 2012
1308       </div>
1309       <div class="body">
1310         <p>In <a href="http://www.idg.no/computerworld/article243690.ece">an
1311 article today</a> published by Computerworld Norway, the photographer
1312 <a href="http://www.urke.com/eirik/">Eirik Helland Urke</a> reports
1313 that the video editor application included with
1314 <a href="http://www.htc.com/www/smartphones/htc-one-x/#specs">HTC One
1315 X</a> have some quite surprising terms of use.  The article is mostly
1316 based on the twitter message from mister Urke, stating:
1317
1318 <p><blockquote>
1319 "<a href="http://twitter.com/urke/status/194062269724897280">Drøy
1320 brukeravtale: HTC kan bruke MINE redigerte videoer kommersielt. Selv
1321 kan jeg KUN bruke dem privat.</a>"
1322 </blockquote></p>
1323
1324 <p>I quickly translated it to this English message:</p>
1325
1326 <p><blockquote>
1327 "Arrogant user agreement: HTC can use MY edited videos
1328 commercially.  Although I can ONLY use them privately."
1329 </blockquote></p>
1330
1331 <p>I've been unable to find the text of the license term myself, but
1332 suspect it is a variation of the MPEG-LA terms I
1333 <a href="http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">discovered
1334 with my Canon IXUS 130</a>.  The HTC One X specification specifies that
1335 the recording format of the phone is .amr for audio and .mp3 for
1336 video.  AMR is
1337 <a href="http://en.wikipedia.org/wiki/Adaptive_Multi-Rate_audio_codec#Licensing_and_patent_issues">Adaptive
1338 Multi-Rate audio codec</a> with patents which according to the
1339 Wikipedia article require an license agreement with
1340 <a href="http://www.voiceage.com/">VoiceAge</a>.  MP4 is
1341 <a href="http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Patent_licensing">MPEG4 with
1342 H.264</a>, which according to Wikipedia require a licence agreement
1343 with <a href="http://www.mpegla.com/">MPEG-LA</a>.</p>
1344
1345 <p>I know why I prefer
1346 <a href="http://www.digistan.org/open-standard:definition">free and open
1347 standards</a> also for video.</p>
1348
1349       </div>
1350       <div class="tags">
1351
1352
1353         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1354
1355
1356       </div>
1357     </div>
1358     <div class="padding"></div>
1359
1360     <div class="entry">
1361       <div class="title">
1362         <a href="http://people.skolelinux.org/pere/blog/RAND_terms___non_reasonable_and_discriminatory.html">RAND terms - non-reasonable and discriminatory</a>
1363       </div>
1364       <div class="date">
1365         19th April 2012
1366       </div>
1367       <div class="body">
1368         <p>Here in Norway, the
1369 <a href="http://www.regjeringen.no/nb/dep/fad.html?id=339"> Ministry of
1370 Government Administration, Reform and Church Affairs</a> is behind
1371 a <a href="http://standard.difi.no/forvaltningsstandarder">directory of
1372 standards</a> that are recommended or mandatory for use by the
1373 government.  When the directory was created, the people behind it made
1374 an effort to ensure that everyone would be able to implement the
1375 standards and compete on equal terms to supply software and solutions
1376 to the government.  Free software and non-free software could compete
1377 on the same level.</p>
1378
1379 <p>But recently, some standards with RAND
1380 (<a href="http://en.wikipedia.org/wiki/Reasonable_and_non-discriminatory_licensing">Reasonable
1381 And Non-Discriminatory</a>) terms have made their way into the
1382 directory.  And while this might not sound too bad, the fact is that
1383 standard specifications with RAND terms often block free software from
1384 implementing them.  The reasonable part of RAND mean that the cost per
1385 user/unit is low,and the non-discriminatory part mean that everyone
1386 willing to pay will get a license.  Both sound great in theory.  In
1387 practice, to get such license one need to be able to count users, and
1388 be able to pay a small amount of money per unit or user.  By
1389 definition, users of free software do not need to register their use.
1390 So counting users or units is not possible for free software projects.
1391 And given that people will use the software without handing any money
1392 to the author, it is not really economically possible for a free
1393 software author to pay a small amount of money to license the rights
1394 to implement a standard when the income available is zero.  The result
1395 in these situations is that free software are locked out from
1396 implementing standards with RAND terms.</p>
1397
1398 <p>Because of this, when I see someone claiming the terms of a
1399 standard is reasonable and non-discriminatory, all I can think of is
1400 how this really is non-reasonable and discriminatory.  Because free
1401 software developers are working in a global market, it does not really
1402 help to know that software patents are not supposed to be enforceable
1403 in Norway.  The patent regimes in other countries affect us even here.
1404 I really hope the people behind the standard directory will pay more
1405 attention to these issues in the future.</p>
1406
1407 <p>You can find more on the issues with RAND, FRAND and RAND-Z terms
1408 from Simon Phipps
1409 (<a href="http://blogs.computerworlduk.com/simon-says/2010/11/rand-not-so-reasonable/">RAND:
1410 Not So Reasonable?</a>).</p>
1411
1412 <p>Update 2012-04-21: Just came across a
1413 <a href="http://blogs.computerworlduk.com/open-enterprise/2012/04/of-microsoft-netscape-patents-and-open-standards/index.htm">blog
1414 post from Glyn Moody</a> over at Computer World UK warning about the
1415 same issue, and urging people to speak out to the UK government.  I
1416 can only urge Norwegian users to do the same for
1417 <a href="http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder">the
1418 hearing taking place at the moment</a> (respond before 2012-04-27).
1419 It proposes to require video conferencing standards including
1420 specifications with RAND terms.</p>
1421
1422       </div>
1423       <div class="tags">
1424
1425
1426         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
1427
1428
1429       </div>
1430     </div>
1431     <div class="padding"></div>
1432
1433     <div class="entry">
1434       <div class="title">
1435         <a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html">Hvordan enkelt laste ned filmer fra NRK</a>
1436       </div>
1437       <div class="date">
1438          5th November 2011
1439       </div>
1440       <div class="body">
1441         <p>Ofte har jeg lyst til å laste ned et innslag fra NRKs nettsted for
1442 å se det senere når jeg ikke er på nett, eller for å ha det
1443 tilgjengelig når jeg en gang i fremtiden ønsker å referere til
1444 innslaget selv om NRK har fjernet det fra sine nettsider.  I dag fant
1445 jeg et lite script som fikser jobben.</p>
1446
1447 <p>Scriptet er laget av Jan Henning Thorsen og tilgjengelig fra
1448 <a href="http://jhthorsen.github.com/snippets/nrk-downloader/">github</a>,
1449 og gjør det veldig enkelt å laste ned.  Kjør <tt>nrk-downloader.sh
1450 http://www1.nrk.no/nett-tv/klipp/582810</tt> for å hente ned et enkelt
1451 innslag eller <tt>nrk-downloader.sh
1452 http://www1.nrk.no/nett-tv/kategori/3521</tt> for å laste ned alle
1453 episodene i en serie.</p>
1454
1455 <p>Det er ikke rakettforskning å laste ned NRK-"strømmer", og
1456 tidligere gjorde jeg dette manuelt med mplayer.  Scriptet til
1457 Hr. Thorsen gjør det raskere og enklere for meg, men jeg vil ikke si
1458 at det er en revolusjonerende løsning.  Jeg mener jo fortsatt at
1459 påstanden fra NRKs ansatte om at det er
1460 <a href="http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html">vesensforskjellig
1461 å legge tilgjengelig for nedlasting og for streaming</a> er
1462 meningsløs.</p>
1463
1464       </div>
1465       <div class="tags">
1466
1467
1468         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1469
1470
1471       </div>
1472     </div>
1473     <div class="padding"></div>
1474
1475     <div class="entry">
1476       <div class="title">
1477         <a href="http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html">What is missing in the Debian desktop, or why my parents use Kubuntu</a>
1478       </div>
1479       <div class="date">
1480         29th July 2011
1481       </div>
1482       <div class="body">
1483         <p>While at Debconf11, I have several times during discussions
1484 mentioned the issues I believe should be improved in Debian for its
1485 desktop to be useful for more people.  The use case for this is my
1486 parents, which are currently running Kubuntu which solve the
1487 issues.</p>
1488
1489 <p>I suspect these four missing features are not very hard to
1490 implement.  After all, they are present in Ubuntu, so if we wanted to
1491 do this in Debian we would have a source.</p>
1492
1493 <ol>
1494
1495 <li><strong>Simple GUI based upgrade of packages.</strong> When there
1496 are new packages available for upgrades, a icon in the KDE status bar
1497 indicate this, and clicking on it will activate the simple upgrade
1498 tool to handle it.  I have no problem guiding both of my parents
1499 through the process over the phone.  If a kernel reboot is required,
1500 this too is indicated by the status bars and the upgrade tool.  Last
1501 time I checked, nothing with the same features was working in KDE in
1502 Debian.</li>
1503
1504 <li><strong>Simple handling of missing Firefox browser
1505 plugins.</strong> When the browser encounter a MIME type it do not
1506 currently have a handler for, it will ask the user if the system
1507 should search for a package that would add support for this MIME type,
1508 and if the user say yes, the APT sources will be searched for packages
1509 advertising the MIME type in their control file (visible in the
1510 Packages file in the APT archive).  If one or more packages are found,
1511 it is a simple click of the mouse to add support for the missing mime
1512 type.  If the package require the user to accept some non-free
1513 license, this is explained to the user.  The entire process make it
1514 more clear to the user why something do not work in the browser, and
1515 make the chances higher for the user to blame the web page authors and
1516 not the browser for any missing features.</li>
1517
1518 <li><strong>Simple handling of missing multimedia codec/format
1519 handlers.</strong> When the media players encounter a format or codec
1520 it is not supporting, a dialog pop up asking the user if the system
1521 should search for a package that would add support for it.  This
1522 happen with things like MP3, Windows Media or H.264.  The selection
1523 and installation procedure is very similar to the Firefox browser
1524 plugin handling.  This is as far as I know implemented using a
1525 gstreamer hook.  The end result is that the user easily get access to
1526 the codecs that are present from the APT archives available, while
1527 explaining more on why a given format is unsupported by Ubuntu.</li>
1528
1529 <li><strong>Better browser handling of some MIME types.</strong> When
1530 displaying a text/plain file in my Debian browser, it will propose to
1531 start emacs to show it.  If I remember correctly, when doing the same
1532 in Kunbutu it show the file as a text file in the browser.  At least I
1533 know Opera will show text files within the browser.  I much prefer the
1534 latter behaviour.</li>
1535
1536 </ol>
1537
1538 <p>There are other nice features as well, like the simplified suite
1539 upgrader, but given that I am the one mostly doing the dist-upgrade,
1540 it do not matter much.</p>
1541
1542 <p>I really hope we could get these features in place for the next
1543 Debian release.  It would require the coordinated effort of several
1544 maintainers, but would make the end user experience a lot better.</p>
1545
1546       </div>
1547       <div class="tags">
1548
1549
1550         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1551
1552
1553       </div>
1554     </div>
1555     <div class="padding"></div>
1556
1557     <div class="entry">
1558       <div class="title">
1559         <a href="http://people.skolelinux.org/pere/blog/Gnash_enteres_Google_Summer_of_Code_2011.html">Gnash enteres Google Summer of Code 2011</a>
1560       </div>
1561       <div class="date">
1562          6th April 2011
1563       </div>
1564       <div class="body">
1565         <p><a href="http://www.getgnash.org/">The Gnash project</a> is still
1566 the most promising solution for a Free Software Flash implementation.
1567 A few days ago the project
1568 <a href="http://lists.gnu.org/archive/html/gnash-dev/2011-04/msg00011.html">announced</a>
1569 that it will participate in Google Summer of Code.  I hope many
1570 students apply, and that some of them succeed in getting AVM2 support
1571 into Gnash.</p>
1572
1573       </div>
1574       <div class="tags">
1575
1576
1577         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1578
1579
1580       </div>
1581     </div>
1582     <div class="padding"></div>
1583
1584     <div class="entry">
1585       <div class="title">
1586         <a href="http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html">Why isn't Debian Edu using VLC?</a>
1587       </div>
1588       <div class="date">
1589         27th November 2010
1590       </div>
1591       <div class="body">
1592         <p>In the latest issue of Linux Journal, the readers choices were
1593 presented, and the winner among the multimedia player were VLC.
1594 Personally, I like VLC, and it is my player of choice when I first try
1595 to play a video file or stream.  Only if VLC fail will I drag out
1596 gmplayer to see if it can do better.  The reason is mostly the failure
1597 model and trust.  When VLC fail, it normally pop up a error message
1598 reporting the problem.  When mplayer fail, it normally segfault or
1599 just hangs.  The latter failure mode drain my trust in the program.<p>
1600
1601 <p>But even if VLC is my player of choice, we have choosen to use
1602 mplayer in <a href="http://www.skolelinux.org/">Debian
1603 Edu/Skolelinux</a>.  The reason is simple.  We need a good browser
1604 plugin to play web videos seamlessly, and the VLC browser plugin is
1605 not very good.  For example, it lack in-line control buttons, so there
1606 is no way for the user to pause the video.  Also, when I
1607 <a href="http://wiki.debian.org/DebianEdu/BrowserMultimedia">last
1608 tested the browser plugins</a> available in Debian, the VLC plugin
1609 failed on several video pages where mplayer based plugins worked.  If
1610 the browser plugin for VLC was as good as the gecko-mediaplayer
1611 package (which uses mplayer), we would switch.</P>
1612
1613 <p>While VLC is a good player, its user interface is slightly
1614 annoying.  The most annoying feature is its inconsistent use of
1615 keyboard shortcuts.  When the player is in full screen mode, its
1616 shortcuts are different from when it is playing the video in a window.
1617 For example, space only work as pause when in full screen mode.  I
1618 wish it had consisten shortcuts and that space also would work when in
1619 window mode.  Another nice shortcut in gmplayer is [enter] to restart
1620 the current video.  It is very nice when playing short videos from the
1621 web and want to restart it when new people arrive to have a look at
1622 what is going on.</p>
1623
1624       </div>
1625       <div class="tags">
1626
1627
1628         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1629
1630
1631       </div>
1632     </div>
1633     <div class="padding"></div>
1634
1635     <div class="entry">
1636       <div class="title">
1637         <a href="http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html">Best å ikke fortelle noen at streaming er nedlasting...</a>
1638       </div>
1639       <div class="date">
1640         30th October 2010
1641       </div>
1642       <div class="body">
1643         <p>I dag la jeg inn en kommentar på en sak hos NRKBeta
1644 <a href="http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/">om
1645 hvordan TV-serien Blindpassasjer ble laget</a> i forbindelse med at
1646 filmene NRK la ut ikke var tilgjengelig i et
1647 <a href="http://www.digistan.org/open-standard:definition">fritt og
1648 åpent format</a>.  Dette var det jeg skrev publiserte der 07:39.</p>
1649
1650 <p><blockquote>
1651 <p>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
1652 nedlasting.  Mange av oss som kan mer enn gjennomsnittet om systemer
1653 som dette, vet at det stort sett er mulig å lure ut ting med den
1654 nødvendige forkunnskapen."</p>
1655
1656 <p>Haha.  Å streame innhold er det samme som å laste ned innhold, så å
1657 beskytte en stream mot nedlasting er ikke mulig.  Å skrive noe slikt
1658 er å forlede leseren.</p>
1659
1660 <p>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
1661 vil tillate streaming men ikke nedlasting meningsløs.</p>
1662
1663 <p>Anbefaler forresten å lese
1664 <a href="http://blogs.computerworlduk.com/simon-says/2010/10/drm-is-toxic-to-culture/index.htm">http://blogs.computerworlduk.com/simon-says/2010/10/drm-is-toxic-to-culture/index.htm</a>
1665 om hva som ville være konsekvensen hvis digitale avspillingssperrer
1666 (DRM) fungerte.  Det gjør de naturligvis ikke teknisk - det er jo
1667 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
1668 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
1669 opp under.</p>
1670 </blockquote></p>
1671
1672 <p>Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
1673 NRKBeta:</p>
1674
1675 <p><blockquote>
1676 <p>From: Anders Hofseth &lt;XXX@gmail.com>
1677 <br>To: "pere@hungry.com" &lt;pere@hungry.com>
1678 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>, Jon Ståle Carlsen &lt;XXX@gmail.com>, Henrik Lied &lt;XXX@gmail.com>
1679 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
1680 <br>Date: Sat, 30 Oct 2010 07:58:44 +0200</p>
1681
1682 <p>Hei Petter.
1683 <br>Det du forsøker dra igang er egentlig en interessant diskusjon,
1684 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
1685 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
1686 særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
1687
1688 <p>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
1689 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
1690 konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
1691
1692 <p>Med hilsen,
1693 <br>-anders</p>
1694
1695 <p>Ring meg om noe er uklart: 95XXXXXXX</p>
1696 </blockquote></p>
1697
1698 <p>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
1699 over følgende svar.  I og med at debatten er fjernet fra NRK Betas
1700 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
1701 Har fjernet epostadresser og telefonnummer til de involverte, for å
1702 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.</p>
1703
1704 <p><blockquote>
1705 <p>From: Petter Reinholdtsen &lt;pere@hungry.com>
1706 <br>To: Anders Hofseth &lt;XXX@gmail.com>
1707 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>,
1708 <br>        Jon Ståle Carlsen &lt;XXX@gmail.com>,
1709 <br>        Henrik Lied &lt;XXX@gmail.com>
1710 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
1711 <br>Date: Sat, 30 Oct 2010 08:24:34 +0200</p>
1712
1713 <p>[Anders Hofseth]
1714 <br>> Hei Petter.</p>
1715
1716 <p>Hei.</p>
1717
1718 <p>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
1719 <br>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
1720 <br>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
1721 <br>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
1722
1723 <p>Godt å se at du er enig i at dette er en interessant diskusjon.  Den
1724 vil nok fortsette en stund til.  :)</p>
1725
1726 <p>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
1727 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
1728 fortsette å legge ut arkivmateriale.</p>
1729
1730 <p>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
1731 faktum, som er at streaming er det samme som nedlasting, og at innhold
1732 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
1733 det.</p>
1734
1735 <p>Det du sier er jo at klarering av arkivmateriale for publisering på
1736 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
1737 Det er ikke et argument som holder vann. :)</p>
1738
1739 <p>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
1740 <br>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
1741 <br>> konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
1742
1743 <p>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
1744 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
1745 mot de som vil låse kulturen inne.  Jeg synes det er en skam at NRK
1746 godtar å forlede publikum.  Ville heller at NRK krever at innhold som
1747 skal sendes skal være uten bruksbegresninger og kan publiseres i
1748 formater som heller ikke har bruksbegresninger (bruksbegresningene til
1749 H.264 burde få varselbjellene i NRK til å ringe).</p>
1750
1751 <p>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
1752 påstander om at "streaming beskytter mot nedlasting" som bare er egnet
1753 til å bygge opp om en myte som er skadelig for samfunnet som helhet.</p>
1754
1755 <p>Anbefaler &lt;URL:<a href="http://webmink.com/2010/09/03/h-264-and-foss/">http://webmink.com/2010/09/03/h-264-and-foss/</a>> og en
1756 titt på
1757 &lt;URL: <a href="http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html</a> >.
1758 for å se hva slags bruksbegresninger H.264 innebærer.</p>
1759
1760 <p>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
1761 kan brukes før rettighetshaverene også innser at de er med på å skade
1762 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
1763 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
1764 langt på overtid.</p>
1765
1766 <p>> Ring meg om noe er uklart: XXX</p>
1767
1768 <p>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
1769 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
1770 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
1771 for videre diskusjon hadde dere i mine øyne kommet fra det med
1772 ryggraden på plass.</p>
1773
1774 <p>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.</p>
1775
1776 <p>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
1777 &lt;URL: <a href="http://www.archive.org/details/CopyingIsNotTheft">http://www.archive.org/details/CopyingIsNotTheft</a> > og
1778 &lt;URL: <a href="http://patentabsurdity.com/">http://patentabsurdity.com/</a> > hadde vært noe å kringkaste på
1779 NRK1. :)</p>
1780
1781 <p>Vennlig hilsen,
1782 <br>--
1783 <br>Petter Reinholdtsen</p>
1784
1785       </div>
1786       <div class="tags">
1787
1788
1789         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1790
1791
1792       </div>
1793     </div>
1794     <div class="padding"></div>
1795
1796     <div class="entry">
1797       <div class="title">
1798         <a href="http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html">Software updates 2010-10-24</a>
1799       </div>
1800       <div class="date">
1801         24th October 2010
1802       </div>
1803       <div class="body">
1804         <p>Some updates.</p>
1805
1806 <p>My <a href="http://pledgebank.com/gnash-avm2">gnash pledge</a> to
1807 raise money for the project is going well.  The lower limit of 10
1808 signers was reached in 24 hours, and so far 13 people have signed it.
1809 More signers and more funding is most welcome, and I am really curious
1810 how far we can get before the time limit of December 24 is reached.
1811 :)</p>
1812
1813 <p>On the #gnash IRC channel on irc.freenode.net, I was just tipped
1814 about what appear to be a great code coverage tool capable of
1815 generating code coverage stats without any changes to the source code.
1816 It is called
1817 <a href="http://simonkagstrom.github.com/kcov/index.html">kcov</a>,
1818 and can be used using <tt>kcov &lt;directory&gt; &lt;binary&gt;</tt>.
1819 It is missing in Debian, but the git source built just fine in Squeeze
1820 after I installed libelf-dev, libdwarf-dev, pkg-config and
1821 libglib2.0-dev.  Failed to build in Lenny, but suspect that is
1822 solvable.  I hope kcov make it into Debian soon.</p>
1823
1824 <p>Finally found time to wrap up the release notes for <a
1825 href="http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html">a
1826 new alpha release of Debian Edu</a>, and just published the second
1827 alpha test release of the Squeeze based Debian Edu /
1828 <a href="http://www.skolelinux.org/">Skolelinux</a>
1829 release.  Give it a try if you need a complete linux solution for your
1830 school, including central infrastructure server, workstations, thin
1831 client servers and diskless workstations.  A nice touch added
1832 yesterday is RDP support on the thin client servers, for windows
1833 clients to get a Linux desktop on request.</p>
1834
1835       </div>
1836       <div class="tags">
1837
1838
1839         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>.
1840
1841
1842       </div>
1843     </div>
1844     <div class="padding"></div>
1845
1846     <div class="entry">
1847       <div class="title">
1848         <a href="http://people.skolelinux.org/pere/blog/Pledge_for_funding_to_the_Gnash_project_to_get_AVM2_support.html">Pledge for funding to the Gnash project to get AVM2 support</a>
1849       </div>
1850       <div class="date">
1851         19th October 2010
1852       </div>
1853       <div class="body">
1854         <p><a href="http://www.getgnash.org/">The Gnash project</a> is the
1855 most promising solution for a Free Software Flash implementation. It
1856 has done great so far, but there is still far to go, and recently its
1857 funding has dried up.  I believe AVM2 support in Gnash is vital to the
1858 continued progress of the project, as more and more sites show up with
1859 AVM2 flash files.</p>
1860
1861 <p>To try to get funding for developing such support, I have started
1862 <a href="http://www.pledgebank.com/gnash-avm2">a pledge</a> with the
1863 following text:</P>
1864
1865 <p><blockquote>
1866
1867   <p>"I will pay 100$ to the Gnash project to develop AVM2 support but
1868   only if 10 other people will do the same."</p>
1869
1870   <p>- Petter Reinholdtsen, free software developer</p>
1871
1872   <p>Deadline to sign up by: 24th December 2010</p>
1873
1874   <p>The Gnash project need to get support for the new Flash file
1875   format AVM2 to work with a lot of sites using Flash on the
1876   web. Gnash already work with a lot of Flash sites using the old AVM1
1877   format, but more and more sites are using the AVM2 format these
1878   days. The project web page is available from
1879   http://www.getgnash.org/ . Gnash is a free software implementation
1880   of Adobe Flash, allowing those of us that do not accept the terms of
1881   the Adobe Flash license to get access to Flash sites.</p>
1882
1883   <p>The project need funding to get developers to put aside enough
1884   time to develop the AVM2 support, and this pledge is my way to try
1885   to get this to happen.</p>
1886
1887   <p>The project accept donations via the OpenMediaNow foundation,
1888   <a href="http://www.openmedianow.org/?q=node/32">http://www.openmedianow.org/?q=node/32</a> .</p>
1889
1890 </blockquote></p>
1891
1892 <p>I hope you will support this effort too.  I hope more than 10
1893 people will participate to make this happen.  The more money the
1894 project gets, the more features it can develop using these funds.
1895 :)</p>
1896
1897       </div>
1898       <div class="tags">
1899
1900
1901         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1902
1903
1904       </div>
1905     </div>
1906     <div class="padding"></div>
1907
1908     <div class="entry">
1909       <div class="title">
1910         <a href="http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">Terms of use for video produced by a Canon IXUS 130 digital camera</a>
1911       </div>
1912       <div class="date">
1913          9th September 2010
1914       </div>
1915       <div class="body">
1916         <p>A few days ago I had the mixed pleasure of bying a new digital
1917 camera, a Canon IXUS 130.  It was instructive and very disturbing to
1918 be able to verify that also this camera producer have the nerve to
1919 specify how I can or can not use the videos produced with the camera.
1920 Even thought I was aware of the issue, the options with new cameras
1921 are limited and I ended up bying the camera anyway.  What is the
1922 problem, you might ask?  It is software patents, MPEG-4, H.264 and the
1923 MPEG-LA that is the problem, and our right to record our experiences
1924 without asking for permissions that is at risk.
1925
1926 <p>On page 27 of the Danish instruction manual, this section is
1927 written:</p>
1928
1929 <blockquote>
1930 <p>This product is licensed under AT&T patents for the MPEG-4 standard
1931 and may be used for encoding MPEG-4 compliant video and/or decoding
1932 MPEG-4 compliant video that was encoded only (1) for a personal and
1933 non-commercial purpose or (2) by a video provider licensed under the
1934 AT&T patents to provide MPEG-4 compliant video.</p>
1935
1936 <p>No license is granted or implied for any other use for MPEG-4
1937 standard.</p>
1938 </blockquote>
1939
1940 <p>In short, the camera producer have chosen to use technology
1941 (MPEG-4/H.264) that is only provided if I used it for personal and
1942 non-commercial purposes, or ask for permission from the organisations
1943 holding the knowledge monopoly (patent) for technology used.</p>
1944
1945 <p>This issue has been brewing for a while, and I recommend you to
1946 read
1947 "<a href="http://www.osnews.com/story/23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA">Why
1948 Our Civilization's Video Art and Culture is Threatened by the
1949 MPEG-LA</a>" by Eugenia Loli-Queru and
1950 "<a href="http://webmink.com/2010/09/03/h-264-and-foss/">H.264 Is Not
1951 The Sort Of Free That Matters</a>" by Simon Phipps to learn more about
1952 the issue.  The solution is to support the
1953 <a href="http://www.digistan.org/open-standard:definition">free and
1954 open standards</a> for video, like <a href="http://www.theora.org/">Ogg
1955 Theora</a>, and avoid MPEG-4 and H.264 if you can.</p>
1956
1957       </div>
1958       <div class="tags">
1959
1960
1961         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1962
1963
1964       </div>
1965     </div>
1966     <div class="padding"></div>
1967
1968     <div class="entry">
1969       <div class="title">
1970         <a href="http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html">Some notes on Flash in Debian and Debian Edu</a>
1971       </div>
1972       <div class="date">
1973          4th September 2010
1974       </div>
1975       <div class="body">
1976         <p>In the <a href="http://popcon.debian.org/unknown/by_vote">Debian
1977 popularity-contest numbers</a>, the adobe-flashplugin package the
1978 second most popular used package that is missing in Debian.  The sixth
1979 most popular is flashplayer-mozilla.  This is a clear indication that
1980 working flash is important for Debian users.  Around 10 percent of the
1981 users submitting data to popcon.debian.org have this package
1982 installed.</p>
1983
1984 <p>In the report written by Lars Risan in August 2008
1985 («<a href="http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile&do=view&target=Skolelinux_i_bruk_rapport_1.0.pdf">Skolelinux
1986 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
1987 stiftelsen SLX Debian Labs</a>»), one of the most important problems
1988 schools experienced with <a href="http://www.skolelinux.org/">Debian
1989 Edu/Skolelinux</a> was the lack of working Flash.  A lot of educational
1990 web sites require Flash to work, and lacking working Flash support in
1991 the web browser and the problems with installing it was perceived as a
1992 good reason to stay with Windows.</p>
1993
1994 <p>I once saw a funny and sad comment in a web forum, where Linux was
1995 said to be the retarded cousin that did not really understand
1996 everything you told him but could work fairly well.  This was a
1997 comment regarding the problems Linux have with proprietary formats and
1998 non-standard web pages, and is sad because it exposes a fairly common
1999 understanding of whose fault it is if web pages that only work in for
2000 example Internet Explorer 6 fail to work on Firefox, and funny because
2001 it explain very well how annoying it is for users when Linux
2002 distributions do not work with the documents they receive or the web
2003 pages they want to visit.</p>
2004
2005 <p>This is part of the reason why I believe it is important for Debian
2006 and Debian Edu to have a well working Flash implementation in the
2007 distribution, to get at least popular sites as Youtube and Google
2008 Video to working out of the box.  For Squeeze, Debian have the chance
2009 to include the latest version of Gnash that will make this happen, as
2010 the new release 0.8.8 was published a few weeks ago and is resting in
2011 unstable.  The new version work with more sites that version 0.8.7.
2012 The Gnash maintainers have asked for a freeze exception, but the
2013 release team have not had time to reply to it yet.  I hope they agree
2014 with me that Flash is important for the Debian desktop users, and thus
2015 accept the new package into Squeeze.</p>
2016
2017       </div>
2018       <div class="tags">
2019
2020
2021         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
2022
2023
2024       </div>
2025     </div>
2026     <div class="padding"></div>
2027
2028     <div class="entry">
2029       <div class="title">
2030         <a href="http://people.skolelinux.org/pere/blog/Regjerningens_oppsummering_av_h_ringen_om_standardkatalogen_versjon_2.html">Regjerningens oppsummering av høringen om standardkatalogen versjon 2</a>
2031       </div>
2032       <div class="date">
2033          9th July 2009
2034       </div>
2035       <div class="body">
2036         <p>For å forstå mer om hvorfor standardkatalogens versjon 2 ble som
2037 den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
2038 for regjeringen da de tok sin avgjørelse.  De er nå lagt ut på NUUGs
2039 wiki, direkte tilgjengelig via "<a
2040 href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon.pdf">Referansekatalogen
2041 v2.0 - Oppsummering av høring</a>" og "<a
2042 href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon-katalogutkast.pdf">Referansekatalog
2043 for IT-standarder i offentlig sektor Versjon 2.0, dd.mm.åååå -
2044 UTKAST</a>".</p>
2045
2046 <p>Det er tre ting jeg merker meg i oppsummeringen fra
2047 høringsuttalelsen da jeg skummet igjennom den.  Det første er at
2048 forståelsen av hvordan programvarepatenter påvirker fri
2049 programvareutvikling også i Norge når en argumenterer med at
2050 royalty-betaling ikke er et relevant problem i Norge.  Det andre er at
2051 FAD ikke har en prinsipiell forståelse av verdien av en enkelt
2052 standard innenfor hvert område.  Det siste er at påstander i
2053 høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
2054 Microsoft om hvordan Ogg blir standardisert og påstanden fra
2055 politidirektoratet om patentproblemer i Theora).</p>
2056
2057       </div>
2058       <div class="tags">
2059
2060
2061         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
2062
2063
2064       </div>
2065     </div>
2066     <div class="padding"></div>
2067
2068     <div class="entry">
2069       <div class="title">
2070         <a href="http://people.skolelinux.org/pere/blog/Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html">Regjerningen forlater prinsippet om ingen royalty-betaling i standardkatalogen versjon 2</a>
2071       </div>
2072       <div class="date">
2073          6th July 2009
2074       </div>
2075       <div class="body">
2076         <p>Jeg ble glad da regjeringen
2077 <a href="http://www.digi.no/817635/her-er-statens-nye-it-standarder">annonserte</a>
2078 versjon 2 av
2079 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf">statens
2080 referansekatalog over standarder</a>, men trist da jeg leste hva som
2081 faktisk var vedtatt etter
2082 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html">høringen</a>.
2083 De fleste av de valgte åpne standardene er gode og vil bidra til at
2084 alle kan delta på like vilkår i å lage løsninger for staten, men
2085 noen av dem blokkerer for de som ikke har anledning til å benytte
2086 spesifikasjoner som krever betaling for bruk (såkalt
2087 royalty-betaling).  Det gjelder spesifikt for H.264 for video og MP3
2088 for lyd.  Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
2089 Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
2090 fra statens websider gjøre dette uten å måtte bruke programmer der
2091 betaling for bruk var nødvendig.  Når det nå er gjort valgfritt for
2092 de statlige etatene å bruke enten H.264 eller Theora (og MP3 eler
2093 Vorbis), så vil en bli tvunget til å forholde seg til
2094 royalty-belastede standarder for å få tilgang til videoen og
2095 lyden.</p>
2096
2097 <p>Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
2098 at alle standarder som ble valgt til å være påkrevd i katalogen skulle
2099 være uten royalty-betaling.  Jeg håper det ikke betyr at en har mistet
2100 all forståelse for hvilke prinsipper som må følges for å oppnå
2101 likeverdig konkurranse mellom aktørene i IT-bransjen.  NUUG advarte
2102 mot dette i
2103 <a href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2">sin
2104 høringsuttalelse</a>, men ser ut til å ha blitt ignorert.</p>
2105
2106 <p>Oppdatering 2012-06-29: Kom over <ahref="
2107 http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf">en
2108 rapport til FAD</a> fra da versjon 1 av katalogen ble vedtatt, og der
2109 er det tydelig at problemstillingen var kjent og forstått.</p>
2110
2111       </div>
2112       <div class="tags">
2113
2114
2115         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
2116
2117
2118       </div>
2119     </div>
2120     <div class="padding"></div>
2121
2122     <div class="entry">
2123       <div class="title">
2124         <a href="http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html">Microsofts misvisende argumentasjon rundt multimediaformater</a>
2125       </div>
2126       <div class="date">
2127         26th June 2009
2128       </div>
2129       <div class="body">
2130         <p>I
2131 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf">Microsoft
2132 sin høringsuttalelse</a> til
2133 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html?id=549422">forslag
2134 til versjon 2 av statens referansekatalog over standarder</a>, lirer
2135 de av seg følgende FUD-perle:</p>
2136
2137 <p><blockquote>"Vorbis, OGG, Theora og FLAC er alle tekniske
2138   spesifikasjoner overordnet styrt av xiph.org, som er en
2139   ikke-kommersiell organisasjon.  Etablerte og anerkjente
2140   standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
2141   innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
2142   Det er derimot helt opp til hver enkelt organisasjon å bestemme
2143   hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
2144   spesifikasjonene bør derfor ikke defineres som åpne
2145   standarder."</blockquote></p>
2146
2147 <p>De vokter seg vel for å nevne den anerkjente
2148 standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
2149 IP og det meste av protokoller på Internet, og RFC-standardene som
2150 IETF står bak.  Ogg er spesifisert i
2151 <a href="http://ietf.org/rfc/rfc3533.txt">RFC 3533</a>, og er uten
2152 tvil å anse som en åpen standard.  Vorbis er
2153 <a href="http://ietf.org/rfc/rfc5215.txt">RFC 5215</a>.  Theora er
2154
2155 under standardisering via IETF, med
2156 <a href="http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt">siste
2157 utkast publisert 2006-07-21</a> (riktignok er dermed teksten ikke
2158 skrevet i stein ennå, men det blir neppe endringer som ikke er
2159 bakoverkompatibel).  De kan være inne på noe når det gjelder FLAC da
2160 jeg ikke finner tegn til at <a
2161 href="http://flac.sourceforge.net/format.html">spesifikasjonen
2162 tilgjengelig på web</a> er på tur via noen
2163 standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
2164 og Vorbis også har involvert seg i Flac siden 2003, så ser jeg ikke
2165 bort fra at også den organiseres via IETF.  Jeg kjenner personlig lite
2166 til FLAC.</p>
2167
2168 <p>Uredelig argumentasjon bør en holde seg for god til å komme med,
2169 spesielt når det er så enkelt i dagens Internet-hverdag å gå
2170 misvisende påstander etter i sømmene.</p>
2171
2172       </div>
2173       <div class="tags">
2174
2175
2176         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
2177
2178
2179       </div>
2180     </div>
2181     <div class="padding"></div>
2182
2183     <div class="entry">
2184       <div class="title">
2185         <a href="http://people.skolelinux.org/pere/blog/When_web_browser_developers_make_a_video_player___.html">When web browser developers make a video player...</a>
2186       </div>
2187       <div class="date">
2188         17th January 2009
2189       </div>
2190       <div class="body">
2191         <p>As part of the work we do in <a href="http://www.nuug.no">NUUG</a>
2192 to publish video recordings of our monthly presentations, we provide a
2193 page with embedded video for easy access to the recording.  Putting a
2194 good set of HTML tags together to get working embedded video in all
2195 browsers and across all operating systems is not easy.  I hope this
2196 will become easier when the &lt;video&gt; tag is implemented in all
2197 browsers, but I am not sure.  We provide the recordings in several
2198 formats, MPEG1, Ogg Theora, H.264 and Quicktime, and want the
2199 browser/media plugin to pick one it support and use it to play the
2200 recording, using whatever embed mechanism the browser understand.
2201 There is at least four different tags to use for this, the new HTML5
2202 &lt;video&gt; tag, the &lt;object&gt; tag, the &lt;embed&gt; tag and
2203 the &lt;applet&gt; tag.  All of these take a lot of options, and
2204 finding the best options is a major challenge.</p>
2205
2206 <p>I just tested the experimental Opera browser available from <a
2207 href="http://labs.opera.com">labs.opera.com</a>, to see how it handled
2208 a &lt;video&gt; tag with a few video sources and no extra attributes.
2209 I was not very impressed.  The browser start by fetching a picture
2210 from the video stream.  Not sure if it is the first frame, but it is
2211 definitely very early in the recording.  So far, so good. Next,
2212 instead of streaming the 76 MiB video file, it start to download all
2213 of it, but do not start to play the video.  This mean I have to wait
2214 for several minutes for the downloading to finish.  When the download
2215 is done, the playing of the video do not start!  Waiting for the
2216 download, but I do not get to see the video?  Some testing later, I
2217 discover that I have to add the controls="true" attribute to be able
2218 to get a play button to pres to start the video.  Adding
2219 autoplay="true" did not help.  I sure hope this is a misfeature of the
2220 test version of Opera, and that future implementations of the
2221 &lt;video&gt; tag will stream recordings by default, or at least start
2222 playing when the download is done.</p>
2223
2224 <p>The test page I used (since changed to add more attributes) is
2225 <a href="http://www.nuug.no/aktiviteter/20090113-foredrag-om-foredrag/">available
2226 from the nuug site</a>.  Will have to test it with the new Firefox
2227 too.</p>
2228
2229 <p>In the test process, I discovered a missing feature.  I was unable
2230 to find a way to get the URL of the playing video out of Opera, so I
2231 am not quite sure it picked the Ogg Theora version of the video.  I
2232 sure hope it was using the announced Ogg Theora support. :)</p>
2233
2234       </div>
2235       <div class="tags">
2236
2237
2238         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
2239
2240
2241       </div>
2242     </div>
2243     <div class="padding"></div>
2244
2245     <div class="entry">
2246       <div class="title">
2247         <a href="http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html">The sorry state of multimedia browser plugins in Debian</a>
2248       </div>
2249       <div class="date">
2250         25th November 2008
2251       </div>
2252       <div class="body">
2253         <p>Recently I have spent some time evaluating the multimedia browser
2254 plugins available in Debian Lenny, to see which one we should use by
2255 default in Debian Edu.  We need an embedded video playing plugin with
2256 control buttons to pause or stop the video, and capable of streaming
2257 all the multimedia content available on the web.  The test results and
2258 notes are available on
2259 <a href="http://wiki.debian.org/DebianEdu/BrowserMultimedia">the
2260 Debian wiki</a>.  I was surprised how few of the plugins are able to
2261 fill this need.  My personal video player favorite, VLC, has a really
2262 bad plugin which fail on a lot of the test pages.  A lot of the MIME
2263 types I would expect to work with any free software player (like
2264 video/ogg), just do not work.  And simple formats like the
2265 audio/x-mplegurl format (m3u playlists), just isn't supported by the
2266 totem and vlc plugins.  I hope the situation will improve soon.  No
2267 wonder sites use the proprietary Adobe flash to play video.</p>
2268
2269 <p>For Lenny, we seem to end up with the mplayer plugin.  It seem to
2270 be the only one fitting our needs. :/</p>
2271
2272       </div>
2273       <div class="tags">
2274
2275
2276         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
2277
2278
2279       </div>
2280     </div>
2281     <div class="padding"></div>
2282
2283     <p style="text-align: right;"><a href="multimedia.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
2284     <div id="sidebar">
2285
2286
2287
2288 <h2>Archive</h2>
2289 <ul>
2290
2291 <li>2014
2292 <ul>
2293
2294 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
2295
2296 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
2297
2298 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
2299
2300 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
2301
2302 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
2303
2304 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
2305
2306 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
2307
2308 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
2309
2310 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
2311
2312 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
2313
2314 </ul></li>
2315
2316 <li>2013
2317 <ul>
2318
2319 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
2320
2321 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
2322
2323 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
2324
2325 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
2326
2327 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
2328
2329 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
2330
2331 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
2332
2333 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
2334
2335 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
2336
2337 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
2338
2339 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
2340
2341 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
2342
2343 </ul></li>
2344
2345 <li>2012
2346 <ul>
2347
2348 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
2349
2350 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
2351
2352 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
2353
2354 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
2355
2356 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
2357
2358 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
2359
2360 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
2361
2362 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
2363
2364 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
2365
2366 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
2367
2368 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
2369
2370 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
2371
2372 </ul></li>
2373
2374 <li>2011
2375 <ul>
2376
2377 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
2378
2379 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
2380
2381 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
2382
2383 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
2384
2385 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
2386
2387 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
2388
2389 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
2390
2391 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
2392
2393 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
2394
2395 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
2396
2397 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
2398
2399 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
2400
2401 </ul></li>
2402
2403 <li>2010
2404 <ul>
2405
2406 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
2407
2408 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
2409
2410 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
2411
2412 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
2413
2414 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
2415
2416 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
2417
2418 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
2419
2420 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
2421
2422 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
2423
2424 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
2425
2426 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
2427
2428 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
2429
2430 </ul></li>
2431
2432 <li>2009
2433 <ul>
2434
2435 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
2436
2437 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
2438
2439 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
2440
2441 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
2442
2443 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
2444
2445 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
2446
2447 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
2448
2449 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
2450
2451 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
2452
2453 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
2454
2455 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
2456
2457 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
2458
2459 </ul></li>
2460
2461 <li>2008
2462 <ul>
2463
2464 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
2465
2466 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
2467
2468 </ul></li>
2469
2470 </ul>
2471
2472
2473
2474 <h2>Tags</h2>
2475 <ul>
2476
2477  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
2478
2479  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
2480
2481  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
2482
2483  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
2484
2485  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (8)</a></li>
2486
2487  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (14)</a></li>
2488
2489  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
2490
2491  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
2492
2493  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (107)</a></li>
2494
2495  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (151)</a></li>
2496
2497  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
2498
2499  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (15)</a></li>
2500
2501  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (12)</a></li>
2502
2503  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
2504
2505  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (261)</a></li>
2506
2507  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
2508
2509  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
2510
2511  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (13)</a></li>
2512
2513  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (8)</a></li>
2514
2515  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
2516
2517  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (41)</a></li>
2518
2519  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (10)</a></li>
2520
2521  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (19)</a></li>
2522
2523  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
2524
2525  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
2526
2527  <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
2528
2529  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
2530
2531  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
2532
2533  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (31)</a></li>
2534
2535  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (248)</a></li>
2536
2537  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (163)</a></li>
2538
2539  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (11)</a></li>
2540
2541  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
2542
2543  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (48)</a></li>
2544
2545  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (75)</a></li>
2546
2547  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
2548
2549  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
2550
2551  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
2552
2553  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
2554
2555  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
2556
2557  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
2558
2559  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
2560
2561  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
2562
2563  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (41)</a></li>
2564
2565  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
2566
2567  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
2568
2569  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (45)</a></li>
2570
2571  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
2572
2573  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
2574
2575  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (26)</a></li>
2576
2577  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (2)</a></li>
2578
2579  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
2580
2581  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (44)</a></li>
2582
2583  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
2584
2585  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (33)</a></li>
2586
2587 </ul>
2588
2589
2590     </div>
2591     <p style="text-align: right">
2592  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
2593 </p>
2594
2595   </body>
2596 </html>