blog/tags/multimedia/index.html

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