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