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">
5 <meta http-equiv=
"Content-Type" content=
"text/html;charset=utf-8" />
6 <title>Petter Reinholdtsen: Entries Tagged multimedia
</title>
7 <link rel=
"stylesheet" type=
"text/css" media=
"screen" href=
"http://people.skolelinux.org/pere/blog/style.css" />
8 <link rel=
"stylesheet" type=
"text/css" media=
"screen" href=
"http://people.skolelinux.org/pere/blog/vim.css" />
9 <link rel=
"alternate" title=
"RSS Feed" href=
"multimedia.rss" type=
"application/rss+xml" />
14 <a href=
"http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen
</a>
21 <h3>Entries tagged "multimedia".
</h3>
25 <a href=
"http://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>
31 <p>I use the
<a href=
"https://sourceforge.net/p/lsdvd/">lsdvd tool
</a>
32 to handle my fairly large DVD collection. It is a nice command line
33 tool to get details about a DVD, like title, tracks, track length,
34 etc, in XML, perl or human readable format. But lsdvd have not seen
35 any new development since
2006 and had a few irritating bugs affecting
36 its use with some DVDs. Upstream seemed to be dead, and in January I
37 sent a small probe asking for a version control repository for the
38 project, without any reply. But I use it regularly and would like to
39 get
<a href=
"https://packages.qa.debian.org/lsdvd">an updated version
40 into Debian
</a>. So two weeks ago I tried harder to get in touch with
41 the project admin, and after getting a reply from him explaining that
42 he was no longer interested in the project, I asked if I could take
43 over. And yesterday, I became project admin.
</p>
45 <p>I've been in touch with a Gentoo developer and the Debian
46 maintainer interested in joining forces to maintain the upstream
47 project, and I hope we can get a new release out fairly quickly,
48 collecting the patches spread around on the internet into on place.
49 I've added the relevant Debian patches to the freshly created git
50 repository, and expect the Gentoo patches to make it too. If you got
51 a DVD collection and care about command line tools, check out
52 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/">the git source
</a> and join
53 <a href=
"https://sourceforge.net/p/lsdvd/mailman/">the project mailing
60 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>.
65 <div class=
"padding"></div>
69 <a href=
"http://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>
75 <p>Two years later, I am still not sure if it is legal here in Norway
76 to use or publish a video in H
.264 or MPEG4 format edited by the
77 commercially licensed video editors, without limiting the use to
78 create "personal" or "non-commercial" videos or get a license
79 agreement with
<a href=
"http://www.mpegla.com">MPEG LA
</a>. If one
80 want to publish and broadcast video in a non-personal or commercial
81 setting, it might be that those tools can not be used, or that video
82 format can not be used, without breaking their copyright license. I
84 <a href=
"http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">Back
85 then
</a>, I found that the copyright license terms for Adobe Premiere
86 and Apple Final Cut Pro both specified that one could not use the
87 program to produce anything else without a patent license from MPEG
88 LA. The issue is not limited to those two products, though. Other
89 much used products like those from Avid and Sorenson Media have terms
90 of use are similar to those from Adobe and Apple. The complicating
91 factor making me unsure if those terms have effect in Norway or not is
92 that the patents in question are not valid in Norway, but copyright
95 <p>These are the terms for Avid Artist Suite, according to their
96 <a href=
"http://www.avid.com/US/about-avid/legal-notices/legal-enduserlicense2">published
98 <a href=
"http://www.avid.com/static/resources/common/documents/corporate/LICENSE.pdf">license
99 text
</a> (converted to lower case text for easier reading):
</p>
102 <p>18.2. MPEG-
4. MPEG-
4 technology may be included with the
103 software. MPEG LA, L.L.C. requires this notice:
</p>
105 <p>This product is licensed under the MPEG-
4 visual patent portfolio
106 license for the personal and non-commercial use of a consumer for (i)
107 encoding video in compliance with the MPEG-
4 visual standard (“MPEG-
4
108 video”) and/or (ii) decoding MPEG-
4 video that was encoded by a
109 consumer engaged in a personal and non-commercial activity and/or was
110 obtained from a video provider licensed by MPEG LA to provide MPEG-
4
111 video. No license is granted or shall be implied for any other
112 use. Additional information including that relating to promotional,
113 internal and commercial uses and licensing may be obtained from MPEG
114 LA, LLC. See http://www.mpegla.com. This product is licensed under
115 the MPEG-
4 systems patent portfolio license for encoding in compliance
116 with the MPEG-
4 systems standard, except that an additional license
117 and payment of royalties are necessary for encoding in connection with
118 (i) data stored or replicated in physical media which is paid for on a
119 title by title basis and/or (ii) data which is paid for on a title by
120 title basis and is transmitted to an end user for permanent storage
121 and/or use, such additional license may be obtained from MPEG LA,
122 LLC. See http://www.mpegla.com for additional details.
</p>
124 <p>18.3. H
.264/AVC. H
.264/AVC technology may be included with the
125 software. MPEG LA, L.L.C. requires this notice:
</p>
127 <p>This product is licensed under the AVC patent portfolio license for
128 the personal use of a consumer or other uses in which it does not
129 receive remuneration to (i) encode video in compliance with the AVC
130 standard (“AVC video”) and/or (ii) decode AVC video that was encoded
131 by a consumer engaged in a personal activity and/or was obtained from
132 a video provider licensed to provide AVC video. No license is granted
133 or shall be implied for any other use. Additional information may be
134 obtained from MPEG LA, L.L.C. See http://www.mpegla.com.
</p>
137 <p>Note the requirement that the videos created can only be used for
138 personal or non-commercial purposes.
</p>
140 <p>The Sorenson Media software have
141 <a href=
"http://www.sorensonmedia.com/terms/">similar terms
</a>:
</p>
145 <p>With respect to a license from Sorenson pertaining to MPEG-
4 Video
146 Decoders and/or Encoders: Any such product is licensed under the
147 MPEG-
4 visual patent portfolio license for the personal and
148 non-commercial use of a consumer for (i) encoding video in compliance
149 with the MPEG-
4 visual standard (“MPEG-
4 video”) and/or (ii) decoding
150 MPEG-
4 video that was encoded by a consumer engaged in a personal and
151 non-commercial activity and/or was obtained from a video provider
152 licensed by MPEG LA to provide MPEG-
4 video. No license is granted or
153 shall be implied for any other use. Additional information including
154 that relating to promotional, internal and commercial uses and
155 licensing may be obtained from MPEG LA, LLC. See
156 http://www.mpegla.com.
</p>
158 <p>With respect to a license from Sorenson pertaining to MPEG-
4
159 Consumer Recorded Data Encoder, MPEG-
4 Systems Internet Data Encoder,
160 MPEG-
4 Mobile Data Encoder, and/or MPEG-
4 Unique Use Encoder: Any such
161 product is licensed under the MPEG-
4 systems patent portfolio license
162 for encoding in compliance with the MPEG-
4 systems standard, except
163 that an additional license and payment of royalties are necessary for
164 encoding in connection with (i) data stored or replicated in physical
165 media which is paid for on a title by title basis and/or (ii) data
166 which is paid for on a title by title basis and is transmitted to an
167 end user for permanent storage and/or use. Such additional license may
168 be obtained from MPEG LA, LLC. See http://www.mpegla.com for
169 additional details.
</p>
173 <p>Some free software like
174 <a href=
"https://handbrake.fr/">Handbrake
</A> and
175 <a href=
"http://ffmpeg.org/">FFMPEG
</a> uses GPL/LGPL licenses and do
176 not have any such terms included, so for those, there is no
177 requirement to limit the use to personal and non-commercial.
</p>
183 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
188 <div class=
"padding"></div>
192 <a href=
"http://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>
198 <p>Jeg har fortsatt behov for å kunne laste ned innslag fra NRKs
199 nettsted av og til for å se senere når jeg ikke er på nett, men
200 <a href=
"http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html">min
201 oppskrift fra
2011</a> sluttet å fungere da NRK byttet
202 avspillermetode. I dag fikk jeg endelig lett etter oppdatert løsning,
203 og jeg er veldig glad for å fortelle at den enkleste måten å laste ned
204 innslag er å bruke siste versjon
2014.06.07 av
205 <a href=
"http://rg3.github.io/youtube-dl/">youtube-dl
</a>. Støtten i
206 youtube-dl
<a href=
"https://github.com/rg3/youtube-dl/issues/2980">kom
207 inn for
23 dager siden
</a> og
208 <a href=
"http://packages.qa.debian.org/y/youtube-dl.html">versjonen i
209 Debian
</a> fungerer fint også som backport til Debian Wheezy. Det er
210 et lite problem, det håndterer kun URLer med små bokstaver, men hvis
211 en har en URL med store bokstaver kan en bare gjøre alle store om til
212 små bokstaver for å få youtube-dl til å laste ned. Rapporterte
214 <a href=
"https://github.com/rg3/youtube-dl/issues/2980">problemet til
215 utviklerne
</a>, og antar de får fikset det snart.
</p>
217 <p>Dermed er alt klart til å laste ned dokumentarene om
218 <a href=
"http://tv.nrk.no/program/KOID23005014/usas-hemmelige-avlytting">USAs
219 hemmelige avlytting
</a> og
220 <a href=
"http://tv.nrk.no/program/KOID23005114/selskapene-bak-usas-avlytting">Selskapene
221 bak USAs avlytting
</a>, i tillegg til
222 <a href=
"http://tv.nrk.no/program/KOID20005814/et-moete-med-edward-snowden">intervjuet
223 med Edward Snowden gjort av den tyske tv-kanalen ARD
</a>. Anbefaler
224 alle å se disse, sammen med
225 <a href=
"http://media.ccc.de/browse/congress/2013/30C3_-_5713_-_en_-_saal_2_-_201312301130_-_to_protect_and_infect_part_2_-_jacob.html">foredraget
226 til Jacob Appelbaum på siste CCC-konferanse
</a>, for å forstå mer om
227 hvordan overvåkningen av borgerne brer om seg.
</p>
229 <p>Takk til gode venner på foreningen NUUGs IRC-kanal
230 <a href=
"irc://irc.freenode.net/%23nuug">#nuug på irc.freenode.net
</a>
231 for tipsene som fikk meg i mål
</a>.
</p>
233 <p><strong>Oppdatering
2014-
06-
17</strong>: Etter at jeg publiserte
234 denne, ble jeg tipset om bloggposten
235 "
<a href=
"http://ingvar.blog.redpill-linpro.com/2012/05/31/downloading-hd-content-from-tv-nrk-no/">Downloading
236 HD content from tv.nrk.no
</a>" av Ingvar Hagelund, som har alternativ
237 implementasjon og tips for å lage mkv-fil med undertekstene inkludert.
238 Kanskje den passer bedre for deg? I tillegg ble feilen i youtube-dl
239 ble fikset litt senere ut på dagen i går, samt at youtube-dl fikk
240 støtte for å laste ned undertitler. Takk til Anders Einar Hilden for
241 god innsats og youtube-dl-utviklerne for rask respons.</p>
247 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia
">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk
">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video
">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web
">web</a>.
252 <div class="padding
"></div>
256 <a href="http://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>
262 <p>I've been following <a href="http://www.getgnash.org/
">the Gnash
263 project</a> for quite a while now. It is a free software
264 implementation of Adobe Flash, both a standalone player and a browser
265 plugin. Gnash implement support for the AVM1 format (and not the
266 newer AVM2 format - see
267 <a href="http://lightspark.github.io/
">Lightspark</a> for that one),
268 allowing several flash based sites to work. Thanks to the friendly
269 developers at Youtube, it also work with Youtube videos, because the
270 Javascript code at Youtube detect Gnash and serve a AVM1 player to
271 those users. :) Would be great if someone found time to implement AVM2
272 support, but it has not happened yet. If you install both Lightspark
273 and Gnash, Lightspark will invoke Gnash if it find a AVM1 flash file,
274 so you can get both handled as free software. Unfortunately,
275 Lightspark so far only implement a small subset of AVM2, and many
276 sites do not work yet.</p>
278 <p>A few months ago, I started looking at
279 <a href="http://scan.coverity.com/
">Coverity</a>, the static source
280 checker used to find heaps and heaps of bugs in free software (thanks
281 to the donation of a scanning service to free software projects by the
282 company developing this non-free code checker), and Gnash was one of
283 the projects I decided to check out. Coverity is able to find lock
284 errors, memory errors, dead code and more. A few days ago they even
285 extended it to also be able to find the heartbleed bug in OpenSSL.
286 There are heaps of checks being done on the instrumented code, and the
287 amount of bogus warnings is quite low compared to the other static
288 code checkers I have tested over the years.</p>
290 <p>Since a few weeks ago, I've been working with the other Gnash
291 developers squashing bugs discovered by Coverity. I was quite happy
292 today when I checked the current status and saw that of the 777 issues
293 detected so far, 374 are marked as fixed. This make me confident that
294 the next Gnash release will be more stable and more dependable than
295 the previous one. Most of the reported issues were and are in the
296 test suite, but it also found a few in the rest of the code.</p>
298 <p>If you want to help out, you find us on
299 <a href="https://lists.gnu.org/mailman/listinfo/gnash-dev
">the
300 gnash-dev mailing list</a> and on
301 <a href="irc://irc.freenode.net/#gnash
">the #gnash channel on
302 irc.freenode.net IRC server</a>.</p>
308 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english
">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia
">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video
">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web
">web</a>.
313 <div class="padding
"></div>
317 <a href="http://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>
323 <p>Keeping your DVD collection safe from scratches and curious
324 children fingers while still having it available when you want to see a
325 movie is not straight forward. My preferred method at the moment is
326 to store a full copy of the ISO on a hard drive, and use VLC, Popcorn
327 Hour or other useful players to view the resulting file. This way the
328 subtitles and bonus material are still available and using the ISO is
329 just like inserting the original DVD record in the DVD player.</p>
331 <p>Earlier I used dd for taking security copies, but it do not handle
332 DVDs giving read errors (which are quite a few of them). I've also
334 <a href="http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html
">dvdbackup
335 and genisoimage</a>, but these days I use the marvellous python library
337 <a href="http://bblank.thinkmo.de/blog/new-software-python-dvdvideo
">python-dvdvideo</a>
338 written by Bastian Blank. It is
339 <a href="http://packages.qa.debian.org/p/python-dvdvideo.html
">in Debian
340 already</a> and the binary package name is python3-dvdvideo. Instead
341 of trying to read every block from the DVD, it parses the file
342 structure and figure out which block on the DVD is actually in used,
343 and only read those blocks from the DVD. This work surprisingly well,
344 and I have been able to almost backup my entire DVD collection using
347 <p>So far, python-dvdvideo have failed on between 10 and
348 20 DVDs, which is a small fraction of my collection. The most common
350 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
720831">DVDs
351 using UTF-16 instead of UTF-8 characters</a>, which according to
352 Bastian is against the DVD specification (and seem to cause some
353 players to fail too). A rarer problem is what seem to be inconsistent
354 DVD structures, as the python library
355 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
723079">claim
356 there is a overlap between objects</a>. An equally rare problem claim
357 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
741878">some
358 value is out of range</a>. No idea what is going on there. I wish I
359 knew enough about the DVD format to fix these, to ensure my movie
360 collection will stay with me in the future.</p>
362 <p>So, if you need to keep your DVDs safe, back them up using
363 python-dvdvideo. :)</p>
369 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english
">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia
">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett
">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video
">video</a>.
374 <div class="padding
"></div>
378 <a href="http://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html
">IETF activity to standardise video codec</a>
385 <a href="http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html
">Opus
386 codec made</a> it into <a href="http://www.ietf.org/
">IETF</a> as
387 <a href="http://tools.ietf.org/html/rfc6716
">RFC 6716</a>, I had a look
388 to see if there is any activity in IETF to standardise a video codec
389 too, and I was happy to discover that there is some activity in this
390 area. A non-"working group" mailing list
391 <a href=
"https://www.ietf.org/mailman/listinfo/video-codec">video-codec
</a>
393 <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
394 formal working group should be formed.
</p>
396 <p>I look forward to see how this plays out. There is already
397 <a href=
"http://www.ietf.org/mail-archive/web/video-codec/current/msg00003.html">an
398 email from someone
</a> in the MPEG group at ISO asking people to
399 participate in the ISO group. Given how ISO failed with OOXML and given
400 that it so far (as far as I can remember) only have produced
401 multimedia formats requiring royalty payments, I suspect
402 joining the ISO group would be a complete waste of time, but I am not
403 involved in any codec work and my opinion will not matter much.
</p>
405 <p>If one of my readers is involved with codec work, I hope she will
406 join this work to standardise a royalty free video codec within
413 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>.
418 <div class=
"padding"></div>
422 <a href=
"http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html">IETF standardize its first multimedia codec: Opus
</a>
428 <p>Yesterday,
<a href=
"http://www.ietf.org/">IETF
</a> announced the
430 <a href=
"http://tools.ietf.org/html/rfc6716">RFC
6716, the Definition
431 of the Opus Audio Codec
</a>, a low latency, variable bandwidth, codec
432 intended for both VoIP, film and music. This is the first time, as
433 far as I know, that IETF have standardized a multimedia codec. In
434 <a href=
"http://tools.ietf.org/html/rfc3533">RFC
3533</a>, IETF
435 standardized the OGG container format, and it has proven to be a great
436 royalty free container for audio, video and movies. I hope IETF will
437 continue to standardize more royalty free codeces, after ISO and MPEG
438 have proven incapable of securing everyone equal rights to publish
439 multimedia content on the Internet.
</p>
441 <p>IETF require two interoperating independent implementations to
442 ratify a standard, and have so far ensured to only standardize royalty
443 free specifications. Both are key factors to allow everyone (rich and
444 poor), to compete on equal terms on the Internet.
</p>
446 <p>Visit the
<a href=
"http://opus-codec.org/">Opus project page
</a> if
447 you want to learn more about the solution.
</p>
453 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>.
458 <div class=
"padding"></div>
462 <a href=
"http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html">Git repository for song book for Computer Scientists
</a>
469 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html">mentioned
470 this summer
</a>, I have created a Computer Science song book a few
471 years ago, and today I finally found time to create a public
472 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook">Gitorious
473 repository for the project
</a>.
</p>
475 <p>If you want to help out, please clone the source and submit patches
476 to the HTML version. To generate the PDF and PostScript version,
477 please use prince XML, or let me know about a useful free software
478 processor capable of creating a good looking PDF from the HTML.
</p>
480 <p>Want to sing? You can still find the song book in HTML, PDF and
481 PostScript formats at
482 <a href=
"http://www.hungry.com/~pere/cs-songbook/">Petter's Computer
483 Science Songbook
</a>.
</p>
489 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>.
494 <div class=
"padding"></div>
498 <a href=
"http://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>
504 <p>I føljetongen om H
.264
505 <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
506 jeg leserne i undring
</a> om hvor pakken fra MPEG-LA tok veien, og om
507 hvilke selskaper i Norge som har avtale med MPEG-LA. Da Ryan hos
508 MPEG-LA dro på ferie sendte jeg min melding videre til hans kollega,
509 og dagen etter fikk jeg følgende svar derfra:
</p>
512 <p>Date: Fri,
29 Jun
2012 18:
32:
34 +
0000
513 <br>From: Sidney Wolf
<SWolf (at) mpegla.com
>
514 <br>To: Petter Reinholdtsen
<pere (at) hungry.com
>
515 <br>Cc: Ryan Rodriguez
<RRodriguez (at) mpegla.com
>
516 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?
</p>
518 <p>Dear Mr. Reinholdtsen,
</p>
520 <p>Thank you for your message. As you know, Ryan is currently our of the
521 office, so it will be my pleasure to assist you.
</p>
523 <p>Per your request, attached please find an electronic copy of the
524 AVC Patent Portfolio License. Please note that the electronic copy of
525 the License is provided as a convenience and for informational
526 purposes only. When concluding the Licenses, only the hard copies
527 provided by MPEG LA may be used.
</p>
529 <p>To your question, MPEG LA lists our Licensees on our website
530 according to each program. The lists are in alphabetical order, so it
531 is very easy to search.
</p>
533 <p>I hope that this was helpful. If we can be of additional
534 assistance, please let me know.
</p>
539 <br>Manager, Global Licensing
543 <p>Selv om et epostvedlegg er nyttig for mottakeren, så håpet jeg å få
544 et dokument jeg kunne dele med alle leserne av bloggen min, og ikke et
545 som må deles på individuell basis. Opphavsretten krever godkjenning
546 fra rettighetsinnehaver før en kan gjøre slikt, så dermed fulgte jeg
547 opp med et spørsmål om dette var greit.
</p>
550 <p>Date: Wed,
4 Jul
2012 20:
25:
06 +
0200
551 <br>From: Petter Reinholdtsen
<pere (at) hungry.com
>
552 <br>To: Sidney Wolf
<SWolf (at) mpegla.com
>
553 <br>Cc: Ryan Rodriguez
<RRodriguez (at) mpegla.com
>
554 <br>Subject: Re: Do NRK have a license agreement with MPEG-LA?
</p>
556 <p>Thank you for your reply.
</p>
559 <br>> Per your request, attached please find an electronic copy of the AVC
560 <br>> Patent Portfolio License. Please note that the electronic copy of
561 <br>> the License is provided as a convenience and for informational
562 <br>> purposes only. When concluding the Licenses, only the hard copies
563 <br>> provided by MPEG LA may be used.
</p>
565 <p>This is useful for me to learn, but the reason I asked for the
566 Internet address of the licensing document was to ensure I could
567 publish a link to it when I discuss the topic of H
.264 licensing here
568 in Norway, and allow others to verify my observations. I can not do
569 the same with an email attachment. Thus I would like to ask you if it
570 is OK with MPEG LA that I publish this document on the Internet for
573 <p>> To your question, MPEG LA lists our Licensees on our website
574 <br>> according to each program. The lists are in alphabetical order, so
575 <br>> it is very easy to search.
</p>
577 <p>I am afraid this do not help me locate Norwegian companies in the
578 list of Licensees. I do not know the name of all companies and
579 organisations in Norway, and thus do not know how to locate the
580 Norwegian ones on that list.
</p>
582 <p>> I hope that this was helpful. If we can be of additional assistance,
583 <br>> please let me know.
</p>
585 <p>Absoutely helpful to learn more about how MPEG LA handle licensing.
</p>
589 <br>Petter Reinholdtsen
</p>
592 <p>Jeg håpet også at det skulle være mulig å få vite hvilke av de
593 mange hundre som har avtale med MPEG-LA om bruk av H
.264 som holdt til
594 i Norge. Begge mine håp falt i grus med svaret fra MPEG-LA.
597 <p>Date: Thu,
5 Jul
2012 17:
42:
39 +
0000
598 <br>From: Sidney Wolf
<SWolf (at) mpegla.com
>
599 <br>To: 'Petter Reinholdtsen'
<pere (at) hungry.com
>
600 <br>Cc: Ryan Rodriguez
<RRodriguez (at) mpegla.com
>
601 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?
</p>
603 <p>Dear Mr. Reinholdtsen,
</p>
605 <p>Thank you for your reply.
</p>
607 <p>We appreciate the additional explanation you have provided and for
608 asking our permission to publish the electronic copy of the License in
609 advance of doing so. Typically, MPEG LA prefers to distribute the
610 electronic copies of our Licenses to interested parties. Therefore,
611 please feel free to send interested parties to the AVC portion of our
612 website, http://www.mpegla.com/main/programs/AVC/Pages/Intro.aspx for
613 their further reference.
</p>
615 <p>As previously mentioned, MPEG LA maintains a list of Licensees in good
616 standing on our website according to each program. Due to the large
617 volume of Licensees, it would be administratively impractical to
618 provide this level of detail to interested parties. Therefore, I am
619 afraid we are not in a position to assist you with your request.
</p>
624 <br>Manager, Global Licensing
628 <p>Men takket være epostvedlegget kunne jeg søke på Google etter
629 setningen "WHEREAS, a video standard commonly referred to as AVC has
630 been defined and is referred to in this Agreement as the “AVC
631 Standard” (as more fully defined herein below)" som finnes i avtalen,
632 og lokalisere en kopi fra
2007 av
633 <a href=
"http://www.sec.gov/Archives/edgar/data/1342960/000119312509050004/dex1024.htm">lisensavtalen
634 mellom MPEG-LA og DivX, Inc.
</a>, slik at mine lesere kan se hvordan
635 avtalen så ut da. Jeg har ikke sammenlignet tekstene for å se om noe
636 har endret seg siden den tid, men satser på at teksten er representativ.
</p>
638 <p>Jeg aner fortsatt ikke hvor FedEx tok veien med pakken fra
641 <p>Update
2012-
07-
06: Jeg er visst ikke den første som forsøker å få
642 klarhet i problemstillinger rundt H
.264, og kom nettopp over en veldig
643 interessant bloggpost fra
2010 hos LibreVideo med tittelen
644 "
<a href=
"http://www.librevideo.org/blog/2010/06/14/mpeg-la-answers-some-questions-about-avch-264-licensing/">MPEG-LA
645 answers some questions about AVC/H
.264 licensing
</a>. Anbefales!
</p>
651 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
656 <div class=
"padding"></div>
660 <a href=
"http://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>
666 <p>Da fikk jeg nettopp svar fra
667 <a href=
"http://www.dss.dep.no/">Departementenes servicesenter
</a>
669 <a href=
"http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">mitt
670 spørsmål om avtale rundt bruk av H
.264</a>. De har ingen avtale med
671 MPEG LA eller dets representanter. Her er svaret.
675 <p>Date: Fri,
29 Jun
2012 07:
04:
42 +
0000
676 <br>From: Nielsen Mette Haga
<Mette-Haga.Nielsen (at) dss.dep.no
>
677 <br>To: Petter Reinholdtsen
<petter.reinholdtsen (at) ...
>
678 <br>CC: Postmottak
<Postmottak (at) dss.dep.no
>
679 <br>Subject: SV: Innsynsbegjæring om MPEG/H
.264-relaterte avtaler
</p>
681 <p>DSS har ikke inngått noen egen lisensavtale med MPEG-LA eller noen som
682 representerer MPEG-LA i Norge. Videoløsningen på regjeringen.no er
683 levert av Smartcom:tv. Lisensforholdet rundt H
.264 er ikke omtalt i
684 vår avtale med Smartcom.
</p>
686 <p>Vennlig hilsen
</p>
688 <p>Mette Haga Nielsen
689 <br>Fung. seksjonssjef
</p>
691 <p>Departementenes servicesenter
</p>
693 <p>Informasjonsforvaltning
696 <br>E-post mette-haga.nielsen (at) dss.dep.no
</p>
699 <p>Hvis den norske regjeringen representert ved DSS ikke har slik
700 avtale, så kan en kanskje konkludere med at det ikke trengs? Jeg er
701 ikke trygg på at det er god juridisk grunn å stå på, men det er i det
702 minste interessant å vite at hverken NRK eller DSS har funnet det
703 nødvendig å ha avtale om bruk av H
.264.
</p>
705 <p>Det forklarer ikke hvordan de kan ignorere bruksvilkårene knyttet
706 til bruk av opphavsrettsbeskyttet materiale de bruker til
707 videoproduksjon, med mindre slike vilkår kan ignoreres av selskaper og
708 privatpersoner i Norge. Har de lov til å bryte vilkårene, eller har
709 de brutt dem og så langt sluppet unna med det? Jeg aner ikke.
</p>
715 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
720 <div class=
"padding"></div>
724 <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">MPEG-LA mener NRK må ha avtale med dem for å kringkaste og publisere H
.264-video
</a>
731 <a href=
"http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html">nektet
732 å spore opp eventuell avtale med MPEG-LA
</a> eller andre om bruk av
733 MPEG/H
.264-video etter at jeg
<a
734 href=
"http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">ba
735 om innsyn i slike avtaler
</a>, tenkte jeg at i stedet for å forsøke å
736 få NRK til å finne en slik avtale, så burde det være like enkelt å
737 spørre MPEG-LA om de hadde avtale med NRK. Spørsmålet ble sendt før
738 jeg fikk tips fra Kieran Kunhya om hvor listen over lisensinnehavere
739 "in Good Standing" befant seg. MPEG-LA svarte meg i dag, og kan
740 fortelle at NRK ikke har noen avtale med dem, så da er i det minste det
741 slått fast. Ikke overraskende mener MPEG-LA at det trengs en avtale
742 med MPEG-LA for å streame H
.264, men deres rammer er jo
743 rettstilstanden i USA og ikke Norge. Jeg tar dermed den delen av
744 svaret med en klype salt. Jeg er dermed fortsatt ikke klok på om det
745 trengs en avtale, og hvis det trengs en avtale her i Norge, heller
746 ikke sikker på om NRK har en avtale med noen andre enn MPEG-LA som
747 gjør at de ikke trenger avtale direkte med MPEG-LA. Jeg håper NRKs
748 jurister har vurdert dette, og at det er mulig å få tilgang til
749 vurderingen uansett om de trenger en avtale eller ikke.
</p>
751 <p>Her er epostutvekslingen med MPEG-LA så langt. Håper ikke
752 utvekslingen fører til NRK plutselig får en litt uventet pakke fra
756 <p>Date: Mon,
25 Jun
2012 15:
29:
37 +
0200
757 <br>From: Petter Reinholdtsen
<pere (at) hungry.com
>
758 <br>To: licensing-web (at) mpegla.com
759 <br>Subject: Do NRK have a license agreement with MPEG-LA?
</p>
761 <p>Hi. I have a small question for you, that I hope it is OK that I
764 <p>Is there any license agreements between MPEG-LA and NRK,
<URL:
765 <a href=
"http://www.nrk.no/">http://www.nrk.no/
</a> >, the
766 Norwegian national broadcasting cooperation? I am not sure if they
767 need one, and am just curious if such agreeement exist.
</p>
769 <p>The postal address is
</p>
773 <br>Postbox
8500, Majorstuen
778 <p>if it make it easier for you to locate such agreement.
</p>
780 <p>Can you tell me how many entities in Norway have an agreement with
781 MPEG-LA, and the name of these entities?
</p>
785 <br>Petter Reinholdtsen
788 <p>I dag, to dager senere, fikk jeg følgende svar:
</p>
791 <p>Date: Thu,
28 Jun
2012 14:
11:
17 +
0000
792 <br>From: Ryan Rodriguez
<RRodriguez (at) mpegla.com
>
793 <br>To: Petter Reinholdtsen
<pere (at) hungry.com
>
794 <br>CC: MD Administration
<MDAdministration (at) mpegla.com
>
795 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?
</p>
797 <p>Dear Mr. Reinholdtsen,
</p>
799 <p>Thank you for your message and for your interest in MPEG LA. We
800 appreciate hearing from you and I will be happy to assist you.
</p>
802 <p>To begin, I will assume that you are referring to AVC/H
.264
803 technology in your message below, as this technology is commonly used
804 in the transmission of video content. In that case, please allow me
805 to briefly summarize the coverage provided by our AVC Patent Portfolio
808 <P>Our AVC License provides coverage for end products and video
809 services that make use of AVC/H
.264 technology. Accordingly, the
810 party offering such end products and video to End Users concludes the
811 AVC License and is responsible for paying the applicable royalties
812 associated with the end products/video they offer.
</p>
814 <p>While the Norwegian Broadcast Corporation (NRK) is not currently a
815 Licensee to MPEG LA's AVC License (or any other Portfolio License
816 offered by MPEG LA), if NRK offers AVC Video to End Users for
817 remuneration (for example, Title-by-Title, Subscription, Free
818 Television, or Internet Broadcast AVC Video), then NRK will need to
819 conclude the AVC License and may be responsible for paying applicable
820 royalties associated with the AVC Video it distributes.
</p>
822 <p>Today I will send you a FedEx package containing a copy of our AVC
823 License for your review. You should receive the License document
824 within the next few days.
</p>
826 <p>Meanwhile, MPEG LA currently has several Norwegian Licensees that
827 can be found under the "Licensees" header within the respective
828 portion of our website. For example, you may find our list of
829 Licensees in Good Standing to our AVC License in the AVC portion of
831 <a href=
"http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx">http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx
</a></p>
833 <p>I hope the above information is helpful. If you have additional
834 questions or need further assistance with the AVC License, please feel
835 free to contact me directly. I look forward to hearing from you again
843 <br>Licensing Associate
845 <br>5425 Wisconsin Avenue
847 <br>Chevy Chase, MD
20815
849 <br>Phone: +
1 (
301)
986-
6660 x211
850 <br>Fax: +
1 (
301)
986-
8575
851 <br>Email: rrodriguez (at) mpegla.com
</p>
855 <p>Meldingen om utsendt FedEx-pakke var så merkelig at jeg
856 øyeblikkelig sendte svar tilbake og spurte hva i alle dager han mente,
857 da han jo ikke hadde fått noen postadresse som nådde meg.
</p>
861 <p>Date: Thu,
28 Jun
2012 16:
36:
15 +
0200
862 <br>From: Petter Reinholdtsen
<pere (at) hungry.com
>
863 <br>To: Ryan Rodriguez
<RRodriguez (at) mpegla.com
>
864 <br>Cc: MD Administration
<MDAdministration (at) mpegla.com
>
865 <br>Subject: Re: Do NRK have a license agreement with MPEG-LA?
</p>
868 <br>> Dear Mr. Reinholdtsen,
</p>
870 <p>Thank you for your quick reply.
</p>
872 <p>> Today I will send you a FedEx package containing a copy of our AVC
873 <br>> License for your review. You should receive the License document
874 <br>> within the next few days.
</p>
876 <p>The part about sending a FedEx package confused me, though. I did not
877 <br>give you my address, nor am I associated with NRK in any way, so I hope
878 <br>you did not try to send me a package using the address of NRK. If you
879 <br>would send me the Internet address of to the document, it would be more
880 <br>useful to me to be able to download it as an electronic document.
</p>
882 <p>> Meanwhile, MPEG LA currently has several Norwegian Licensees that can
883 <br>> be found under the "Licensees" header within the respective portion
884 <br>> of our website. For example, you may find our list of Licensees in
885 <br>> Good Standing to our AVC License in the AVC portion of our website,
886 <br>> http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx
</p>
888 <p>How can I recognize the Norwegian licensees?
</p>
892 <br>Petter Reinholdtsen
</p>
895 <p>Selv om jeg svarte kun noen minutter etter at jeg fikk eposten fra
896 MPEG-LA, fikk jeg eposten under som automatisk var beskjed på min
897 siste epost. Får håpe noen likevel følger opp "FedEx-pakken". For å
898 øke sjansen for at noen revurderer utsending av pakke uten mottaker,
899 videresendte jeg min epost til swolf (at) mpegla.com, så får vi se.
900 Har ikke hørt noe mer
3 timer senere, så jeg mistenker at ingen leste
901 min epost tidsnok.
</p>
905 <p>Date: Thu,
28 Jun
2012 14:
36:
20 +
0000
906 <br>From: Ryan Rodriguez
<RRodriguez (at) mpegla.com
>
907 <br>To: Petter Reinholdtsen
<pere (at) hungry.com
>
908 <br>Subject: Automatic reply: Do NRK have a license agreement with MPEG-LA?
</p>
910 <p>Thank you for your message.
</p>
912 <p>I will be out of the office until Thursday, July
5 and will respond
913 to all messages upon my return. If this is a matter that requires
914 immediate attention, please contact Sidney Wolf (swolf (at)
922 <br>Licensing Associate
927 <p>Litt klokere, men fortsatt ikke klok på mitt opprinnelige spørsmål,
928 som er om en trenger avtale med MPEG-LA for å publisere eller
929 kringkaste H
.264-video i Norge.
</p>
935 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
940 <div class=
"padding"></div>
944 <a href=
"http://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>
950 <p>Jeg fikk nettopp svar fra NRK på
951 <a href=
"http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">min
952 forespørsel om kopi av avtale
</a> med MPEG-LA eller andre om bruk av
953 MPEG og/eller H
.264. Svaret har fått saksreferanse
2011/
371 (mon tro
954 hva slags sak fra
2011 dette er?) hos NRK og lyder som følger:
</p>
958 <p><strong>Svar på innsynsbegjæring i MPEG / H
.264-relaterte
961 <p>Viser til innsynsbegjæring av
19. juni
2012. Kravet om innsyn
962 gjelder avtale som gjør at NRK «ikke er begrenset av de generelle
963 bruksvilkårene som gjelder for utstyr som bruker MPEG og/eller
966 <p>I henhold til offentleglova §
28 annet ledd må innsynskravet gjelde
967 en bestemt sak eller i rimelig utstrekning saker av en bestemt
968 sak. Det er på det rene at det aktuelle innsynskravet ikke gjelder en
969 bestemt sak. Spørsmålet som reiser seg er om identifiseringsgraden er
970 tilstrekkelig. I Justisdepartementets «Rettleiar til offentleglova»
973 <p>«Kravet om at innsynskravet må gjelde ei bestemt sak er til hinder
974 for at eit innsynskrav kan gjelde alle saker av ein bestemt art, utan
975 at den enkelte saka blir identifisert. Ein kan med andre ord i
976 utgangspunktet ikkje krevje innsyn i til dømes alle saker om
977 utsleppsløyve hos Statens forureiningstilsyn frå dei siste tre åra,
978 med mindre ein identifiserer kvar enkelt sak, til dømes med tilvising
979 til dato, partar eller liknande.»
</p>
981 <p>Vedrørende denne begrensningen har Justisdepartementet uttalt
982 følgende (Lovavdelingens uttalelser JDLOV-
2010-
3295):
</p>
984 <p><em>«Bakgrunnen for avgrensinga av kva innsynskravet kan gjelde,
985 er fyrst og fremst at meir generelle innsynskrav, utan noka form for
986 identifikasjon av kva ein eigentleg ynskjer, ville vere svært
987 vanskelege å handsame for forvaltninga.»
</em></p>
989 <p>I samme sak uttaler Lovavdelingen følgende:
</p>
991 <p><em>«Det følgjer vidare av offentleglova §
28 andre ledd at det `i
992 rimeleg utstrekning' kan krevjast innsyn i `saker av ein bestemt
993 art'. Vilkåret om at eit innsynskrav berre `i rimeleg utstrekning' kan
994 gjelde saker av ein bestemt art, er i hovudsak knytt til kor
995 arbeidskrevjande det vil vere å finne fram til dei aktuelle
996 dokumenta. I tillegg reknar vi med at vilkåret kan gje grunnlag for å
997 nekte innsyn i tilfelle der innsynskravet er så omfattande (gjeld så
998 mange dokument) at arbeidsmengda som ville gått med til å handsame
999 det, er større enn det ein `i rimeleg utstrekning' kan krevje (sjølv
1000 om det nok skal mykje til).»
</em></p>
1002 <p>NRK har ikke noen egen sammenstilling over avtaler innenfor
1003 bestemte områder som omtales i innsynsbegjæringen. De måtte søkes på
1004 vanlig måte. I tillegg finnes ikke noen automatisert måte å finne
1005 avtaler som «ikke er begrenset av de generelle bruksvilkårene som
1006 gjelder for utstyr som bruker MPEG og/eller H
.264». En slik
1007 gjennomgang av avtaler måtte gjøres manuelt av en person med
1008 spesialistkunnskap. Dette vil kreve at NRK avsetter omfattende
1009 ressurser for å finne frem relevante avtaler og for deretter å vurdere
1010 om de dekkes av det innsynsbegjæringen omfattes.
</p>
1012 <p>På bakgrunn av dette nekter NRK innsyn, med den begrunnelsen at
1013 innsynskravet er så omfattende at arbeidsmengden for å håndtere kravet
1014 vil være langt større enn det som i rimelig utstrekning kan kreves i
1015 henhold til offentleglova §
28 annet ledd.
</p>
1017 <p>Avslag på deres innsynsbegjæring kan påklages til Kultur- og
1018 kirkedepartementet innen tre uker fra det tidspunkt avslaget kommer
1019 frem til mottakeren, i henhold til reglene i offentleglova §
32,
1020 jf. forvaltningsloven kapittel VI. Klagen skal stiles til Kultur- og
1021 kirkedepartementet, og sendes til NRK.
</p>
1023 <p>NRK er imidlertid etter Offentleglova forpliktet å gi ut journaler,
1024 slik at en eventuell søknad om innsyn kan tydeligere identifisere
1025 hvilke dokumenter som det ønskes innsyn i. NRKs offentlige journaler
1026 for inneværende og forrige måned ligger ute på
1027 NRK.no/innsyn. Journaler som går lengre tilbake i tid, kan sendes ut
1028 på forespørsel til innsyn (at) nrk.no.
</p>
1031 <br>Dokumentarkivet i NRK
1032 <br>v/ Elin Brandsrud
1033 <br>Tel. direkte:
23 04 29 29
1034 <br>Post: RBM3, Postboks
8500 Majorstuen,
0340 Oslo
1035 <br>innsyn (at) nrk.no
</p>
1040 <a href=
"http://people.skolelinux.org/pere/blog/images/2012-06-25-video-mpegla-nrk.pdf">i
1041 PDF-form som vedlegg på epost
</a>. Jeg er litt usikker på hvordan jeg
1042 best går videre for å bli klok, men jeg har jo i hvert fall tre uker
1043 på å vurdere om jeg skal klage. Enten må nok forespørselen
1044 reformuleres eller så må jeg vel klage. Synes jo det er merkelig at
1045 NRK ikke har bedre kontroll med hvilke avtaler de har inngått. Det
1046 burde jo være noen i ledelsen som vet om de har signert en avtale med
1047 MPEG-LA eller ikke...
</p>
1049 <p>Oppdatering
2012-
06-
25 20:
20: Et google-søk på "
2011/
371 nrk"
1050 sendte meg til postjournalen for
1051 <a href=
"http://nrk.no/contentfile/file/1.8212365!offentligjournal19062012.pdf">2012-
06-
19</a>
1053 <a href=
"http://nrk.no/contentfile/file/1.8214156!offentligjournal20062012.pdf">2012-
06-
20</a>
1054 hos NRK som viser mine forespørsler og viser at sakens tittel hos NRK
1055 er "Graphic Systems Regions MA
2378/
10E". Videre søk etter "Graphic
1056 Systems Regions" viser at dette er saken til et anbud om
1057 "
<a href=
"http://no.mercell.com/m/mts/Tender/27179412.aspx">a graphics
1058 system for
12 or
13 sites broadcasting regional news
</a>" hos Mercell
1059 Sourcing Service, også omtalt på
1060 <a href="http://www.publictenders.net/tender/
595705">Public
1062 <a href="http://www.doffin.no/search/show/search_view.aspx?ID=JAN155521
">Doffin</a>.
1063 Jeg er dog usikker på hvordan dette er relatert til min
1066 <p>Oppdatering 2012-06-25 22:40: Ble tipset av Kieran Kunhya, fra
1068 <a href="http://code.google.com/p/open-broadcast-encoder/
">Open
1069 Broadcast Encoder</a>, at listen over de som har lisensavtale med
1071 <a href="http://www.mpeg-la.com/main/programs/AVC/Pages/Licensees.aspx
">tilgjengelig
1072 på web</a>. Veldig fint å oppdage hvor den finnes, da jeg må ha lett
1073 etter feil ting da jeg forsøke å finne den. Der står ikke NRK, men
1074 flere andre "Broadcasting Company"-oppføringer. Lurer på om det betyr
1075 at NRK ikke trenger avtale, eller noe helt annet?
</p>
1081 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
1086 <div class=
"padding"></div>
1090 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html">Song book for Computer Scientists
</a>
1096 <p>Many years ago, while studying Computer Science at the
1097 <a href=
"http://www.uit.no/">University of Tromsø
</a>, I started
1098 collecting computer related songs for use at parties. The original
1099 version was written in LaTeX, but a few years ago I got help from
1100 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
1101 while keeping the ability to create a nice book in PDF format. I have
1102 not had time to maintain the book for a while now, and guess I should
1103 put it up on some public version control repository where others can
1104 help me extend and update the book. If anyone is volunteering to help
1105 me with this, send me an email. Also let me know if there are songs
1106 missing in my book.
</p>
1108 <p>I have not mentioned the book on my blog so far, and it occured to
1109 me today that I really should let all my readers share the joys of
1110 singing out load about programming, computers and computer networks.
1111 Especially now that
<a href=
"http://debconf12.debconf.org/">Debconf
1112 12</a> is about to start (and I am not going). Want to sing? Check
1113 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/">Petter's
1114 Computer Science Songbook
</a>.
1120 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>.
1125 <div class=
"padding"></div>
1129 <a href=
"http://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>
1135 <p>Trengs det avtale med MPEG-LA for å ha lovlig rett til å
1136 distribuere og kringkaste video i MPEG4 eller med videokodingen H
.264?
1137 <a href=
"http://webmink.com/essays/h-264/">H
.264 og MPEG4 er jo ikke en
1138 fri og åpen standard
</a> i henhold til
1139 <a href=
"http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">definisjonen
1140 til Digistan
</a>, så i enkelte land er det ingen tvil om at du må ha
1141 en slik avtale, men jeg må innrømme at jeg ikke vet om det også
1142 gjelder Norge. Det ser uansett ut til å være en juridisk interessant
1143 problemstilling. Men jeg tenkte her om dagen som så, at hvis det er
1144 nødvendig, så har store aktører som
1145 <a href=
"http://www.nrk.no/">NRK
</a> og
1146 <a href=
"http://www.regjeringen.no/">regjeringen
</a> skaffet seg en
1147 slik avtale. Jeg har derfor sendt forespørsel til begge (for
1148 regjeringen sin del er det Departementenes Servicesenter som gjør
1149 jobben), og bedt om kopi av eventuelle avtaler de har om bruk av MPEG
1150 og/eller H
.264 med MPEG-LA eller andre aktører som opererer på vegne
1151 av MPEG-LA. Her er kopi av eposten jeg har sendt til
1152 <a href=
"http://www.dss.dep.no/">Departementenes Servicesenter
</a>.
1153 Forespørselen til NRK er veldig lik.
</p>
1157 <p>Date: Tue,
19 Jun
2012 15:
18:
33 +
0200
1158 <br>From: Petter Reinholdtsen
1159 <br>To: postmottak@dss.dep.no
1160 <br>Subject: Innsynsbegjæring om MPEG/H
.264-relaterte avtaler
1162 <p>Hei. Jeg ber herved om innsyn og kopi av dokumenter i DSS relatert
1163 til avtaler rundt bruk av videoformatene MPEG og H
.264. Jeg er
1164 spesielt interessert i å vite om DSS har lisensavtale med MPEG-LA
1165 eller noen som representerer MPEG-LA i Norge.
</p>
1167 <p>MPEG og H
.264 er videoformater som brukes både til kringkasting
1168 (f.eks. i bakkenett og kabel-TV) og videopublisering på web, deriblant
1169 via Adobe Flash. MPEG-LA,
<URL:
1170 <a href=
"http://www.mpeg-la.com/">http://www.mpeg-la.com/
</a> >, er
1171 en organisasjon som har fått oppgaven, av de kjente rettighetshavere
1172 av immaterielle rettigheter knyttet til MPEG og H
.264, å selge
1173 bruksrett for MPEG og H
.264.
</p>
1175 <p>Via regjeringen.no kringkastes med MPEG og H
.264-baserte
1176 videoformater, og dette ser ut til å være organisert av DSS. Jeg
1177 antar dermed at DSS har avtale med en eller annen aktør om dette.
</p>
1179 <p>F.eks. har Adobe Premiere Pro har følgende klausul i følge
<URL:
1180 <a href=
"http://news.cnet.com/8301-30685_3-20000101-264.html">http://news.cnet.com/
8301-
30685_3-
20000101-
264.html
</a>
1185 <p>6.17. AVC DISTRIBUTION. The following notice applies to software
1186 containing AVC import and export functionality: THIS PRODUCT IS
1187 LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND
1188 NON-COMMERCIAL USE OF A CONSUMER TO (a) ENCODE VIDEO IN COMPLIANCE
1189 WITH THE AVC STANDARD (
"AVC VIDEO") AND/OR (b) DECODE AVC VIDEO THAT
1190 WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL
1191 ACTIVITY AND/OR AVC VIDEO THAT WAS OBTAINED FROM A VIDEO PROVIDER
1192 LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
1193 IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED
1194 FROM MPEG LA L.L.C. SEE
1195 <a href=
"http://www.mpegla.com">http://www.mpegla.com
</a>.
</p>
1199 <p>Her er det kun "non-commercial" og "personal and non-commercial"
1200 aktivitet som er tillatt uten ekstra avtale med MPEG-LA.
</p>
1202 <p>Et annet tilsvarende eksempel er Apple Final Cut Pro, som har
1203 følgende klausul i følge
<URL:
1204 <a href=
"http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf">http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf
</a>
1209 <p>15. Merknad om H
.264/AVC. Hvis Apple-programvaren inneholder
1210 funksjonalitet for AVC-koding og/eller AVC-dekoding, krever
1211 kommersiell bruk ekstra lisensiering og følgende gjelder:
1212 AVC-FUNKSJONALITETEN I DETTE PRODUKTET KAN KUN ANVENDES AV
1213 FORBRUKERE OG KUN FOR PERSONLIG OG IKKE- KOMMERSIELL BRUK TIL (i)
1214 KODING AV VIDEO I OVERENSSTEMMELSE MED AVC-STANDARDEN (
"AVC-VIDEO")
1215 OG/ELLER (ii) DEKODING AV AVC-VIDEO SOM ER KODET AV EN FORBRUKER TIL
1216 PERSONLIG OG IKKE-KOMMERSIELL BRUK OG/ELLER DEKODING AV AVC-VIDEO
1217 FRA EN VIDEOLEVERANDØR SOM HAR LISENS TIL Å TILBY
1218 AVC-VIDEO. INFORMASJON OM ANNEN BRUK OG LISENSIERING KAN INNHENTES
1219 FRA MPEG LA L.L.C. SE HTTP://WWW.MPEGLA.COM.
</p>
1222 <p>Tilsvarende gjelder for andre programvarepakker, kamera, etc som
1223 bruker MPEG og H
.264, at en må ha en avtale med MPEG-LA for å ha lov
1224 til å bruke programmet/utstyret hvis en skal lage noe annet enn
1225 private filmer og i ikke-kommersiell virksomhet.
</p>
1227 <p>Jeg er altså interessert i kopi av avtaler DSS har som gjør at en
1228 ikke er begrenset av de generelle bruksvilkårene som gjelder for
1229 utstyr som bruker MPEG og/eller H
.264.
</p>
1232 <p>Nå venter jeg spent på svaret. Jeg planlegger å blogge om svaret
1239 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/digistan">digistan
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
1244 <div class=
"padding"></div>
1248 <a href=
"http://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>
1254 <p>In
<a href=
"http://www.idg.no/computerworld/article243690.ece">an
1255 article today
</a> published by Computerworld Norway, the photographer
1256 <a href=
"http://www.urke.com/eirik/">Eirik Helland Urke
</a> reports
1257 that the video editor application included with
1258 <a href=
"http://www.htc.com/www/smartphones/htc-one-x/#specs">HTC One
1259 X
</a> have some quite surprising terms of use. The article is mostly
1260 based on the twitter message from mister Urke, stating:
1263 "
<a href=
"http://twitter.com/urke/status/194062269724897280">Drøy
1264 brukeravtale: HTC kan bruke MINE redigerte videoer kommersielt. Selv
1265 kan jeg KUN bruke dem privat.
</a>"
1268 <p>I quickly translated it to this English message:</p>
1271 "Arrogant user agreement: HTC can use MY edited videos
1272 commercially. Although I can ONLY use them privately.
"
1275 <p>I've been unable to find the text of the license term myself, but
1276 suspect it is a variation of the MPEG-LA terms I
1277 <a href="http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html
">discovered
1278 with my Canon IXUS 130</a>. The HTC One X specification specifies that
1279 the recording format of the phone is .amr for audio and .mp3 for
1281 <a href="http://en.wikipedia.org/wiki/Adaptive_Multi-Rate_audio_codec#Licensing_and_patent_issues
">Adaptive
1282 Multi-Rate audio codec</a> with patents which according to the
1283 Wikipedia article require an license agreement with
1284 <a href="http://www.voiceage.com/
">VoiceAge</a>. MP4 is
1285 <a href="http://en.wikipedia.org/wiki/H
.264/MPEG-
4_AVC#Patent_licensing
">MPEG4 with
1286 H.264</a>, which according to Wikipedia require a licence agreement
1287 with <a href="http://www.mpegla.com/
">MPEG-LA</a>.</p>
1289 <p>I know why I prefer
1290 <a href="http://www.digistan.org/open-standard:definition
">free and open
1291 standards</a> also for video.</p>
1297 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan
">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english
">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia
">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern
">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard
">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video
">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web
">web</a>.
1302 <div class="padding
"></div>
1306 <a href="http://people.skolelinux.org/pere/blog/RAND_terms___non_reasonable_and_discriminatory.html
">RAND terms - non-reasonable and discriminatory</a>
1312 <p>Here in Norway, the
1313 <a href="http://www.regjeringen.no/nb/dep/fad.html?id=
339"> Ministry of
1314 Government Administration, Reform and Church Affairs</a> is behind
1315 a <a href="http://standard.difi.no/forvaltningsstandarder
">directory of
1316 standards</a> that are recommended or mandatory for use by the
1317 government. When the directory was created, the people behind it made
1318 an effort to ensure that everyone would be able to implement the
1319 standards and compete on equal terms to supply software and solutions
1320 to the government. Free software and non-free software could compete
1321 on the same level.</p>
1323 <p>But recently, some standards with RAND
1324 (<a href="http://en.wikipedia.org/wiki/Reasonable_and_non-discriminatory_licensing
">Reasonable
1325 And Non-Discriminatory</a>) terms have made their way into the
1326 directory. And while this might not sound too bad, the fact is that
1327 standard specifications with RAND terms often block free software from
1328 implementing them. The reasonable part of RAND mean that the cost per
1329 user/unit is low,and the non-discriminatory part mean that everyone
1330 willing to pay will get a license. Both sound great in theory. In
1331 practice, to get such license one need to be able to count users, and
1332 be able to pay a small amount of money per unit or user. By
1333 definition, users of free software do not need to register their use.
1334 So counting users or units is not possible for free software projects.
1335 And given that people will use the software without handing any money
1336 to the author, it is not really economically possible for a free
1337 software author to pay a small amount of money to license the rights
1338 to implement a standard when the income available is zero. The result
1339 in these situations is that free software are locked out from
1340 implementing standards with RAND terms.</p>
1342 <p>Because of this, when I see someone claiming the terms of a
1343 standard is reasonable and non-discriminatory, all I can think of is
1344 how this really is non-reasonable and discriminatory. Because free
1345 software developers are working in a global market, it does not really
1346 help to know that software patents are not supposed to be enforceable
1347 in Norway. The patent regimes in other countries affect us even here.
1348 I really hope the people behind the standard directory will pay more
1349 attention to these issues in the future.</p>
1351 <p>You can find more on the issues with RAND, FRAND and RAND-Z terms
1353 (<a href="http://blogs.computerworlduk.com/simon-says/
2010/
11/rand-not-so-reasonable/
">RAND:
1354 Not So Reasonable?</a>).</p>
1356 <p>Update 2012-04-21: Just came across a
1357 <a href="http://blogs.computerworlduk.com/open-enterprise/
2012/
04/of-microsoft-netscape-patents-and-open-standards/index.htm
">blog
1358 post from Glyn Moody</a> over at Computer World UK warning about the
1359 same issue, and urging people to speak out to the UK government. I
1360 can only urge Norwegian users to do the same for
1361 <a href="http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder
">the
1362 hearing taking place at the moment</a> (respond before 2012-04-27).
1363 It proposes to require video conferencing standards including
1364 specifications with RAND terms.</p>
1370 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english
">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia
">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug
">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard
">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video
">video</a>.
1375 <div class="padding
"></div>
1379 <a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html
">Hvordan enkelt laste ned filmer fra NRK</a>
1385 <p>Ofte har jeg lyst til å laste ned et innslag fra NRKs nettsted for
1386 å se det senere når jeg ikke er på nett, eller for å ha det
1387 tilgjengelig når jeg en gang i fremtiden ønsker å referere til
1388 innslaget selv om NRK har fjernet det fra sine nettsider. I dag fant
1389 jeg et lite script som fikser jobben.</p>
1391 <p>Scriptet er laget av Jan Henning Thorsen og tilgjengelig fra
1392 <a href="http://jhthorsen.github.com/snippets/nrk-downloader/
">github</a>,
1393 og gjør det veldig enkelt å laste ned. Kjør <tt>nrk-downloader.sh
1394 http://www1.nrk.no/nett-tv/klipp/582810</tt> for å hente ned et enkelt
1395 innslag eller <tt>nrk-downloader.sh
1396 http://www1.nrk.no/nett-tv/kategori/3521</tt> for å laste ned alle
1397 episodene i en serie.</p>
1399 <p>Det er ikke rakettforskning å laste ned NRK-"strømmer", og
1400 tidligere gjorde jeg dette manuelt med mplayer. Scriptet til
1401 Hr. Thorsen gjør det raskere og enklere for meg, men jeg vil ikke si
1402 at det er en revolusjonerende løsning. Jeg mener jo fortsatt at
1403 påstanden fra NRKs ansatte om at det er
1404 <a href=
"http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html">vesensforskjellig
1405 å legge tilgjengelig for nedlasting og for streaming
</a> er
1412 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
1417 <div class=
"padding"></div>
1421 <a href=
"http://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>
1427 <p>While at Debconf11, I have several times during discussions
1428 mentioned the issues I believe should be improved in Debian for its
1429 desktop to be useful for more people. The use case for this is my
1430 parents, which are currently running Kubuntu which solve the
1433 <p>I suspect these four missing features are not very hard to
1434 implement. After all, they are present in Ubuntu, so if we wanted to
1435 do this in Debian we would have a source.
</p>
1439 <li><strong>Simple GUI based upgrade of packages.
</strong> When there
1440 are new packages available for upgrades, a icon in the KDE status bar
1441 indicate this, and clicking on it will activate the simple upgrade
1442 tool to handle it. I have no problem guiding both of my parents
1443 through the process over the phone. If a kernel reboot is required,
1444 this too is indicated by the status bars and the upgrade tool. Last
1445 time I checked, nothing with the same features was working in KDE in
1448 <li><strong>Simple handling of missing Firefox browser
1449 plugins.
</strong> When the browser encounter a MIME type it do not
1450 currently have a handler for, it will ask the user if the system
1451 should search for a package that would add support for this MIME type,
1452 and if the user say yes, the APT sources will be searched for packages
1453 advertising the MIME type in their control file (visible in the
1454 Packages file in the APT archive). If one or more packages are found,
1455 it is a simple click of the mouse to add support for the missing mime
1456 type. If the package require the user to accept some non-free
1457 license, this is explained to the user. The entire process make it
1458 more clear to the user why something do not work in the browser, and
1459 make the chances higher for the user to blame the web page authors and
1460 not the browser for any missing features.
</li>
1462 <li><strong>Simple handling of missing multimedia codec/format
1463 handlers.
</strong> When the media players encounter a format or codec
1464 it is not supporting, a dialog pop up asking the user if the system
1465 should search for a package that would add support for it. This
1466 happen with things like MP3, Windows Media or H
.264. The selection
1467 and installation procedure is very similar to the Firefox browser
1468 plugin handling. This is as far as I know implemented using a
1469 gstreamer hook. The end result is that the user easily get access to
1470 the codecs that are present from the APT archives available, while
1471 explaining more on why a given format is unsupported by Ubuntu.
</li>
1473 <li><strong>Better browser handling of some MIME types.
</strong> When
1474 displaying a text/plain file in my Debian browser, it will propose to
1475 start emacs to show it. If I remember correctly, when doing the same
1476 in Kunbutu it show the file as a text file in the browser. At least I
1477 know Opera will show text files within the browser. I much prefer the
1478 latter behaviour.
</li>
1482 <p>There are other nice features as well, like the simplified suite
1483 upgrader, but given that I am the one mostly doing the dist-upgrade,
1484 it do not matter much.
</p>
1486 <p>I really hope we could get these features in place for the next
1487 Debian release. It would require the coordinated effort of several
1488 maintainers, but would make the end user experience a lot better.
</p>
1494 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
1499 <div class=
"padding"></div>
1503 <a href=
"http://people.skolelinux.org/pere/blog/Gnash_enteres_Google_Summer_of_Code_2011.html">Gnash enteres Google Summer of Code
2011</a>
1509 <p><a href=
"http://www.getgnash.org/">The Gnash project
</a> is still
1510 the most promising solution for a Free Software Flash implementation.
1511 A few days ago the project
1512 <a href=
"http://lists.gnu.org/archive/html/gnash-dev/2011-04/msg00011.html">announced
</a>
1513 that it will participate in Google Summer of Code. I hope many
1514 students apply, and that some of them succeed in getting AVM2 support
1521 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
1526 <div class=
"padding"></div>
1530 <a href=
"http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html">Why isn't Debian Edu using VLC?
</a>
1536 <p>In the latest issue of Linux Journal, the readers choices were
1537 presented, and the winner among the multimedia player were VLC.
1538 Personally, I like VLC, and it is my player of choice when I first try
1539 to play a video file or stream. Only if VLC fail will I drag out
1540 gmplayer to see if it can do better. The reason is mostly the failure
1541 model and trust. When VLC fail, it normally pop up a error message
1542 reporting the problem. When mplayer fail, it normally segfault or
1543 just hangs. The latter failure mode drain my trust in the program.
<p>
1545 <p>But even if VLC is my player of choice, we have choosen to use
1546 mplayer in
<a href=
"http://www.skolelinux.org/">Debian
1547 Edu/Skolelinux
</a>. The reason is simple. We need a good browser
1548 plugin to play web videos seamlessly, and the VLC browser plugin is
1549 not very good. For example, it lack in-line control buttons, so there
1550 is no way for the user to pause the video. Also, when I
1551 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia">last
1552 tested the browser plugins
</a> available in Debian, the VLC plugin
1553 failed on several video pages where mplayer based plugins worked. If
1554 the browser plugin for VLC was as good as the gecko-mediaplayer
1555 package (which uses mplayer), we would switch.
</P>
1557 <p>While VLC is a good player, its user interface is slightly
1558 annoying. The most annoying feature is its inconsistent use of
1559 keyboard shortcuts. When the player is in full screen mode, its
1560 shortcuts are different from when it is playing the video in a window.
1561 For example, space only work as pause when in full screen mode. I
1562 wish it had consisten shortcuts and that space also would work when in
1563 window mode. Another nice shortcut in gmplayer is [enter] to restart
1564 the current video. It is very nice when playing short videos from the
1565 web and want to restart it when new people arrive to have a look at
1566 what is going on.
</p>
1572 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
1577 <div class=
"padding"></div>
1581 <a href=
"http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html">Best å ikke fortelle noen at streaming er nedlasting...
</a>
1587 <p>I dag la jeg inn en kommentar på en sak hos NRKBeta
1588 <a href=
"http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/">om
1589 hvordan TV-serien Blindpassasjer ble laget
</a> i forbindelse med at
1590 filmene NRK la ut ikke var tilgjengelig i et
1591 <a href=
"http://www.digistan.org/open-standard:definition">fritt og
1592 åpent format
</a>. Dette var det jeg skrev publiserte der
07:
39.
</p>
1595 <p>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
1596 nedlasting. Mange av oss som kan mer enn gjennomsnittet om systemer
1597 som dette, vet at det stort sett er mulig å lure ut ting med den
1598 nødvendige forkunnskapen."</p>
1600 <p>Haha. Å streame innhold er det samme som å laste ned innhold, så å
1601 beskytte en stream mot nedlasting er ikke mulig. Å skrive noe slikt
1602 er å forlede leseren.
</p>
1604 <p>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
1605 vil tillate streaming men ikke nedlasting meningsløs.
</p>
1607 <p>Anbefaler forresten å lese
1608 <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>
1609 om hva som ville være konsekvensen hvis digitale avspillingssperrer
1610 (DRM) fungerte. Det gjør de naturligvis ikke teknisk - det er jo
1611 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
1612 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
1616 <p>Ca.
20 minutter senere får jeg følgende epost fra Anders Hofseth i
1620 <p>From: Anders Hofseth
<XXX@gmail.com
>
1621 <br>To: "pere@hungry.com"
<pere@hungry.com
>
1622 <br>Cc: Eirik Solheim
<XXX@gmail.com
>, Jon Ståle Carlsen
<XXX@gmail.com
>, Henrik Lied
<XXX@gmail.com
>
1623 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del
1"
1624 <br>Date: Sat,
30 Oct
2010 07:
58:
44 +
0200</p>
1627 <br>Det du forsøker dra igang er egentlig en interessant diskusjon,
1628 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
1629 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
1630 særlig lett å klarere ut noe annet arkivmateriale på lang tid.
</p>
1632 <p>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
1633 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
1634 konsekvensene vi beskriver ikke er noe du ønsker heller...
</p>
1639 <p>Ring meg om noe er uklart:
95XXXXXXX
</p>
1642 <p>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
1643 over følgende svar. I og med at debatten er fjernet fra NRK Betas
1644 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
1645 Har fjernet epostadresser og telefonnummer til de involverte, for å
1646 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.
</p>
1649 <p>From: Petter Reinholdtsen
<pere@hungry.com
>
1650 <br>To: Anders Hofseth
<XXX@gmail.com
>
1651 <br>Cc: Eirik Solheim
<XXX@gmail.com
>,
1652 <br> Jon Ståle Carlsen
<XXX@gmail.com
>,
1653 <br> Henrik Lied
<XXX@gmail.com
>
1654 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del
1"
1655 <br>Date: Sat,
30 Oct
2010 08:
24:
34 +
0200</p>
1658 <br>> Hei Petter.
</p>
1662 <p>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
1663 <br>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
1664 <br>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
1665 <br>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.
</p>
1667 <p>Godt å se at du er enig i at dette er en interessant diskusjon. Den
1668 vil nok fortsette en stund til. :)
</p>
1670 <p>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
1671 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
1672 fortsette å legge ut arkivmateriale.
</p>
1674 <p>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
1675 faktum, som er at streaming er det samme som nedlasting, og at innhold
1676 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
1679 <p>Det du sier er jo at klarering av arkivmateriale for publisering på
1680 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
1681 Det er ikke et argument som holder vann. :)
</p>
1683 <p>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
1684 <br>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
1685 <br>> konsekvensene vi beskriver ikke er noe du ønsker heller...
</p>
1687 <p>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
1688 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
1689 mot de som vil låse kulturen inne. Jeg synes det er en skam at NRK
1690 godtar å forlede publikum. Ville heller at NRK krever at innhold som
1691 skal sendes skal være uten bruksbegresninger og kan publiseres i
1692 formater som heller ikke har bruksbegresninger (bruksbegresningene til
1693 H
.264 burde få varselbjellene i NRK til å ringe).
</p>
1695 <p>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
1696 påstander om at "streaming beskytter mot nedlasting" som bare er egnet
1697 til å bygge opp om en myte som er skadelig for samfunnet som helhet.
</p>
1699 <p>Anbefaler
<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
1701 <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> >.
1702 for å se hva slags bruksbegresninger H
.264 innebærer.
</p>
1704 <p>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
1705 kan brukes før rettighetshaverene også innser at de er med på å skade
1706 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
1707 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
1708 langt på overtid.
</p>
1710 <p>> Ring meg om noe er uklart: XXX
</p>
1712 <p>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
1713 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
1714 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
1715 for videre diskusjon hadde dere i mine øyne kommet fra det med
1716 ryggraden på plass.
</p>
1718 <p>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.
</p>
1720 <p>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
1721 <URL:
<a href=
"http://www.archive.org/details/CopyingIsNotTheft">http://www.archive.org/details/CopyingIsNotTheft
</a> > og
1722 <URL:
<a href=
"http://patentabsurdity.com/">http://patentabsurdity.com/
</a> > hadde vært noe å kringkaste på
1727 <br>Petter Reinholdtsen
</p>
1733 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/digistan">digistan
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
1738 <div class=
"padding"></div>
1742 <a href=
"http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html">Software updates
2010-
10-
24</a>
1748 <p>Some updates.
</p>
1750 <p>My
<a href=
"http://pledgebank.com/gnash-avm2">gnash pledge
</a> to
1751 raise money for the project is going well. The lower limit of
10
1752 signers was reached in
24 hours, and so far
13 people have signed it.
1753 More signers and more funding is most welcome, and I am really curious
1754 how far we can get before the time limit of December
24 is reached.
1757 <p>On the #gnash IRC channel on irc.freenode.net, I was just tipped
1758 about what appear to be a great code coverage tool capable of
1759 generating code coverage stats without any changes to the source code.
1761 <a href=
"http://simonkagstrom.github.com/kcov/index.html">kcov
</a>,
1762 and can be used using
<tt>kcov
<directory
> <binary
></tt>.
1763 It is missing in Debian, but the git source built just fine in Squeeze
1764 after I installed libelf-dev, libdwarf-dev, pkg-config and
1765 libglib2.0-dev. Failed to build in Lenny, but suspect that is
1766 solvable. I hope kcov make it into Debian soon.
</p>
1768 <p>Finally found time to wrap up the release notes for
<a
1769 href=
"http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html">a
1770 new alpha release of Debian Edu
</a>, and just published the second
1771 alpha test release of the Squeeze based Debian Edu /
1772 <a href=
"http://www.skolelinux.org/">Skolelinux
</a>
1773 release. Give it a try if you need a complete linux solution for your
1774 school, including central infrastructure server, workstations, thin
1775 client servers and diskless workstations. A nice touch added
1776 yesterday is RDP support on the thin client servers, for windows
1777 clients to get a Linux desktop on request.
</p>
1783 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>.
1788 <div class=
"padding"></div>
1792 <a href=
"http://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>
1798 <p><a href=
"http://www.getgnash.org/">The Gnash project
</a> is the
1799 most promising solution for a Free Software Flash implementation. It
1800 has done great so far, but there is still far to go, and recently its
1801 funding has dried up. I believe AVM2 support in Gnash is vital to the
1802 continued progress of the project, as more and more sites show up with
1803 AVM2 flash files.
</p>
1805 <p>To try to get funding for developing such support, I have started
1806 <a href=
"http://www.pledgebank.com/gnash-avm2">a pledge
</a> with the
1811 <p>"I will pay 100$ to the Gnash project to develop AVM2 support but
1812 only if 10 other people will do the same."</p>
1814 <p>- Petter Reinholdtsen, free software developer
</p>
1816 <p>Deadline to sign up by:
24th December
2010</p>
1818 <p>The Gnash project need to get support for the new Flash file
1819 format AVM2 to work with a lot of sites using Flash on the
1820 web. Gnash already work with a lot of Flash sites using the old AVM1
1821 format, but more and more sites are using the AVM2 format these
1822 days. The project web page is available from
1823 http://www.getgnash.org/ . Gnash is a free software implementation
1824 of Adobe Flash, allowing those of us that do not accept the terms of
1825 the Adobe Flash license to get access to Flash sites.
</p>
1827 <p>The project need funding to get developers to put aside enough
1828 time to develop the AVM2 support, and this pledge is my way to try
1829 to get this to happen.
</p>
1831 <p>The project accept donations via the OpenMediaNow foundation,
1832 <a href=
"http://www.openmedianow.org/?q=node/32">http://www.openmedianow.org/?q=node/
32</a> .
</p>
1836 <p>I hope you will support this effort too. I hope more than
10
1837 people will participate to make this happen. The more money the
1838 project gets, the more features it can develop using these funds.
1845 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/nuug">nuug
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
1850 <div class=
"padding"></div>
1854 <a href=
"http://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>
1860 <p>A few days ago I had the mixed pleasure of bying a new digital
1861 camera, a Canon IXUS
130. It was instructive and very disturbing to
1862 be able to verify that also this camera producer have the nerve to
1863 specify how I can or can not use the videos produced with the camera.
1864 Even thought I was aware of the issue, the options with new cameras
1865 are limited and I ended up bying the camera anyway. What is the
1866 problem, you might ask? It is software patents, MPEG-
4, H
.264 and the
1867 MPEG-LA that is the problem, and our right to record our experiences
1868 without asking for permissions that is at risk.
1870 <p>On page
27 of the Danish instruction manual, this section is
1874 <p>This product is licensed under AT&T patents for the MPEG-
4 standard
1875 and may be used for encoding MPEG-
4 compliant video and/or decoding
1876 MPEG-
4 compliant video that was encoded only (
1) for a personal and
1877 non-commercial purpose or (
2) by a video provider licensed under the
1878 AT&T patents to provide MPEG-
4 compliant video.
</p>
1880 <p>No license is granted or implied for any other use for MPEG-
4
1884 <p>In short, the camera producer have chosen to use technology
1885 (MPEG-
4/H
.264) that is only provided if I used it for personal and
1886 non-commercial purposes, or ask for permission from the organisations
1887 holding the knowledge monopoly (patent) for technology used.
</p>
1889 <p>This issue has been brewing for a while, and I recommend you to
1891 "
<a href=
"http://www.osnews.com/story/23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA">Why
1892 Our Civilization's Video Art and Culture is Threatened by the
1893 MPEG-LA
</a>" by Eugenia Loli-Queru and
1894 "<a href=
"http://webmink.com/2010/09/03/h-264-and-foss/">H
.264 Is Not
1895 The Sort Of Free That Matters
</a>" by Simon Phipps to learn more about
1896 the issue. The solution is to support the
1897 <a href="http://www.digistan.org/open-standard:definition
">free and
1898 open standards</a> for video, like <a href="http://www.theora.org/
">Ogg
1899 Theora</a>, and avoid MPEG-4 and H.264 if you can.</p>
1905 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan
">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english
">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/fildeling
">fildeling</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia
">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug
">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett
">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern
">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard
">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video
">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web
">web</a>.
1910 <div class="padding
"></div>
1914 <a href="http://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>
1920 <p>In the <a href="http://popcon.debian.org/unknown/by_vote
">Debian
1921 popularity-contest numbers</a>, the adobe-flashplugin package the
1922 second most popular used package that is missing in Debian. The sixth
1923 most popular is flashplayer-mozilla. This is a clear indication that
1924 working flash is important for Debian users. Around 10 percent of the
1925 users submitting data to popcon.debian.org have this package
1928 <p>In the report written by Lars Risan in August 2008
1929 («<a href="http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile&do=view&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
1930 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
1931 stiftelsen SLX Debian Labs</a>»), one of the most important problems
1932 schools experienced with <a href="http://www.skolelinux.org/
">Debian
1933 Edu/Skolelinux</a> was the lack of working Flash. A lot of educational
1934 web sites require Flash to work, and lacking working Flash support in
1935 the web browser and the problems with installing it was perceived as a
1936 good reason to stay with Windows.</p>
1938 <p>I once saw a funny and sad comment in a web forum, where Linux was
1939 said to be the retarded cousin that did not really understand
1940 everything you told him but could work fairly well. This was a
1941 comment regarding the problems Linux have with proprietary formats and
1942 non-standard web pages, and is sad because it exposes a fairly common
1943 understanding of whose fault it is if web pages that only work in for
1944 example Internet Explorer 6 fail to work on Firefox, and funny because
1945 it explain very well how annoying it is for users when Linux
1946 distributions do not work with the documents they receive or the web
1947 pages they want to visit.</p>
1949 <p>This is part of the reason why I believe it is important for Debian
1950 and Debian Edu to have a well working Flash implementation in the
1951 distribution, to get at least popular sites as Youtube and Google
1952 Video to working out of the box. For Squeeze, Debian have the chance
1953 to include the latest version of Gnash that will make this happen, as
1954 the new release 0.8.8 was published a few weeks ago and is resting in
1955 unstable. The new version work with more sites that version 0.8.7.
1956 The Gnash maintainers have asked for a freeze exception, but the
1957 release team have not had time to reply to it yet. I hope they agree
1958 with me that Flash is important for the Debian desktop users, and thus
1959 accept the new package into Squeeze.</p>
1965 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian
">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu
">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english
">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia
">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video
">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web
">web</a>.
1970 <div class="padding
"></div>
1974 <a href="http://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>
1980 <p>For å forstå mer om hvorfor standardkatalogens versjon 2 ble som
1981 den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
1982 for regjeringen da de tok sin avgjørelse. De er nå lagt ut på NUUGs
1983 wiki, direkte tilgjengelig via "<a
1984 href=
"http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon.pdf">Referansekatalogen
1985 v2.0 - Oppsummering av høring
</a>" og "<a
1986 href=
"http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon-katalogutkast.pdf">Referansekatalog
1987 for IT-standarder i offentlig sektor Versjon
2.0, dd.mm.åååå -
1990 <p>Det er tre ting jeg merker meg i oppsummeringen fra
1991 høringsuttalelsen da jeg skummet igjennom den. Det første er at
1992 forståelsen av hvordan programvarepatenter påvirker fri
1993 programvareutvikling også i Norge når en argumenterer med at
1994 royalty-betaling ikke er et relevant problem i Norge. Det andre er at
1995 FAD ikke har en prinsipiell forståelse av verdien av en enkelt
1996 standard innenfor hvert område. Det siste er at påstander i
1997 høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
1998 Microsoft om hvordan Ogg blir standardisert og påstanden fra
1999 politidirektoratet om patentproblemer i Theora).</p>
2005 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia
">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk
">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug
">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard
">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video
">video</a>.
2010 <div class="padding
"></div>
2014 <a href="http://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>
2020 <p>Jeg ble glad da regjeringen
2021 <a href="http://www.digi.no/
817635/her-er-statens-nye-it-standarder
">annonserte</a>
2023 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf
">statens
2024 referansekatalog over standarder</a>, men trist da jeg leste hva som
2025 faktisk var vedtatt etter
2026 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/
2009/horing---referansekatalog-versjon-
2.html
">høringen</a>.
2027 De fleste av de valgte åpne standardene er gode og vil bidra til at
2028 alle kan delta på like vilkår i å lage løsninger for staten, men
2029 noen av dem blokkerer for de som ikke har anledning til å benytte
2030 spesifikasjoner som krever betaling for bruk (såkalt
2031 royalty-betaling). Det gjelder spesifikt for H.264 for video og MP3
2032 for lyd. Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
2033 Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
2034 fra statens websider gjøre dette uten å måtte bruke programmer der
2035 betaling for bruk var nødvendig. Når det nå er gjort valgfritt for
2036 de statlige etatene å bruke enten H.264 eller Theora (og MP3 eler
2037 Vorbis), så vil en bli tvunget til å forholde seg til
2038 royalty-belastede standarder for å få tilgang til videoen og
2041 <p>Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
2042 at alle standarder som ble valgt til å være påkrevd i katalogen skulle
2043 være uten royalty-betaling. Jeg håper det ikke betyr at en har mistet
2044 all forståelse for hvilke prinsipper som må følges for å oppnå
2045 likeverdig konkurranse mellom aktørene i IT-bransjen. NUUG advarte
2047 <a href="http://wiki.nuug.no/uttalelser/
200901-standardkatalog-v2
">sin
2048 høringsuttalelse</a>, men ser ut til å ha blitt ignorert.</p>
2050 <p>Oppdatering 2012-06-29: Kom over <ahref="
2051 http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf
">en
2052 rapport til FAD</a> fra da versjon 1 av katalogen ble vedtatt, og der
2053 er det tydelig at problemstillingen var kjent og forstått.</p>
2059 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia
">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk
">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug
">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard
">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video
">video</a>.
2064 <div class="padding
"></div>
2068 <a href="http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html
">Microsofts misvisende argumentasjon rundt multimediaformater</a>
2075 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf
">Microsoft
2076 sin høringsuttalelse</a> til
2077 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/
2009/horing---referansekatalog-versjon-
2.html?id=
549422">forslag
2078 til versjon 2 av statens referansekatalog over standarder</a>, lirer
2079 de av seg følgende FUD-perle:</p>
2081 <p><blockquote>"Vorbis, OGG, Theora og FLAC er alle tekniske
2082 spesifikasjoner overordnet styrt av xiph.org, som er en
2083 ikke-kommersiell organisasjon. Etablerte og anerkjente
2084 standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
2085 innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
2086 Det er derimot helt opp til hver enkelt organisasjon å bestemme
2087 hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
2088 spesifikasjonene bør derfor ikke defineres som åpne
2089 standarder.
"</blockquote></p>
2091 <p>De vokter seg vel for å nevne den anerkjente
2092 standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
2093 IP og det meste av protokoller på Internet, og RFC-standardene som
2094 IETF står bak. Ogg er spesifisert i
2095 <a href="http://ietf.org/rfc/rfc3533.txt
">RFC 3533</a>, og er uten
2096 tvil å anse som en åpen standard. Vorbis er
2097 <a href="http://ietf.org/rfc/rfc5215.txt
">RFC 5215</a>. Theora er
2099 under standardisering via IETF, med
2100 <a href="http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-
00.txt
">siste
2101 utkast publisert 2006-07-21</a> (riktignok er dermed teksten ikke
2102 skrevet i stein ennå, men det blir neppe endringer som ikke er
2103 bakoverkompatibel). De kan være inne på noe når det gjelder FLAC da
2104 jeg ikke finner tegn til at <a
2105 href="http://flac.sourceforge.net/format.html
">spesifikasjonen
2106 tilgjengelig på web</a> er på tur via noen
2107 standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
2108 og Vorbis også har involvert seg i Flac siden 2003, så ser jeg ikke
2109 bort fra at også den organiseres via IETF. Jeg kjenner personlig lite
2112 <p>Uredelig argumentasjon bør en holde seg for god til å komme med,
2113 spesielt når det er så enkelt i dagens Internet-hverdag å gå
2114 misvisende påstander etter i sømmene.</p>
2120 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia
">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk
">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard
">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video
">video</a>.
2125 <div class="padding
"></div>
2129 <a href="http://people.skolelinux.org/pere/blog/When_web_browser_developers_make_a_video_player___.html
">When web browser developers make a video player...</a>
2135 <p>As part of the work we do in <a href="http://www.nuug.no
">NUUG</a>
2136 to publish video recordings of our monthly presentations, we provide a
2137 page with embedded video for easy access to the recording. Putting a
2138 good set of HTML tags together to get working embedded video in all
2139 browsers and across all operating systems is not easy. I hope this
2140 will become easier when the <video> tag is implemented in all
2141 browsers, but I am not sure. We provide the recordings in several
2142 formats, MPEG1, Ogg Theora, H.264 and Quicktime, and want the
2143 browser/media plugin to pick one it support and use it to play the
2144 recording, using whatever embed mechanism the browser understand.
2145 There is at least four different tags to use for this, the new HTML5
2146 <video> tag, the <object> tag, the <embed> tag and
2147 the <applet> tag. All of these take a lot of options, and
2148 finding the best options is a major challenge.</p>
2150 <p>I just tested the experimental Opera browser available from <a
2151 href="http://labs.opera.com
">labs.opera.com</a>, to see how it handled
2152 a <video> tag with a few video sources and no extra attributes.
2153 I was not very impressed. The browser start by fetching a picture
2154 from the video stream. Not sure if it is the first frame, but it is
2155 definitely very early in the recording. So far, so good. Next,
2156 instead of streaming the 76 MiB video file, it start to download all
2157 of it, but do not start to play the video. This mean I have to wait
2158 for several minutes for the downloading to finish. When the download
2159 is done, the playing of the video do not start! Waiting for the
2160 download, but I do not get to see the video? Some testing later, I
2161 discover that I have to add the controls="true" attribute to be able
2162 to get a play button to pres to start the video. Adding
2163 autoplay="true" did not help. I sure hope this is a misfeature of the
2164 test version of Opera, and that future implementations of the
2165 <video
> tag will stream recordings by default, or at least start
2166 playing when the download is done.
</p>
2168 <p>The test page I used (since changed to add more attributes) is
2169 <a href=
"http://www.nuug.no/aktiviteter/20090113-foredrag-om-foredrag/">available
2170 from the nuug site
</a>. Will have to test it with the new Firefox
2173 <p>In the test process, I discovered a missing feature. I was unable
2174 to find a way to get the URL of the playing video out of Opera, so I
2175 am not quite sure it picked the Ogg Theora version of the video. I
2176 sure hope it was using the announced Ogg Theora support. :)
</p>
2182 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/nuug">nuug
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
2187 <div class=
"padding"></div>
2191 <a href=
"http://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>
2197 <p>Recently I have spent some time evaluating the multimedia browser
2198 plugins available in Debian Lenny, to see which one we should use by
2199 default in Debian Edu. We need an embedded video playing plugin with
2200 control buttons to pause or stop the video, and capable of streaming
2201 all the multimedia content available on the web. The test results and
2202 notes are available on
2203 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia">the
2204 Debian wiki
</a>. I was surprised how few of the plugins are able to
2205 fill this need. My personal video player favorite, VLC, has a really
2206 bad plugin which fail on a lot of the test pages. A lot of the MIME
2207 types I would expect to work with any free software player (like
2208 video/ogg), just do not work. And simple formats like the
2209 audio/x-mplegurl format (m3u playlists), just isn't supported by the
2210 totem and vlc plugins. I hope the situation will improve soon. No
2211 wonder sites use the proprietary Adobe flash to play video.
</p>
2213 <p>For Lenny, we seem to end up with the mplayer plugin. It seem to
2214 be the only one fitting our needs. :/
</p>
2220 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
2225 <div class=
"padding"></div>
2227 <p style=
"text-align: right;"><a href=
"multimedia.rss"><img src=
"http://people.skolelinux.org/pere/blog/xml.gif" alt=
"RSS Feed" width=
"36" height=
"14" /></a></p>
2238 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/01/">January (
2)
</a></li>
2240 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/02/">February (
3)
</a></li>
2242 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/03/">March (
8)
</a></li>
2244 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/04/">April (
7)
</a></li>
2246 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/05/">May (
1)
</a></li>
2248 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/06/">June (
2)
</a></li>
2250 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/07/">July (
2)
</a></li>
2252 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/08/">August (
2)
</a></li>
2254 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/09/">September (
4)
</a></li>
2261 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/01/">January (
11)
</a></li>
2263 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/02/">February (
9)
</a></li>
2265 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/03/">March (
9)
</a></li>
2267 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/04/">April (
6)
</a></li>
2269 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/05/">May (
9)
</a></li>
2271 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/06/">June (
10)
</a></li>
2273 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/07/">July (
7)
</a></li>
2275 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/08/">August (
3)
</a></li>
2277 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/09/">September (
5)
</a></li>
2279 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/10/">October (
7)
</a></li>
2281 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/11/">November (
9)
</a></li>
2283 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/12/">December (
3)
</a></li>
2290 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/01/">January (
7)
</a></li>
2292 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/02/">February (
10)
</a></li>
2294 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/03/">March (
17)
</a></li>
2296 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/04/">April (
12)
</a></li>
2298 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/05/">May (
12)
</a></li>
2300 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/06/">June (
20)
</a></li>
2302 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/07/">July (
17)
</a></li>
2304 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/08/">August (
6)
</a></li>
2306 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/09/">September (
9)
</a></li>
2308 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/10/">October (
17)
</a></li>
2310 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/11/">November (
10)
</a></li>
2312 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/12/">December (
7)
</a></li>
2319 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/01/">January (
16)
</a></li>
2321 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/02/">February (
6)
</a></li>
2323 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/03/">March (
6)
</a></li>
2325 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/04/">April (
7)
</a></li>
2327 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/05/">May (
3)
</a></li>
2329 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/06/">June (
2)
</a></li>
2331 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/07/">July (
7)
</a></li>
2333 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/08/">August (
6)
</a></li>
2335 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/09/">September (
4)
</a></li>
2337 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/10/">October (
2)
</a></li>
2339 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/11/">November (
3)
</a></li>
2341 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/12/">December (
1)
</a></li>
2348 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/01/">January (
2)
</a></li>
2350 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/02/">February (
1)
</a></li>
2352 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/03/">March (
3)
</a></li>
2354 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/04/">April (
3)
</a></li>
2356 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/05/">May (
9)
</a></li>
2358 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/06/">June (
14)
</a></li>
2360 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/07/">July (
12)
</a></li>
2362 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/08/">August (
13)
</a></li>
2364 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/09/">September (
7)
</a></li>
2366 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/10/">October (
9)
</a></li>
2368 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/11/">November (
13)
</a></li>
2370 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/12/">December (
12)
</a></li>
2377 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/01/">January (
8)
</a></li>
2379 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/02/">February (
8)
</a></li>
2381 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/03/">March (
12)
</a></li>
2383 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/04/">April (
10)
</a></li>
2385 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/05/">May (
9)
</a></li>
2387 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/06/">June (
3)
</a></li>
2389 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/07/">July (
4)
</a></li>
2391 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/08/">August (
3)
</a></li>
2393 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/09/">September (
1)
</a></li>
2395 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/10/">October (
2)
</a></li>
2397 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/11/">November (
3)
</a></li>
2399 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/12/">December (
3)
</a></li>
2406 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/11/">November (
5)
</a></li>
2408 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/12/">December (
7)
</a></li>
2419 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (
13)
</a></li>
2421 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/amiga">amiga (
1)
</a></li>
2423 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/aros">aros (
1)
</a></li>
2425 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bankid">bankid (
4)
</a></li>
2427 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (
8)
</a></li>
2429 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (
14)
</a></li>
2431 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bsa">bsa (
2)
</a></li>
2433 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (
2)
</a></li>
2435 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian (
102)
</a></li>
2437 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (
149)
</a></li>
2439 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/digistan">digistan (
10)
</a></li>
2441 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/dld">dld (
15)
</a></li>
2443 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/docbook">docbook (
12)
</a></li>
2445 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (
4)
</a></li>
2447 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/english">english (
254)
</a></li>
2449 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (
21)
</a></li>
2451 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (
12)
</a></li>
2453 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (
13)
</a></li>
2455 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (
8)
</a></li>
2457 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (
11)
</a></li>
2459 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/intervju">intervju (
41)
</a></li>
2461 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (
9)
</a></li>
2463 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/kart">kart (
19)
</a></li>
2465 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ldap">ldap (
9)
</a></li>
2467 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/lenker">lenker (
8)
</a></li>
2469 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (
1)
</a></li>
2471 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (
8)
</a></li>
2473 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (
30)
</a></li>
2475 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk (
248)
</a></li>
2477 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/nuug">nuug (
162)
</a></li>
2479 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (
11)
</a></li>
2481 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/open311">open311 (
2)
</a></li>
2483 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (
48)
</a></li>
2485 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/personvern">personvern (
75)
</a></li>
2487 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/raid">raid (
1)
</a></li>
2489 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/reactos">reactos (
1)
</a></li>
2491 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/reprap">reprap (
11)
</a></li>
2493 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rfid">rfid (
3)
</a></li>
2495 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/robot">robot (
9)
</a></li>
2497 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rss">rss (
1)
</a></li>
2499 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ruter">ruter (
4)
</a></li>
2501 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (
2)
</a></li>
2503 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (
41)
</a></li>
2505 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (
4)
</a></li>
2507 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (
4)
</a></li>
2509 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard (
45)
</a></li>
2511 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (
3)
</a></li>
2513 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (
9)
</a></li>
2515 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (
26)
</a></li>
2517 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (
1)
</a></li>
2519 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/valg">valg (
8)
</a></li>
2521 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/video">video (
43)
</a></li>
2523 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (
4)
</a></li>
2525 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/web">web (
33)
</a></li>
2531 <p style=
"text-align: right">
2532 Created by
<a href=
"http://steve.org.uk/Software/chronicle">Chronicle v4.6
</a>