blog/tags/multimedia/index.html

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