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