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="https://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="https://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="https://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="https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html">ONVIF IP camera management tool finally in Debian</a>
  26       </div>
  27       <div class="date">
  28         24th December 2022
  29       </div>
  30       <div class="body">
  31         <p>Merry Christmas to you all.  Here is a small gift to all those with
  32 IP cameras following the <a href="https://www.onvif.org/">ONVIF
  33 specification</a>.  There is finally a nice command line and GUI tool
  34 in Debian to manage ONVIF IP cameras.  After working with upstream for
  35 a few months and sponsoring the upload, I am very happy to report that
  36 the <a href="https://tracker.debian.org/libonvif">libonvif package</a>
  37 entered Debian Sid last night.</p>
  38
  39 <p>The package provide a C library to communicate with such cameras, a
  40 command line tool to locate and update settings of (like password) the
  41 cameras and a GUI tool to configure and control the units as well as
  42 preview the video from the camera.  Libonvif is available on Both
  43 Linux and Windows and the GUI tool uses the Qt library.  The main
  44 competitors are non-free software, while libonvif is GNU GPL licensed.
  45 I am very glad Debian users in the future can control their cameras
  46 using a free software system provided by Debian.  But the ONVIF world
  47 is full of slightly broken firmware, where the cameras pretend to
  48 follow the ONVIF specification but fail to set some configuration
  49 values or refuse to provide video to more than one recipient at the
  50 time, and the onvif project is quite young and might take a while
  51 before it completely work with your camera.  Upstream seem eager to
  52 improve the library, so handling any broken camera might be just <a
  53 href="https://github.com/sr99622/libonvif/">a bug report away</a>.</p>
  54
  55 <p>The package just cleared NEW, and need a new source only upload
  56 before it can enter testing.  This will happen in the next few
  57 days.</p>
  58
  59 <p>As usual, if you use Bitcoin and want to show your support of my
  60 activities, please send Bitcoin donations to my address
  61 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
  62
  63       </div>
  64       <div class="tags">
  65
  66
  67         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
  68
  69
  70       </div>
  71     </div>
  72     <div class="padding"></div>
  73
  74     <div class="entry">
  75       <div class="title">
  76         <a href="https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html">Managing and using ONVIF IP cameras with Linux</a>
  77       </div>
  78       <div class="date">
  79         19th October 2022
  80       </div>
  81       <div class="body">
  82         <p>Recently I have been looking at how to control and collect data
  83 from a handful IP cameras using Linux.  I both wanted to change their
  84 settings and to make their imagery available via a free software
  85 service under my control.  Here is a summary of the tools I found.</p>
  86
  87 <p>First I had to identify the cameras and their protocols.  As far as
  88 I could tell, they were using some SOAP looking protocol and their
  89 internal web server seem to only work with Microsoft Internet Explorer
  90 with some proprietary binary plugin, which in these days of course is
  91 a security disaster and also made it impossible for me to use the
  92 camera web interface.  Luckily I discovered that the SOAP looking
  93 protocol is actually following <a href="https://www.onvif.org/">the
  94 ONVIF specification</a>, which seem to be supported by a lot of IP
  95 cameras these days.</p>
  96
  97 <p>Once the protocol was identified, I was able to find what appear to
  98 be the most popular way to configure ONVIF cameras, the free software
  99 Windows tool named
 100 <a href="https://sourceforge.net/projects/onvifdm/">ONVIF Device
 101 Manager</a>.  Lacking any other options at the time, I tried
 102 unsuccessfully to get it running using Wine, but was missing a dotnet
 103 40 library and I found no way around it to run it on Linux.</p>
 104
 105 <p>The next tool I found to configure the cameras were a non-free Linux Qt
 106 client <a href="https://www.lingodigit.com/onvif_nvcdemo.html">ONVIF
 107 Device Tool</a>.  I did not like its terms of use, so did not spend
 108 much time on it.</p>
 109
 110 <p>To collect the video and make it available in a web interface, I
 111 found the Zoneminder tool in Debian.  A recent version was able to
 112 automatically detect and configure ONVIF devices, so I could use it to
 113 set up motion detection in and collection of the camera output.  I had
 114 initial problems getting the ONVIF autodetection to work, as both
 115 Firefox and Chromium <a href="https://bugs.debian.org/1001188">refused
 116 the inter-tab communication</a> being used by the Zoneminder web
 117 pages, but managed to get konqueror to work.  Apparently the "Enhanced
 118 Tracking Protection" in Firefox cause the problem.  I ended up
 119 upgrading to the Bookworm edition of Zoneminder in the process to try
 120 to fix the issue, and believe the problem might be solved now.</p>
 121
 122 <p>In the process I came across the nice Linux GUI tool
 123 <a href="https://gitlab.com/caspermeijn/onvifviewer/">ONVIF Viewer</a>
 124 allowing me to preview the camera output and validate the login
 125 passwords required.  Sadly its author has grown tired of maintaining
 126 the software, so it might not see any future updates.  Which is sad,
 127 as the viewer is sightly unstable and the picture tend to lock up.
 128 Note, this lockup might be due to limitations in the cameras and not
 129 the viewer implementation.  I suspect the camera is only able to
 130 provide pictures to one client at the time, and the Zoneminder feed
 131 might interfere with the GUI viewer.  I have
 132 <a href="https://bugs.debian.org/1000820">asked for the tool to be
 133 included in Debian</a>.</p>
 134
 135 <p>Finally, I found what appear to be very nice Linux free software
 136 replacement for the Windows tool, named
 137 <a href="https://github.com/sr99622/libonvif/">libonvif</a>.  It
 138 provide a C library to talk to ONVIF devices as well as a command line
 139 and GUI tool using the library.  Using the GUI tool I was able to change
 140 the admin passwords and update other settings of the cameras.  I have
 141 <a href="https://bugs.debian.org/1021980">asked for the package to be
 142 included in Debian</a>.</p>
 143
 144 <p>As usual, if you use Bitcoin and want to show your support of my
 145 activities, please send Bitcoin donations to my address
 146 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 147
 148 <p><strong>Update 2022-10-20</strong>: Since my initial publication of
 149 this text, I got several suggestions for more free software Linux
 150 tools.  There is <a href="https://github.com/quatanium/python-onvif">a
 151 ONVIF python library</a> (already
 152 <a href="https://bugs.debian.org/824240">requested into Debian</a>) and
 153 <a href="https://github.com/FalkTannhaeuser/python-onvif-zeep">a python 3
 154 fork</a> using a different SOAP dependency.  There is also
 155 <a href="https://www.home-assistant.io/integrations/onvif/">support for
 156 ONVIF in Home Assistant</a>, and there is an alternative to Zoneminder
 157 called <a href="https://www.shinobi.video/">Shinobi</a>.  The latter
 158 two are not included in Debian either.  I have not tested any of these
 159 so far.</p>
 160
 161       </div>
 162       <div class="tags">
 163
 164
 165         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
 166
 167
 168       </div>
 169     </div>
 170     <div class="padding"></div>
 171
 172     <div class="entry">
 173       <div class="title">
 174         <a href="https://people.skolelinux.org/pere/blog/CasparCG_Server_for_TV_broadcast_playout_in_Debian.html">CasparCG Server for TV broadcast playout in Debian</a>
 175       </div>
 176       <div class="date">
 177         15th January 2019
 178       </div>
 179       <div class="body">
 180         <p>The layered video playout server created by Sveriges Television,
 181 <a href="https://casparcg.com/">CasparCG Server</a>, entered Debian
 182 today.  This completes many months of work to get the source ready to
 183 go into Debian.  The first upload to the Debian NEW queue happened a
 184 month ago, but the work upstream to prepare it for Debian started more
 185 than two and a half month ago.  So far
 186 <a href="https://tracker.debian.org/pkg/casparcg-server">the
 187 casparcg-server package</a> is only available for amd64, but I hope
 188 this can be improved.  The package is in contrib because it depend on
 189 the <a href="https://tracker.debian.org/pkg/fdk-aac">non-free fdk-aac
 190 library</a>.  The Debian package lack support for streaming web pages
 191 because Debian is missing CEF, Chromium Embedded Framework.  CEF is
 192 wanted by several packages in Debian.  But because the Chromium source
 193 is <a href="https://bugs.debian.org/893448">not available as a build
 194 dependency</a>, it is not yet possible to upload CEF to Debian.  I
 195 hope this will change in the future.</p>
 196
 197 <p>The reason I got involved is that
 198 <a href="https://frikanalen.no/">the Norwegian open channel
 199 Frikanalen</a> is starting to use CasparCG for our HD playout, and I
 200 would like to have all the free software tools we use to run the TV
 201 channel available as packages from the Debian project.  The last
 202 remaining piece in the puzzle is Open Broadcast Encoder, but it depend
 203 on quite a lot of patched libraries which would have to be included in
 204 Debian first.</p>
 205
 206 <p>As usual, if you use Bitcoin and want to show your support of my
 207 activities, please send Bitcoin donations to my address
 208 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 209
 210       </div>
 211       <div class="tags">
 212
 213
 214         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
 215
 216
 217       </div>
 218     </div>
 219     <div class="padding"></div>
 220
 221     <div class="entry">
 222       <div class="title">
 223         <a href="https://people.skolelinux.org/pere/blog/Add_on_to_control_the_projector_from_within_Kodi.html">Add-on to control the projector from within Kodi</a>
 224       </div>
 225       <div class="date">
 226         26th June 2018
 227       </div>
 228       <div class="body">
 229         <p>My movie playing setup involve <a href="https://kodi.tv/">Kodi</a>,
 230 <a href="https://openelec.tv">OpenELEC</a> (probably soon to be
 231 replaced with <a href="https://libreelec.tv/">LibreELEC</a>) and an
 232 Infocus IN76 video projector.  My projector can be controlled via both
 233 a infrared remote controller, and a RS-232 serial line.  The vendor of
 234 my projector, <a href="https://www.infocus.com/">InFocus</a>, had been
 235 sensible enough to document the serial protocol in its user manual, so
 236 it is easily available, and I used it some years ago to write
 237 <a href="https://github.com/petterreinholdtsen/infocus-projector-control">a
 238 small script to control the projector</a>.  For a while now, I longed
 239 for a setup where the projector was controlled by Kodi, for example in
 240 such a way that when the screen saver went on, the projector was
 241 turned off, and when the screen saver exited, the projector was turned
 242 on again.</p>
 243
 244 <p>A few days ago, with very good help from parts of my family, I
 245 managed to find a Kodi Add-on for controlling a Epson projector, and
 246 got in touch with its author to see if we could join forces and make a
 247 Add-on with support for several projectors.  To my pleasure, he was
 248 positive to the idea, and we set out to add InFocus support to his
 249 add-on, and make the add-on suitable for the official Kodi add-on
 250 repository.</p>
 251
 252 <p>The Add-on is now working (for me, at least), with a few minor
 253 adjustments.  The most important change I do relative to the master
 254 branch in the github repository is embedding the
 255 <a href="https://github.com/pyserial/pyserial">pyserial module</a> in
 256 the add-on.  The long term solution is to make a "script" type
 257 pyserial module for Kodi, that can be pulled in as a dependency in
 258 Kodi.  But until that in place, I embed it.</p>
 259
 260 <p>The add-on can be configured to turn on the projector when Kodi
 261 starts, off when Kodi stops as well as turn the projector off when the
 262 screensaver start and on when the screesaver stops.  It can also be
 263 told to set the projector source when turning on the projector.
 264
 265 <p>If this sound interesting to you, check out
 266 <a href="https://github.com/fredrik-eriksson/kodi_projcontrol">the
 267 project github repository</a>.  Perhaps you can send patches to
 268 support your projector too?  As soon as we find time to wrap up the
 269 latest changes, it should be available for easy installation using any
 270 Kodi instance.</p>
 271
 272 <p>For future improvements, I would like to add projector model
 273 detection and the ability to adjust the brightness level of the
 274 projector from within Kodi.  We also need to figure out how to handle
 275 the cooling period of the projector.  My projector refuses to turn on
 276 for 60 seconds after it was turned off.  This is not handled well by
 277 the add-on at the moment.</p>
 278
 279 <p>As usual, if you use Bitcoin and want to show your support of my
 280 activities, please send Bitcoin donations to my address
 281 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 282
 283       </div>
 284       <div class="tags">
 285
 286
 287         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
 288
 289
 290       </div>
 291     </div>
 292     <div class="padding"></div>
 293
 294     <div class="entry">
 295       <div class="title">
 296         <a href="https://people.skolelinux.org/pere/blog/youtube_dl_for_nedlasting_fra_NRK_med_undertekster___nice_free_software.html">youtube-dl for nedlasting fra NRK med undertekster - nice free software</a>
 297       </div>
 298       <div class="date">
 299         28th April 2018
 300       </div>
 301       <div class="body">
 302         <p>I <a href="https://no.wikipedia.org/wiki/VHS">VHS-kassettenes</a>
 303 tid var det rett frem å ta vare på et TV-program en ønsket å kunne se
 304 senere, uten å være avhengig av at programmet ble sendt på nytt.
 305 Kanskje ønsket en å se programmet på hytten der det ikke var
 306 TV-signal, eller av andre grunner ha det tilgjengelig for fremtidig
 307 fornøyelse.  Dette er blitt vanskeligere med introduksjon av
 308 digital-TV og webstreaming, der opptak til harddisk er utenfor de
 309 flestes kontroll hvis de bruker ufri programvare og bokser kontrollert
 310 av andre.  Men for NRK her i Norge, finnes det heldigvis flere fri
 311 programvare-alternativer, som jeg har
 312 <a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html">skrevet</a>
 313 <a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html">om</a>
 314 <a href="http://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html">før</a>.
 315 Så lenge kilden for nedlastingen er lovlig lagt ut på nett (hvilket
 316 jeg antar NRK gjør), så er slik lagring til privat bruk også lovlig i
 317 Norge.</p>
 318
 319 <p>Sist jeg så på saken, i 2016, nevnte jeg at
 320 <a href="https://rg3.github.com/youtube-dl/">youtube-dl</a> ikke kunne
 321 bake undertekster fra NRK inn i videofilene, og at jeg derfor
 322 foretrakk andre alternativer.  Nylig oppdaget jeg at dette har endret
 323 seg.  Fordelen med youtube-dl er at den er tilgjengelig direkte fra
 324 Linux-distribusjoner som <a href="https://www.debian.org/">Debian</a>
 325 og <a href="https://www.ubuntu.com/">Ubuntu</a>, slik at en slipper å
 326 finne ut selv hvordan en skal få dem til å virke.</p>
 327
 328 <p>For å laste ned et NRK-innslag med undertekster, og få den norske
 329 underteksten pakket inn i videofilen, så kan følgende kommando
 330 brukes:</p>
 331
 332 <p><pre>
 333 youtube-dl --write-sub --sub-format ttml \
 334   --convert-subtitles srt --embed-subs \
 335   https://tv.nrk.no/serie/ramm-ferdig-gaa/MUHU11000316/27-04-2018
 336 </pre></p>
 337
 338 <p>URL-eksemplet er dagens toppsak på tv.nrk.no.  Resultatet er en
 339 MP4-fil med filmen og undertekster som kan spilles av med VLC.  Merk
 340 at VLC ikke viser frem undertekster før du aktiverer dem.  For å gjøre
 341 det, høyreklikk med musa i fremviservinduet, velg menyvalget for
 342 undertekst og så norsk språk.  Jeg testet også '--write-auto-sub',
 343 men det kommandolinjeargumentet ser ikke ut til å fungere, så jeg
 344 endte opp med settet med argumentlisten over, som jeg fant i en
 345 feilrapport i youtube-dl-prosjektets samling over feilrapporter.</p>
 346
 347 <p>Denne støtten i youtube-dl gjør det svært enkelt å lagre
 348 NRK-innslag, det være seg nyheter, filmer, serier eller dokumentater,
 349 for å ha dem tilgjengelig for fremtidig referanse og bruk, uavhengig
 350 av hvor lenge innslagene ligger tilgjengelig hos NRK.  Så får det ikke
 351 hjelpe at NRKs jurister mener at det er
 352 <a href="http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html">vesensforskjellig
 353 å legge tilgjengelig for nedlasting og for streaming</a>, når det rent
 354 teknisk er samme sak.</p>
 355
 356 <p>Programmet youtube-dl støtter også en rekke andre nettsteder, se
 357 prosjektoversikten for
 358 <a href="http://rg3.github.io/youtube-dl/supportedsites.html">en
 359 komplett liste</a>.</p>
 360
 361       </div>
 362       <div class="tags">
 363
 364
 365         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
 366
 367
 368       </div>
 369     </div>
 370     <div class="padding"></div>
 371
 372     <div class="entry">
 373       <div class="title">
 374         <a href="https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html">The new "best" multimedia player in Debian?</a>
 375       </div>
 376       <div class="date">
 377          6th June 2016
 378       </div>
 379       <div class="body">
 380         <p>When I set out a few weeks ago to figure out
 381 <a href="http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html">which
 382 multimedia player in Debian claimed to support most file formats /
 383 MIME types</a>, I was a bit surprised how varied the sets of MIME types
 384 the various players claimed support for.  The range was from 55 to 130
 385 MIME types.  I suspect most media formats are supported by all
 386 players, but this is not really reflected in the MimeTypes values in
 387 their desktop files.  There are probably also some bogus MIME types
 388 listed, but it is hard to identify which one this is.</p>
 389
 390 <p>Anyway, in the mean time I got in touch with upstream for some of
 391 the players suggesting to add more MIME types to their desktop files,
 392 and decided to spend some time myself improving the situation for my
 393 favorite media player VLC.  The fixes for VLC entered Debian unstable
 394 yesterday. The complete list of MIME types can be seen on the
 395 <a href="https://wiki.debian.org/DebianMultimedia/PlayerSupport">Multimedia
 396 player MIME type support status</a> Debian wiki page.</p>
 397
 398 <p>The new "best" multimedia player in Debian?  It is VLC, followed by
 399 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
 400 kmplayer.  I am sure some of the other players desktop files support
 401 several of the formats currently listed as working only with vlc,
 402 toten and parole.</p>
 403
 404 <p>A sad observation is that only 14 MIME types are listed as
 405 supported by all the tested multimedia players in Debian in their
 406 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
 407 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
 408 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
 409 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo.  Personally I find
 410 it sad that video/ogg and video/webm is not supported by all the media
 411 players in Debian.  As far as I can tell, all of them can handle both
 412 formats.</p>
 413
 414       </div>
 415       <div class="tags">
 416
 417
 418         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
 419
 420
 421       </div>
 422     </div>
 423     <div class="padding"></div>
 424
 425     <div class="entry">
 426       <div class="title">
 427         <a href="https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html">What is the best multimedia player in Debian?</a>
 428       </div>
 429       <div class="date">
 430          8th May 2016
 431       </div>
 432       <div class="body">
 433         <p><strong>Where I set out to figure out which multimedia player in
 434 Debian claim support for most file formats.</strong></p>
 435
 436 <p>A few years ago, I had a look at the media support for Browser
 437 plugins in Debian, to get an idea which plugins to include in Debian
 438 Edu.  I created a script to extract the set of supported MIME types
 439 for each plugin, and used this to find out which multimedia browser
 440 plugin supported most file formats / media types.
 441 <a href="https://wiki.debian.org/DebianEdu/BrowserMultimedia">The
 442 result</a> can still be seen on the Debian wiki, even though it have
 443 not been updated for a while.  But browser plugins are less relevant
 444 these days, so I thought it was time to look at standalone
 445 players.</p>
 446
 447 <p>A few days ago I was tired of VLC not being listed as a viable
 448 player when I wanted to play videos from the Norwegian National
 449 Broadcasting Company, and decided to investigate why.  The cause is a
 450 <a href="https://bugs.debian.org/822245">missing MIME type in the VLC
 451 desktop file</a>.  In the process I wrote a script to compare the set
 452 of MIME types announced in the desktop file and the browser plugin,
 453 only to discover that there is quite a large difference between the
 454 two for VLC.  This discovery made me dig up the script I used to
 455 compare browser plugins, and adjust it to compare desktop files
 456 instead, to try to figure out which multimedia player in Debian
 457 support most file formats.</p>
 458
 459 <p>The result can be seen on the Debian Wiki, as
 460 <a href="https://wiki.debian.org/DebianMultimedia/PlayerSupport">a
 461 table listing all MIME types supported by one of the packages included
 462 in the table</a>, with the package supporting most MIME types being
 463 listed first in the table.</p>
 464
 465 </p>The best multimedia player in Debian?  It is totem, followed by
 466 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
 467 kmplayer.  Time for the other players to update their announced MIME
 468 support?</p>
 469
 470       </div>
 471       <div class="tags">
 472
 473
 474         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
 475
 476
 477       </div>
 478     </div>
 479     <div class="padding"></div>
 480
 481     <div class="entry">
 482       <div class="title">
 483         <a href="https://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html">Nedlasting fra NRK, som Matroska med undertekster</a>
 484       </div>
 485       <div class="date">
 486          2nd January 2016
 487       </div>
 488       <div class="body">
 489         <p>Det kommer stadig nye løsninger for å ta lagre unna innslag fra NRK
 490 for å se på det senere.  For en stund tilbake kom jeg over et script
 491 nrkopptak laget av Ingvar Hagelund.  Han fjernet riktignok sitt script
 492 etter forespørsel fra Erik Bolstad i NRK, men noen tok heldigvis og
 493 gjorde det <a href="https://github.com/liangqi/nrkopptak">tilgjengelig
 494 via github</a>.</p>
 495
 496 <p>Scriptet kan lagre som MPEG4 eller Matroska, og bake inn
 497 undertekster i fila på et vis som blant annet VLC forstår.  For å
 498 bruke scriptet, kopier ned git-arkivet og kjør</p>
 499
 500 <p><pre>
 501 nrkopptak/bin/nrk-opptak k <ahref="https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-1/episode-1">https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-1/episode-1</a>
 502 </pre></p>
 503
 504 <p>URL-eksemplet er dagens toppsak på tv.nrk.no.  Argument 'k' ber
 505 scriptet laste ned og lagre som Matroska.  Det finnes en rekke andre
 506 muligheter for valg av kvalitet og format.</p>
 507
 508 <p>Jeg foretrekker dette scriptet fremfor youtube-dl, som
 509 <a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html">
 510 nevnt i 2014 støtter NRK</a> og en rekke andre videokilder, på grunn
 511 av at nrkopptak samler undertekster og video i en enkelt fil, hvilket
 512 gjør håndtering enklere på disk.</p>
 513
 514       </div>
 515       <div class="tags">
 516
 517
 518         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
 519
 520
 521       </div>
 522     </div>
 523     <div class="padding"></div>
 524
 525     <div class="entry">
 526       <div class="title">
 527         <a href="https://people.skolelinux.org/pere/blog/MPEG_LA_on__Internet_Broadcast_AVC_Video__licensing_and_non_private_use.html">MPEG LA on "Internet Broadcast AVC Video" licensing and non-private use</a>
 528       </div>
 529       <div class="date">
 530          7th July 2015
 531       </div>
 532       <div class="body">
 533         <p>After asking the Norwegian Broadcasting Company (NRK)
 534 <a href="http://people.skolelinux.org/pere/blog/Hva_gj_r_at_NRK_kan_distribuere_H_264_video_uten_patentavtale_med_MPEG_LA_.html">why
 535 they can broadcast and stream H.264 video without an agreement with
 536 the MPEG LA</a>, I was wiser, but still confused.  So I asked MPEG LA
 537 if their understanding matched that of NRK.  As far as I can tell, it
 538 does not.</p>
 539
 540 <p>I started by asking for more information about the various
 541 licensing classes and what exactly is covered by the "Internet
 542 Broadcast AVC Video" class that NRK pointed me at to explain why NRK
 543 did not need a license for streaming H.264 video:
 544
 545 <p><blockquote>
 546
 547 <p>According to
 548 <a href="http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf">a
 549 MPEG LA press release dated 2010-02-02</a>, there is no charge when
 550 using MPEG AVC/H.264 according to the terms of "Internet Broadcast AVC
 551 Video".  I am trying to understand exactly what the terms of "Internet
 552 Broadcast AVC Video" is, and wondered if you could help me.  What
 553 exactly is covered by these terms, and what is not?</p>
 554
 555 <p>The only source of more information I have been able to find is a
 556 PDF named
 557 <a href="http://www.mpegla.com/main/programs/avc/Documents/avcweb.pdf">AVC
 558 Patent Portfolio License Briefing</a>, which states this about the
 559 fees:</p>
 560
 561 <ul>
 562  <li>Where End User pays for AVC Video
 563   <ul>
 564    <li>Subscription (not limited by title) – 100,000 or fewer
 565      subscribers/yr = no royalty; &gt; 100,000 to 250,000 subscribers/yr =
 566      $25,000; &gt;250,000 to 500,000 subscribers/yr = $50,000; &gt;500,000 to
 567      1M subscribers/yr = $75,000; &gt;1M subscribers/yr = $100,000</li>
 568
 569    <li>Title-by-Title - 12 minutes or less = no royalty; &gt;12 minutes in
 570      length = lower of (a) 2% or (b) $0.02 per title</li>
 571   </ul></li>
 572
 573  <li>Where remuneration is from other sources
 574   <ul>
 575    <li>Free Television - (a) one-time $2,500 per transmission encoder or
 576      (b) annual fee starting at $2,500 for &gt; 100,000 HH rising to
 577      maximum $10,000 for &gt;1,000,000 HH</li>
 578
 579    <li>Internet Broadcast AVC Video (not title-by-title, not subscription)
 580      – no royalty for life of the AVC Patent Portfolio License</li>
 581   </ul></li>
 582 </ul>
 583
 584 <p>Am I correct in assuming that the four categories listed is the
 585 categories used when selecting licensing terms, and that "Internet
 586 Broadcast AVC Video" is the category for things that do not fall into
 587 one of the other three categories?  Can you point me to a good source
 588 explaining what is ment by "title-by-title" and "Free Television" in
 589 the license terms for AVC/H.264?</p>
 590
 591 <p>Will a web service providing H.264 encoded video content in a
 592 "video on demand" fashing similar to Youtube and Vimeo, where no
 593 subscription is required and no payment is required from end users to
 594 get access to the videos, fall under the terms of the "Internet
 595 Broadcast AVC Video", ie no royalty for life of the AVC Patent
 596 Portfolio license?  Does it matter if some users are subscribed to get
 597 access to personalized services?</p>
 598
 599 <p>Note, this request and all answers will be published on the
 600 Internet.</p>
 601 </blockquote></p>
 602
 603 <p>The answer came quickly from Benjamin J. Myers, Licensing Associate
 604 with the MPEG LA:</p>
 605
 606 <p><blockquote>
 607 <p>Thank you for your message and for your interest in MPEG LA.  We
 608 appreciate hearing from you and I will be happy to assist you.</p>
 609
 610 <p>As you are aware, MPEG LA offers our AVC Patent Portfolio License
 611 which provides coverage under patents that are essential for use of
 612 the AVC/H.264 Standard (MPEG-4 Part 10).  Specifically, coverage is
 613 provided for end products and video content that make use of AVC/H.264
 614 technology.  Accordingly, the party offering such end products and
 615 video to End Users concludes the AVC License and is responsible for
 616 paying the applicable royalties.</p>
 617
 618 <p>Regarding Internet Broadcast AVC Video, the AVC License generally
 619 defines such content to be video that is distributed to End Users over
 620 the Internet free-of-charge.  Therefore, if a party offers a service
 621 which allows users to upload AVC/H.264 video to its website, and such
 622 AVC Video is delivered to End Users for free, then such video would
 623 receive coverage under the sublicense for Internet Broadcast AVC
 624 Video, which is not subject to any royalties for the life of the AVC
 625 License.  This would also apply in the scenario where a user creates a
 626 free online account in order to receive a customized offering of free
 627 AVC Video content.  In other words, as long as the End User is given
 628 access to or views AVC Video content at no cost to the End User, then
 629 no royalties would be payable under our AVC License.</p>
 630
 631 <p>On the other hand, if End Users pay for access to AVC Video for a
 632 specific period of time (e.g., one month, one year, etc.), then such
 633 video would constitute Subscription AVC Video.  In cases where AVC
 634 Video is delivered to End Users on a pay-per-view basis, then such
 635 content would constitute Title-by-Title AVC Video.  If a party offers
 636 Subscription or Title-by-Title AVC Video to End Users, then they would
 637 be responsible for paying the applicable royalties you noted below.</p>
 638
 639 <p>Finally, in the case where AVC Video is distributed for free
 640 through an "over-the-air, satellite and/or cable transmission", then
 641 such content would constitute Free Television AVC Video and would be
 642 subject to the applicable royalties.</p>
 643
 644 <p>For your reference, I have attached
 645 <a href="http://people.skolelinux.org/pere/blog/images/2015-07-07-mpegla.pdf">a
 646 .pdf copy of the AVC License</a>. You will find the relevant
 647 sublicense information regarding AVC Video in Sections 2.2 through
 648 2.5, and the corresponding royalties in Section 3.1.2 through 3.1.4.
 649 You will also find the definitions of Title-by-Title AVC Video,
 650 Subscription AVC Video, Free Television AVC Video, and Internet
 651 Broadcast AVC Video in Section 1 of the License.  Please note that the
 652 electronic copy is provided for informational purposes only and cannot
 653 be used for execution.</p>
 654
 655 <p>I hope the above information is helpful.  If you have additional
 656 questions or need further assistance with the AVC License, please feel
 657 free to contact me directly.</p>
 658 </blockquote></p>
 659
 660 <p>Having a fresh copy of the license text was useful, and knowing
 661 that the definition of Title-by-Title required payment per title made
 662 me aware that my earlier understanding of that phrase had been wrong.
 663 But I still had a few questions:</p>
 664
 665 <p><blockquote>
 666 <p>I have a small followup question.  Would it be possible for me to get
 667 a license with MPEG LA even if there are no royalties to be paid?  The
 668 reason I ask, is that some video related products have a copyright
 669 clause limiting their use without a license with MPEG LA.  The clauses
 670 typically look similar to this:
 671
 672 <p><blockquote>
 673   This product is licensed under the AVC patent portfolio license for
 674   the personal and non-commercial use of a consumer to (a) encode
 675   video in compliance with the AVC standard ("AVC video") and/or (b)
 676   decode AVC video that was encoded by a consumer engaged in a
 677   personal and non-commercial activity and/or AVC video that was
 678   obtained from a video provider licensed to provide AVC video. No
 679   license is granted or shall be implied for any other use. additional
 680   information may be obtained from MPEG LA L.L.C.
 681 </blockquote></p>
 682
 683 <p>It is unclear to me if this clause mean that I need to enter into
 684 an agreement with MPEG LA to use the product in question, even if
 685 there are no royalties to be paid to MPEG LA.  I suspect it will
 686 differ depending on the jurisdiction, and mine is Norway.  What is
 687 MPEG LAs view on this?</p>
 688 </blockquote></p>
 689
 690 <p>According to the answer, MPEG LA believe those using such tools for
 691 non-personal or commercial use need a license with them:</p>
 692
 693 <p><blockquote>
 694
 695 <p>With regard to the Notice to Customers, I would like to begin by
 696 clarifying that the Notice from Section 7.1 of the AVC License
 697 reads:</p>
 698
 699 <p>THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR
 700 THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT
 701 RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC
 702 STANDARD ("AVC VIDEO") AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED
 703 BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM
 704 A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED
 705 OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE
 706 OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM</p>
 707
 708 <p>The Notice to Customers is intended to inform End Users of the
 709 personal usage rights (for example, to watch video content) included
 710 with the product they purchased, and to encourage any party using the
 711 product for commercial purposes to contact MPEG LA in order to become
 712 licensed for such use (for example, when they use an AVC Product to
 713 deliver Title-by-Title, Subscription, Free Television or Internet
 714 Broadcast AVC Video to End Users, or to re-Sell a third party's AVC
 715 Product as their own branded AVC Product).</p>
 716
 717 <p>Therefore, if a party is to be licensed for its use of an AVC
 718 Product to Sell AVC Video on a Title-by-Title, Subscription, Free
 719 Television or Internet Broadcast basis, that party would need to
 720 conclude the AVC License, even in the case where no royalties were
 721 payable under the License.  On the other hand, if that party (either a
 722 Consumer or business customer) simply uses an AVC Product for their
 723 own internal purposes and not for the commercial purposes referenced
 724 above, then such use would be included in the royalty paid for the AVC
 725 Products by the licensed supplier.</p>
 726
 727 <p>Finally, I note that our AVC License provides worldwide coverage in
 728 countries that have AVC Patent Portfolio Patents, including
 729 Norway.</p>
 730
 731 <p>I hope this clarification is helpful.  If I may be of any further
 732 assistance, just let me know.</p>
 733 </blockquote></p>
 734
 735 <p>The mentioning of Norwegian patents made me a bit confused, so I
 736 asked for more information:</p>
 737
 738 <p><blockquote>
 739
 740 <p>But one minor question at the end.  If I understand you correctly,
 741 you state in the quote above that there are patents in the AVC Patent
 742 Portfolio that are valid in Norway.  This make me believe I read the
 743 list available from &lt;URL:
 744 <a href="http://www.mpegla.com/main/programs/AVC/Pages/PatentList.aspx">http://www.mpegla.com/main/programs/AVC/Pages/PatentList.aspx</a>
 745 &gt; incorrectly, as I believed the "NO" prefix in front of patents
 746 were Norwegian patents, and the only one I could find under Mitsubishi
 747 Electric Corporation expired in 2012.  Which patents are you referring
 748 to that are relevant for Norway?</p>
 749
 750 </blockquote></p>
 751
 752 <p>Again, the quick answer explained how to read the list of patents
 753 in that list:</p>
 754
 755 <p><blockquote>
 756
 757 <p>Your understanding is correct that the last AVC Patent Portfolio
 758 Patent in Norway expired on 21 October 2012.  Therefore, where AVC
 759 Video is both made and Sold in Norway after that date, then no
 760 royalties would be payable for such AVC Video under the AVC License.
 761 With that said, our AVC License provides historic coverage for AVC
 762 Products and AVC Video that may have been manufactured or Sold before
 763 the last Norwegian AVC patent expired.  I would also like to clarify
 764 that coverage is provided for the country of manufacture and the
 765 country of Sale that has active AVC Patent Portfolio Patents.</p>
 766
 767 <p>Therefore, if a party offers AVC Products or AVC Video for Sale in
 768 a country with active AVC Patent Portfolio Patents (for example,
 769 Sweden, Denmark, Finland, etc.), then that party would still need
 770 coverage under the AVC License even if such products or video are
 771 initially made in a country without active AVC Patent Portfolio
 772 Patents (for example, Norway).  Similarly, a party would need to
 773 conclude the AVC License if they make AVC Products or AVC Video in a
 774 country with active AVC Patent Portfolio Patents, but eventually Sell
 775 such AVC Products or AVC Video in a country without active AVC Patent
 776 Portfolio Patents.</p>
 777 </blockquote></p>
 778
 779 <p>As far as I understand it, MPEG LA believe anyone using Adobe
 780 Premiere and other video related software with a H.264 distribution
 781 license need a license agreement with MPEG LA to use such tools for
 782 anything non-private or commercial, while it is OK to set up a
 783 Youtube-like service as long as no-one pays to get access to the
 784 content.  I still have no clear idea how this applies to Norway, where
 785 none of the patents MPEG LA is licensing are valid.  Will the
 786 copyright terms take precedence or can those terms be ignored because
 787 the patents are not valid in Norway?</p>
 788
 789       </div>
 790       <div class="tags">
 791
 792
 793         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
 794
 795
 796       </div>
 797     </div>
 798     <div class="padding"></div>
 799
 800     <div class="entry">
 801       <div class="title">
 802         <a href="https://people.skolelinux.org/pere/blog/MakerCon_Nordic_videos_now_available_on_Frikanalen.html">MakerCon Nordic videos now available on Frikanalen</a>
 803       </div>
 804       <div class="date">
 805          2nd July 2015
 806       </div>
 807       <div class="body">
 808         <p>Last oktober I was involved on behalf of
 809 <a href="http://www.nuug.no/">NUUG</a> with recording the talks at
 810 <a href="http://www.makercon.no/">MakerCon Nordic</a>, a conference for
 811 the Maker movement.  Since then it has been the plan to publish the
 812 recordings on <a href="http://www.frikanalen.no/">Frikanalen</a>, which
 813 finally happened the last few days.  A few talks are missing because
 814 the speakers asked the organizers to not publish them, but most of the
 815 talks are available.  The talks are being broadcasted on RiksTV
 816 channel 50 and using multicast on Uninett, as well as being available
 817 from the Frikanalen web site.  The unedited recordings are
 818 <a href="https://www.youtube.com/user/MakerConNordic/">available on
 819 Youtube too</a>.</p>
 820
 821 <p>This is the list of talks available at the moment.  Visit the
 822 <a href="http://beta.frikanalen.no/video/?q=makercon">Frikanalen video
 823 pages</a> to view them.</p>
 824
 825 <ul>
 826
 827   <li>Evolutionary algorithms as a design tool - from art
 828       to robotics (Kyrre Glette)</li>
 829
 830   <li>Make and break (Hans Gerhard Meier)</li>
 831
 832   <li>Making a one year school course for young makers
 833       (Olav Helland)</li>
 834
 835   <li>Innovation Inspiration - IPR Databases as a Source of
 836       Inspiration (Hege Langlo)</li>
 837
 838   <li>Making a toy for makers (Erik Torstensson)</li>
 839
 840   <li>How to make 3D printer electronics (Elias Bakken)</li>
 841
 842   <li>Hovering Clouds: Looking at online tool offerings for Product
 843       Design and 3D Printing (William Kempton)</li>
 844
 845   <li>Travelling maker stories (Øyvind Nydal Dahl)</li>
 846
 847   <li>Making the first Maker Faire in Sweden (Nils Olander)</li>
 848
 849   <li>Breaking the mold: Printing 1000’s of parts (Espen Sivertsen)</li>
 850
 851   <li>Ultimaker — and open source 3D printing (Erik de Bruijn)</li>
 852
 853   <li>Autodesk’s 3D Printing Platform: Sparking innovation (Hilde
 854       Sevens)</li>
 855
 856   <li>How Making is Changing the World – and How You Can Too!
 857       (Jennifer Turliuk)</li>
 858
 859   <li>Open-Source Adventuring: OpenROV, OpenExplorer and the Future of
 860       Connected Exploration (David Lang)</li>
 861
 862   <li>Making in Norway (Haakon Karlsen Jr., Graham Hayward and Jens
 863       Dyvik)</li>
 864
 865   <li>The Impact of the Maker Movement (Mike Senese)</li>
 866
 867 </ul>
 868
 869 <p>Part of the reason this took so long was that the scripts NUUG had
 870 to prepare a recording for publication were five years old and no
 871 longer worked with the current video processing tools (command line
 872 argument changes).  In addition, we needed better audio normalization,
 873 which sent me on a detour to
 874 <a href="http://people.skolelinux.org/pere/blog/Measuring_and_adjusting_the_loudness_of_a_TV_channel_using_bs1770gain.html">package
 875 bs1770gain for Debian</a>.  Now this is in place and it became a lot
 876 easier to publish NUUG videos on Frikanalen.</p>
 877
 878       </div>
 879       <div class="tags">
 880
 881
 882         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
 883
 884
 885       </div>
 886     </div>
 887     <div class="padding"></div>
 888
 889     <div class="entry">
 890       <div class="title">
 891         <a href="https://people.skolelinux.org/pere/blog/Measuring_and_adjusting_the_loudness_of_a_TV_channel_using_bs1770gain.html">Measuring and adjusting the loudness of a TV channel using bs1770gain</a>
 892       </div>
 893       <div class="date">
 894         11th June 2015
 895       </div>
 896       <div class="body">
 897         <p>Television loudness is the source of frustration for viewers
 898 everywhere.  Some channels are very load, others are less loud, and
 899 ads tend to shout very high to get the attention of the viewers, and
 900 the viewers do not like this.  This fact is well known to the TV
 901 channels.  See for example the BBC white paper
 902 "<a href="http://downloads.bbc.co.uk/rd/pubs/whp/whp-pdf-files/WHP202.pdf">Terminology
 903 for loudness and level dBTP, LU, and all that</a>" from 2011 for a
 904 summary of the problem domain.  To better address the need for even
 905 loadness, the TV channels got together several years ago to agree on a
 906 new way to measure loudness in digital files as one step in
 907 standardizing loudness.  From this came the ITU-R standard BS.1770,
 908 "<a href="http://www.itu.int/rec/R-REC-BS.1770/en">Algorithms to
 909 measure audio programme loudness and true-peak audio level</a>".</p>
 910
 911 <p>The ITU-R BS.1770 specification describe an algorithm to measure
 912 loadness in LUFS (Loudness Units, referenced to Full Scale). But
 913 having a way to measure is not enough.  To get the same loudness
 914 across TV channels, one also need to decide which value to standardize
 915 on.  For European TV channels, this was done in the EBU Recommondaton
 916 R128, "<a href="https://tech.ebu.ch/docs/r/r128.pdf">Loudness
 917 normalisation and permitted maximum level of audio signals</a>", which
 918 specifies a recommended level of -23 LUFS.  In Norway, I have been
 919 told that NRK, TV2, MTG and SBS have decided among themselves to
 920 follow the R128 recommondation for playout from 2016-03-01.</p>
 921
 922 <p>There are free software available to measure and adjust the loudness
 923 level using the LUFS.  In Debian, I am aware of a library named
 924 <a href="https://tracker.debian.org/pkg/libebur128">libebur128</a>
 925 able to measure the loudness and since yesterday morning a new binary
 926 named <a href="http://bs1770gain.sourceforge.net">bs1770gain</a>
 927 capable of both measuring and adjusting was uploaded and is waiting
 928 for NEW processing.  I plan to maintain the latter in Debian under the
 929 <a href="https://qa.debian.org/developer.php?email=pkg-multimedia-maintainers%40lists.alioth.debian.org">Debian
 930 multimedia</a> umbrella.</p>
 931
 932 <p>The free software based TV channel I am involved in,
 933 <a href="http://www.frikanalen.no/">Frikanalen</a>, plan to follow the
 934 R128 recommondation ourself as soon as we can adjust the software to
 935 do so, and the bs1770gain tool seem like a good fit for that part of
 936 the puzzle to measure loudness on new video uploaded to Frikanalen.
 937 Personally, I plan to use bs1770gain to adjust the loudness of videos
 938 I upload to Frikanalen on behalf of <a href="http://www.nuug.no/">the
 939 NUUG member organisation</a>.  The program seem to be able to measure
 940 the LUFS value of any media file handled by ffmpeg, but I've only
 941 successfully adjusted the LUFS value of WAV files.  I suspect it
 942 should be able to adjust it for all the formats handled by ffmpeg.</p>
 943
 944       </div>
 945       <div class="tags">
 946
 947
 948         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
 949
 950
 951       </div>
 952     </div>
 953     <div class="padding"></div>
 954
 955     <div class="entry">
 956       <div class="title">
 957         <a href="https://people.skolelinux.org/pere/blog/Hva_gj_r_at_NRK_kan_distribuere_H_264_video_uten_patentavtale_med_MPEG_LA_.html">Hva gjør at NRK kan distribuere H.264-video uten patentavtale med MPEG LA?</a>
 958       </div>
 959       <div class="date">
 960         10th June 2015
 961       </div>
 962       <div class="body">
 963         <p>Helt siden jeg i 2012 fikk beskjed fra MPEG LA om at
 964 <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">NRK
 965 trengte patentavtale med dem</a> hvis de distribuerte H.264-video til
 966 sluttbrukere, har jeg lurt på hva som gjør at NRK ikke har slik
 967 avtale.  For noen dager siden fikk jeg endelig gjort noe med min
 968 undring, og sendte 2015-05-28 følgende epost til info (at) nrk.no med
 969 tittel "Hva gjør at NRK kan distribuere H.264-video uten patentavtale
 970 med MPEG LA?":</p>
 971
 972 <p><blockquote>
 973 <p>Jeg lurer på en ting rundt NRKs bruk av H.264-video på sine
 974 websider samt distribusjon via RiksTV og kabel-TV.  Har NRK vurdert om
 975 det er behov for en patentavtale med
 976 <a href="http://www.mpegla.com/">MPEG LA</a> slik det står i
 977 programvarelisensene til blant annet Apple Final Cut Studio, Adobe
 978 Premiere Pro, Avid og Apples Final Cut Pro X?</p>
 979
 980 <p>Hvis dere har vurdert dette, hva var utfallet av en slik vurdering?</p>
 981
 982 <p>Hvis dere ikke har vurdert dette, har NRK planer om å vurdere behovet
 983 for patentavtale?</p>
 984
 985 <p>I følge en artikkel på
 986 <a href="https://nrkbeta.no/2012/02/01/siste-kutt-for-final-cut/">NRK
 987 Beta i 2012</a> har NRK brukt eller testet både Apple Final Cut
 988 Studio, Adobe Premiere Pro, Avid og Apples Final Cut Pro X til bruk
 989 for å redigere video før sending. Alle disse har bruksvilkår
 990 understøttet av opphavsretten som sier at de kun kan brukes til å lage
 991 filmer til personlig og ikke-kommersiell bruk - med mindre en har en
 992 lisensavtale med MPEG LA om bruk av patenter utstedt i USA for H.264.
 993 Se f.eks. <a href="http://www.avid.com/static/resources/common/documents/corporate/LICENSE.pdf">bruksvilkårene for Avid</a>, <a href="http://news.cnet.com/8301-30685_3-20000101-264.html">Adobe Premiere</a> og <a href="http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf">Apple Final
 994 Cut Studio</a> og søk etter "MPEG LA".</p>
 995
 996 <p>Dette får meg til å lure på om det er brudd på opphavsretten å bruke
 997 disse verktøyene i strid med bruksvilkårene uten patentavtale med MPEG
 998 LA.  Men NRK bruker jo tilsynelatende disse verktøyene uten patentavtale
 999 med MPEG LA.</p>
1000
1001 <p>I følge forfatteren av Open Broadcast Encoder finnes det to typer
1002 H.264-relaterte avtaler en kan få med MPEG LA. Det er én for å lage
1003 programvare og utstyr som produserer H.264-video, og en annen for å
1004 kringkaste video som bruker H.264. Dette forteller meg at selv om
1005 produsentene av utstyr og programvare som NRK bruker har en slik avtale
1006 med MPEG LA, så trenges det en egen avtale for å kringkaste video på det
1007 formatet.</p>
1008
1009 <p>I følge Ryan Rodriguez hos MPEG LA, da jeg spurte ham på epost i
1010 juni 2012, har NRK ikke en slik avtale med MPEG LA. Han sa videre at
1011 NRK trenger en slik avtale hvis NRK tilbyr H.264-kodet video til
1012 sluttbrukere.  Jeg sjekket listen med
1013 <a href="http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx">organisasjoner
1014 med avtale med MPEG LA</a> og NRK står fortsatt ikke der.</p>
1015
1016 <p>Jeg lurer dermed på hva som gjør at NRK kan bruke de overnevnte
1017 videoredigeringsverktøyene, som tilsynelatende har krav om avtale med
1018 MPEG LA for å kunne brukes slik NRK bruker dem, til å lage videofiler
1019 for distribusjon uten å ha en avtale med MPEG LA om distribusjon av
1020 H.264-video?  Dette er spesielt interessant å vite for oss andre som
1021 også vurderer å spre H.264-video etter å ha redigert dem med disse mye
1022 brukte videoredigeringsverktøyene.</p>
1023 </blockquote></p>
1024
1025 <p>Samme dag fikk jeg automatisk svar om at min henvendelse hadde fått
1026 saksid 1294699.  Jeg fikk deretter følgende respons fra NRK
1027 2015-06-09:</p>
1028
1029 <p><blockquote>
1030 <p>Hei, beklager lang svartid, men det tok litt tid å finne ut hvem som kunne
1031 svare på dette.</p>
1032
1033 <p>For selskaper som leverer h.264 til sluttbrukere på nett (f.eks
1034 NRKs nett- tv utgaver som bruker h.264) - og som leverer slike
1035 tjenester uten betaling fra forbrukere – er det heller ikke påkrevd
1036 noen patentavtale.</p>
1037
1038 <p><a href="http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y">http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y</a></p>
1039
1040 <p>Med vennlig hilsen
1041 <br>Gunn Helen Berg
1042 <br>Informasjonskonsulent, Publikumsservice</p>
1043
1044 <p>NRK
1045 <br>Strategidivisjonen
1046 <Br>Sentralbord: +47 23 04 70 00
1047 <br>Post: NRK Publikumsservice, 8608 Mo i Rana
1048 <br>nrk.no / info (at) nrk.no</p>
1049 </blockquote></p>
1050
1051 Da dette ikke helt var svar på det jeg lurte på, sendte jeg samme dag
1052 oppfølgerepost tilbake:
1053
1054 <p><blockquote>
1055 <p>[Gunn Helen Berg]
1056 <br>> Hei, beklager lang svartid, men det tok litt tid å finne ut hvem som
1057 <br>> kunne svare på dette.</p>
1058
1059 <p>Takk for svar.  Men det besvarte ikke helt det jeg spurte om.</p>
1060
1061 <p>> For selskaper som leverer h.264 til sluttbrukere på nett (f.eks NRKs
1062 <br>> nett- tv utgaver som bruker h.264) - og som leverer slike tjenester
1063 <br>> uten betaling fra forbrukere – er det heller ikke påkrevd noen
1064 <br>> patentavtale.
1065 <br>>
1066 <br>> http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y</p>
1067
1068 <p>Spørsmålet er ikke kun om MPEG LA krever patentavtale eller ikke
1069 (hvilket ikke helt besvares av pressemeldingen omtalt over, gitt at
1070 pressemeldingen kom i 2010, to år før MPEG LA ansvarlige for
1071 internasjonal lisensiering egen Ryan Rodriguez fortalte meg på epost
1072 at NRK trenger en lisens.</p>
1073
1074 <p>Det er uklart fra pressemeldingen hva "Internet Broadcast AVC
1075 Video" konkret betyr, men i følge en
1076 <a href="http://www.mpegla.com/main/programs/avc/Documents/avcweb.pdf">presentasjon
1077 fra MPEG LA med tema "AVC PAtent Portfoli License Briefing" datert
1078 2015-05-15</a> gjelder "Internet Broadcast AVC Video" kun kringkasting
1079 på Internet som ikke tilbyr valg av enkeltinnslag ("not
1080 title-by-title"), hvilket jo NRK gjør på sine nettsider.  I tillegg
1081 kringkaster jo NRK H.264-video også utenom Internet (RiksTV, kabel,
1082 satelitt), hvilket helt klart ikke er dekket av vilkårene omtalt i
1083 pressemeldingen.</p>
1084
1085 <p>Spørsmålet mitt er hvordan NRK kan bruke verktøy med bruksvilkår
1086 som krever avtale med MPEG LA for det NRK bruker dem til, når NRK ikke
1087 har avtale med MPEG LA.  Hvis jeg forsto spørsmålet riktig, så mener
1088 NRK at dere ikke trenger avtale med MPEG LA, men uten slik avtale kan
1089 dere vel ikke bruke hverken Apple Final Cut Studio, Adobe Premiere
1090 Pro, Avid eller Apples Final Cut Pro X for å redigere video før
1091 sending?</p>
1092
1093 <p>Mine konkrete spørsmål var altså:</p>
1094
1095 <ul>
1096
1097 <li>Hvis NRK har vurdert om det er behov for en patentavtale med MPEG LA
1098    slik det er krav om i programvarelisensene til blant annet Apple
1099    Final Cut Studio, Adobe Premiere Pro, Avid og Apples Final Cut Pro X,
1100    hva var utfallet av en slik vurdering? Kan jeg få kopi av vurderingen
1101    hvis den er gjort skriftlig?</li>
1102
1103 <li>Hvis NRK ikke har vurdert dette, har NRK planer om å vurdere behovet
1104    for patentavtale?</li>
1105
1106 <li>Hva slags saksnummer fikk min henvendelse i NRKs offentlige
1107    postjournal?  Jeg ser at postjournalen ikke er publisert for den
1108    aktuelle perioden ennå, så jeg fikk ikke sjekket selv.</li>
1109
1110 </ul>
1111 </blockquote></p>
1112
1113 <p>Det hjelper å ha funnet rette vedkommende i NRK, for denne gangen
1114 fikk jeg svar tilbake dagen etter (2015-06-10), fra Geir Børdalen i
1115 NRK:</p>
1116
1117 <p><blockquote>
1118 <p>Hei Petter Reinholdtsen</p>
1119
1120 <p>Jeg har sjekket saken med distribusjonssjef for tv, Arild Hellgren
1121 (som var teknologidirektør da bakkenettet ble satt opp). NRK v/
1122 Hellgren hadde møte med MPEG LA sammen med den europeiske
1123 kringkastingsunionen EBU før bakkenettet for TV ble satt opp
1124 (igangsatt høsten 2007). I dette møtet ble det avklart at NRK/EBU ikke
1125 trengte noen patentavtale for h.264 i forbindelse med oppsett av
1126 bakkenettet eller bruk av MPEG4 h.264 som kompresjonsalgoritme fordi
1127 tjenesten «in full»(nor: helt) var betalt av utsendelseselskapene og
1128 ikke av forbrukerne.</p>
1129
1130 <p><a href="http://www.nrk.no/oppdrag/digitalt-bakkenett-1.3214555">http://www.nrk.no/oppdrag/digitalt-bakkenett-1.3214555</a></p>
1131
1132 <p>Det er også klart slått fast at selskaper som leverer video basert
1133 på MPEG4 h.264 til sluttbrukere på nett, heller ikke påkrevd noen
1134 patentavtale – så lenge de leverer slike tjenester uten betaling fra
1135 sluttbrukere.</p>
1136
1137 <a href="http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y">http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y</a>
1138
1139 <p>“MPEG LA announced today that its AVC Patent Portfolio License will
1140 continue not to charge royalties for Internet Video that is free to
1141 end users (known as “Internet Broadcast AVC Video”) during the entire
1142 life of this License. MPEG LA previously announced it would not charge
1143 royalties for such video through December 31, 2015 (see
1144 <a href="http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf">http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf</a>),
1145 and today’s announcement makes clear that royalties will continue not
1146 to be charged for such video beyond that time. Products and services
1147 other than Internet Broadcast AVC Video continue to be
1148 royalty-bearing.”</p>
1149
1150 <p>Vi har derfor ikke noe behov for å vurdere noen patentavtale med
1151 MPEG LA.</p>
1152
1153 <p>Understreker for øvrig at NRK ikke er låst til MPEG4 – h.264 som
1154 utsendelsesformat – og at vi har brukt og bruker flere andre
1155 alternativer i våre tjenester. Ulike «devicer» har ofte behov for
1156 forskjellige løsninger – og NRK har forsøkt å levere med best mulig
1157 kvalitet /økonomi /stabilitet avhengig av
1158 plattform. Produksjonsformater i NRK spenner for øvrig over en rekke
1159 forskjellige formater – hvor MPEG4 bare er en av disse. Når NRK kjøper
1160 teknisk utstyr er betaling for kodekstøtte ofte en del av
1161 anskaffelsesprisen for denne maskinvaren (enten dette er spesialiserte
1162 enkodere eller forskjellige typer produksjonsutstyr).</p>
1163
1164 <p>Vennlig hilsen
1165 <br>Geir Børdalen</p>
1166
1167 <p>________________________________________
1168 <br>Geir Børdalen
1169 <br>Investeringsansvarlig NRK / Hovedprosjektleder - Origo
1170 <br>Avdeling for utvikling, innovasjon, investering og eiendom
1171 <br>NRK medietjenester
1172 <br>Sentralbord: +47 23 04 70 00
1173 <br>Post: NRK, AUTV (RBM5), Pb. 8500 Majorstuen, 0340 Oslo
1174 <br>nrk.no
1175 </blockquote></p>
1176
1177 <p>Et godt og grundig svar, som var informativt om hvordan NRK tenker
1178 rundt patentavtale med MPEG LA, men heller ikke helt besvarte det jeg
1179 lurte på, så jeg sendte epostoppfølging samme dag.</p>
1180
1181 <p><blockquote>
1182 <p>[Geir Børdalen]
1183 <br>> Hei Petter Reinholdtsen</p>
1184
1185 <p>Hei, og takk for raskt svar.  Er min henvendelse journalført slik
1186 at den dukker opp i NRKs postjournal?</p>
1187
1188 <p>Svaret ditt var meget nyttig, og jeg forstår ut fra det du skriver
1189 at avklaringen med MPEG LA rundt H.264-distribusjon via bakkenettet
1190 gjelder alle TV-kanaler i Norge.  Hvilke saksnummer fikk dokumenter
1191 som ble opprettet i forbindelse med det omtalte møtet NRK v/Hellgren
1192 og EBU hadde med MPEG LA (dvs. referater, avtaler, etc),
1193 f.eks. dokumentet der formuleringen "in full" som du omtaler
1194 finnes?<p>
1195
1196 <p>Men det er et par ting jeg fortsatt ikke forstår.  Det ene er
1197 hvorfor NRKs forståelse av hva "Internet Broadcast AVC Video" dekker
1198 ser ut til å avvike fra det som presenteres i
1199 <a href="http://www.mpegla.com/main/programs/avc/Documents/avcweb.pdf">lysark
1200 fra MPEG LA</a> i mai, der MPEG LA på lysark med overskriften
1201 "AVC/H.264 License Terms Participation Fees" og undertittel "Where
1202 remuneration is from other sources" skriver "Internet Broadcast AVC
1203 Video (not title-by-title, not subscription) – no royalty for life of
1204 the AVC Patent Portfolio License".</p>
1205
1206 <p>Her leser jeg MPEG LA dithen at det kun er kringkasting uten
1207 abonnement via Internet som er dekket at vilkårne omtalt i
1208 pressemeldingen, mens jeg forstår deg dithen at NRK mener NRKs
1209 nettsider som også har enkeltfilmer og innslag (som jeg forstår dekket
1210 av formuleringen "title-by-title") dekkes av "Internet Broadcast AVC
1211 Video" fra MPEG LA.  Hva baserer dere denne tolkningen på?  Jeg har
1212 ikke sett noe skriftlig fra MPEG LA som støtter NRKs tolkning, og
1213 lurer på om dere har andre kilder enn den pressemeldingen fra 5 år
1214 tilbake, der NRKS forståelse av hva "Internet Broadcast AVC Video"
1215 dekker er beskrevet?</p>
1216
1217 <p>Det andre er at eposten din ikke nevnte spørsmålet mitt om
1218 bruksvilkårene til videoredigeringsverktøyene som NRK bruker.  Disse
1219 har som tidligere nevnt krav om at de kun skal brukes til private og
1220 ikke-kommersielle formål med mindre en har avtale med MPEG LA, og uten
1221 avtale med MPEG LA kan det jo virke som om NRK bruker verktøyene i
1222 strid med bruksvilkårene.  Hva gjør at disse bruksvilkårene ikke
1223 gjelder for NRK?</p>
1224 </blockquote></p>
1225
1226 <p>Noen minutter senere får jeg foreløpig siste svar i
1227 føljetongen:</p>
1228
1229 <p><blockquote>
1230 <p>Hei igjen</p>
1231
1232 <p>Vårt dokumentarkiv har fått en kopi (journalføringsnr kan jeg
1233 dessverre ikke gi deg).<p>
1234
1235 <p>> Svaret ditt var meget nyttig, og jeg forstår ut fra det du
1236 <br>> skriver at avklaringen med MPEG LA rundt H.264-distribusjon via
1237 <br>> bakkenettet gjelder alle TV-kanaler i Norge.</p>
1238
1239 <p>Svar: Kan ikke svare for andre enn for NRK/EBU - og for bakkenettet
1240 i Norge er det kun NRK som er et lisensbasert selskap. Kan ikke gi noe
1241 svar på saksnr på dokumenter eller ytterligere informasjon da jeg selv
1242 ikke var del i dette.</p>
1243
1244 <p>> Men det er et par ting jeg fortsatt ikke forstår.  ...</p>
1245
1246 <p>Svar: Kan ikke gå ytterligere inn i dette fra min side og mitt
1247 fagfelt som er produksjon/publisering og systemstrukturene bak
1248 disse. For øvrig ligger det etter vår formening ingen begrensninger
1249 for NRK i mulighetene til publisering mht til kodek i
1250 produksjonssystemer. Som tidligere skrevet mener vi at NRK ikke
1251 trenger noen avtale med MPEG LA og støtter oss til det vi allerede har
1252 kommunisert i forrige epost.</p>
1253
1254 <p>Mvh
1255 <br>Geir Børdalen</p>
1256 </blockquote></p>
1257
1258 <p>Det syntes vanskelig å komme videre når NRK ikke ønsker å gå inn i
1259 problemstillingen rundt bruksvilkårene til videoredigeringsverktøyene
1260 NRK bruker, så jeg sendte takk for svarene og avsluttet utvekslingen
1261 så langt:</p>
1262
1263 <p><blockquote>
1264 <p>Tusen takk for rask respons, og oppklarende forklaring om hvordan
1265 NRK tenker rundt MPEG LA.</p>
1266
1267 <p>Jeg vil høre med NRK-arkivet for å se om de kan spore opp de
1268 omtalte dokumentene.  Jeg setter pris på om du kan dele titler, dato
1269 eller annen informasjon som kan gjøre det enklere for arkivet å finne
1270 dem.</p>
1271
1272 <p>Når det gjelder hvordan bruksvilkårene til
1273 videoredigeringsverktøyene skal tolkes, så skal jeg høre med MPEG LA
1274 og produsentene av verktøyene for å forsøke å få klarhet i hva de
1275 mener er rikgig rettstilstand.</p>
1276 </blockquote></p>
1277
1278 <p>Jeg ble litt klokere, men fortsatt er det uklart for meg hva som er
1279 grunnlaget til NRK for å se bort fra bruksvilkår i
1280 videoredigeringsprogramvare som krever MPEG LA-avtale til alt annet
1281 enn privat og ikke-kommersiell bruk.</p>
1282
1283       </div>
1284       <div class="tags">
1285
1286
1287         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
1288
1289
1290       </div>
1291     </div>
1292     <div class="padding"></div>
1293
1294     <div class="entry">
1295       <div class="title">
1296         <a href="https://people.skolelinux.org/pere/blog/Hvordan_vurderer_regjeringen_H_264_patentutfordringen_.html">Hvordan vurderer regjeringen H.264-patentutfordringen?</a>
1297       </div>
1298       <div class="date">
1299         16th November 2014
1300       </div>
1301       <div class="body">
1302         <p>For en stund tilbake spurte jeg Fornyingsdepartementet om hvilke
1303 juridiske vurderinger rundt patentproblemstillingen som var gjort da
1304 H.264 ble tatt inn i <a href="http://standard.difi.no/">statens
1305 referansekatalog over standarder</a>.  Stig Hornnes i FAD tipset meg
1306 om følgende som står i oppsumeringen til høringen om
1307 referansekatalogen versjon 2.0, som jeg siden ved hjelp av en
1308 innsynsforespørsel fikk tak i
1309 <a href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon.pdf">PDF-utgaven av</a>
1310 datert 2009-06-03 (saksnummer 200803291, saksbehandler Henrik
1311 Linnestad).</p>
1312
1313 <p>Der står det følgende om problemstillingen:</p>
1314
1315 <p><blockquote>
1316 <strong>4.4 Patentproblematikk</strong>
1317
1318 <p>NUUG og Opera ser det som særlig viktig at forslagene knyttet til
1319 lyd og video baserer seg på de royalty-frie standardene Vorbis, Theora
1320 og FLAC.</p>
1321
1322 <p>Kommentarene relaterer seg til at enkelte standarder er åpne, men
1323 inneholder tekniske prosedyrer som det i USA (og noen andre land som
1324 Japan) er gitt patentrettigheter til. I vårt tilfelle berører dette
1325 spesielt standardene Mp3 og H.264, selv om Politidirektoratet peker på
1326 at det muligens kan være tilsvarende problematikk også for Theora og
1327 Vorbis.  Dette medfører at det i USA kan kreves royalties for bruk av
1328 tekniske løsninger knyttet til standardene, et krav som også
1329 håndheves. Patenter kan imidlertid bare hevdes i de landene hvor
1330 patentet er gitt, så amerikanske patenter gjelder ikke andre steder
1331 enn USA.</p>
1332
1333 <p>Spesielt for utvikling av fri programvare er patenter
1334 problematisk. GPL, en "grunnleggende" lisens for distribusjon av fri
1335 programvare, avviser at programvare kan distribueres under denne
1336 lisensen hvis det inneholder referanser til patenterte rutiner som
1337 utløser krav om royalties. Det er imidlertid uproblematisk å
1338 distribuere fri programvareløsninger under GPL som benytter de
1339 aktuelle standardene innen eller mellom land som ikke anerkjenner
1340 patentene. Derfor finner vi også flere implementeringer av Mp3 og
1341 H.264 som er fri programvare, lisensiert under GPL.</p>
1342
1343 <p>I Norge og EU er patentlovgivningen langt mer restriktiv enn i USA,
1344 men det er også her mulig å få patentert metoder for løsning av et
1345 problem som relaterer seg til databehandling. Det er AIF bekjent ikke
1346 relevante patenter i EU eller Norge hva gjelder H.264 og Mp3, men
1347 muligheten for at det finnes patenter uten at det er gjort krav om
1348 royalties eller at det senere vil gis slike patenter kan ikke helt
1349 avvises.</p>
1350
1351 <p>AIF mener det er et behov for å gi offentlige virksomheter mulighet
1352 til å benytte antatt royaltyfrie åpne standarder som et likeverdig
1353 alternativ eller i tillegg til de markedsledende åpne standardene.</p>
1354
1355 </blockquote></p>
1356
1357 <p>Det ser dermed ikke ut til at de har vurdert patentspørsmålet i
1358 sammenheng med opphavsrettsvilkår slik de er formulert for f.eks.
1359 Apple Final Cut Pro, Adobe Premiere Pro, Avid og Sorenson-verktøyene,
1360 der det kreves brukstillatelse for patenter som ikke er gyldige i
1361 Norge for å bruke disse verktøyene til annet en personlig og ikke
1362 kommersiell aktivitet når det gjelder H.264-video.  Jeg må nok lete
1363 videre etter svar på det spørsmålet.</p>
1364
1365       </div>
1366       <div class="tags">
1367
1368
1369         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
1370
1371
1372       </div>
1373     </div>
1374     <div class="padding"></div>
1375
1376     <div class="entry">
1377       <div class="title">
1378         <a href="https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html">New lsdvd release version 0.17 is ready</a>
1379       </div>
1380       <div class="date">
1381          4th October 2014
1382       </div>
1383       <div class="body">
1384         <p>The <a href="https://sourceforge.net/p/lsdvd/">lsdvd project</a>
1385 got a new set of developers a few weeks ago, after the original
1386 developer decided to step down and pass the project to fresh blood.
1387 This project is now maintained by Petter Reinholdtsen and Steve
1388 Dibb.</p>
1389
1390 <p>I just wrapped up
1391 <a href="https://sourceforge.net/p/lsdvd/mailman/message/32896061/">a
1392 new lsdvd release</a>, available in git or from
1393 <a href="https://sourceforge.net/projects/lsdvd/files/lsdvd/">the
1394 download page</a>.  This is the changelog dated 2014-10-03 for version
1395 0.17.</p>
1396
1397 <ul>
1398
1399  <li>Ignore 'phantom' audio, subtitle tracks</li>
1400  <li>Check for garbage in the program chains, which indicate that a track is
1401    non-existant, to work around additional copy protection</li>
1402  <li>Fix displaying content type for audio tracks, subtitles</li>
1403  <li>Fix pallete display of first entry</li>
1404  <li>Fix include orders</li>
1405  <li>Ignore read errors in titles that would not be displayed anyway</li>
1406  <li>Fix the chapter count</li>
1407  <li>Make sure the array size and the array limit used when initialising
1408    the palette size is the same.</li>
1409  <li>Fix array printing.</li>
1410  <li>Correct subsecond calculations.</li>
1411  <li>Add sector information to the output format.</li>
1412  <li>Clean up code to be closer to ANSI C and compile without warnings
1413    with more GCC compiler warnings.</li>
1414
1415 </ul>
1416
1417 <p>This change bring together patches for lsdvd in use in various
1418 Linux and Unix distributions, as well as patches submitted to the
1419 project the last nine years.  Please check it out. :)</p>
1420
1421       </div>
1422       <div class="tags">
1423
1424
1425         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>.
1426
1427
1428       </div>
1429     </div>
1430     <div class="padding"></div>
1431
1432     <div class="entry">
1433       <div class="title">
1434         <a href="https://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>
1435       </div>
1436       <div class="date">
1437         25th September 2014
1438       </div>
1439       <div class="body">
1440         <p>I use the <a href="https://sourceforge.net/p/lsdvd/">lsdvd tool</a>
1441 to handle my fairly large DVD collection.  It is a nice command line
1442 tool to get details about a DVD, like title, tracks, track length,
1443 etc, in XML, Perl or human readable format.  But lsdvd have not seen
1444 any new development since 2006 and had a few irritating bugs affecting
1445 its use with some DVDs.  Upstream seemed to be dead, and in January I
1446 sent a small probe asking for a version control repository for the
1447 project, without any reply.  But I use it regularly and would like to
1448 get <a href="https://packages.qa.debian.org/lsdvd">an updated version
1449 into Debian</a>.  So two weeks ago I tried harder to get in touch with
1450 the project admin, and after getting a reply from him explaining that
1451 he was no longer interested in the project, I asked if I could take
1452 over.  And yesterday, I became project admin.</p>
1453
1454 <p>I've been in touch with a Gentoo developer and the Debian
1455 maintainer interested in joining forces to maintain the upstream
1456 project, and I hope we can get a new release out fairly quickly,
1457 collecting the patches spread around on the internet into on place.
1458 I've added the relevant Debian patches to the freshly created git
1459 repository, and expect the Gentoo patches to make it too.  If you got
1460 a DVD collection and care about command line tools, check out
1461 <a href="https://sourceforge.net/p/lsdvd/git/ci/master/tree/">the git source</a> and join
1462 <a href="https://sourceforge.net/p/lsdvd/mailman/">the project mailing
1463 list</a>. :)</p>
1464
1465       </div>
1466       <div class="tags">
1467
1468
1469         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>.
1470
1471
1472       </div>
1473     </div>
1474     <div class="padding"></div>
1475
1476     <div class="entry">
1477       <div class="title">
1478         <a href="https://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>
1479       </div>
1480       <div class="date">
1481         25th August 2014
1482       </div>
1483       <div class="body">
1484         <p>Two years later, I am still not sure if it is legal here in Norway
1485 to use or publish a video in H.264 or MPEG4 format edited by the
1486 commercially licensed video editors, without limiting the use to
1487 create "personal" or "non-commercial" videos or get a license
1488 agreement with <a href="http://www.mpegla.com">MPEG LA</a>.  If one
1489 want to publish and broadcast video in a non-personal or commercial
1490 setting, it might be that those tools can not be used, or that video
1491 format can not be used, without breaking their copyright license.  I
1492 am not sure.
1493 <a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">Back
1494 then</a>, I found that the copyright license terms for Adobe Premiere
1495 and Apple Final Cut Pro both specified that one could not use the
1496 program to produce anything else without a patent license from MPEG
1497 LA.  The issue is not limited to those two products, though.  Other
1498 much used products like those from Avid and Sorenson Media have terms
1499 of use are similar to those from Adobe and Apple.  The complicating
1500 factor making me unsure if those terms have effect in Norway or not is
1501 that the patents in question are not valid in Norway, but copyright
1502 licenses are.</p>
1503
1504 <p>These are the terms for Avid Artist Suite, according to their
1505 <a href="http://www.avid.com/US/about-avid/legal-notices/legal-enduserlicense2">published
1506 end user</a>
1507 <a href="http://www.avid.com/static/resources/common/documents/corporate/LICENSE.pdf">license
1508 text</a> (converted to lower case text for easier reading):</p>
1509
1510 <p><blockquote>
1511 <p>18.2. MPEG-4. MPEG-4 technology may be included with the
1512 software. MPEG LA, L.L.C. requires this notice: </p>
1513
1514 <p>This product is licensed under the MPEG-4 visual patent portfolio
1515 license for the personal and non-commercial use of a consumer for (i)
1516 encoding video in compliance with the MPEG-4 visual standard (“MPEG-4
1517 video”) and/or (ii) decoding MPEG-4 video that was encoded by a
1518 consumer engaged in a personal and non-commercial activity and/or was
1519 obtained from a video provider licensed by MPEG LA to provide MPEG-4
1520 video.  No license is granted or shall be implied for any other
1521 use. Additional information including that relating to promotional,
1522 internal and commercial uses and licensing may be obtained from MPEG
1523 LA, LLC.  See http://www.mpegla.com. This product is licensed under
1524 the MPEG-4 systems patent portfolio license for encoding in compliance
1525 with the MPEG-4 systems standard, except that an additional license
1526 and payment of royalties are necessary for encoding in connection with
1527 (i) data stored or replicated in physical media which is paid for on a
1528 title by title basis and/or (ii) data which is paid for on a title by
1529 title basis and is transmitted to an end user for permanent storage
1530 and/or use, such additional license may be obtained from MPEG LA,
1531 LLC. See http://www.mpegla.com for additional details.</p>
1532
1533 <p>18.3. H.264/AVC. H.264/AVC technology may be included with the
1534 software.  MPEG LA, L.L.C. requires this notice:</p>
1535
1536 <p>This product is licensed under the AVC patent portfolio license for
1537 the personal use of a consumer or other uses in which it does not
1538 receive remuneration to (i) encode video in compliance with the AVC
1539 standard (“AVC video”) and/or (ii) decode AVC video that was encoded
1540 by a consumer engaged in a personal activity and/or was obtained from
1541 a video provider licensed to provide AVC video. No license is granted
1542 or shall be implied for any other use. Additional information may be
1543 obtained from MPEG LA, L.L.C. See http://www.mpegla.com.</p>
1544 </blockquote></p>
1545
1546 <p>Note the requirement that the videos created can only be used for
1547 personal or non-commercial purposes.</p>
1548
1549 <p>The Sorenson Media software have
1550 <a href="http://www.sorensonmedia.com/terms/">similar terms</a>:</p>
1551
1552 <p><blockquote>
1553
1554 <p>With respect to a license from Sorenson pertaining to MPEG-4 Video
1555 Decoders and/or Encoders: Any such product is licensed under the
1556 MPEG-4 visual patent portfolio license for the personal and
1557 non-commercial use of a consumer for (i) encoding video in compliance
1558 with the MPEG-4 visual standard (“MPEG-4 video”) and/or (ii) decoding
1559 MPEG-4 video that was encoded by a consumer engaged in a personal and
1560 non-commercial activity and/or was obtained from a video provider
1561 licensed by MPEG LA to provide MPEG-4 video. No license is granted or
1562 shall be implied for any other use. Additional information including
1563 that relating to promotional, internal and commercial uses and
1564 licensing may be obtained from MPEG LA, LLC. See
1565 http://www.mpegla.com.</p>
1566
1567 <p>With respect to a license from Sorenson pertaining to MPEG-4
1568 Consumer Recorded Data Encoder, MPEG-4 Systems Internet Data Encoder,
1569 MPEG-4 Mobile Data Encoder, and/or MPEG-4 Unique Use Encoder: Any such
1570 product is licensed under the MPEG-4 systems patent portfolio license
1571 for encoding in compliance with the MPEG-4 systems standard, except
1572 that an additional license and payment of royalties are necessary for
1573 encoding in connection with (i) data stored or replicated in physical
1574 media which is paid for on a title by title basis and/or (ii) data
1575 which is paid for on a title by title basis and is transmitted to an
1576 end user for permanent storage and/or use. Such additional license may
1577 be obtained from MPEG LA, LLC. See http://www.mpegla.com for
1578 additional details.</p>
1579
1580 </blockquote></p>
1581
1582 <p>Some free software like
1583 <a href="https://handbrake.fr/">Handbrake</A> and
1584 <a href="http://ffmpeg.org/">FFMPEG</a> uses GPL/LGPL licenses and do
1585 not have any such terms included, so for those, there is no
1586 requirement to limit the use to personal and non-commercial.</p>
1587
1588       </div>
1589       <div class="tags">
1590
1591
1592         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
1593
1594
1595       </div>
1596     </div>
1597     <div class="padding"></div>
1598
1599     <div class="entry">
1600       <div class="title">
1601         <a href="https://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>
1602       </div>
1603       <div class="date">
1604         16th June 2014
1605       </div>
1606       <div class="body">
1607         <p>Jeg har fortsatt behov for å kunne laste ned innslag fra NRKs
1608 nettsted av og til for å se senere når jeg ikke er på nett, men
1609 <a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html">min
1610 oppskrift fra 2011</a> sluttet å fungere da NRK byttet
1611 avspillermetode.  I dag fikk jeg endelig lett etter oppdatert løsning,
1612 og jeg er veldig glad for å fortelle at den enkleste måten å laste ned
1613 innslag er å bruke siste versjon 2014.06.07 av
1614 <a href="http://rg3.github.io/youtube-dl/">youtube-dl</a>.  Støtten i
1615 youtube-dl <a href="https://github.com/rg3/youtube-dl/issues/2980">kom
1616 inn for 23 dager siden</a> og
1617 <a href="http://packages.qa.debian.org/y/youtube-dl.html">versjonen i
1618 Debian</a> fungerer fint også som backport til Debian Wheezy.  Det er
1619 et lite problem, det håndterer kun URLer med små bokstaver, men hvis
1620 en har en URL med store bokstaver kan en bare gjøre alle store om til
1621 små bokstaver for å få youtube-dl til å laste ned.  Rapporterte
1622 nettopp
1623 <a href="https://github.com/rg3/youtube-dl/issues/2980">problemet til
1624 utviklerne</a>, og antar de får fikset det snart.</p>
1625
1626 <p>Dermed er alt klart til å laste ned dokumentarene om
1627 <a href="http://tv.nrk.no/program/KOID23005014/usas-hemmelige-avlytting">USAs
1628 hemmelige avlytting</a> og
1629 <a href="http://tv.nrk.no/program/KOID23005114/selskapene-bak-usas-avlytting">Selskapene
1630 bak USAs avlytting</a>, i tillegg til
1631 <a href="http://tv.nrk.no/program/KOID20005814/et-moete-med-edward-snowden">intervjuet
1632 med Edward Snowden gjort av den tyske tv-kanalen ARD</a>.  Anbefaler
1633 alle å se disse, sammen med
1634 <a href="http://media.ccc.de/browse/congress/2013/30C3_-_5713_-_en_-_saal_2_-_201312301130_-_to_protect_and_infect_part_2_-_jacob.html">foredraget
1635 til Jacob Appelbaum på siste CCC-konferanse</a>, for å forstå mer om
1636 hvordan overvåkningen av borgerne brer om seg.</p>
1637
1638 <p>Takk til gode venner på foreningen NUUGs IRC-kanal
1639 <a href="irc://irc.freenode.net/%23nuug">#nuug på irc.freenode.net</a>
1640 for tipsene som fikk meg i mål</a>.</p>
1641
1642 <p><strong>Oppdatering 2014-06-17</strong>: Etter at jeg publiserte
1643 denne, ble jeg tipset om bloggposten
1644 "<a href="http://ingvar.blog.redpill-linpro.com/2012/05/31/downloading-hd-content-from-tv-nrk-no/">Downloading
1645 HD content from tv.nrk.no</a>" av Ingvar Hagelund, som har alternativ
1646 implementasjon og tips for å lage mkv-fil med undertekstene inkludert.
1647 Kanskje den passer bedre for deg?  I tillegg ble feilen i youtube-dl
1648 ble fikset litt senere ut på dagen i går, samt at youtube-dl fikk
1649 støtte for å laste ned undertitler.  Takk til Anders Einar Hilden for
1650 god innsats og youtube-dl-utviklerne for rask respons.</p>
1651
1652       </div>
1653       <div class="tags">
1654
1655
1656         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
1657
1658
1659       </div>
1660     </div>
1661     <div class="padding"></div>
1662
1663     <div class="entry">
1664       <div class="title">
1665         <a href="https://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>
1666       </div>
1667       <div class="date">
1668         29th April 2014
1669       </div>
1670       <div class="body">
1671         <p>I've been following <a href="http://www.getgnash.org/">the Gnash
1672 project</a> for quite a while now.  It is a free software
1673 implementation of Adobe Flash, both a standalone player and a browser
1674 plugin.  Gnash implement support for the AVM1 format (and not the
1675 newer AVM2 format - see
1676 <a href="http://lightspark.github.io/">Lightspark</a> for that one),
1677 allowing several flash based sites to work.  Thanks to the friendly
1678 developers at Youtube, it also work with Youtube videos, because the
1679 Javascript code at Youtube detect Gnash and serve a AVM1 player to
1680 those users. :) Would be great if someone found time to implement AVM2
1681 support, but it has not happened yet.  If you install both Lightspark
1682 and Gnash, Lightspark will invoke Gnash if it find a AVM1 flash file,
1683 so you can get both handled as free software.  Unfortunately,
1684 Lightspark so far only implement a small subset of AVM2, and many
1685 sites do not work yet.</p>
1686
1687 <p>A few months ago, I started looking at
1688 <a href="http://scan.coverity.com/">Coverity</a>, the static source
1689 checker used to find heaps and heaps of bugs in free software (thanks
1690 to the donation of a scanning service to free software projects by the
1691 company developing this non-free code checker), and Gnash was one of
1692 the projects I decided to check out.  Coverity is able to find lock
1693 errors, memory errors, dead code and more.  A few days ago they even
1694 extended it to also be able to find the heartbleed bug in OpenSSL.
1695 There are heaps of checks being done on the instrumented code, and the
1696 amount of bogus warnings is quite low compared to the other static
1697 code checkers I have tested over the years.</p>
1698
1699 <p>Since a few weeks ago, I've been working with the other Gnash
1700 developers squashing bugs discovered by Coverity.  I was quite happy
1701 today when I checked the current status and saw that of the 777 issues
1702 detected so far, 374 are marked as fixed.  This make me confident that
1703 the next Gnash release will be more stable and more dependable than
1704 the previous one.  Most of the reported issues were and are in the
1705 test suite, but it also found a few in the rest of the code.</p>
1706
1707 <p>If you want to help out, you find us on
1708 <a href="https://lists.gnu.org/mailman/listinfo/gnash-dev">the
1709 gnash-dev mailing list</a> and on
1710 <a href="irc://irc.freenode.net/#gnash">the #gnash channel on
1711 irc.freenode.net IRC server</a>.</p>
1712
1713       </div>
1714       <div class="tags">
1715
1716
1717         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
1718
1719
1720       </div>
1721     </div>
1722     <div class="padding"></div>
1723
1724     <div class="entry">
1725       <div class="title">
1726         <a href="https://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>
1727       </div>
1728       <div class="date">
1729         21st March 2014
1730       </div>
1731       <div class="body">
1732         <p>Keeping your DVD collection safe from scratches and curious
1733 children fingers while still having it available when you want to see a
1734 movie is not straight forward.  My preferred method at the moment is
1735 to store a full copy of the ISO on a hard drive, and use VLC, Popcorn
1736 Hour or other useful players to view the resulting file.  This way the
1737 subtitles and bonus material are still available and using the ISO is
1738 just like inserting the original DVD record in the DVD player.</p>
1739
1740 <p>Earlier I used dd for taking security copies, but it do not handle
1741 DVDs giving read errors (which are quite a few of them).  I've also
1742 tried using
1743 <a href="http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html">dvdbackup
1744 and genisoimage</a>, but these days I use the marvellous python library
1745 and program
1746 <a href="http://bblank.thinkmo.de/blog/new-software-python-dvdvideo">python-dvdvideo</a>
1747 written by Bastian Blank.  It is
1748 <a href="http://packages.qa.debian.org/p/python-dvdvideo.html">in Debian
1749 already</a> and the binary package name is python3-dvdvideo. Instead
1750 of trying to read every block from the DVD, it parses the file
1751 structure and figure out which block on the DVD is actually in used,
1752 and only read those blocks from the DVD.  This work surprisingly well,
1753 and I have been able to almost backup my entire DVD collection using
1754 this method.</p>
1755
1756 <p>So far, python-dvdvideo have failed on between 10 and
1757 20 DVDs, which is a small fraction of my collection.  The most common
1758 problem is
1759 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720831">DVDs
1760 using UTF-16 instead of UTF-8 characters</a>, which according to
1761 Bastian is against the DVD specification (and seem to cause some
1762 players to fail too).  A rarer problem is what seem to be inconsistent
1763 DVD structures, as the python library
1764 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723079">claim
1765 there is a overlap between objects</a>.  An equally rare problem claim
1766 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741878">some
1767 value is out of range</a>.  No idea what is going on there.  I wish I
1768 knew enough about the DVD format to fix these, to ensure my movie
1769 collection will stay with me in the future.</p>
1770
1771 <p>So, if you need to keep your DVDs safe, back them up using
1772 python-dvdvideo. :)</p>
1773
1774       </div>
1775       <div class="tags">
1776
1777
1778         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
1779
1780
1781       </div>
1782     </div>
1783     <div class="padding"></div>
1784
1785     <div class="entry">
1786       <div class="title">
1787         <a href="https://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html">IETF activity to standardise video codec</a>
1788       </div>
1789       <div class="date">
1790         15th September 2012
1791       </div>
1792       <div class="body">
1793         <p>After the
1794 <a href="http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html">Opus
1795 codec made</a> it into <a href="http://www.ietf.org/">IETF</a> as
1796 <a href="http://tools.ietf.org/html/rfc6716">RFC 6716</a>, I had a look
1797 to see if there is any activity in IETF to standardise a video codec
1798 too, and I was happy to discover that there is some activity in this
1799 area.  A non-"working group" mailing list
1800 <a href="https://www.ietf.org/mailman/listinfo/video-codec">video-codec</a>
1801 was
1802 <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
1803 formal working group should be formed.</p>
1804
1805 <p>I look forward to see how this plays out.  There is already
1806 <a href="http://www.ietf.org/mail-archive/web/video-codec/current/msg00003.html">an
1807 email from someone</a> in the MPEG group at ISO asking people to
1808 participate in the ISO group.  Given how ISO failed with OOXML and given
1809 that it so far (as far as I can remember) only have produced
1810 multimedia formats requiring royalty payments, I suspect
1811 joining the ISO group would be a complete waste of time, but I am not
1812 involved in any codec work and my opinion will not matter much.</p>
1813
1814 <p>If one of my readers is involved with codec work, I hope she will
1815 join this work to standardise a royalty free video codec within
1816 IETF.</p>
1817
1818       </div>
1819       <div class="tags">
1820
1821
1822         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
1823
1824
1825       </div>
1826     </div>
1827     <div class="padding"></div>
1828
1829     <div class="entry">
1830       <div class="title">
1831         <a href="https://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html">IETF standardize its first multimedia codec: Opus</a>
1832       </div>
1833       <div class="date">
1834         12th September 2012
1835       </div>
1836       <div class="body">
1837         <p>Yesterday, <a href="http://www.ietf.org/">IETF</a> announced the
1838 publication of of
1839 <a href="http://tools.ietf.org/html/rfc6716">RFC 6716, the Definition
1840 of the Opus Audio Codec</a>, a low latency, variable bandwidth, codec
1841 intended for both VoIP, film and music.  This is the first time, as
1842 far as I know, that IETF have standardized a multimedia codec.  In
1843 <a href="http://tools.ietf.org/html/rfc3533">RFC 3533</a>, IETF
1844 standardized the OGG container format, and it has proven to be a great
1845 royalty free container for audio, video and movies.  I hope IETF will
1846 continue to standardize more royalty free codeces, after ISO and MPEG
1847 have proven incapable of securing everyone equal rights to publish
1848 multimedia content on the Internet.</p>
1849
1850 <p>IETF require two interoperating independent implementations to
1851 ratify a standard, and have so far ensured to only standardize royalty
1852 free specifications.  Both are key factors to allow everyone (rich and
1853 poor), to compete on equal terms on the Internet.</p>
1854
1855 <p>Visit the <a href="http://opus-codec.org/">Opus project page</a> if
1856 you want to learn more about the solution.</p>
1857
1858       </div>
1859       <div class="tags">
1860
1861
1862         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
1863
1864
1865       </div>
1866     </div>
1867     <div class="padding"></div>
1868
1869     <div class="entry">
1870       <div class="title">
1871         <a href="https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html">Git repository for song book for Computer Scientists</a>
1872       </div>
1873       <div class="date">
1874          7th September 2012
1875       </div>
1876       <div class="body">
1877         <p>As I
1878 <a href="http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html">mentioned
1879 this summer</a>, I have created a Computer Science song book a few
1880 years ago, and today I finally found time to create a public
1881 <a href="https://gitorious.org/pere-cs-songbook/pere-cs-songbook">Gitorious
1882 repository for the project</a>.</p>
1883
1884 <p>If you want to help out, please clone the source and submit patches
1885 to the HTML version.  To generate the PDF and PostScript version,
1886 please use prince XML, or let me know about a useful free software
1887 processor capable of creating a good looking PDF from the HTML.</p>
1888
1889 <p>Want to sing?  You can still find the song book in HTML, PDF and
1890 PostScript formats at
1891 <a href="http://www.hungry.com/~pere/cs-songbook/">Petter's Computer
1892 Science Songbook</a>.</p>
1893
1894       </div>
1895       <div class="tags">
1896
1897
1898         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>.
1899
1900
1901       </div>
1902     </div>
1903     <div class="padding"></div>
1904
1905     <div class="entry">
1906       <div class="title">
1907         <a href="https://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>
1908       </div>
1909       <div class="date">
1910          5th July 2012
1911       </div>
1912       <div class="body">
1913         <p>I føljetongen om H.264
1914 <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
1915 jeg leserne i undring</a> om hvor pakken fra MPEG-LA tok veien, og om
1916 hvilke selskaper i Norge som har avtale med MPEG-LA.  Da Ryan hos
1917 MPEG-LA dro på ferie sendte jeg min melding videre til hans kollega,
1918 og dagen etter fikk jeg følgende svar derfra:</p>
1919
1920 <p><blockquote>
1921 <p>Date: Fri, 29 Jun 2012 18:32:34 +0000
1922 <br>From: Sidney Wolf &lt;SWolf (at) mpegla.com&gt;
1923 <br>To: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
1924 <br>Cc: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
1925 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
1926
1927 <p>Dear Mr. Reinholdtsen,</p>
1928
1929 <p>Thank you for your message. As you know, Ryan is currently our of the
1930 office, so it will be my pleasure to assist you.</p>
1931
1932 <p>Per your request, attached please find an electronic copy of the
1933 AVC Patent Portfolio License. Please note that the electronic copy of
1934 the License is provided as a convenience and for informational
1935 purposes only. When concluding the Licenses, only the hard copies
1936 provided by MPEG LA may be used.</p>
1937
1938 <p>To your question, MPEG LA lists our Licensees on our website
1939 according to each program.  The lists are in alphabetical order, so it
1940 is very easy to search.</p>
1941
1942 <p>I hope that this was helpful. If we can be of additional
1943 assistance, please let me know.</p>
1944
1945 <p>Kind regards,</p>
1946
1947 <p>Sidney A. Wolf
1948 <br>Manager, Global Licensing
1949 <br>MPEG LA</p>
1950 </blockquote></p>
1951
1952 <p>Selv om et epostvedlegg er nyttig for mottakeren, så håpet jeg å få
1953 et dokument jeg kunne dele med alle leserne av bloggen min, og ikke et
1954 som må deles på individuell basis.  Opphavsretten krever godkjenning
1955 fra rettighetsinnehaver før en kan gjøre slikt, så dermed fulgte jeg
1956 opp med et spørsmål om dette var greit.</p>
1957
1958 <p><blockquote>
1959 <p>Date: Wed, 4 Jul 2012 20:25:06 +0200
1960 <br>From: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
1961 <br>To: Sidney Wolf &lt;SWolf (at) mpegla.com&gt;
1962 <br>Cc: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
1963 <br>Subject: Re: Do NRK have a license agreement with MPEG-LA?</p>
1964
1965 <p>Thank you for your reply.</p>
1966
1967 <p>[Sidney Wolf]
1968 <br>&gt; Per your request, attached please find an electronic copy of the AVC
1969 <br>&gt; Patent Portfolio License. Please note that the electronic copy of
1970 <br>&gt; the License is provided as a convenience and for informational
1971 <br>&gt; purposes only. When concluding the Licenses, only the hard copies
1972 <br>&gt; provided by MPEG LA may be used.</p>
1973
1974 <p>This is useful for me to learn, but the reason I asked for the
1975 Internet address of the licensing document was to ensure I could
1976 publish a link to it when I discuss the topic of H.264 licensing here
1977 in Norway, and allow others to verify my observations.  I can not do
1978 the same with an email attachment.  Thus I would like to ask you if it
1979 is OK with MPEG LA that I publish this document on the Internet for
1980 others to read?</p>
1981
1982 <p>&gt; To your question, MPEG LA lists our Licensees on our website
1983 <br>&gt; according to each program. The lists are in alphabetical order, so
1984 <br>&gt; it is very easy to search.</p>
1985
1986 <p>I am afraid this do not help me locate Norwegian companies in the
1987 list of Licensees.  I do not know the name of all companies and
1988 organisations in Norway, and thus do not know how to locate the
1989 Norwegian ones on that list.</p>
1990
1991 <p>&gt; I hope that this was helpful. If we can be of additional assistance,
1992 <br>&gt; please let me know.</p>
1993
1994 <p>Absoutely helpful to learn more about how MPEG LA handle licensing.</p>
1995
1996 <p>--
1997 <br>Happy hacking
1998 <br>Petter Reinholdtsen</p>
1999 </blockquote></p>
2000
2001 <p>Jeg håpet også at det skulle være mulig å få vite hvilke av de
2002 mange hundre som har avtale med MPEG-LA om bruk av H.264 som holdt til
2003 i Norge.  Begge mine håp falt i grus med svaret fra MPEG-LA.
2004
2005 <p><blockquote>
2006 <p>Date: Thu, 5 Jul 2012 17:42:39 +0000
2007 <br>From: Sidney Wolf &lt;SWolf (at) mpegla.com&gt;
2008 <br>To: 'Petter Reinholdtsen' &lt;pere (at) hungry.com&gt;
2009 <br>Cc: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
2010 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
2011
2012 <p>Dear Mr. Reinholdtsen,</p>
2013
2014 <p>Thank you for your reply.</p>
2015
2016 <p>We appreciate the additional explanation you have provided and for
2017 asking our permission to publish the electronic copy of the License in
2018 advance of doing so.  Typically, MPEG LA prefers to distribute the
2019 electronic copies of our Licenses to interested parties. Therefore,
2020 please feel free to send interested parties to the AVC portion of our
2021 website, http://www.mpegla.com/main/programs/AVC/Pages/Intro.aspx for
2022 their further reference.</p>
2023
2024 <p>As previously mentioned, MPEG LA maintains a list of Licensees in good
2025 standing on our website according to each program. Due to the large
2026 volume of Licensees, it would be administratively impractical to
2027 provide this level of detail to interested parties.  Therefore, I am
2028 afraid we are not in a position to assist you with your request.</p>
2029
2030 <p>Kind regards,</p>
2031
2032 <p>Sidney A. Wolf
2033 <br>Manager, Global Licensing
2034 <br>MPEG LA</p>
2035 </blockquote></p>
2036
2037 <p>Men takket være epostvedlegget kunne jeg søke på Google etter
2038 setningen "WHEREAS, a video standard commonly referred to as AVC has
2039 been defined and is referred to in this Agreement as the “AVC
2040 Standard” (as more fully defined herein below)" som finnes i avtalen,
2041 og lokalisere en kopi fra 2007 av
2042 <a href="http://www.sec.gov/Archives/edgar/data/1342960/000119312509050004/dex1024.htm">lisensavtalen
2043 mellom MPEG-LA og DivX, Inc.</a>, slik at mine lesere kan se hvordan
2044 avtalen så ut da.  Jeg har ikke sammenlignet tekstene for å se om noe
2045 har endret seg siden den tid, men satser på at teksten er representativ.</p>
2046
2047 <p>Jeg aner fortsatt ikke hvor FedEx tok veien med pakken fra
2048 MPEG-LA.</p>
2049
2050 <p>Update 2012-07-06: Jeg er visst ikke den første som forsøker å få
2051 klarhet i problemstillinger rundt H.264, og kom nettopp over en veldig
2052 interessant bloggpost fra 2010 hos LibreVideo med tittelen
2053 "<a href="http://www.librevideo.org/blog/2010/06/14/mpeg-la-answers-some-questions-about-avch-264-licensing/">MPEG-LA
2054 answers some questions about AVC/H.264 licensing</a>.  Anbefales!</p>
2055
2056       </div>
2057       <div class="tags">
2058
2059
2060         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
2061
2062
2063       </div>
2064     </div>
2065     <div class="padding"></div>
2066
2067     <div class="entry">
2068       <div class="title">
2069         <a href="https://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>
2070       </div>
2071       <div class="date">
2072         29th June 2012
2073       </div>
2074       <div class="body">
2075         <p>Da fikk jeg nettopp svar fra
2076 <a href="http://www.dss.dep.no/">Departementenes servicesenter</a>
2077 (DSS) på
2078 <a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">mitt
2079 spørsmål om avtale rundt bruk av H.264</a>.  De har ingen avtale med
2080 MPEG LA eller dets representanter.  Her er svaret.
2081
2082 <p><blockquote>
2083
2084 <p>Date: Fri, 29 Jun 2012 07:04:42 +0000
2085 <br>From: Nielsen Mette Haga &lt;Mette-Haga.Nielsen (at) dss.dep.no&gt;
2086 <br>To: Petter Reinholdtsen &lt;petter.reinholdtsen (at) ...&gt;
2087 <br>CC: Postmottak &lt;Postmottak (at) dss.dep.no&gt;
2088 <br>Subject: SV: Innsynsbegjæring om MPEG/H.264-relaterte avtaler</p>
2089
2090 <p>DSS har ikke inngått noen egen lisensavtale med MPEG-LA eller noen som
2091 representerer MPEG-LA i Norge. Videoløsningen på regjeringen.no er
2092 levert av Smartcom:tv. Lisensforholdet rundt H.264 er ikke omtalt i
2093 vår avtale med Smartcom.</p>
2094
2095 <p>Vennlig hilsen</p>
2096
2097 <p>Mette Haga Nielsen
2098 <br>Fung. seksjonssjef</p>
2099
2100 <p>Departementenes servicesenter</p>
2101
2102 <p>Informasjonsforvaltning
2103
2104 <p>Mobil 93 09 83 51
2105 <br>E-post mette-haga.nielsen (at) dss.dep.no</p>
2106 </blockquote></p>
2107
2108 <p>Hvis den norske regjeringen representert ved DSS ikke har slik
2109 avtale, så kan en kanskje konkludere med at det ikke trengs?  Jeg er
2110 ikke trygg på at det er god juridisk grunn å stå på, men det er i det
2111 minste interessant å vite at hverken NRK eller DSS har funnet det
2112 nødvendig å ha avtale om bruk av H.264.</p>
2113
2114 <p>Det forklarer ikke hvordan de kan ignorere bruksvilkårene knyttet
2115 til bruk av opphavsrettsbeskyttet materiale de bruker til
2116 videoproduksjon, med mindre slike vilkår kan ignoreres av selskaper og
2117 privatpersoner i Norge.  Har de lov til å bryte vilkårene, eller har
2118 de brutt dem og så langt sluppet unna med det?  Jeg aner ikke.</p>
2119
2120       </div>
2121       <div class="tags">
2122
2123
2124         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
2125
2126
2127       </div>
2128     </div>
2129     <div class="padding"></div>
2130
2131     <div class="entry">
2132       <div class="title">
2133         <a href="https://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>
2134       </div>
2135       <div class="date">
2136         28th June 2012
2137       </div>
2138       <div class="body">
2139         <p>Etter at NRK
2140 <a href="http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html">nektet
2141 å spore opp eventuell avtale med MPEG-LA</a> eller andre om bruk av
2142 MPEG/H.264-video etter at jeg <a
2143 href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">ba
2144 om innsyn i slike avtaler</a>, tenkte jeg at i stedet for å forsøke å
2145 få NRK til å finne en slik avtale, så burde det være like enkelt å
2146 spørre MPEG-LA om de hadde avtale med NRK.  Spørsmålet ble sendt før
2147 jeg fikk tips fra Kieran Kunhya om hvor listen over lisensinnehavere
2148 "in Good Standing" befant seg.  MPEG-LA svarte meg i dag, og kan
2149 fortelle at NRK ikke har noen avtale med dem, så da er i det minste det
2150 slått fast.  Ikke overraskende mener MPEG-LA at det trengs en avtale
2151 med MPEG-LA for å streame H.264, men deres rammer er jo
2152 rettstilstanden i USA og ikke Norge.  Jeg tar dermed den delen av
2153 svaret med en klype salt.  Jeg er dermed fortsatt ikke klok på om det
2154 trengs en avtale, og hvis det trengs en avtale her i Norge, heller
2155 ikke sikker på om NRK har en avtale med noen andre enn MPEG-LA som
2156 gjør at de ikke trenger avtale direkte med MPEG-LA.  Jeg håper NRKs
2157 jurister har vurdert dette, og at det er mulig å få tilgang til
2158 vurderingen uansett om de trenger en avtale eller ikke.</p>
2159
2160 <p>Her er epostutvekslingen med MPEG-LA så langt.  Håper ikke
2161 utvekslingen fører til NRK plutselig får en litt uventet pakke fra
2162 MPEG-LA.</p>
2163
2164 <p><blockquote>
2165 <p>Date: Mon, 25 Jun 2012 15:29:37 +0200
2166 <br>From: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
2167 <br>To: licensing-web (at) mpegla.com
2168 <br>Subject: Do NRK have a license agreement with MPEG-LA?</p>
2169
2170 <p>Hi.  I have a small question for you, that I hope it is OK that I
2171 ask.</p>
2172
2173 <p>Is there any license agreements between MPEG-LA and NRK, &lt;URL:
2174 <a href="http://www.nrk.no/">http://www.nrk.no/</a> &gt;, the
2175 Norwegian national broadcasting cooperation?  I am not sure if they
2176 need one, and am just curious if such agreeement exist.</p>
2177
2178 <p>The postal address is</p>
2179
2180 <p><blockquote>
2181   NRK
2182   <br>Postbox 8500, Majorstuen
2183   <br>0340 Oslo
2184   <br>Norway
2185 </blockquote></p>
2186
2187 <p>if it make it easier for you to locate such agreement.</p>
2188
2189 <p>Can you tell me how many entities in Norway have an agreement with
2190 MPEG-LA, and the name of these entities?</p>
2191
2192 <p>--
2193 <br>Happy hacking
2194 <br>Petter Reinholdtsen
2195 </blockquote></p>
2196
2197 <p>I dag, to dager senere, fikk jeg følgende svar:</p>
2198
2199 <p><blockquote>
2200 <p>Date: Thu, 28 Jun 2012 14:11:17 +0000
2201 <br>From: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com>
2202 <br>To: Petter Reinholdtsen &lt;pere (at) hungry.com>
2203 <br>CC: MD Administration &lt;MDAdministration (at) mpegla.com>
2204 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
2205
2206 <p>Dear Mr. Reinholdtsen,</p>
2207
2208 <p>Thank you for your message and for your interest in MPEG LA. We
2209 appreciate hearing from you and I will be happy to assist you.</p>
2210
2211 <p>To begin, I will assume that you are referring to AVC/H.264
2212 technology in your message below, as this technology is commonly used
2213 in the transmission of video content.  In that case, please allow me
2214 to briefly summarize the coverage provided by our AVC Patent Portfolio
2215 License.</p>
2216
2217 <P>Our AVC License provides coverage for end products and video
2218 services that make use of AVC/H.264 technology.  Accordingly, the
2219 party offering such end products and video to End Users concludes the
2220 AVC License and is responsible for paying the applicable royalties
2221 associated with the end products/video they offer.</p>
2222
2223 <p>While the Norwegian Broadcast Corporation (NRK) is not currently a
2224 Licensee to MPEG LA's AVC License (or any other Portfolio License
2225 offered by MPEG LA), if NRK offers AVC Video to End Users for
2226 remuneration (for example, Title-by-Title, Subscription, Free
2227 Television, or Internet Broadcast AVC Video), then NRK will need to
2228 conclude the AVC License and may be responsible for paying applicable
2229 royalties associated with the AVC Video it distributes.</p>
2230
2231 <p>Today I will send you a FedEx package containing a copy of our AVC
2232 License for your review.  You should receive the License document
2233 within the next few days.</p>
2234
2235 <p>Meanwhile, MPEG LA currently has several Norwegian Licensees that
2236 can be found under the "Licensees" header within the respective
2237 portion of our website.  For example, you may find our list of
2238 Licensees in Good Standing to our AVC License in the AVC portion of
2239 our website,
2240 <a href="http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx">http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx</a></p>
2241
2242 <p>I hope the above information is helpful.  If you have additional
2243 questions or need further assistance with the AVC License, please feel
2244 free to contact me directly.  I look forward to hearing from you again
2245 soon.</p>
2246
2247 <p>Best regards,</p>
2248
2249 <p>Ryan</p>
2250
2251 <p>Ryan M. Rodriguez
2252 <br>Licensing Associate
2253 <br>MPEG LA
2254 <br>5425 Wisconsin Avenue
2255 <br>Suite 801
2256 <br>Chevy Chase, MD 20815
2257 <br>U.S.A.
2258 <br>Phone:  +1 (301) 986-6660 x211
2259 <br>Fax:    +1 (301) 986-8575
2260 <br>Email: rrodriguez (at) mpegla.com</p>
2261
2262 </blockquote></p>
2263
2264 <p>Meldingen om utsendt FedEx-pakke var så merkelig at jeg
2265 øyeblikkelig sendte svar tilbake og spurte hva i alle dager han mente,
2266 da han jo ikke hadde fått noen postadresse som nådde meg.</p>
2267
2268 <p><blockquote>
2269
2270 <p>Date: Thu, 28 Jun 2012 16:36:15 +0200
2271 <br>From: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
2272 <br>To: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
2273 <br>Cc: MD Administration &lt;MDAdministration (at) mpegla.com&gt;
2274 <br>Subject: Re: Do NRK have a license agreement with MPEG-LA?</p>
2275
2276 <p>[Ryan Rodriguez]
2277 <br>&gt; Dear Mr. Reinholdtsen,</p>
2278
2279 <p>Thank you for your quick reply.</p>
2280
2281 <p>&gt; Today I will send you a FedEx package containing a copy of our AVC
2282 <br>&gt; License for your review.  You should receive the License document
2283 <br>&gt; within the next few days.</p>
2284
2285 <p>The part about sending a FedEx package confused me, though.  I did not
2286 <br>give you my address, nor am I associated with NRK in any way, so I hope
2287 <br>you did not try to send me a package using the address of NRK.  If you
2288 <br>would send me the Internet address of to the document, it would be more
2289 <br>useful to me to be able to download it as an electronic document.</p>
2290
2291 <p>&gt; Meanwhile, MPEG LA currently has several Norwegian Licensees that can
2292 <br>&gt; be found under the "Licensees" header within the respective portion
2293 <br>&gt; of our website.  For example, you may find our list of Licensees in
2294 <br>&gt; Good Standing to our AVC License in the AVC portion of our website,
2295 <br>&gt; http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx</p>
2296
2297 <p>How can I recognize the Norwegian licensees?</p>
2298
2299 <p>--
2300 <br>Happy hacking
2301 <br>Petter Reinholdtsen</p>
2302 </blockquote></p>
2303
2304 <p>Selv om jeg svarte kun noen minutter etter at jeg fikk eposten fra
2305 MPEG-LA, fikk jeg eposten under som automatisk var beskjed på min
2306 siste epost.  Får håpe noen likevel følger opp "FedEx-pakken".  For å
2307 øke sjansen for at noen revurderer utsending av pakke uten mottaker,
2308 videresendte jeg min epost til swolf (at) mpegla.com, så får vi se.
2309 Har ikke hørt noe mer 3 timer senere, så jeg mistenker at ingen leste
2310 min epost tidsnok.</p>
2311
2312 <p><blockquote>
2313
2314 <p>Date: Thu, 28 Jun 2012 14:36:20 +0000
2315 <br>From: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
2316 <br>To: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
2317 <br>Subject: Automatic reply: Do NRK have a license agreement with MPEG-LA?</p>
2318
2319 <p>Thank you for your message.</p>
2320
2321 <p>I will be out of the office until Thursday, July 5 and will respond
2322 to all messages upon my return.  If this is a matter that requires
2323 immediate attention, please contact Sidney Wolf (swolf (at)
2324 mpegla.com)</p>
2325
2326 <p>Best regards,</p>
2327
2328 <p>Ryan</p>
2329
2330 <p>Ryan M. Rodriguez
2331 <br>Licensing Associate
2332 <br>MPEG LA</p>
2333
2334 </blockquote></p>
2335
2336 <p>Litt klokere, men fortsatt ikke klok på mitt opprinnelige spørsmål,
2337 som er om en trenger avtale med MPEG-LA for å publisere eller
2338 kringkaste H.264-video i Norge.</p>
2339
2340       </div>
2341       <div class="tags">
2342
2343
2344         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
2345
2346
2347       </div>
2348     </div>
2349     <div class="padding"></div>
2350
2351     <div class="entry">
2352       <div class="title">
2353         <a href="https://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>
2354       </div>
2355       <div class="date">
2356         25th June 2012
2357       </div>
2358       <div class="body">
2359         <p>Jeg fikk nettopp svar fra NRK på
2360 <a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">min
2361 forespørsel om kopi av avtale</a> med MPEG-LA eller andre om bruk av
2362 MPEG og/eller H.264.  Svaret har fått saksreferanse 2011/371 (mon tro
2363 hva slags sak fra 2011 dette er?) hos NRK og lyder som følger:</p>
2364
2365 <p><blockquote>
2366
2367 <p><strong>Svar på innsynsbegjæring i MPEG / H.264-relaterte
2368 avtaler</strong></p>
2369
2370 <p>Viser til innsynsbegjæring av 19. juni 2012. Kravet om innsyn
2371 gjelder avtale som gjør at NRK «ikke er begrenset av de generelle
2372 bruksvilkårene som gjelder for utstyr som bruker MPEG og/eller
2373 H.264».</p>
2374
2375 <p>I henhold til offentleglova § 28 annet ledd må innsynskravet gjelde
2376 en bestemt sak eller i rimelig utstrekning saker av en bestemt
2377 sak. Det er på det rene at det aktuelle innsynskravet ikke gjelder en
2378 bestemt sak. Spørsmålet som reiser seg er om identifiseringsgraden er
2379 tilstrekkelig. I Justisdepartementets «Rettleiar til offentleglova»
2380 står følgende:</p>
2381
2382 <p>«Kravet om at innsynskravet må gjelde ei bestemt sak er til hinder
2383 for at eit innsynskrav kan gjelde alle saker av ein bestemt art, utan
2384 at den enkelte saka blir identifisert.  Ein kan med andre ord i
2385 utgangspunktet ikkje krevje innsyn i til dømes alle saker om
2386 utsleppsløyve hos Statens forureiningstilsyn frå dei siste tre åra,
2387 med mindre ein identifiserer kvar enkelt sak, til dømes med tilvising
2388 til dato, partar eller liknande.»</p>
2389
2390 <p>Vedrørende denne begrensningen har Justisdepartementet uttalt
2391 følgende (Lovavdelingens uttalelser JDLOV-2010-3295):</p>
2392
2393 <p><em>«Bakgrunnen for avgrensinga av kva innsynskravet kan gjelde,
2394 er fyrst og fremst at meir generelle innsynskrav, utan noka form for
2395 identifikasjon av kva ein eigentleg ynskjer, ville vere svært
2396 vanskelege å handsame for forvaltninga.»</em></p>
2397
2398 <p>I samme sak uttaler Lovavdelingen følgende:</p>
2399
2400 <p><em>«Det følgjer vidare av offentleglova § 28 andre ledd at det `i
2401 rimeleg utstrekning' kan krevjast innsyn i `saker av ein bestemt
2402 art'. Vilkåret om at eit innsynskrav berre `i rimeleg utstrekning' kan
2403 gjelde saker av ein bestemt art, er i hovudsak knytt til kor
2404 arbeidskrevjande det vil vere å finne fram til dei aktuelle
2405 dokumenta. I tillegg reknar vi med at vilkåret kan gje grunnlag for å
2406 nekte innsyn i tilfelle der innsynskravet er så omfattande (gjeld så
2407 mange dokument) at arbeidsmengda som ville gått med til å handsame
2408 det, er større enn det ein `i rimeleg utstrekning' kan krevje (sjølv
2409 om det nok skal mykje til).»</em></p>
2410
2411 <p>NRK har ikke noen egen sammenstilling over avtaler innenfor
2412 bestemte områder som omtales i innsynsbegjæringen. De måtte søkes på
2413 vanlig måte. I tillegg finnes ikke noen automatisert måte å finne
2414 avtaler som «ikke er begrenset av de generelle bruksvilkårene som
2415 gjelder for utstyr som bruker MPEG og/eller H.264». En slik
2416 gjennomgang av avtaler måtte gjøres manuelt av en person med
2417 spesialistkunnskap. Dette vil kreve at NRK avsetter omfattende
2418 ressurser for å finne frem relevante avtaler og for deretter å vurdere
2419 om de dekkes av det innsynsbegjæringen omfattes.</p>
2420
2421 <p>På bakgrunn av dette nekter NRK innsyn, med den begrunnelsen at
2422 innsynskravet er så omfattende at arbeidsmengden for å håndtere kravet
2423 vil være langt større enn det som i rimelig utstrekning kan kreves i
2424 henhold til offentleglova § 28 annet ledd.</p>
2425
2426 <p>Avslag på deres innsynsbegjæring kan påklages til Kultur- og
2427 kirkedepartementet innen tre uker fra det tidspunkt avslaget kommer
2428 frem til mottakeren, i henhold til reglene i offentleglova § 32,
2429 jf. forvaltningsloven kapittel VI. Klagen skal stiles til Kultur- og
2430 kirkedepartementet, og sendes til NRK.</p>
2431
2432 <p>NRK er imidlertid etter Offentleglova forpliktet å gi ut journaler,
2433 slik at en eventuell søknad om innsyn kan tydeligere identifisere
2434 hvilke dokumenter som det ønskes innsyn i. NRKs offentlige journaler
2435 for inneværende og forrige måned ligger ute på
2436 NRK.no/innsyn. Journaler som går lengre tilbake i tid, kan sendes ut
2437 på forespørsel til innsyn (at) nrk.no.</p>
2438
2439 <p>Med hilsen
2440 <br>Dokumentarkivet i NRK
2441 <br>v/ Elin Brandsrud
2442 <br>Tel. direkte: 23 04 29 29
2443 <br>Post: RBM3, Postboks 8500 Majorstuen, 0340 Oslo
2444 <br>innsyn (at) nrk.no</p>
2445
2446 </blockquote></p>
2447
2448 <p>Svaret kom
2449 <a href="http://people.skolelinux.org/pere/blog/images/2012-06-25-video-mpegla-nrk.pdf">i
2450 PDF-form som vedlegg på epost</a>.  Jeg er litt usikker på hvordan jeg
2451 best går videre for å bli klok, men jeg har jo i hvert fall tre uker
2452 på å vurdere om jeg skal klage.  Enten må nok forespørselen
2453 reformuleres eller så må jeg vel klage.  Synes jo det er merkelig at
2454 NRK ikke har bedre kontroll med hvilke avtaler de har inngått.  Det
2455 burde jo være noen i ledelsen som vet om de har signert en avtale med
2456 MPEG-LA eller ikke...</p>
2457
2458 <p>Oppdatering 2012-06-25 20:20: Et google-søk på "2011/371 nrk"
2459 sendte meg til postjournalen for
2460 <a href="http://nrk.no/contentfile/file/1.8212365!offentligjournal19062012.pdf">2012-06-19</a>
2461 og
2462 <a href="http://nrk.no/contentfile/file/1.8214156!offentligjournal20062012.pdf">2012-06-20</a>
2463 hos NRK som viser mine forespørsler og viser at sakens tittel hos NRK
2464 er "Graphic Systems Regions MA 2378/10E".  Videre søk etter "Graphic
2465 Systems Regions" viser at dette er saken til et anbud om
2466 "<a href="http://no.mercell.com/m/mts/Tender/27179412.aspx">a graphics
2467 system for 12 or 13 sites broadcasting regional news</a>" hos Mercell
2468 Sourcing Service, også omtalt på
2469 <a href="http://www.publictenders.net/tender/595705">Public
2470 Tenders</a> og
2471 <a href="http://www.doffin.no/search/show/search_view.aspx?ID=JAN155521">Doffin</a>.
2472 Jeg er dog usikker på hvordan dette er relatert til min
2473 forespørsel.</p>
2474
2475 <p>Oppdatering 2012-06-25 22:40: Ble tipset av Kieran Kunhya, fra
2476 miljøet rundt
2477 <a href="http://code.google.com/p/open-broadcast-encoder/">Open
2478 Broadcast Encoder</a>, at listen over de som har lisensavtale med
2479 MPEG-LA er
2480 <a href="http://www.mpeg-la.com/main/programs/AVC/Pages/Licensees.aspx">tilgjengelig
2481 på web</a>.  Veldig fint å oppdage hvor den finnes, da jeg må ha lett
2482 etter feil ting da jeg forsøke å finne den.  Der står ikke NRK, men
2483 flere andre "Broadcasting Company"-oppføringer.  Lurer på om det betyr
2484 at NRK ikke trenger avtale, eller noe helt annet?</p>
2485
2486       </div>
2487       <div class="tags">
2488
2489
2490         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
2491
2492
2493       </div>
2494     </div>
2495     <div class="padding"></div>
2496
2497     <div class="entry">
2498       <div class="title">
2499         <a href="https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html">Song book for Computer Scientists</a>
2500       </div>
2501       <div class="date">
2502         24th June 2012
2503       </div>
2504       <div class="body">
2505         <p>Many years ago, while studying Computer Science at the
2506 <a href="http://www.uit.no/">University of Tromsø</a>, I started
2507 collecting computer related songs for use at parties.  The original
2508 version was written in LaTeX, but a few years ago I got help from
2509 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
2510 while keeping the ability to create a nice book in PDF format.  I have
2511 not had time to maintain the book for a while now, and guess I should
2512 put it up on some public version control repository where others can
2513 help me extend and update the book.  If anyone is volunteering to help
2514 me with this, send me an email.  Also let me know if there are songs
2515 missing in my book.</p>
2516
2517 <p>I have not mentioned the book on my blog so far, and it occured to
2518 me today that I really should let all my readers share the joys of
2519 singing out load about programming, computers and computer networks.
2520 Especially now that <a href="http://debconf12.debconf.org/">Debconf
2521 12</a> is about to start (and I am not going).  Want to sing?  Check
2522 out <a href="http://www.hungry.com/~pere/cs-songbook/">Petter's
2523 Computer Science Songbook</a>.
2524
2525       </div>
2526       <div class="tags">
2527
2528
2529         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>.
2530
2531
2532       </div>
2533     </div>
2534     <div class="padding"></div>
2535
2536     <div class="entry">
2537       <div class="title">
2538         <a href="https://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>
2539       </div>
2540       <div class="date">
2541         21st June 2012
2542       </div>
2543       <div class="body">
2544         <p>Trengs det avtale med MPEG-LA for å ha lovlig rett til å
2545 distribuere og kringkaste video i MPEG4 eller med videokodingen H.264?
2546 <a href="http://webmink.com/essays/h-264/">H.264 og MPEG4 er jo ikke en
2547 fri og åpen standard</a> i henhold til
2548 <a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">definisjonen
2549 til Digistan</a>, så i enkelte land er det ingen tvil om at du må ha
2550 en slik avtale, men jeg må innrømme at jeg ikke vet om det også
2551 gjelder Norge.  Det ser uansett ut til å være en juridisk interessant
2552 problemstilling.  Men jeg tenkte her om dagen som så, at hvis det er
2553 nødvendig, så har store aktører som
2554 <a href="http://www.nrk.no/">NRK</a> og
2555 <a href="http://www.regjeringen.no/">regjeringen</a> skaffet seg en
2556 slik avtale.  Jeg har derfor sendt forespørsel til begge (for
2557 regjeringen sin del er det Departementenes Servicesenter som gjør
2558 jobben), og bedt om kopi av eventuelle avtaler de har om bruk av MPEG
2559 og/eller H.264 med MPEG-LA eller andre aktører som opererer på vegne
2560 av MPEG-LA.  Her er kopi av eposten jeg har sendt til
2561 <a href="http://www.dss.dep.no/">Departementenes Servicesenter</a>.
2562 Forespørselen til NRK er veldig lik.</p>
2563
2564 <p><blockquote>
2565
2566 <p>Date: Tue, 19 Jun 2012 15:18:33 +0200
2567 <br>From: Petter Reinholdtsen
2568 <br>To: postmottak@dss.dep.no
2569 <br>Subject: Innsynsbegjæring om MPEG/H.264-relaterte avtaler
2570
2571 <p>Hei.  Jeg ber herved om innsyn og kopi av dokumenter i DSS relatert
2572 til avtaler rundt bruk av videoformatene MPEG og H.264.  Jeg er
2573 spesielt interessert i å vite om DSS har lisensavtale med MPEG-LA
2574 eller noen som representerer MPEG-LA i Norge.</p>
2575
2576 <p>MPEG og H.264 er videoformater som brukes både til kringkasting
2577 (f.eks. i bakkenett og kabel-TV) og videopublisering på web, deriblant
2578 via Adobe Flash.  MPEG-LA, &lt;URL:
2579 <a href="http://www.mpeg-la.com/">http://www.mpeg-la.com/</a> &gt;, er
2580 en organisasjon som har fått oppgaven, av de kjente rettighetshavere
2581 av immaterielle rettigheter knyttet til MPEG og H.264, å selge
2582 bruksrett for MPEG og H.264.</p>
2583
2584 <p>Via regjeringen.no kringkastes med MPEG og H.264-baserte
2585 videoformater, og dette ser ut til å være organisert av DSS.  Jeg
2586 antar dermed at DSS har avtale med en eller annen aktør om dette.</p>
2587
2588 <p>F.eks. har Adobe Premiere Pro har følgende klausul i følge &lt;URL:
2589 <a href="http://news.cnet.com/8301-30685_3-20000101-264.html">http://news.cnet.com/8301-30685_3-20000101-264.html</a>
2590 &gt;:</p>
2591
2592 <p><blockquote>
2593
2594   <p>6.17. AVC DISTRIBUTION. The following notice applies to software
2595   containing AVC import and export functionality: THIS PRODUCT IS
2596   LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND
2597   NON-COMMERCIAL USE OF A CONSUMER TO (a) ENCODE VIDEO IN COMPLIANCE
2598   WITH THE AVC STANDARD ("AVC VIDEO") AND/OR (b) DECODE AVC VIDEO THAT
2599   WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL
2600   ACTIVITY AND/OR AVC VIDEO THAT WAS OBTAINED FROM A VIDEO PROVIDER
2601   LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
2602   IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED
2603   FROM MPEG LA L.L.C. SEE
2604   <a href="http://www.mpegla.com">http://www.mpegla.com</a>.</p>
2605
2606 </blockquote></p>
2607
2608 <p>Her er det kun "non-commercial" og "personal and non-commercial"
2609 aktivitet som er tillatt uten ekstra avtale med MPEG-LA.</p>
2610
2611 <p>Et annet tilsvarende eksempel er Apple Final Cut Pro, som har
2612 følgende klausul i følge &lt;URL:
2613 <a href="http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf">http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf</a>
2614 &gt;:</p>
2615
2616 <p><blockquote>
2617
2618   <p>15. Merknad om H.264/AVC. Hvis Apple-programvaren inneholder
2619   funksjonalitet for AVC-koding og/eller AVC-dekoding, krever
2620   kommersiell bruk ekstra lisensiering og følgende gjelder:
2621   AVC-FUNKSJONALITETEN I DETTE PRODUKTET KAN KUN ANVENDES AV
2622   FORBRUKERE OG KUN FOR PERSONLIG OG IKKE- KOMMERSIELL BRUK TIL (i)
2623   KODING AV VIDEO I OVERENSSTEMMELSE MED AVC-STANDARDEN ("AVC-VIDEO")
2624   OG/ELLER (ii) DEKODING AV AVC-VIDEO SOM ER KODET AV EN FORBRUKER TIL
2625   PERSONLIG OG IKKE-KOMMERSIELL BRUK OG/ELLER DEKODING AV AVC-VIDEO
2626   FRA EN VIDEOLEVERANDØR SOM HAR LISENS TIL Å TILBY
2627   AVC-VIDEO. INFORMASJON OM ANNEN BRUK OG LISENSIERING KAN INNHENTES
2628   FRA MPEG LA L.L.C. SE HTTP://WWW.MPEGLA.COM.</p>
2629 </blockquote></p>
2630
2631 <p>Tilsvarende gjelder for andre programvarepakker, kamera, etc som
2632 bruker MPEG og H.264, at en må ha en avtale med MPEG-LA for å ha lov
2633 til å bruke programmet/utstyret hvis en skal lage noe annet enn
2634 private filmer og i ikke-kommersiell virksomhet.</p>
2635
2636 <p>Jeg er altså interessert i kopi av avtaler DSS har som gjør at en
2637 ikke er begrenset av de generelle bruksvilkårene som gjelder for
2638 utstyr som bruker MPEG og/eller H.264.</p>
2639 </blockquote></p>
2640
2641 <p>Nå venter jeg spent på svaret.  Jeg planlegger å blogge om svaret
2642 her.</p>
2643
2644       </div>
2645       <div class="tags">
2646
2647
2648         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
2649
2650
2651       </div>
2652     </div>
2653     <div class="padding"></div>
2654
2655     <div class="entry">
2656       <div class="title">
2657         <a href="https://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>
2658       </div>
2659       <div class="date">
2660         26th April 2012
2661       </div>
2662       <div class="body">
2663         <p>In <a href="http://www.idg.no/computerworld/article243690.ece">an
2664 article today</a> published by Computerworld Norway, the photographer
2665 <a href="http://www.urke.com/eirik/">Eirik Helland Urke</a> reports
2666 that the video editor application included with
2667 <a href="http://www.htc.com/www/smartphones/htc-one-x/#specs">HTC One
2668 X</a> have some quite surprising terms of use.  The article is mostly
2669 based on the twitter message from mister Urke, stating:
2670
2671 <p><blockquote>
2672 "<a href="http://twitter.com/urke/status/194062269724897280">Drøy
2673 brukeravtale: HTC kan bruke MINE redigerte videoer kommersielt. Selv
2674 kan jeg KUN bruke dem privat.</a>"
2675 </blockquote></p>
2676
2677 <p>I quickly translated it to this English message:</p>
2678
2679 <p><blockquote>
2680 "Arrogant user agreement: HTC can use MY edited videos
2681 commercially.  Although I can ONLY use them privately."
2682 </blockquote></p>
2683
2684 <p>I've been unable to find the text of the license term myself, but
2685 suspect it is a variation of the MPEG-LA terms I
2686 <a href="http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">discovered
2687 with my Canon IXUS 130</a>.  The HTC One X specification specifies that
2688 the recording format of the phone is .amr for audio and .mp3 for
2689 video.  AMR is
2690 <a href="http://en.wikipedia.org/wiki/Adaptive_Multi-Rate_audio_codec#Licensing_and_patent_issues">Adaptive
2691 Multi-Rate audio codec</a> with patents which according to the
2692 Wikipedia article require an license agreement with
2693 <a href="http://www.voiceage.com/">VoiceAge</a>.  MP4 is
2694 <a href="http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Patent_licensing">MPEG4 with
2695 H.264</a>, which according to Wikipedia require a licence agreement
2696 with <a href="http://www.mpegla.com/">MPEG-LA</a>.</p>
2697
2698 <p>I know why I prefer
2699 <a href="http://www.digistan.org/open-standard:definition">free and open
2700 standards</a> also for video.</p>
2701
2702       </div>
2703       <div class="tags">
2704
2705
2706         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
2707
2708
2709       </div>
2710     </div>
2711     <div class="padding"></div>
2712
2713     <div class="entry">
2714       <div class="title">
2715         <a href="https://people.skolelinux.org/pere/blog/RAND_terms___non_reasonable_and_discriminatory.html">RAND terms - non-reasonable and discriminatory</a>
2716       </div>
2717       <div class="date">
2718         19th April 2012
2719       </div>
2720       <div class="body">
2721         <p>Here in Norway, the
2722 <a href="http://www.regjeringen.no/nb/dep/fad.html?id=339"> Ministry of
2723 Government Administration, Reform and Church Affairs</a> is behind
2724 a <a href="http://standard.difi.no/forvaltningsstandarder">directory of
2725 standards</a> that are recommended or mandatory for use by the
2726 government.  When the directory was created, the people behind it made
2727 an effort to ensure that everyone would be able to implement the
2728 standards and compete on equal terms to supply software and solutions
2729 to the government.  Free software and non-free software could compete
2730 on the same level.</p>
2731
2732 <p>But recently, some standards with RAND
2733 (<a href="http://en.wikipedia.org/wiki/Reasonable_and_non-discriminatory_licensing">Reasonable
2734 And Non-Discriminatory</a>) terms have made their way into the
2735 directory.  And while this might not sound too bad, the fact is that
2736 standard specifications with RAND terms often block free software from
2737 implementing them.  The reasonable part of RAND mean that the cost per
2738 user/unit is low,and the non-discriminatory part mean that everyone
2739 willing to pay will get a license.  Both sound great in theory.  In
2740 practice, to get such license one need to be able to count users, and
2741 be able to pay a small amount of money per unit or user.  By
2742 definition, users of free software do not need to register their use.
2743 So counting users or units is not possible for free software projects.
2744 And given that people will use the software without handing any money
2745 to the author, it is not really economically possible for a free
2746 software author to pay a small amount of money to license the rights
2747 to implement a standard when the income available is zero.  The result
2748 in these situations is that free software are locked out from
2749 implementing standards with RAND terms.</p>
2750
2751 <p>Because of this, when I see someone claiming the terms of a
2752 standard is reasonable and non-discriminatory, all I can think of is
2753 how this really is non-reasonable and discriminatory.  Because free
2754 software developers are working in a global market, it does not really
2755 help to know that software patents are not supposed to be enforceable
2756 in Norway.  The patent regimes in other countries affect us even here.
2757 I really hope the people behind the standard directory will pay more
2758 attention to these issues in the future.</p>
2759
2760 <p>You can find more on the issues with RAND, FRAND and RAND-Z terms
2761 from Simon Phipps
2762 (<a href="http://blogs.computerworlduk.com/simon-says/2010/11/rand-not-so-reasonable/">RAND:
2763 Not So Reasonable?</a>).</p>
2764
2765 <p>Update 2012-04-21: Just came across a
2766 <a href="http://blogs.computerworlduk.com/open-enterprise/2012/04/of-microsoft-netscape-patents-and-open-standards/index.htm">blog
2767 post from Glyn Moody</a> over at Computer World UK warning about the
2768 same issue, and urging people to speak out to the UK government.  I
2769 can only urge Norwegian users to do the same for
2770 <a href="http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder">the
2771 hearing taking place at the moment</a> (respond before 2012-04-27).
2772 It proposes to require video conferencing standards including
2773 specifications with RAND terms.</p>
2774
2775       </div>
2776       <div class="tags">
2777
2778
2779         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
2780
2781
2782       </div>
2783     </div>
2784     <div class="padding"></div>
2785
2786     <div class="entry">
2787       <div class="title">
2788         <a href="https://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html">Hvordan enkelt laste ned filmer fra NRK</a>
2789       </div>
2790       <div class="date">
2791          5th November 2011
2792       </div>
2793       <div class="body">
2794         <p>Ofte har jeg lyst til å laste ned et innslag fra NRKs nettsted for
2795 å se det senere når jeg ikke er på nett, eller for å ha det
2796 tilgjengelig når jeg en gang i fremtiden ønsker å referere til
2797 innslaget selv om NRK har fjernet det fra sine nettsider.  I dag fant
2798 jeg et lite script som fikser jobben.</p>
2799
2800 <p>Scriptet er laget av Jan Henning Thorsen og tilgjengelig fra
2801 <a href="http://jhthorsen.github.com/snippets/nrk-downloader/">github</a>,
2802 og gjør det veldig enkelt å laste ned.  Kjør <tt>nrk-downloader.sh
2803 http://www1.nrk.no/nett-tv/klipp/582810</tt> for å hente ned et enkelt
2804 innslag eller <tt>nrk-downloader.sh
2805 http://www1.nrk.no/nett-tv/kategori/3521</tt> for å laste ned alle
2806 episodene i en serie.</p>
2807
2808 <p>Det er ikke rakettforskning å laste ned NRK-"strømmer", og
2809 tidligere gjorde jeg dette manuelt med mplayer.  Scriptet til
2810 Hr. Thorsen gjør det raskere og enklere for meg, men jeg vil ikke si
2811 at det er en revolusjonerende løsning.  Jeg mener jo fortsatt at
2812 påstanden fra NRKs ansatte om at det er
2813 <a href="http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html">vesensforskjellig
2814 å legge tilgjengelig for nedlasting og for streaming</a> er
2815 meningsløs.</p>
2816
2817       </div>
2818       <div class="tags">
2819
2820
2821         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
2822
2823
2824       </div>
2825     </div>
2826     <div class="padding"></div>
2827
2828     <div class="entry">
2829       <div class="title">
2830         <a href="https://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>
2831       </div>
2832       <div class="date">
2833         29th July 2011
2834       </div>
2835       <div class="body">
2836         <p>While at Debconf11, I have several times during discussions
2837 mentioned the issues I believe should be improved in Debian for its
2838 desktop to be useful for more people.  The use case for this is my
2839 parents, which are currently running Kubuntu which solve the
2840 issues.</p>
2841
2842 <p>I suspect these four missing features are not very hard to
2843 implement.  After all, they are present in Ubuntu, so if we wanted to
2844 do this in Debian we would have a source.</p>
2845
2846 <ol>
2847
2848 <li><strong>Simple GUI based upgrade of packages.</strong> When there
2849 are new packages available for upgrades, a icon in the KDE status bar
2850 indicate this, and clicking on it will activate the simple upgrade
2851 tool to handle it.  I have no problem guiding both of my parents
2852 through the process over the phone.  If a kernel reboot is required,
2853 this too is indicated by the status bars and the upgrade tool.  Last
2854 time I checked, nothing with the same features was working in KDE in
2855 Debian.</li>
2856
2857 <li><strong>Simple handling of missing Firefox browser
2858 plugins.</strong> When the browser encounter a MIME type it do not
2859 currently have a handler for, it will ask the user if the system
2860 should search for a package that would add support for this MIME type,
2861 and if the user say yes, the APT sources will be searched for packages
2862 advertising the MIME type in their control file (visible in the
2863 Packages file in the APT archive).  If one or more packages are found,
2864 it is a simple click of the mouse to add support for the missing mime
2865 type.  If the package require the user to accept some non-free
2866 license, this is explained to the user.  The entire process make it
2867 more clear to the user why something do not work in the browser, and
2868 make the chances higher for the user to blame the web page authors and
2869 not the browser for any missing features.</li>
2870
2871 <li><strong>Simple handling of missing multimedia codec/format
2872 handlers.</strong> When the media players encounter a format or codec
2873 it is not supporting, a dialog pop up asking the user if the system
2874 should search for a package that would add support for it.  This
2875 happen with things like MP3, Windows Media or H.264.  The selection
2876 and installation procedure is very similar to the Firefox browser
2877 plugin handling.  This is as far as I know implemented using a
2878 gstreamer hook.  The end result is that the user easily get access to
2879 the codecs that are present from the APT archives available, while
2880 explaining more on why a given format is unsupported by Ubuntu.</li>
2881
2882 <li><strong>Better browser handling of some MIME types.</strong> When
2883 displaying a text/plain file in my Debian browser, it will propose to
2884 start emacs to show it.  If I remember correctly, when doing the same
2885 in Kunbutu it show the file as a text file in the browser.  At least I
2886 know Opera will show text files within the browser.  I much prefer the
2887 latter behaviour.</li>
2888
2889 </ol>
2890
2891 <p>There are other nice features as well, like the simplified suite
2892 upgrader, but given that I am the one mostly doing the dist-upgrade,
2893 it do not matter much.</p>
2894
2895 <p>I really hope we could get these features in place for the next
2896 Debian release.  It would require the coordinated effort of several
2897 maintainers, but would make the end user experience a lot better.</p>
2898
2899       </div>
2900       <div class="tags">
2901
2902
2903         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
2904
2905
2906       </div>
2907     </div>
2908     <div class="padding"></div>
2909
2910     <div class="entry">
2911       <div class="title">
2912         <a href="https://people.skolelinux.org/pere/blog/Gnash_enteres_Google_Summer_of_Code_2011.html">Gnash enteres Google Summer of Code 2011</a>
2913       </div>
2914       <div class="date">
2915          6th April 2011
2916       </div>
2917       <div class="body">
2918         <p><a href="http://www.getgnash.org/">The Gnash project</a> is still
2919 the most promising solution for a Free Software Flash implementation.
2920 A few days ago the project
2921 <a href="http://lists.gnu.org/archive/html/gnash-dev/2011-04/msg00011.html">announced</a>
2922 that it will participate in Google Summer of Code.  I hope many
2923 students apply, and that some of them succeed in getting AVM2 support
2924 into Gnash.</p>
2925
2926       </div>
2927       <div class="tags">
2928
2929
2930         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
2931
2932
2933       </div>
2934     </div>
2935     <div class="padding"></div>
2936
2937     <div class="entry">
2938       <div class="title">
2939         <a href="https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html">Why isn't Debian Edu using VLC?</a>
2940       </div>
2941       <div class="date">
2942         27th November 2010
2943       </div>
2944       <div class="body">
2945         <p>In the latest issue of Linux Journal, the readers choices were
2946 presented, and the winner among the multimedia player were VLC.
2947 Personally, I like VLC, and it is my player of choice when I first try
2948 to play a video file or stream.  Only if VLC fail will I drag out
2949 gmplayer to see if it can do better.  The reason is mostly the failure
2950 model and trust.  When VLC fail, it normally pop up a error message
2951 reporting the problem.  When mplayer fail, it normally segfault or
2952 just hangs.  The latter failure mode drain my trust in the program.<p>
2953
2954 <p>But even if VLC is my player of choice, we have choosen to use
2955 mplayer in <a href="http://www.skolelinux.org/">Debian
2956 Edu/Skolelinux</a>.  The reason is simple.  We need a good browser
2957 plugin to play web videos seamlessly, and the VLC browser plugin is
2958 not very good.  For example, it lack in-line control buttons, so there
2959 is no way for the user to pause the video.  Also, when I
2960 <a href="http://wiki.debian.org/DebianEdu/BrowserMultimedia">last
2961 tested the browser plugins</a> available in Debian, the VLC plugin
2962 failed on several video pages where mplayer based plugins worked.  If
2963 the browser plugin for VLC was as good as the gecko-mediaplayer
2964 package (which uses mplayer), we would switch.</P>
2965
2966 <p>While VLC is a good player, its user interface is slightly
2967 annoying.  The most annoying feature is its inconsistent use of
2968 keyboard shortcuts.  When the player is in full screen mode, its
2969 shortcuts are different from when it is playing the video in a window.
2970 For example, space only work as pause when in full screen mode.  I
2971 wish it had consisten shortcuts and that space also would work when in
2972 window mode.  Another nice shortcut in gmplayer is [enter] to restart
2973 the current video.  It is very nice when playing short videos from the
2974 web and want to restart it when new people arrive to have a look at
2975 what is going on.</p>
2976
2977       </div>
2978       <div class="tags">
2979
2980
2981         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
2982
2983
2984       </div>
2985     </div>
2986     <div class="padding"></div>
2987
2988     <div class="entry">
2989       <div class="title">
2990         <a href="https://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html">Best å ikke fortelle noen at streaming er nedlasting...</a>
2991       </div>
2992       <div class="date">
2993         30th October 2010
2994       </div>
2995       <div class="body">
2996         <p>I dag la jeg inn en kommentar på en sak hos NRKBeta
2997 <a href="http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/">om
2998 hvordan TV-serien Blindpassasjer ble laget</a> i forbindelse med at
2999 filmene NRK la ut ikke var tilgjengelig i et
3000 <a href="http://www.digistan.org/open-standard:definition">fritt og
3001 åpent format</a>.  Dette var det jeg skrev publiserte der 07:39.</p>
3002
3003 <p><blockquote>
3004 <p>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
3005 nedlasting.  Mange av oss som kan mer enn gjennomsnittet om systemer
3006 som dette, vet at det stort sett er mulig å lure ut ting med den
3007 nødvendige forkunnskapen."</p>
3008
3009 <p>Haha.  Å streame innhold er det samme som å laste ned innhold, så å
3010 beskytte en stream mot nedlasting er ikke mulig.  Å skrive noe slikt
3011 er å forlede leseren.</p>
3012
3013 <p>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
3014 vil tillate streaming men ikke nedlasting meningsløs.</p>
3015
3016 <p>Anbefaler forresten å lese
3017 <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>
3018 om hva som ville være konsekvensen hvis digitale avspillingssperrer
3019 (DRM) fungerte.  Det gjør de naturligvis ikke teknisk - det er jo
3020 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
3021 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
3022 opp under.</p>
3023 </blockquote></p>
3024
3025 <p>Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
3026 NRKBeta:</p>
3027
3028 <p><blockquote>
3029 <p>From: Anders Hofseth &lt;XXX@gmail.com>
3030 <br>To: "pere@hungry.com" &lt;pere@hungry.com>
3031 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>, Jon Ståle Carlsen &lt;XXX@gmail.com>, Henrik Lied &lt;XXX@gmail.com>
3032 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
3033 <br>Date: Sat, 30 Oct 2010 07:58:44 +0200</p>
3034
3035 <p>Hei Petter.
3036 <br>Det du forsøker dra igang er egentlig en interessant diskusjon,
3037 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
3038 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
3039 særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
3040
3041 <p>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
3042 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
3043 konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
3044
3045 <p>Med hilsen,
3046 <br>-anders</p>
3047
3048 <p>Ring meg om noe er uklart: 95XXXXXXX</p>
3049 </blockquote></p>
3050
3051 <p>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
3052 over følgende svar.  I og med at debatten er fjernet fra NRK Betas
3053 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
3054 Har fjernet epostadresser og telefonnummer til de involverte, for å
3055 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.</p>
3056
3057 <p><blockquote>
3058 <p>From: Petter Reinholdtsen &lt;pere@hungry.com>
3059 <br>To: Anders Hofseth &lt;XXX@gmail.com>
3060 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>,
3061 <br>        Jon Ståle Carlsen &lt;XXX@gmail.com>,
3062 <br>        Henrik Lied &lt;XXX@gmail.com>
3063 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
3064 <br>Date: Sat, 30 Oct 2010 08:24:34 +0200</p>
3065
3066 <p>[Anders Hofseth]
3067 <br>> Hei Petter.</p>
3068
3069 <p>Hei.</p>
3070
3071 <p>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
3072 <br>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
3073 <br>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
3074 <br>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
3075
3076 <p>Godt å se at du er enig i at dette er en interessant diskusjon.  Den
3077 vil nok fortsette en stund til.  :)</p>
3078
3079 <p>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
3080 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
3081 fortsette å legge ut arkivmateriale.</p>
3082
3083 <p>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
3084 faktum, som er at streaming er det samme som nedlasting, og at innhold
3085 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
3086 det.</p>
3087
3088 <p>Det du sier er jo at klarering av arkivmateriale for publisering på
3089 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
3090 Det er ikke et argument som holder vann. :)</p>
3091
3092 <p>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
3093 <br>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
3094 <br>> konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
3095
3096 <p>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
3097 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
3098 mot de som vil låse kulturen inne.  Jeg synes det er en skam at NRK
3099 godtar å forlede publikum.  Ville heller at NRK krever at innhold som
3100 skal sendes skal være uten bruksbegresninger og kan publiseres i
3101 formater som heller ikke har bruksbegresninger (bruksbegresningene til
3102 H.264 burde få varselbjellene i NRK til å ringe).</p>
3103
3104 <p>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
3105 påstander om at "streaming beskytter mot nedlasting" som bare er egnet
3106 til å bygge opp om en myte som er skadelig for samfunnet som helhet.</p>
3107
3108 <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
3109 titt på
3110 &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> >.
3111 for å se hva slags bruksbegresninger H.264 innebærer.</p>
3112
3113 <p>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
3114 kan brukes før rettighetshaverene også innser at de er med på å skade
3115 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
3116 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
3117 langt på overtid.</p>
3118
3119 <p>> Ring meg om noe er uklart: XXX</p>
3120
3121 <p>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
3122 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
3123 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
3124 for videre diskusjon hadde dere i mine øyne kommet fra det med
3125 ryggraden på plass.</p>
3126
3127 <p>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.</p>
3128
3129 <p>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
3130 &lt;URL: <a href="http://www.archive.org/details/CopyingIsNotTheft">http://www.archive.org/details/CopyingIsNotTheft</a> > og
3131 &lt;URL: <a href="http://patentabsurdity.com/">http://patentabsurdity.com/</a> > hadde vært noe å kringkaste på
3132 NRK1. :)</p>
3133
3134 <p>Vennlig hilsen,
3135 <br>--
3136 <br>Petter Reinholdtsen</p>
3137
3138       </div>
3139       <div class="tags">
3140
3141
3142         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
3143
3144
3145       </div>
3146     </div>
3147     <div class="padding"></div>
3148
3149     <div class="entry">
3150       <div class="title">
3151         <a href="https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html">Software updates 2010-10-24</a>
3152       </div>
3153       <div class="date">
3154         24th October 2010
3155       </div>
3156       <div class="body">
3157         <p>Some updates.</p>
3158
3159 <p>My <a href="http://pledgebank.com/gnash-avm2">gnash pledge</a> to
3160 raise money for the project is going well.  The lower limit of 10
3161 signers was reached in 24 hours, and so far 13 people have signed it.
3162 More signers and more funding is most welcome, and I am really curious
3163 how far we can get before the time limit of December 24 is reached.
3164 :)</p>
3165
3166 <p>On the #gnash IRC channel on irc.freenode.net, I was just tipped
3167 about what appear to be a great code coverage tool capable of
3168 generating code coverage stats without any changes to the source code.
3169 It is called
3170 <a href="http://simonkagstrom.github.com/kcov/index.html">kcov</a>,
3171 and can be used using <tt>kcov &lt;directory&gt; &lt;binary&gt;</tt>.
3172 It is missing in Debian, but the git source built just fine in Squeeze
3173 after I installed libelf-dev, libdwarf-dev, pkg-config and
3174 libglib2.0-dev.  Failed to build in Lenny, but suspect that is
3175 solvable.  I hope kcov make it into Debian soon.</p>
3176
3177 <p>Finally found time to wrap up the release notes for <a
3178 href="http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html">a
3179 new alpha release of Debian Edu</a>, and just published the second
3180 alpha test release of the Squeeze based Debian Edu /
3181 <a href="http://www.skolelinux.org/">Skolelinux</a>
3182 release.  Give it a try if you need a complete linux solution for your
3183 school, including central infrastructure server, workstations, thin
3184 client servers and diskless workstations.  A nice touch added
3185 yesterday is RDP support on the thin client servers, for windows
3186 clients to get a Linux desktop on request.</p>
3187
3188       </div>
3189       <div class="tags">
3190
3191
3192         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>.
3193
3194
3195       </div>
3196     </div>
3197     <div class="padding"></div>
3198
3199     <div class="entry">
3200       <div class="title">
3201         <a href="https://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>
3202       </div>
3203       <div class="date">
3204         19th October 2010
3205       </div>
3206       <div class="body">
3207         <p><a href="http://www.getgnash.org/">The Gnash project</a> is the
3208 most promising solution for a Free Software Flash implementation. It
3209 has done great so far, but there is still far to go, and recently its
3210 funding has dried up.  I believe AVM2 support in Gnash is vital to the
3211 continued progress of the project, as more and more sites show up with
3212 AVM2 flash files.</p>
3213
3214 <p>To try to get funding for developing such support, I have started
3215 <a href="http://www.pledgebank.com/gnash-avm2">a pledge</a> with the
3216 following text:</P>
3217
3218 <p><blockquote>
3219
3220   <p>"I will pay 100$ to the Gnash project to develop AVM2 support but
3221   only if 10 other people will do the same."</p>
3222
3223   <p>- Petter Reinholdtsen, free software developer</p>
3224
3225   <p>Deadline to sign up by: 24th December 2010</p>
3226
3227   <p>The Gnash project need to get support for the new Flash file
3228   format AVM2 to work with a lot of sites using Flash on the
3229   web. Gnash already work with a lot of Flash sites using the old AVM1
3230   format, but more and more sites are using the AVM2 format these
3231   days. The project web page is available from
3232   http://www.getgnash.org/ . Gnash is a free software implementation
3233   of Adobe Flash, allowing those of us that do not accept the terms of
3234   the Adobe Flash license to get access to Flash sites.</p>
3235
3236   <p>The project need funding to get developers to put aside enough
3237   time to develop the AVM2 support, and this pledge is my way to try
3238   to get this to happen.</p>
3239
3240   <p>The project accept donations via the OpenMediaNow foundation,
3241   <a href="http://www.openmedianow.org/?q=node/32">http://www.openmedianow.org/?q=node/32</a> .</p>
3242
3243 </blockquote></p>
3244
3245 <p>I hope you will support this effort too.  I hope more than 10
3246 people will participate to make this happen.  The more money the
3247 project gets, the more features it can develop using these funds.
3248 :)</p>
3249
3250       </div>
3251       <div class="tags">
3252
3253
3254         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
3255
3256
3257       </div>
3258     </div>
3259     <div class="padding"></div>
3260
3261     <div class="entry">
3262       <div class="title">
3263         <a href="https://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>
3264       </div>
3265       <div class="date">
3266          9th September 2010
3267       </div>
3268       <div class="body">
3269         <p>A few days ago I had the mixed pleasure of bying a new digital
3270 camera, a Canon IXUS 130.  It was instructive and very disturbing to
3271 be able to verify that also this camera producer have the nerve to
3272 specify how I can or can not use the videos produced with the camera.
3273 Even thought I was aware of the issue, the options with new cameras
3274 are limited and I ended up bying the camera anyway.  What is the
3275 problem, you might ask?  It is software patents, MPEG-4, H.264 and the
3276 MPEG-LA that is the problem, and our right to record our experiences
3277 without asking for permissions that is at risk.
3278
3279 <p>On page 27 of the Danish instruction manual, this section is
3280 written:</p>
3281
3282 <blockquote>
3283 <p>This product is licensed under AT&T patents for the MPEG-4 standard
3284 and may be used for encoding MPEG-4 compliant video and/or decoding
3285 MPEG-4 compliant video that was encoded only (1) for a personal and
3286 non-commercial purpose or (2) by a video provider licensed under the
3287 AT&T patents to provide MPEG-4 compliant video.</p>
3288
3289 <p>No license is granted or implied for any other use for MPEG-4
3290 standard.</p>
3291 </blockquote>
3292
3293 <p>In short, the camera producer have chosen to use technology
3294 (MPEG-4/H.264) that is only provided if I used it for personal and
3295 non-commercial purposes, or ask for permission from the organisations
3296 holding the knowledge monopoly (patent) for technology used.</p>
3297
3298 <p>This issue has been brewing for a while, and I recommend you to
3299 read
3300 "<a href="http://www.osnews.com/story/23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA">Why
3301 Our Civilization's Video Art and Culture is Threatened by the
3302 MPEG-LA</a>" by Eugenia Loli-Queru and
3303 "<a href="http://webmink.com/2010/09/03/h-264-and-foss/">H.264 Is Not
3304 The Sort Of Free That Matters</a>" by Simon Phipps to learn more about
3305 the issue.  The solution is to support the
3306 <a href="http://www.digistan.org/open-standard:definition">free and
3307 open standards</a> for video, like <a href="http://www.theora.org/">Ogg
3308 Theora</a>, and avoid MPEG-4 and H.264 if you can.</p>
3309
3310       </div>
3311       <div class="tags">
3312
3313
3314         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/fildeling">fildeling</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
3315
3316
3317       </div>
3318     </div>
3319     <div class="padding"></div>
3320
3321     <div class="entry">
3322       <div class="title">
3323         <a href="https://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>
3324       </div>
3325       <div class="date">
3326          4th September 2010
3327       </div>
3328       <div class="body">
3329         <p>In the <a href="http://popcon.debian.org/unknown/by_vote">Debian
3330 popularity-contest numbers</a>, the adobe-flashplugin package the
3331 second most popular used package that is missing in Debian.  The sixth
3332 most popular is flashplayer-mozilla.  This is a clear indication that
3333 working flash is important for Debian users.  Around 10 percent of the
3334 users submitting data to popcon.debian.org have this package
3335 installed.</p>
3336
3337 <p>In the report written by Lars Risan in August 2008
3338 («<a href="http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile&do=view&target=Skolelinux_i_bruk_rapport_1.0.pdf">Skolelinux
3339 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
3340 stiftelsen SLX Debian Labs</a>»), one of the most important problems
3341 schools experienced with <a href="http://www.skolelinux.org/">Debian
3342 Edu/Skolelinux</a> was the lack of working Flash.  A lot of educational
3343 web sites require Flash to work, and lacking working Flash support in
3344 the web browser and the problems with installing it was perceived as a
3345 good reason to stay with Windows.</p>
3346
3347 <p>I once saw a funny and sad comment in a web forum, where Linux was
3348 said to be the retarded cousin that did not really understand
3349 everything you told him but could work fairly well.  This was a
3350 comment regarding the problems Linux have with proprietary formats and
3351 non-standard web pages, and is sad because it exposes a fairly common
3352 understanding of whose fault it is if web pages that only work in for
3353 example Internet Explorer 6 fail to work on Firefox, and funny because
3354 it explain very well how annoying it is for users when Linux
3355 distributions do not work with the documents they receive or the web
3356 pages they want to visit.</p>
3357
3358 <p>This is part of the reason why I believe it is important for Debian
3359 and Debian Edu to have a well working Flash implementation in the
3360 distribution, to get at least popular sites as Youtube and Google
3361 Video to working out of the box.  For Squeeze, Debian have the chance
3362 to include the latest version of Gnash that will make this happen, as
3363 the new release 0.8.8 was published a few weeks ago and is resting in
3364 unstable.  The new version work with more sites that version 0.8.7.
3365 The Gnash maintainers have asked for a freeze exception, but the
3366 release team have not had time to reply to it yet.  I hope they agree
3367 with me that Flash is important for the Debian desktop users, and thus
3368 accept the new package into Squeeze.</p>
3369
3370       </div>
3371       <div class="tags">
3372
3373
3374         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
3375
3376
3377       </div>
3378     </div>
3379     <div class="padding"></div>
3380
3381     <div class="entry">
3382       <div class="title">
3383         <a href="https://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>
3384       </div>
3385       <div class="date">
3386          9th July 2009
3387       </div>
3388       <div class="body">
3389         <p>For å forstå mer om hvorfor standardkatalogens versjon 2 ble som
3390 den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
3391 for regjeringen da de tok sin avgjørelse.  De er nå lagt ut på NUUGs
3392 wiki, direkte tilgjengelig via "<a
3393 href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon.pdf">Referansekatalogen
3394 v2.0 - Oppsummering av høring</a>" og "<a
3395 href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon-katalogutkast.pdf">Referansekatalog
3396 for IT-standarder i offentlig sektor Versjon 2.0, dd.mm.åååå -
3397 UTKAST</a>".</p>
3398
3399 <p>Det er tre ting jeg merker meg i oppsummeringen fra
3400 høringsuttalelsen da jeg skummet igjennom den.  Det første er at
3401 forståelsen av hvordan programvarepatenter påvirker fri
3402 programvareutvikling også i Norge når en argumenterer med at
3403 royalty-betaling ikke er et relevant problem i Norge.  Det andre er at
3404 FAD ikke har en prinsipiell forståelse av verdien av en enkelt
3405 standard innenfor hvert område.  Det siste er at påstander i
3406 høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
3407 Microsoft om hvordan Ogg blir standardisert og påstanden fra
3408 politidirektoratet om patentproblemer i Theora).</p>
3409
3410       </div>
3411       <div class="tags">
3412
3413
3414         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
3415
3416
3417       </div>
3418     </div>
3419     <div class="padding"></div>
3420
3421     <div class="entry">
3422       <div class="title">
3423         <a href="https://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>
3424       </div>
3425       <div class="date">
3426          6th July 2009
3427       </div>
3428       <div class="body">
3429         <p>Jeg ble glad da regjeringen
3430 <a href="http://www.digi.no/817635/her-er-statens-nye-it-standarder">annonserte</a>
3431 versjon 2 av
3432 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf">statens
3433 referansekatalog over standarder</a>, men trist da jeg leste hva som
3434 faktisk var vedtatt etter
3435 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html">høringen</a>.
3436 De fleste av de valgte åpne standardene er gode og vil bidra til at
3437 alle kan delta på like vilkår i å lage løsninger for staten, men
3438 noen av dem blokkerer for de som ikke har anledning til å benytte
3439 spesifikasjoner som krever betaling for bruk (såkalt
3440 royalty-betaling).  Det gjelder spesifikt for H.264 for video og MP3
3441 for lyd.  Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
3442 Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
3443 fra statens websider gjøre dette uten å måtte bruke programmer der
3444 betaling for bruk var nødvendig.  Når det nå er gjort valgfritt for
3445 de statlige etatene å bruke enten H.264 eller Theora (og MP3 eler
3446 Vorbis), så vil en bli tvunget til å forholde seg til
3447 royalty-belastede standarder for å få tilgang til videoen og
3448 lyden.</p>
3449
3450 <p>Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
3451 at alle standarder som ble valgt til å være påkrevd i katalogen skulle
3452 være uten royalty-betaling.  Jeg håper det ikke betyr at en har mistet
3453 all forståelse for hvilke prinsipper som må følges for å oppnå
3454 likeverdig konkurranse mellom aktørene i IT-bransjen.  NUUG advarte
3455 mot dette i
3456 <a href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2">sin
3457 høringsuttalelse</a>, men ser ut til å ha blitt ignorert.</p>
3458
3459 <p>Oppdatering 2012-06-29: Kom over <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf">en
3460 rapport til FAD</a> fra da versjon 1 av katalogen ble vedtatt, og der
3461 er det tydelig at problemstillingen var kjent og forstått.</p>
3462
3463       </div>
3464       <div class="tags">
3465
3466
3467         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
3468
3469
3470       </div>
3471     </div>
3472     <div class="padding"></div>
3473
3474     <div class="entry">
3475       <div class="title">
3476         <a href="https://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html">Microsofts misvisende argumentasjon rundt multimediaformater</a>
3477       </div>
3478       <div class="date">
3479         26th June 2009
3480       </div>
3481       <div class="body">
3482         <p>I
3483 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf">Microsoft
3484 sin høringsuttalelse</a> til
3485 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html?id=549422">forslag
3486 til versjon 2 av statens referansekatalog over standarder</a>, lirer
3487 de av seg følgende FUD-perle:</p>
3488
3489 <p><blockquote>"Vorbis, OGG, Theora og FLAC er alle tekniske
3490   spesifikasjoner overordnet styrt av xiph.org, som er en
3491   ikke-kommersiell organisasjon.  Etablerte og anerkjente
3492   standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
3493   innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
3494   Det er derimot helt opp til hver enkelt organisasjon å bestemme
3495   hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
3496   spesifikasjonene bør derfor ikke defineres som åpne
3497   standarder."</blockquote></p>
3498
3499 <p>De vokter seg vel for å nevne den anerkjente
3500 standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
3501 IP og det meste av protokoller på Internet, og RFC-standardene som
3502 IETF står bak.  Ogg er spesifisert i
3503 <a href="http://ietf.org/rfc/rfc3533.txt">RFC 3533</a>, og er uten
3504 tvil å anse som en åpen standard.  Vorbis er
3505 <a href="http://ietf.org/rfc/rfc5215.txt">RFC 5215</a>.  Theora er
3506
3507 under standardisering via IETF, med
3508 <a href="http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt">siste
3509 utkast publisert 2006-07-21</a> (riktignok er dermed teksten ikke
3510 skrevet i stein ennå, men det blir neppe endringer som ikke er
3511 bakoverkompatibel).  De kan være inne på noe når det gjelder FLAC da
3512 jeg ikke finner tegn til at <a
3513 href="http://flac.sourceforge.net/format.html">spesifikasjonen
3514 tilgjengelig på web</a> er på tur via noen
3515 standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
3516 og Vorbis også har involvert seg i Flac siden 2003, så ser jeg ikke
3517 bort fra at også den organiseres via IETF.  Jeg kjenner personlig lite
3518 til FLAC.</p>
3519
3520 <p>Uredelig argumentasjon bør en holde seg for god til å komme med,
3521 spesielt når det er så enkelt i dagens Internet-hverdag å gå
3522 misvisende påstander etter i sømmene.</p>
3523
3524       </div>
3525       <div class="tags">
3526
3527
3528         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
3529
3530
3531       </div>
3532     </div>
3533     <div class="padding"></div>
3534
3535     <div class="entry">
3536       <div class="title">
3537         <a href="https://people.skolelinux.org/pere/blog/When_web_browser_developers_make_a_video_player___.html">When web browser developers make a video player...</a>
3538       </div>
3539       <div class="date">
3540         17th January 2009
3541       </div>
3542       <div class="body">
3543         <p>As part of the work we do in <a href="http://www.nuug.no">NUUG</a>
3544 to publish video recordings of our monthly presentations, we provide a
3545 page with embedded video for easy access to the recording.  Putting a
3546 good set of HTML tags together to get working embedded video in all
3547 browsers and across all operating systems is not easy.  I hope this
3548 will become easier when the &lt;video&gt; tag is implemented in all
3549 browsers, but I am not sure.  We provide the recordings in several
3550 formats, MPEG1, Ogg Theora, H.264 and Quicktime, and want the
3551 browser/media plugin to pick one it support and use it to play the
3552 recording, using whatever embed mechanism the browser understand.
3553 There is at least four different tags to use for this, the new HTML5
3554 &lt;video&gt; tag, the &lt;object&gt; tag, the &lt;embed&gt; tag and
3555 the &lt;applet&gt; tag.  All of these take a lot of options, and
3556 finding the best options is a major challenge.</p>
3557
3558 <p>I just tested the experimental Opera browser available from <a
3559 href="http://labs.opera.com">labs.opera.com</a>, to see how it handled
3560 a &lt;video&gt; tag with a few video sources and no extra attributes.
3561 I was not very impressed.  The browser start by fetching a picture
3562 from the video stream.  Not sure if it is the first frame, but it is
3563 definitely very early in the recording.  So far, so good. Next,
3564 instead of streaming the 76 MiB video file, it start to download all
3565 of it, but do not start to play the video.  This mean I have to wait
3566 for several minutes for the downloading to finish.  When the download
3567 is done, the playing of the video do not start!  Waiting for the
3568 download, but I do not get to see the video?  Some testing later, I
3569 discover that I have to add the controls="true" attribute to be able
3570 to get a play button to pres to start the video.  Adding
3571 autoplay="true" did not help.  I sure hope this is a misfeature of the
3572 test version of Opera, and that future implementations of the
3573 &lt;video&gt; tag will stream recordings by default, or at least start
3574 playing when the download is done.</p>
3575
3576 <p>The test page I used (since changed to add more attributes) is
3577 <a href="http://www.nuug.no/aktiviteter/20090113-foredrag-om-foredrag/">available
3578 from the nuug site</a>.  Will have to test it with the new Firefox
3579 too.</p>
3580
3581 <p>In the test process, I discovered a missing feature.  I was unable
3582 to find a way to get the URL of the playing video out of Opera, so I
3583 am not quite sure it picked the Ogg Theora version of the video.  I
3584 sure hope it was using the announced Ogg Theora support. :)</p>
3585
3586       </div>
3587       <div class="tags">
3588
3589
3590         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
3591
3592
3593       </div>
3594     </div>
3595     <div class="padding"></div>
3596
3597     <div class="entry">
3598       <div class="title">
3599         <a href="https://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>
3600       </div>
3601       <div class="date">
3602         25th November 2008
3603       </div>
3604       <div class="body">
3605         <p>Recently I have spent some time evaluating the multimedia browser
3606 plugins available in Debian Lenny, to see which one we should use by
3607 default in Debian Edu.  We need an embedded video playing plugin with
3608 control buttons to pause or stop the video, and capable of streaming
3609 all the multimedia content available on the web.  The test results and
3610 notes are available on
3611 <a href="http://wiki.debian.org/DebianEdu/BrowserMultimedia">the
3612 Debian wiki</a>.  I was surprised how few of the plugins are able to
3613 fill this need.  My personal video player favorite, VLC, has a really
3614 bad plugin which fail on a lot of the test pages.  A lot of the MIME
3615 types I would expect to work with any free software player (like
3616 video/ogg), just do not work.  And simple formats like the
3617 audio/x-mplegurl format (m3u playlists), just isn't supported by the
3618 totem and vlc plugins.  I hope the situation will improve soon.  No
3619 wonder sites use the proprietary Adobe flash to play video.</p>
3620
3621 <p>For Lenny, we seem to end up with the mplayer plugin.  It seem to
3622 be the only one fitting our needs. :/</p>
3623
3624       </div>
3625       <div class="tags">
3626
3627
3628         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
3629
3630
3631       </div>
3632     </div>
3633     <div class="padding"></div>
3634
3635     <p style="text-align: right;"><a href="multimedia.rss"><img src="https://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
3636     <div id="sidebar">
3637
3638
3639
3640 <h2>Archive</h2>
3641 <ul>
3642
3643 <li>2023
3644 <ul>
3645
3646 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/01/">January (3)</a></li>
3647
3648 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/02/">February (1)</a></li>
3649
3650 </ul></li>
3651
3652 <li>2022
3653 <ul>
3654
3655 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/02/">February (1)</a></li>
3656
3657 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/03/">March (3)</a></li>
3658
3659 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/04/">April (2)</a></li>
3660
3661 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/06/">June (2)</a></li>
3662
3663 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/07/">July (1)</a></li>
3664
3665 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/09/">September (1)</a></li>
3666
3667 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/10/">October (1)</a></li>
3668
3669 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/12/">December (1)</a></li>
3670
3671 </ul></li>
3672
3673 <li>2021
3674 <ul>
3675
3676 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/01/">January (2)</a></li>
3677
3678 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/02/">February (1)</a></li>
3679
3680 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/05/">May (1)</a></li>
3681
3682 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/06/">June (1)</a></li>
3683
3684 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/07/">July (3)</a></li>
3685
3686 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/08/">August (1)</a></li>
3687
3688 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/09/">September (1)</a></li>
3689
3690 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/10/">October (1)</a></li>
3691
3692 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/12/">December (1)</a></li>
3693
3694 </ul></li>
3695
3696 <li>2020
3697 <ul>
3698
3699 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/02/">February (2)</a></li>
3700
3701 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/03/">March (2)</a></li>
3702
3703 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/04/">April (2)</a></li>
3704
3705 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/05/">May (3)</a></li>
3706
3707 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/06/">June (2)</a></li>
3708
3709 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/07/">July (1)</a></li>
3710
3711 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/09/">September (1)</a></li>
3712
3713 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/10/">October (1)</a></li>
3714
3715 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/11/">November (1)</a></li>
3716
3717 </ul></li>
3718
3719 <li>2019
3720 <ul>
3721
3722 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/01/">January (4)</a></li>
3723
3724 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/02/">February (3)</a></li>
3725
3726 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/03/">March (3)</a></li>
3727
3728 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/05/">May (2)</a></li>
3729
3730 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/06/">June (5)</a></li>
3731
3732 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/07/">July (2)</a></li>
3733
3734 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/08/">August (1)</a></li>
3735
3736 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/09/">September (1)</a></li>
3737
3738 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/11/">November (1)</a></li>
3739
3740 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/12/">December (4)</a></li>
3741
3742 </ul></li>
3743
3744 <li>2018
3745 <ul>
3746
3747 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/01/">January (1)</a></li>
3748
3749 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/02/">February (5)</a></li>
3750
3751 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/03/">March (5)</a></li>
3752
3753 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/04/">April (3)</a></li>
3754
3755 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/06/">June (2)</a></li>
3756
3757 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/07/">July (5)</a></li>
3758
3759 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/08/">August (3)</a></li>
3760
3761 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/09/">September (3)</a></li>
3762
3763 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/10/">October (5)</a></li>
3764
3765 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/11/">November (2)</a></li>
3766
3767 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/12/">December (4)</a></li>
3768
3769 </ul></li>
3770
3771 <li>2017
3772 <ul>
3773
3774 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
3775
3776 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
3777
3778 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
3779
3780 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/04/">April (2)</a></li>
3781
3782 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/06/">June (5)</a></li>
3783
3784 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/07/">July (1)</a></li>
3785
3786 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/08/">August (1)</a></li>
3787
3788 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/09/">September (3)</a></li>
3789
3790 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/10/">October (5)</a></li>
3791
3792 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/11/">November (3)</a></li>
3793
3794 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/12/">December (4)</a></li>
3795
3796 </ul></li>
3797
3798 <li>2016
3799 <ul>
3800
3801 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
3802
3803 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
3804
3805 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
3806
3807 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
3808
3809 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
3810
3811 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
3812
3813 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
3814
3815 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
3816
3817 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
3818
3819 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
3820
3821 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
3822
3823 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
3824
3825 </ul></li>
3826
3827 <li>2015
3828 <ul>
3829
3830 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
3831
3832 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
3833
3834 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
3835
3836 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
3837
3838 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
3839
3840 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
3841
3842 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
3843
3844 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
3845
3846 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
3847
3848 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
3849
3850 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
3851
3852 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
3853
3854 </ul></li>
3855
3856 <li>2014
3857 <ul>
3858
3859 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
3860
3861 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
3862
3863 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
3864
3865 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
3866
3867 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
3868
3869 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
3870
3871 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
3872
3873 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
3874
3875 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
3876
3877 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
3878
3879 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
3880
3881 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
3882
3883 </ul></li>
3884
3885 <li>2013
3886 <ul>
3887
3888 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
3889
3890 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
3891
3892 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
3893
3894 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
3895
3896 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
3897
3898 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
3899
3900 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
3901
3902 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
3903
3904 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
3905
3906 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
3907
3908 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
3909
3910 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
3911
3912 </ul></li>
3913
3914 <li>2012
3915 <ul>
3916
3917 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
3918
3919 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
3920
3921 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
3922
3923 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
3924
3925 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
3926
3927 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
3928
3929 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
3930
3931 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
3932
3933 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
3934
3935 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
3936
3937 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
3938
3939 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
3940
3941 </ul></li>
3942
3943 <li>2011
3944 <ul>
3945
3946 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
3947
3948 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
3949
3950 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
3951
3952 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
3953
3954 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
3955
3956 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
3957
3958 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
3959
3960 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
3961
3962 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
3963
3964 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
3965
3966 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
3967
3968 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
3969
3970 </ul></li>
3971
3972 <li>2010
3973 <ul>
3974
3975 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
3976
3977 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
3978
3979 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
3980
3981 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
3982
3983 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
3984
3985 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
3986
3987 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
3988
3989 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
3990
3991 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
3992
3993 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
3994
3995 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
3996
3997 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
3998
3999 </ul></li>
4000
4001 <li>2009
4002 <ul>
4003
4004 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
4005
4006 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
4007
4008 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
4009
4010 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
4011
4012 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
4013
4014 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
4015
4016 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
4017
4018 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
4019
4020 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
4021
4022 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
4023
4024 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
4025
4026 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
4027
4028 </ul></li>
4029
4030 <li>2008
4031 <ul>
4032
4033 <li><a href="https://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
4034
4035 <li><a href="https://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
4036
4037 </ul></li>
4038
4039 </ul>
4040
4041
4042
4043 <h2>Tags</h2>
4044 <ul>
4045
4046  <li><a href="https://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (19)</a></li>
4047
4048  <li><a href="https://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
4049
4050  <li><a href="https://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
4051
4052  <li><a href="https://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
4053
4054  <li><a href="https://people.skolelinux.org/pere/blog/tags/betalkontant">betalkontant (9)</a></li>
4055
4056  <li><a href="https://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (12)</a></li>
4057
4058  <li><a href="https://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (17)</a></li>
4059
4060  <li><a href="https://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
4061
4062  <li><a href="https://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
4063
4064  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian">debian (188)</a></li>
4065
4066  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (159)</a></li>
4067
4068  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (9)</a></li>
4069
4070  <li><a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan (11)</a></li>
4071
4072  <li><a href="https://people.skolelinux.org/pere/blog/tags/dld">dld (18)</a></li>
4073
4074  <li><a href="https://people.skolelinux.org/pere/blog/tags/docbook">docbook (30)</a></li>
4075
4076  <li><a href="https://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
4077
4078  <li><a href="https://people.skolelinux.org/pere/blog/tags/english">english (444)</a></li>
4079
4080  <li><a href="https://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
4081
4082  <li><a href="https://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (14)</a></li>
4083
4084  <li><a href="https://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (34)</a></li>
4085
4086  <li><a href="https://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
4087
4088  <li><a href="https://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (20)</a></li>
4089
4090  <li><a href="https://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
4091
4092  <li><a href="https://people.skolelinux.org/pere/blog/tags/intervju">intervju (43)</a></li>
4093
4094  <li><a href="https://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (16)</a></li>
4095
4096  <li><a href="https://people.skolelinux.org/pere/blog/tags/kart">kart (23)</a></li>
4097
4098  <li><a href="https://people.skolelinux.org/pere/blog/tags/kodi">kodi (4)</a></li>
4099
4100  <li><a href="https://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
4101
4102  <li><a href="https://people.skolelinux.org/pere/blog/tags/lego">lego (5)</a></li>
4103
4104  <li><a href="https://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
4105
4106  <li><a href="https://people.skolelinux.org/pere/blog/tags/linuxcnc">linuxcnc (4)</a></li>
4107
4108  <li><a href="https://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
4109
4110  <li><a href="https://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
4111
4112  <li><a href="https://people.skolelinux.org/pere/blog/tags/madewithcc">madewithcc (3)</a></li>
4113
4114  <li><a href="https://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
4115
4116  <li><a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (44)</a></li>
4117
4118  <li><a href="https://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (13)</a></li>
4119
4120  <li><a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5 (23)</a></li>
4121
4122  <li><a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk (320)</a></li>
4123
4124  <li><a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug (198)</a></li>
4125
4126  <li><a href="https://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (40)</a></li>
4127
4128  <li><a href="https://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
4129
4130  <li><a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (75)</a></li>
4131
4132  <li><a href="https://people.skolelinux.org/pere/blog/tags/personvern">personvern (114)</a></li>
4133
4134  <li><a href="https://people.skolelinux.org/pere/blog/tags/raid">raid (2)</a></li>
4135
4136  <li><a href="https://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
4137
4138  <li><a href="https://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
4139
4140  <li><a href="https://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
4141
4142  <li><a href="https://people.skolelinux.org/pere/blog/tags/robot">robot (17)</a></li>
4143
4144  <li><a href="https://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
4145
4146  <li><a href="https://people.skolelinux.org/pere/blog/tags/ruter">ruter (7)</a></li>
4147
4148  <li><a href="https://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
4149
4150  <li><a href="https://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (59)</a></li>
4151
4152  <li><a href="https://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
4153
4154  <li><a href="https://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
4155
4156  <li><a href="https://people.skolelinux.org/pere/blog/tags/standard">standard (74)</a></li>
4157
4158  <li><a href="https://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (7)</a></li>
4159
4160  <li><a href="https://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (14)</a></li>
4161
4162  <li><a href="https://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (64)</a></li>
4163
4164  <li><a href="https://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (5)</a></li>
4165
4166  <li><a href="https://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
4167
4168  <li><a href="https://people.skolelinux.org/pere/blog/tags/valg">valg (9)</a></li>
4169
4170  <li><a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri (20)</a></li>
4171
4172  <li><a href="https://people.skolelinux.org/pere/blog/tags/video">video (77)</a></li>
4173
4174  <li><a href="https://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
4175
4176  <li><a href="https://people.skolelinux.org/pere/blog/tags/web">web (42)</a></li>
4177
4178 </ul>
4179
4180
4181     </div>
4182     <p style="text-align: right">
4183  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
4184 </p>
4185
4186   </body>
4187 </html>