]> pere.pagekite.me Git - homepage.git/blob - blog/tags/multimedia/multimedia.rss
b080c78bbacffa9932baa6f38c366ce9d8a5a417
[homepage.git] / blog / tags / multimedia / multimedia.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
3 <channel>
4 <title>Petter Reinholdtsen - Entries tagged multimedia</title>
5 <description>Entries tagged multimedia</description>
6 <link>http://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>Hvordan vurderer regjeringen H.264-patentutfordringen?</title>
11 <link>http://people.skolelinux.org/pere/blog/Hvordan_vurderer_regjeringen_H_264_patentutfordringen_.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hvordan_vurderer_regjeringen_H_264_patentutfordringen_.html</guid>
13 <pubDate>Sun, 16 Nov 2014 10:30:00 +0100</pubDate>
14 <description>&lt;p&gt;For en stund tilbake spurte jeg Fornyingsdepartementet om hvilke
15 juridiske vurderinger rundt patentproblemstillingen som var gjort da
16 H.264 ble tatt inn i &lt;a href=&quot;http://standard.difi.no/&quot;&gt;statens
17 referansekatalog over standarder&lt;/a&gt;. Stig Hornnes i FAD tipset meg
18 om følgende som står i oppsumeringen til høringen om
19 referansekatalogen versjon 2.0, som jeg siden ved hjelp av en
20 innsynsforespørsel fikk tak i
21 &lt;a href=&quot;http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&amp;do=get&amp;target=kongelig-resolusjon.pdf&quot;&gt;PDF-utgaven&lt;/a&gt;
22 datert 2009-06-03 (saksnummer 200803291, saksbehandler Henrik
23 Linnestad).&lt;/p&gt;
24
25 &lt;p&gt;Der står det følgende om problemstillingen:&lt;/p&gt;
26
27 &lt;p&gt;&lt;blockquote&gt;
28 &lt;strong&gt;4.4 Patentproblematikk&lt;/strong&gt;
29
30 &lt;p&gt;NUUG og Opera ser det som særlig viktig at forslagene knyttet til
31 lyd og video baserer seg på de royalty-frie standardene Vorbis, Theora
32 og FLAC.&lt;/p&gt;
33
34 &lt;p&gt;Kommentarene relaterer seg til at enkelte standarder er åpne, men
35 inneholder tekniske prosedyrer som det i USA (og noen andre land som
36 Japan) er gitt patentrettigheter til. I vårt tilfelle berører dette
37 spesielt standardene Mp3 og H.264, selv om Politidirektoratet peker på
38 at det muligens kan være tilsvarende problematikk også for Theora og
39 Vorbis. Dette medfører at det i USA kan kreves royalties for bruk av
40 tekniske løsninger knyttet til standardene, et krav som også
41 håndheves. Patenter kan imidlertid bare hevdes i de landene hvor
42 patentet er gitt, så amerikanske patenter gjelder ikke andre steder
43 enn USA.&lt;/p&gt;
44
45 &lt;p&gt;Spesielt for utvikling av fri programvare er patenter
46 problematisk. GPL, en &quot;grunnleggende&quot; lisens for distribusjon av fri
47 programvare, avviser at programvare kan distribueres under denne
48 lisensen hvis det inneholder referanser til patenterte rutiner som
49 utløser krav om royalties. Det er imidlertid uproblematisk å
50 distribuere fri programvareløsninger under GPL som benytter de
51 aktuelle standardene innen eller mellom land som ikke anerkjenner
52 patentene. Derfor finner vi også flere implementeringer av Mp3 og
53 H.264 som er fri programvare, lisensiert under GPL.&lt;/p&gt;
54
55 &lt;p&gt;I Norge og EU er patentlovgivningen langt mer restriktiv enn i USA,
56 men det er også her mulig å få patentert metoder for løsning av et
57 problem som relaterer seg til databehandling. Det er AIF bekjent ikke
58 relevante patenter i EU eller Norge hva gjelder H.264 og Mp3, men
59 muligheten for at det finnes patenter uten at det er gjort krav om
60 royalties eller at det senere vil gis slike patenter kan ikke helt
61 avvises.&lt;/p&gt;
62
63 &lt;p&gt;AIF mener det er et behov for å gi offentlige virksomheter mulighet
64 til å benytte antatt royaltyfrie åpne standarder som et likeverdig
65 alternativ eller i tillegg til de markedsledende åpne standardene.&lt;/p&gt;
66
67 &lt;/blockquote&gt;&lt;/p&gt;
68
69 &lt;p&gt;Det ser dermed ikke ut til at de har vurdert patentspørsmålet i
70 sammenheng med opphavsrettsvilkår slik de er formulert for f.eks.
71 Apple Final Cut Pro, Adobe Premiere Pro, Avid og Sorenson-verktøyene,
72 der det kreves brukstillatelse for patenter som ikke er gyldige i
73 Norge for å bruke disse verktøyene til annet en personlig og ikke
74 kommersiell aktivitet når det gjelder H.264-video. Jeg må nok lete
75 videre etter svar på det spørsmålet.&lt;/p&gt;
76 </description>
77 </item>
78
79 <item>
80 <title>New lsdvd release version 0.17 is ready</title>
81 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
82 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
83 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
84 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
85 got a new set of developers a few weeks ago, after the original
86 developer decided to step down and pass the project to fresh blood.
87 This project is now maintained by Petter Reinholdtsen and Steve
88 Dibb.&lt;/p&gt;
89
90 &lt;p&gt;I just wrapped up
91 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
92 new lsdvd release&lt;/a&gt;, available in git or from
93 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
94 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
95 0.17.&lt;/p&gt;
96
97 &lt;ul&gt;
98
99 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
100 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
101 non-existant, to work around additional copy protection&lt;/li&gt;
102 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
103 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
104 &lt;li&gt;Fix include orders&lt;/li&gt;
105 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
106 &lt;li&gt;Fix the chapter count&lt;/li&gt;
107 &lt;li&gt;Make sure the array size and the array limit used when initialising
108 the palette size is the same.&lt;/li&gt;
109 &lt;li&gt;Fix array printing.&lt;/li&gt;
110 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
111 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
112 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
113 with more GCC compiler warnings.&lt;/li&gt;
114
115 &lt;/ul&gt;
116
117 &lt;p&gt;This change bring together patches for lsdvd in use in various
118 Linux and Unix distributions, as well as patches submitted to the
119 project the last nine years. Please check it out. :)&lt;/p&gt;
120 </description>
121 </item>
122
123 <item>
124 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
125 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
126 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
127 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
128 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
129 to handle my fairly large DVD collection. It is a nice command line
130 tool to get details about a DVD, like title, tracks, track length,
131 etc, in XML, Perl or human readable format. But lsdvd have not seen
132 any new development since 2006 and had a few irritating bugs affecting
133 its use with some DVDs. Upstream seemed to be dead, and in January I
134 sent a small probe asking for a version control repository for the
135 project, without any reply. But I use it regularly and would like to
136 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
137 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
138 the project admin, and after getting a reply from him explaining that
139 he was no longer interested in the project, I asked if I could take
140 over. And yesterday, I became project admin.&lt;/p&gt;
141
142 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
143 maintainer interested in joining forces to maintain the upstream
144 project, and I hope we can get a new release out fairly quickly,
145 collecting the patches spread around on the internet into on place.
146 I&#39;ve added the relevant Debian patches to the freshly created git
147 repository, and expect the Gentoo patches to make it too. If you got
148 a DVD collection and care about command line tools, check out
149 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
150 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
151 list&lt;/a&gt;. :)&lt;/p&gt;
152 </description>
153 </item>
154
155 <item>
156 <title>Do you need an agreement with MPEG-LA to publish and broadcast H.264 video in Norway?</title>
157 <link>http://people.skolelinux.org/pere/blog/Do_you_need_an_agreement_with_MPEG_LA_to_publish_and_broadcast_H_264_video_in_Norway_.html</link>
158 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Do_you_need_an_agreement_with_MPEG_LA_to_publish_and_broadcast_H_264_video_in_Norway_.html</guid>
159 <pubDate>Mon, 25 Aug 2014 22:10:00 +0200</pubDate>
160 <description>&lt;p&gt;Two years later, I am still not sure if it is legal here in Norway
161 to use or publish a video in H.264 or MPEG4 format edited by the
162 commercially licensed video editors, without limiting the use to
163 create &quot;personal&quot; or &quot;non-commercial&quot; videos or get a license
164 agreement with &lt;a href=&quot;http://www.mpegla.com&quot;&gt;MPEG LA&lt;/a&gt;. If one
165 want to publish and broadcast video in a non-personal or commercial
166 setting, it might be that those tools can not be used, or that video
167 format can not be used, without breaking their copyright license. I
168 am not sure.
169 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html&quot;&gt;Back
170 then&lt;/a&gt;, I found that the copyright license terms for Adobe Premiere
171 and Apple Final Cut Pro both specified that one could not use the
172 program to produce anything else without a patent license from MPEG
173 LA. The issue is not limited to those two products, though. Other
174 much used products like those from Avid and Sorenson Media have terms
175 of use are similar to those from Adobe and Apple. The complicating
176 factor making me unsure if those terms have effect in Norway or not is
177 that the patents in question are not valid in Norway, but copyright
178 licenses are.&lt;/p&gt;
179
180 &lt;p&gt;These are the terms for Avid Artist Suite, according to their
181 &lt;a href=&quot;http://www.avid.com/US/about-avid/legal-notices/legal-enduserlicense2&quot;&gt;published
182 end user&lt;/a&gt;
183 &lt;a href=&quot;http://www.avid.com/static/resources/common/documents/corporate/LICENSE.pdf&quot;&gt;license
184 text&lt;/a&gt; (converted to lower case text for easier reading):&lt;/p&gt;
185
186 &lt;p&gt;&lt;blockquote&gt;
187 &lt;p&gt;18.2. MPEG-4. MPEG-4 technology may be included with the
188 software. MPEG LA, L.L.C. requires this notice: &lt;/p&gt;
189
190 &lt;p&gt;This product is licensed under the MPEG-4 visual patent portfolio
191 license for the personal and non-commercial use of a consumer for (i)
192 encoding video in compliance with the MPEG-4 visual standard (“MPEG-4
193 video”) and/or (ii) decoding MPEG-4 video that was encoded by a
194 consumer engaged in a personal and non-commercial activity and/or was
195 obtained from a video provider licensed by MPEG LA to provide MPEG-4
196 video. No license is granted or shall be implied for any other
197 use. Additional information including that relating to promotional,
198 internal and commercial uses and licensing may be obtained from MPEG
199 LA, LLC. See http://www.mpegla.com. This product is licensed under
200 the MPEG-4 systems patent portfolio license for encoding in compliance
201 with the MPEG-4 systems standard, except that an additional license
202 and payment of royalties are necessary for encoding in connection with
203 (i) data stored or replicated in physical media which is paid for on a
204 title by title basis and/or (ii) data which is paid for on a title by
205 title basis and is transmitted to an end user for permanent storage
206 and/or use, such additional license may be obtained from MPEG LA,
207 LLC. See http://www.mpegla.com for additional details.&lt;/p&gt;
208
209 &lt;p&gt;18.3. H.264/AVC. H.264/AVC technology may be included with the
210 software. MPEG LA, L.L.C. requires this notice:&lt;/p&gt;
211
212 &lt;p&gt;This product is licensed under the AVC patent portfolio license for
213 the personal use of a consumer or other uses in which it does not
214 receive remuneration to (i) encode video in compliance with the AVC
215 standard (“AVC video”) and/or (ii) decode AVC video that was encoded
216 by a consumer engaged in a personal activity and/or was obtained from
217 a video provider licensed to provide AVC video. No license is granted
218 or shall be implied for any other use. Additional information may be
219 obtained from MPEG LA, L.L.C. See http://www.mpegla.com.&lt;/p&gt;
220 &lt;/blockquote&gt;&lt;/p&gt;
221
222 &lt;p&gt;Note the requirement that the videos created can only be used for
223 personal or non-commercial purposes.&lt;/p&gt;
224
225 &lt;p&gt;The Sorenson Media software have
226 &lt;a href=&quot;http://www.sorensonmedia.com/terms/&quot;&gt;similar terms&lt;/a&gt;:&lt;/p&gt;
227
228 &lt;p&gt;&lt;blockquote&gt;
229
230 &lt;p&gt;With respect to a license from Sorenson pertaining to MPEG-4 Video
231 Decoders and/or Encoders: Any such product is licensed under the
232 MPEG-4 visual patent portfolio license for the personal and
233 non-commercial use of a consumer for (i) encoding video in compliance
234 with the MPEG-4 visual standard (“MPEG-4 video”) and/or (ii) decoding
235 MPEG-4 video that was encoded by a consumer engaged in a personal and
236 non-commercial activity and/or was obtained from a video provider
237 licensed by MPEG LA to provide MPEG-4 video. No license is granted or
238 shall be implied for any other use. Additional information including
239 that relating to promotional, internal and commercial uses and
240 licensing may be obtained from MPEG LA, LLC. See
241 http://www.mpegla.com.&lt;/p&gt;
242
243 &lt;p&gt;With respect to a license from Sorenson pertaining to MPEG-4
244 Consumer Recorded Data Encoder, MPEG-4 Systems Internet Data Encoder,
245 MPEG-4 Mobile Data Encoder, and/or MPEG-4 Unique Use Encoder: Any such
246 product is licensed under the MPEG-4 systems patent portfolio license
247 for encoding in compliance with the MPEG-4 systems standard, except
248 that an additional license and payment of royalties are necessary for
249 encoding in connection with (i) data stored or replicated in physical
250 media which is paid for on a title by title basis and/or (ii) data
251 which is paid for on a title by title basis and is transmitted to an
252 end user for permanent storage and/or use. Such additional license may
253 be obtained from MPEG LA, LLC. See http://www.mpegla.com for
254 additional details.&lt;/p&gt;
255
256 &lt;/blockquote&gt;&lt;/p&gt;
257
258 &lt;p&gt;Some free software like
259 &lt;a href=&quot;https://handbrake.fr/&quot;&gt;Handbrake&lt;/A&gt; and
260 &lt;a href=&quot;http://ffmpeg.org/&quot;&gt;FFMPEG&lt;/a&gt; uses GPL/LGPL licenses and do
261 not have any such terms included, so for those, there is no
262 requirement to limit the use to personal and non-commercial.&lt;/p&gt;
263 </description>
264 </item>
265
266 <item>
267 <title>Hvordan enkelt laste ned filmer fra NRK med den &quot;nye&quot; løsningen</title>
268 <link>http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html</link>
269 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html</guid>
270 <pubDate>Mon, 16 Jun 2014 19:20:00 +0200</pubDate>
271 <description>&lt;p&gt;Jeg har fortsatt behov for å kunne laste ned innslag fra NRKs
272 nettsted av og til for å se senere når jeg ikke er på nett, men
273 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html&quot;&gt;min
274 oppskrift fra 2011&lt;/a&gt; sluttet å fungere da NRK byttet
275 avspillermetode. I dag fikk jeg endelig lett etter oppdatert løsning,
276 og jeg er veldig glad for å fortelle at den enkleste måten å laste ned
277 innslag er å bruke siste versjon 2014.06.07 av
278 &lt;a href=&quot;http://rg3.github.io/youtube-dl/&quot;&gt;youtube-dl&lt;/a&gt;. Støtten i
279 youtube-dl &lt;a href=&quot;https://github.com/rg3/youtube-dl/issues/2980&quot;&gt;kom
280 inn for 23 dager siden&lt;/a&gt; og
281 &lt;a href=&quot;http://packages.qa.debian.org/y/youtube-dl.html&quot;&gt;versjonen i
282 Debian&lt;/a&gt; fungerer fint også som backport til Debian Wheezy. Det er
283 et lite problem, det håndterer kun URLer med små bokstaver, men hvis
284 en har en URL med store bokstaver kan en bare gjøre alle store om til
285 små bokstaver for å få youtube-dl til å laste ned. Rapporterte
286 nettopp
287 &lt;a href=&quot;https://github.com/rg3/youtube-dl/issues/2980&quot;&gt;problemet til
288 utviklerne&lt;/a&gt;, og antar de får fikset det snart.&lt;/p&gt;
289
290 &lt;p&gt;Dermed er alt klart til å laste ned dokumentarene om
291 &lt;a href=&quot;http://tv.nrk.no/program/KOID23005014/usas-hemmelige-avlytting&quot;&gt;USAs
292 hemmelige avlytting&lt;/a&gt; og
293 &lt;a href=&quot;http://tv.nrk.no/program/KOID23005114/selskapene-bak-usas-avlytting&quot;&gt;Selskapene
294 bak USAs avlytting&lt;/a&gt;, i tillegg til
295 &lt;a href=&quot;http://tv.nrk.no/program/KOID20005814/et-moete-med-edward-snowden&quot;&gt;intervjuet
296 med Edward Snowden gjort av den tyske tv-kanalen ARD&lt;/a&gt;. Anbefaler
297 alle å se disse, sammen med
298 &lt;a href=&quot;http://media.ccc.de/browse/congress/2013/30C3_-_5713_-_en_-_saal_2_-_201312301130_-_to_protect_and_infect_part_2_-_jacob.html&quot;&gt;foredraget
299 til Jacob Appelbaum på siste CCC-konferanse&lt;/a&gt;, for å forstå mer om
300 hvordan overvåkningen av borgerne brer om seg.&lt;/p&gt;
301
302 &lt;p&gt;Takk til gode venner på foreningen NUUGs IRC-kanal
303 &lt;a href=&quot;irc://irc.freenode.net/%23nuug&quot;&gt;#nuug på irc.freenode.net&lt;/a&gt;
304 for tipsene som fikk meg i mål&lt;/a&gt;.&lt;/p&gt;
305
306 &lt;p&gt;&lt;strong&gt;Oppdatering 2014-06-17&lt;/strong&gt;: Etter at jeg publiserte
307 denne, ble jeg tipset om bloggposten
308 &quot;&lt;a href=&quot;http://ingvar.blog.redpill-linpro.com/2012/05/31/downloading-hd-content-from-tv-nrk-no/&quot;&gt;Downloading
309 HD content from tv.nrk.no&lt;/a&gt;&quot; av Ingvar Hagelund, som har alternativ
310 implementasjon og tips for å lage mkv-fil med undertekstene inkludert.
311 Kanskje den passer bedre for deg? I tillegg ble feilen i youtube-dl
312 ble fikset litt senere ut på dagen i går, samt at youtube-dl fikk
313 støtte for å laste ned undertitler. Takk til Anders Einar Hilden for
314 god innsats og youtube-dl-utviklerne for rask respons.&lt;/p&gt;
315 </description>
316 </item>
317
318 <item>
319 <title>Half the Coverity issues in Gnash fixed in the next release</title>
320 <link>http://people.skolelinux.org/pere/blog/Half_the_Coverity_issues_in_Gnash_fixed_in_the_next_release.html</link>
321 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Half_the_Coverity_issues_in_Gnash_fixed_in_the_next_release.html</guid>
322 <pubDate>Tue, 29 Apr 2014 14:20:00 +0200</pubDate>
323 <description>&lt;p&gt;I&#39;ve been following &lt;a href=&quot;http://www.getgnash.org/&quot;&gt;the Gnash
324 project&lt;/a&gt; for quite a while now. It is a free software
325 implementation of Adobe Flash, both a standalone player and a browser
326 plugin. Gnash implement support for the AVM1 format (and not the
327 newer AVM2 format - see
328 &lt;a href=&quot;http://lightspark.github.io/&quot;&gt;Lightspark&lt;/a&gt; for that one),
329 allowing several flash based sites to work. Thanks to the friendly
330 developers at Youtube, it also work with Youtube videos, because the
331 Javascript code at Youtube detect Gnash and serve a AVM1 player to
332 those users. :) Would be great if someone found time to implement AVM2
333 support, but it has not happened yet. If you install both Lightspark
334 and Gnash, Lightspark will invoke Gnash if it find a AVM1 flash file,
335 so you can get both handled as free software. Unfortunately,
336 Lightspark so far only implement a small subset of AVM2, and many
337 sites do not work yet.&lt;/p&gt;
338
339 &lt;p&gt;A few months ago, I started looking at
340 &lt;a href=&quot;http://scan.coverity.com/&quot;&gt;Coverity&lt;/a&gt;, the static source
341 checker used to find heaps and heaps of bugs in free software (thanks
342 to the donation of a scanning service to free software projects by the
343 company developing this non-free code checker), and Gnash was one of
344 the projects I decided to check out. Coverity is able to find lock
345 errors, memory errors, dead code and more. A few days ago they even
346 extended it to also be able to find the heartbleed bug in OpenSSL.
347 There are heaps of checks being done on the instrumented code, and the
348 amount of bogus warnings is quite low compared to the other static
349 code checkers I have tested over the years.&lt;/p&gt;
350
351 &lt;p&gt;Since a few weeks ago, I&#39;ve been working with the other Gnash
352 developers squashing bugs discovered by Coverity. I was quite happy
353 today when I checked the current status and saw that of the 777 issues
354 detected so far, 374 are marked as fixed. This make me confident that
355 the next Gnash release will be more stable and more dependable than
356 the previous one. Most of the reported issues were and are in the
357 test suite, but it also found a few in the rest of the code.&lt;/p&gt;
358
359 &lt;p&gt;If you want to help out, you find us on
360 &lt;a href=&quot;https://lists.gnu.org/mailman/listinfo/gnash-dev&quot;&gt;the
361 gnash-dev mailing list&lt;/a&gt; and on
362 &lt;a href=&quot;irc://irc.freenode.net/#gnash&quot;&gt;the #gnash channel on
363 irc.freenode.net IRC server&lt;/a&gt;.&lt;/p&gt;
364 </description>
365 </item>
366
367 <item>
368 <title>Video DVD reader library / python-dvdvideo - nice free software</title>
369 <link>http://people.skolelinux.org/pere/blog/Video_DVD_reader_library___python_dvdvideo___nice_free_software.html</link>
370 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Video_DVD_reader_library___python_dvdvideo___nice_free_software.html</guid>
371 <pubDate>Fri, 21 Mar 2014 15:25:00 +0100</pubDate>
372 <description>&lt;p&gt;Keeping your DVD collection safe from scratches and curious
373 children fingers while still having it available when you want to see a
374 movie is not straight forward. My preferred method at the moment is
375 to store a full copy of the ISO on a hard drive, and use VLC, Popcorn
376 Hour or other useful players to view the resulting file. This way the
377 subtitles and bonus material are still available and using the ISO is
378 just like inserting the original DVD record in the DVD player.&lt;/p&gt;
379
380 &lt;p&gt;Earlier I used dd for taking security copies, but it do not handle
381 DVDs giving read errors (which are quite a few of them). I&#39;ve also
382 tried using
383 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html&quot;&gt;dvdbackup
384 and genisoimage&lt;/a&gt;, but these days I use the marvellous python library
385 and program
386 &lt;a href=&quot;http://bblank.thinkmo.de/blog/new-software-python-dvdvideo&quot;&gt;python-dvdvideo&lt;/a&gt;
387 written by Bastian Blank. It is
388 &lt;a href=&quot;http://packages.qa.debian.org/p/python-dvdvideo.html&quot;&gt;in Debian
389 already&lt;/a&gt; and the binary package name is python3-dvdvideo. Instead
390 of trying to read every block from the DVD, it parses the file
391 structure and figure out which block on the DVD is actually in used,
392 and only read those blocks from the DVD. This work surprisingly well,
393 and I have been able to almost backup my entire DVD collection using
394 this method.&lt;/p&gt;
395
396 &lt;p&gt;So far, python-dvdvideo have failed on between 10 and
397 20 DVDs, which is a small fraction of my collection. The most common
398 problem is
399 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720831&quot;&gt;DVDs
400 using UTF-16 instead of UTF-8 characters&lt;/a&gt;, which according to
401 Bastian is against the DVD specification (and seem to cause some
402 players to fail too). A rarer problem is what seem to be inconsistent
403 DVD structures, as the python library
404 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723079&quot;&gt;claim
405 there is a overlap between objects&lt;/a&gt;. An equally rare problem claim
406 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741878&quot;&gt;some
407 value is out of range&lt;/a&gt;. No idea what is going on there. I wish I
408 knew enough about the DVD format to fix these, to ensure my movie
409 collection will stay with me in the future.&lt;/p&gt;
410
411 &lt;p&gt;So, if you need to keep your DVDs safe, back them up using
412 python-dvdvideo. :)&lt;/p&gt;
413 </description>
414 </item>
415
416 <item>
417 <title>IETF activity to standardise video codec</title>
418 <link>http://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html</link>
419 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html</guid>
420 <pubDate>Sat, 15 Sep 2012 20:00:00 +0200</pubDate>
421 <description>&lt;p&gt;After the
422 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html&quot;&gt;Opus
423 codec made&lt;/a&gt; it into &lt;a href=&quot;http://www.ietf.org/&quot;&gt;IETF&lt;/a&gt; as
424 &lt;a href=&quot;http://tools.ietf.org/html/rfc6716&quot;&gt;RFC 6716&lt;/a&gt;, I had a look
425 to see if there is any activity in IETF to standardise a video codec
426 too, and I was happy to discover that there is some activity in this
427 area. A non-&quot;working group&quot; mailing list
428 &lt;a href=&quot;https://www.ietf.org/mailman/listinfo/video-codec&quot;&gt;video-codec&lt;/a&gt;
429 was
430 &lt;a href=&quot;http://ietf.10.n7.nabble.com/New-Non-WG-Mailing-List-video-codec-Video-codec-BoF-discussion-list-td119548.html&quot;&gt;created 2012-08-20&lt;/a&gt;. It is intended to discuss the topic and if a
431 formal working group should be formed.&lt;/p&gt;
432
433 &lt;p&gt;I look forward to see how this plays out. There is already
434 &lt;a href=&quot;http://www.ietf.org/mail-archive/web/video-codec/current/msg00003.html&quot;&gt;an
435 email from someone&lt;/a&gt; in the MPEG group at ISO asking people to
436 participate in the ISO group. Given how ISO failed with OOXML and given
437 that it so far (as far as I can remember) only have produced
438 multimedia formats requiring royalty payments, I suspect
439 joining the ISO group would be a complete waste of time, but I am not
440 involved in any codec work and my opinion will not matter much.&lt;/p&gt;
441
442 &lt;p&gt;If one of my readers is involved with codec work, I hope she will
443 join this work to standardise a royalty free video codec within
444 IETF.&lt;/p&gt;
445 </description>
446 </item>
447
448 <item>
449 <title>IETF standardize its first multimedia codec: Opus</title>
450 <link>http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html</link>
451 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html</guid>
452 <pubDate>Wed, 12 Sep 2012 13:50:00 +0200</pubDate>
453 <description>&lt;p&gt;Yesterday, &lt;a href=&quot;http://www.ietf.org/&quot;&gt;IETF&lt;/a&gt; announced the
454 publication of of
455 &lt;a href=&quot;http://tools.ietf.org/html/rfc6716&quot;&gt;RFC 6716, the Definition
456 of the Opus Audio Codec&lt;/a&gt;, a low latency, variable bandwidth, codec
457 intended for both VoIP, film and music. This is the first time, as
458 far as I know, that IETF have standardized a multimedia codec. In
459 &lt;a href=&quot;http://tools.ietf.org/html/rfc3533&quot;&gt;RFC 3533&lt;/a&gt;, IETF
460 standardized the OGG container format, and it has proven to be a great
461 royalty free container for audio, video and movies. I hope IETF will
462 continue to standardize more royalty free codeces, after ISO and MPEG
463 have proven incapable of securing everyone equal rights to publish
464 multimedia content on the Internet.&lt;/p&gt;
465
466 &lt;p&gt;IETF require two interoperating independent implementations to
467 ratify a standard, and have so far ensured to only standardize royalty
468 free specifications. Both are key factors to allow everyone (rich and
469 poor), to compete on equal terms on the Internet.&lt;/p&gt;
470
471 &lt;p&gt;Visit the &lt;a href=&quot;http://opus-codec.org/&quot;&gt;Opus project page&lt;/a&gt; if
472 you want to learn more about the solution.&lt;/p&gt;
473 </description>
474 </item>
475
476 <item>
477 <title>Git repository for song book for Computer Scientists</title>
478 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
479 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
480 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
481 <description>&lt;p&gt;As I
482 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
483 this summer&lt;/a&gt;, I have created a Computer Science song book a few
484 years ago, and today I finally found time to create a public
485 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
486 repository for the project&lt;/a&gt;.&lt;/p&gt;
487
488 &lt;p&gt;If you want to help out, please clone the source and submit patches
489 to the HTML version. To generate the PDF and PostScript version,
490 please use prince XML, or let me know about a useful free software
491 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
492
493 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
494 PostScript formats at
495 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
496 Science Songbook&lt;/a&gt;.&lt;/p&gt;
497 </description>
498 </item>
499
500 <item>
501 <title>Mer oppfølging fra MPEG-LA om avtale med dem for å kringkaste og publisere H.264-video</title>
502 <link>http://people.skolelinux.org/pere/blog/Mer_oppf_lging_fra_MPEG_LA_om_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html</link>
503 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Mer_oppf_lging_fra_MPEG_LA_om_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html</guid>
504 <pubDate>Thu, 5 Jul 2012 23:50:00 +0200</pubDate>
505 <description>&lt;p&gt;I føljetongen om H.264
506 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html&quot;&gt;forlot
507 jeg leserne i undring&lt;/a&gt; om hvor pakken fra MPEG-LA tok veien, og om
508 hvilke selskaper i Norge som har avtale med MPEG-LA. Da Ryan hos
509 MPEG-LA dro på ferie sendte jeg min melding videre til hans kollega,
510 og dagen etter fikk jeg følgende svar derfra:&lt;/p&gt;
511
512 &lt;p&gt;&lt;blockquote&gt;
513 &lt;p&gt;Date: Fri, 29 Jun 2012 18:32:34 +0000
514 &lt;br&gt;From: Sidney Wolf &amp;lt;SWolf (at) mpegla.com&amp;gt;
515 &lt;br&gt;To: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
516 &lt;br&gt;Cc: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
517 &lt;br&gt;Subject: RE: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
518
519 &lt;p&gt;Dear Mr. Reinholdtsen,&lt;/p&gt;
520
521 &lt;p&gt;Thank you for your message. As you know, Ryan is currently our of the
522 office, so it will be my pleasure to assist you.&lt;/p&gt;
523
524 &lt;p&gt;Per your request, attached please find an electronic copy of the
525 AVC Patent Portfolio License. Please note that the electronic copy of
526 the License is provided as a convenience and for informational
527 purposes only. When concluding the Licenses, only the hard copies
528 provided by MPEG LA may be used.&lt;/p&gt;
529
530 &lt;p&gt;To your question, MPEG LA lists our Licensees on our website
531 according to each program. The lists are in alphabetical order, so it
532 is very easy to search.&lt;/p&gt;
533
534 &lt;p&gt;I hope that this was helpful. If we can be of additional
535 assistance, please let me know.&lt;/p&gt;
536
537 &lt;p&gt;Kind regards,&lt;/p&gt;
538
539 &lt;p&gt;Sidney A. Wolf
540 &lt;br&gt;Manager, Global Licensing
541 &lt;br&gt;MPEG LA&lt;/p&gt;
542 &lt;/blockquote&gt;&lt;/p&gt;
543
544 &lt;p&gt;Selv om et epostvedlegg er nyttig for mottakeren, så håpet jeg å få
545 et dokument jeg kunne dele med alle leserne av bloggen min, og ikke et
546 som må deles på individuell basis. Opphavsretten krever godkjenning
547 fra rettighetsinnehaver før en kan gjøre slikt, så dermed fulgte jeg
548 opp med et spørsmål om dette var greit.&lt;/p&gt;
549
550 &lt;p&gt;&lt;blockquote&gt;
551 &lt;p&gt;Date: Wed, 4 Jul 2012 20:25:06 +0200
552 &lt;br&gt;From: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
553 &lt;br&gt;To: Sidney Wolf &amp;lt;SWolf (at) mpegla.com&amp;gt;
554 &lt;br&gt;Cc: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
555 &lt;br&gt;Subject: Re: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
556
557 &lt;p&gt;Thank you for your reply.&lt;/p&gt;
558
559 &lt;p&gt;[Sidney Wolf]
560 &lt;br&gt;&amp;gt; Per your request, attached please find an electronic copy of the AVC
561 &lt;br&gt;&amp;gt; Patent Portfolio License. Please note that the electronic copy of
562 &lt;br&gt;&amp;gt; the License is provided as a convenience and for informational
563 &lt;br&gt;&amp;gt; purposes only. When concluding the Licenses, only the hard copies
564 &lt;br&gt;&amp;gt; provided by MPEG LA may be used.&lt;/p&gt;
565
566 &lt;p&gt;This is useful for me to learn, but the reason I asked for the
567 Internet address of the licensing document was to ensure I could
568 publish a link to it when I discuss the topic of H.264 licensing here
569 in Norway, and allow others to verify my observations. I can not do
570 the same with an email attachment. Thus I would like to ask you if it
571 is OK with MPEG LA that I publish this document on the Internet for
572 others to read?&lt;/p&gt;
573
574 &lt;p&gt;&amp;gt; To your question, MPEG LA lists our Licensees on our website
575 &lt;br&gt;&amp;gt; according to each program. The lists are in alphabetical order, so
576 &lt;br&gt;&amp;gt; it is very easy to search.&lt;/p&gt;
577
578 &lt;p&gt;I am afraid this do not help me locate Norwegian companies in the
579 list of Licensees. I do not know the name of all companies and
580 organisations in Norway, and thus do not know how to locate the
581 Norwegian ones on that list.&lt;/p&gt;
582
583 &lt;p&gt;&amp;gt; I hope that this was helpful. If we can be of additional assistance,
584 &lt;br&gt;&amp;gt; please let me know.&lt;/p&gt;
585
586 &lt;p&gt;Absoutely helpful to learn more about how MPEG LA handle licensing.&lt;/p&gt;
587
588 &lt;p&gt;--
589 &lt;br&gt;Happy hacking
590 &lt;br&gt;Petter Reinholdtsen&lt;/p&gt;
591 &lt;/blockquote&gt;&lt;/p&gt;
592
593 &lt;p&gt;Jeg håpet også at det skulle være mulig å få vite hvilke av de
594 mange hundre som har avtale med MPEG-LA om bruk av H.264 som holdt til
595 i Norge. Begge mine håp falt i grus med svaret fra MPEG-LA.
596
597 &lt;p&gt;&lt;blockquote&gt;
598 &lt;p&gt;Date: Thu, 5 Jul 2012 17:42:39 +0000
599 &lt;br&gt;From: Sidney Wolf &amp;lt;SWolf (at) mpegla.com&amp;gt;
600 &lt;br&gt;To: &#39;Petter Reinholdtsen&#39; &amp;lt;pere (at) hungry.com&amp;gt;
601 &lt;br&gt;Cc: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
602 &lt;br&gt;Subject: RE: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
603
604 &lt;p&gt;Dear Mr. Reinholdtsen,&lt;/p&gt;
605
606 &lt;p&gt;Thank you for your reply.&lt;/p&gt;
607
608 &lt;p&gt;We appreciate the additional explanation you have provided and for
609 asking our permission to publish the electronic copy of the License in
610 advance of doing so. Typically, MPEG LA prefers to distribute the
611 electronic copies of our Licenses to interested parties. Therefore,
612 please feel free to send interested parties to the AVC portion of our
613 website, http://www.mpegla.com/main/programs/AVC/Pages/Intro.aspx for
614 their further reference.&lt;/p&gt;
615
616 &lt;p&gt;As previously mentioned, MPEG LA maintains a list of Licensees in good
617 standing on our website according to each program. Due to the large
618 volume of Licensees, it would be administratively impractical to
619 provide this level of detail to interested parties. Therefore, I am
620 afraid we are not in a position to assist you with your request.&lt;/p&gt;
621
622 &lt;p&gt;Kind regards,&lt;/p&gt;
623
624 &lt;p&gt;Sidney A. Wolf
625 &lt;br&gt;Manager, Global Licensing
626 &lt;br&gt;MPEG LA&lt;/p&gt;
627 &lt;/blockquote&gt;&lt;/p&gt;
628
629 &lt;p&gt;Men takket være epostvedlegget kunne jeg søke på Google etter
630 setningen &quot;WHEREAS, a video standard commonly referred to as AVC has
631 been defined and is referred to in this Agreement as the “AVC
632 Standard” (as more fully defined herein below)&quot; som finnes i avtalen,
633 og lokalisere en kopi fra 2007 av
634 &lt;a href=&quot;http://www.sec.gov/Archives/edgar/data/1342960/000119312509050004/dex1024.htm&quot;&gt;lisensavtalen
635 mellom MPEG-LA og DivX, Inc.&lt;/a&gt;, slik at mine lesere kan se hvordan
636 avtalen så ut da. Jeg har ikke sammenlignet tekstene for å se om noe
637 har endret seg siden den tid, men satser på at teksten er representativ.&lt;/p&gt;
638
639 &lt;p&gt;Jeg aner fortsatt ikke hvor FedEx tok veien med pakken fra
640 MPEG-LA.&lt;/p&gt;
641
642 &lt;p&gt;Update 2012-07-06: Jeg er visst ikke den første som forsøker å få
643 klarhet i problemstillinger rundt H.264, og kom nettopp over en veldig
644 interessant bloggpost fra 2010 hos LibreVideo med tittelen
645 &quot;&lt;a href=&quot;http://www.librevideo.org/blog/2010/06/14/mpeg-la-answers-some-questions-about-avch-264-licensing/&quot;&gt;MPEG-LA
646 answers some questions about AVC/H.264 licensing&lt;/a&gt;. Anbefales!&lt;/p&gt;
647 </description>
648 </item>
649
650 <item>
651 <title>Departementenes servicesenter har ingen avtale om bruk av H.264 med MPEG-LA</title>
652 <link>http://people.skolelinux.org/pere/blog/Departementenes_servicesenter_har_ingen_avtale_om_bruk_av_H_264_med_MPEG_LA.html</link>
653 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Departementenes_servicesenter_har_ingen_avtale_om_bruk_av_H_264_med_MPEG_LA.html</guid>
654 <pubDate>Fri, 29 Jun 2012 09:40:00 +0200</pubDate>
655 <description>&lt;p&gt;Da fikk jeg nettopp svar fra
656 &lt;a href=&quot;http://www.dss.dep.no/&quot;&gt;Departementenes servicesenter&lt;/a&gt;
657 (DSS) på
658 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html&quot;&gt;mitt
659 spørsmål om avtale rundt bruk av H.264&lt;/a&gt;. De har ingen avtale med
660 MPEG LA eller dets representanter. Her er svaret.
661
662 &lt;p&gt;&lt;blockquote&gt;
663
664 &lt;p&gt;Date: Fri, 29 Jun 2012 07:04:42 +0000
665 &lt;br&gt;From: Nielsen Mette Haga &amp;lt;Mette-Haga.Nielsen (at) dss.dep.no&amp;gt;
666 &lt;br&gt;To: Petter Reinholdtsen &amp;lt;petter.reinholdtsen (at) ...&amp;gt;
667 &lt;br&gt;CC: Postmottak &amp;lt;Postmottak (at) dss.dep.no&amp;gt;
668 &lt;br&gt;Subject: SV: Innsynsbegjæring om MPEG/H.264-relaterte avtaler&lt;/p&gt;
669
670 &lt;p&gt;DSS har ikke inngått noen egen lisensavtale med MPEG-LA eller noen som
671 representerer MPEG-LA i Norge. Videoløsningen på regjeringen.no er
672 levert av Smartcom:tv. Lisensforholdet rundt H.264 er ikke omtalt i
673 vår avtale med Smartcom.&lt;/p&gt;
674
675 &lt;p&gt;Vennlig hilsen&lt;/p&gt;
676
677 &lt;p&gt;Mette Haga Nielsen
678 &lt;br&gt;Fung. seksjonssjef&lt;/p&gt;
679
680 &lt;p&gt;Departementenes servicesenter&lt;/p&gt;
681
682 &lt;p&gt;Informasjonsforvaltning
683
684 &lt;p&gt;Mobil 93 09 83 51
685 &lt;br&gt;E-post mette-haga.nielsen (at) dss.dep.no&lt;/p&gt;
686 &lt;/blockquote&gt;&lt;/p&gt;
687
688 &lt;p&gt;Hvis den norske regjeringen representert ved DSS ikke har slik
689 avtale, så kan en kanskje konkludere med at det ikke trengs? Jeg er
690 ikke trygg på at det er god juridisk grunn å stå på, men det er i det
691 minste interessant å vite at hverken NRK eller DSS har funnet det
692 nødvendig å ha avtale om bruk av H.264.&lt;/p&gt;
693
694 &lt;p&gt;Det forklarer ikke hvordan de kan ignorere bruksvilkårene knyttet
695 til bruk av opphavsrettsbeskyttet materiale de bruker til
696 videoproduksjon, med mindre slike vilkår kan ignoreres av selskaper og
697 privatpersoner i Norge. Har de lov til å bryte vilkårene, eller har
698 de brutt dem og så langt sluppet unna med det? Jeg aner ikke.&lt;/p&gt;
699 </description>
700 </item>
701
702 <item>
703 <title>MPEG-LA mener NRK må ha avtale med dem for å kringkaste og publisere H.264-video</title>
704 <link>http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html</link>
705 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html</guid>
706 <pubDate>Thu, 28 Jun 2012 20:00:00 +0200</pubDate>
707 <description>&lt;p&gt;Etter at NRK
708 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html&quot;&gt;nektet
709 å spore opp eventuell avtale med MPEG-LA&lt;/a&gt; eller andre om bruk av
710 MPEG/H.264-video etter at jeg &lt;a
711 href=&quot;http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html&quot;&gt;ba
712 om innsyn i slike avtaler&lt;/a&gt;, tenkte jeg at i stedet for å forsøke å
713 få NRK til å finne en slik avtale, så burde det være like enkelt å
714 spørre MPEG-LA om de hadde avtale med NRK. Spørsmålet ble sendt før
715 jeg fikk tips fra Kieran Kunhya om hvor listen over lisensinnehavere
716 &quot;in Good Standing&quot; befant seg. MPEG-LA svarte meg i dag, og kan
717 fortelle at NRK ikke har noen avtale med dem, så da er i det minste det
718 slått fast. Ikke overraskende mener MPEG-LA at det trengs en avtale
719 med MPEG-LA for å streame H.264, men deres rammer er jo
720 rettstilstanden i USA og ikke Norge. Jeg tar dermed den delen av
721 svaret med en klype salt. Jeg er dermed fortsatt ikke klok på om det
722 trengs en avtale, og hvis det trengs en avtale her i Norge, heller
723 ikke sikker på om NRK har en avtale med noen andre enn MPEG-LA som
724 gjør at de ikke trenger avtale direkte med MPEG-LA. Jeg håper NRKs
725 jurister har vurdert dette, og at det er mulig å få tilgang til
726 vurderingen uansett om de trenger en avtale eller ikke.&lt;/p&gt;
727
728 &lt;p&gt;Her er epostutvekslingen med MPEG-LA så langt. Håper ikke
729 utvekslingen fører til NRK plutselig får en litt uventet pakke fra
730 MPEG-LA.&lt;/p&gt;
731
732 &lt;p&gt;&lt;blockquote&gt;
733 &lt;p&gt;Date: Mon, 25 Jun 2012 15:29:37 +0200
734 &lt;br&gt;From: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
735 &lt;br&gt;To: licensing-web (at) mpegla.com
736 &lt;br&gt;Subject: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
737
738 &lt;p&gt;Hi. I have a small question for you, that I hope it is OK that I
739 ask.&lt;/p&gt;
740
741 &lt;p&gt;Is there any license agreements between MPEG-LA and NRK, &amp;lt;URL:
742 &lt;a href=&quot;http://www.nrk.no/&quot;&gt;http://www.nrk.no/&lt;/a&gt; &amp;gt;, the
743 Norwegian national broadcasting cooperation? I am not sure if they
744 need one, and am just curious if such agreeement exist.&lt;/p&gt;
745
746 &lt;p&gt;The postal address is&lt;/p&gt;
747
748 &lt;p&gt;&lt;blockquote&gt;
749 NRK
750 &lt;br&gt;Postbox 8500, Majorstuen
751 &lt;br&gt;0340 Oslo
752 &lt;br&gt;Norway
753 &lt;/blockquote&gt;&lt;/p&gt;
754
755 &lt;p&gt;if it make it easier for you to locate such agreement.&lt;/p&gt;
756
757 &lt;p&gt;Can you tell me how many entities in Norway have an agreement with
758 MPEG-LA, and the name of these entities?&lt;/p&gt;
759
760 &lt;p&gt;--
761 &lt;br&gt;Happy hacking
762 &lt;br&gt;Petter Reinholdtsen
763 &lt;/blockquote&gt;&lt;/p&gt;
764
765 &lt;p&gt;I dag, to dager senere, fikk jeg følgende svar:&lt;/p&gt;
766
767 &lt;p&gt;&lt;blockquote&gt;
768 &lt;p&gt;Date: Thu, 28 Jun 2012 14:11:17 +0000
769 &lt;br&gt;From: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&gt;
770 &lt;br&gt;To: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&gt;
771 &lt;br&gt;CC: MD Administration &amp;lt;MDAdministration (at) mpegla.com&gt;
772 &lt;br&gt;Subject: RE: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
773
774 &lt;p&gt;Dear Mr. Reinholdtsen,&lt;/p&gt;
775
776 &lt;p&gt;Thank you for your message and for your interest in MPEG LA. We
777 appreciate hearing from you and I will be happy to assist you.&lt;/p&gt;
778
779 &lt;p&gt;To begin, I will assume that you are referring to AVC/H.264
780 technology in your message below, as this technology is commonly used
781 in the transmission of video content. In that case, please allow me
782 to briefly summarize the coverage provided by our AVC Patent Portfolio
783 License.&lt;/p&gt;
784
785 &lt;P&gt;Our AVC License provides coverage for end products and video
786 services that make use of AVC/H.264 technology. Accordingly, the
787 party offering such end products and video to End Users concludes the
788 AVC License and is responsible for paying the applicable royalties
789 associated with the end products/video they offer.&lt;/p&gt;
790
791 &lt;p&gt;While the Norwegian Broadcast Corporation (NRK) is not currently a
792 Licensee to MPEG LA&#39;s AVC License (or any other Portfolio License
793 offered by MPEG LA), if NRK offers AVC Video to End Users for
794 remuneration (for example, Title-by-Title, Subscription, Free
795 Television, or Internet Broadcast AVC Video), then NRK will need to
796 conclude the AVC License and may be responsible for paying applicable
797 royalties associated with the AVC Video it distributes.&lt;/p&gt;
798
799 &lt;p&gt;Today I will send you a FedEx package containing a copy of our AVC
800 License for your review. You should receive the License document
801 within the next few days.&lt;/p&gt;
802
803 &lt;p&gt;Meanwhile, MPEG LA currently has several Norwegian Licensees that
804 can be found under the &quot;Licensees&quot; header within the respective
805 portion of our website. For example, you may find our list of
806 Licensees in Good Standing to our AVC License in the AVC portion of
807 our website,
808 &lt;a href=&quot;http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx&quot;&gt;http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx&lt;/a&gt;&lt;/p&gt;
809
810 &lt;p&gt;I hope the above information is helpful. If you have additional
811 questions or need further assistance with the AVC License, please feel
812 free to contact me directly. I look forward to hearing from you again
813 soon.&lt;/p&gt;
814
815 &lt;p&gt;Best regards,&lt;/p&gt;
816
817 &lt;p&gt;Ryan&lt;/p&gt;
818
819 &lt;p&gt;Ryan M. Rodriguez
820 &lt;br&gt;Licensing Associate
821 &lt;br&gt;MPEG LA
822 &lt;br&gt;5425 Wisconsin Avenue
823 &lt;br&gt;Suite 801
824 &lt;br&gt;Chevy Chase, MD 20815
825 &lt;br&gt;U.S.A.
826 &lt;br&gt;Phone: +1 (301) 986-6660 x211
827 &lt;br&gt;Fax: +1 (301) 986-8575
828 &lt;br&gt;Email: rrodriguez (at) mpegla.com&lt;/p&gt;
829
830 &lt;/blockquote&gt;&lt;/p&gt;
831
832 &lt;p&gt;Meldingen om utsendt FedEx-pakke var så merkelig at jeg
833 øyeblikkelig sendte svar tilbake og spurte hva i alle dager han mente,
834 da han jo ikke hadde fått noen postadresse som nådde meg.&lt;/p&gt;
835
836 &lt;p&gt;&lt;blockquote&gt;
837
838 &lt;p&gt;Date: Thu, 28 Jun 2012 16:36:15 +0200
839 &lt;br&gt;From: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
840 &lt;br&gt;To: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
841 &lt;br&gt;Cc: MD Administration &amp;lt;MDAdministration (at) mpegla.com&amp;gt;
842 &lt;br&gt;Subject: Re: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
843
844 &lt;p&gt;[Ryan Rodriguez]
845 &lt;br&gt;&amp;gt; Dear Mr. Reinholdtsen,&lt;/p&gt;
846
847 &lt;p&gt;Thank you for your quick reply.&lt;/p&gt;
848
849 &lt;p&gt;&amp;gt; Today I will send you a FedEx package containing a copy of our AVC
850 &lt;br&gt;&amp;gt; License for your review. You should receive the License document
851 &lt;br&gt;&amp;gt; within the next few days.&lt;/p&gt;
852
853 &lt;p&gt;The part about sending a FedEx package confused me, though. I did not
854 &lt;br&gt;give you my address, nor am I associated with NRK in any way, so I hope
855 &lt;br&gt;you did not try to send me a package using the address of NRK. If you
856 &lt;br&gt;would send me the Internet address of to the document, it would be more
857 &lt;br&gt;useful to me to be able to download it as an electronic document.&lt;/p&gt;
858
859 &lt;p&gt;&amp;gt; Meanwhile, MPEG LA currently has several Norwegian Licensees that can
860 &lt;br&gt;&amp;gt; be found under the &quot;Licensees&quot; header within the respective portion
861 &lt;br&gt;&amp;gt; of our website. For example, you may find our list of Licensees in
862 &lt;br&gt;&amp;gt; Good Standing to our AVC License in the AVC portion of our website,
863 &lt;br&gt;&amp;gt; http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx&lt;/p&gt;
864
865 &lt;p&gt;How can I recognize the Norwegian licensees?&lt;/p&gt;
866
867 &lt;p&gt;--
868 &lt;br&gt;Happy hacking
869 &lt;br&gt;Petter Reinholdtsen&lt;/p&gt;
870 &lt;/blockquote&gt;&lt;/p&gt;
871
872 &lt;p&gt;Selv om jeg svarte kun noen minutter etter at jeg fikk eposten fra
873 MPEG-LA, fikk jeg eposten under som automatisk var beskjed på min
874 siste epost. Får håpe noen likevel følger opp &quot;FedEx-pakken&quot;. For å
875 øke sjansen for at noen revurderer utsending av pakke uten mottaker,
876 videresendte jeg min epost til swolf (at) mpegla.com, så får vi se.
877 Har ikke hørt noe mer 3 timer senere, så jeg mistenker at ingen leste
878 min epost tidsnok.&lt;/p&gt;
879
880 &lt;p&gt;&lt;blockquote&gt;
881
882 &lt;p&gt;Date: Thu, 28 Jun 2012 14:36:20 +0000
883 &lt;br&gt;From: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
884 &lt;br&gt;To: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
885 &lt;br&gt;Subject: Automatic reply: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
886
887 &lt;p&gt;Thank you for your message.&lt;/p&gt;
888
889 &lt;p&gt;I will be out of the office until Thursday, July 5 and will respond
890 to all messages upon my return. If this is a matter that requires
891 immediate attention, please contact Sidney Wolf (swolf (at)
892 mpegla.com)&lt;/p&gt;
893
894 &lt;p&gt;Best regards,&lt;/p&gt;
895
896 &lt;p&gt;Ryan&lt;/p&gt;
897
898 &lt;p&gt;Ryan M. Rodriguez
899 &lt;br&gt;Licensing Associate
900 &lt;br&gt;MPEG LA&lt;/p&gt;
901
902 &lt;/blockquote&gt;&lt;/p&gt;
903
904 &lt;p&gt;Litt klokere, men fortsatt ikke klok på mitt opprinnelige spørsmål,
905 som er om en trenger avtale med MPEG-LA for å publisere eller
906 kringkaste H.264-video i Norge.&lt;/p&gt;
907 </description>
908 </item>
909
910 <item>
911 <title>NRK nekter å finne og utlevere eventuell avtale med MPEG-LA</title>
912 <link>http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html</link>
913 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html</guid>
914 <pubDate>Mon, 25 Jun 2012 15:10:00 +0200</pubDate>
915 <description>&lt;p&gt;Jeg fikk nettopp svar fra NRK på
916 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html&quot;&gt;min
917 forespørsel om kopi av avtale&lt;/a&gt; med MPEG-LA eller andre om bruk av
918 MPEG og/eller H.264. Svaret har fått saksreferanse 2011/371 (mon tro
919 hva slags sak fra 2011 dette er?) hos NRK og lyder som følger:&lt;/p&gt;
920
921 &lt;p&gt;&lt;blockquote&gt;
922
923 &lt;p&gt;&lt;strong&gt;Svar på innsynsbegjæring i MPEG / H.264-relaterte
924 avtaler&lt;/strong&gt;&lt;/p&gt;
925
926 &lt;p&gt;Viser til innsynsbegjæring av 19. juni 2012. Kravet om innsyn
927 gjelder avtale som gjør at NRK «ikke er begrenset av de generelle
928 bruksvilkårene som gjelder for utstyr som bruker MPEG og/eller
929 H.264».&lt;/p&gt;
930
931 &lt;p&gt;I henhold til offentleglova § 28 annet ledd må innsynskravet gjelde
932 en bestemt sak eller i rimelig utstrekning saker av en bestemt
933 sak. Det er på det rene at det aktuelle innsynskravet ikke gjelder en
934 bestemt sak. Spørsmålet som reiser seg er om identifiseringsgraden er
935 tilstrekkelig. I Justisdepartementets «Rettleiar til offentleglova»
936 står følgende:&lt;/p&gt;
937
938 &lt;p&gt;«Kravet om at innsynskravet må gjelde ei bestemt sak er til hinder
939 for at eit innsynskrav kan gjelde alle saker av ein bestemt art, utan
940 at den enkelte saka blir identifisert. Ein kan med andre ord i
941 utgangspunktet ikkje krevje innsyn i til dømes alle saker om
942 utsleppsløyve hos Statens forureiningstilsyn frå dei siste tre åra,
943 med mindre ein identifiserer kvar enkelt sak, til dømes med tilvising
944 til dato, partar eller liknande.»&lt;/p&gt;
945
946 &lt;p&gt;Vedrørende denne begrensningen har Justisdepartementet uttalt
947 følgende (Lovavdelingens uttalelser JDLOV-2010-3295):&lt;/p&gt;
948
949 &lt;p&gt;&lt;em&gt;«Bakgrunnen for avgrensinga av kva innsynskravet kan gjelde,
950 er fyrst og fremst at meir generelle innsynskrav, utan noka form for
951 identifikasjon av kva ein eigentleg ynskjer, ville vere svært
952 vanskelege å handsame for forvaltninga.»&lt;/em&gt;&lt;/p&gt;
953
954 &lt;p&gt;I samme sak uttaler Lovavdelingen følgende:&lt;/p&gt;
955
956 &lt;p&gt;&lt;em&gt;«Det følgjer vidare av offentleglova § 28 andre ledd at det `i
957 rimeleg utstrekning&#39; kan krevjast innsyn i `saker av ein bestemt
958 art&#39;. Vilkåret om at eit innsynskrav berre `i rimeleg utstrekning&#39; kan
959 gjelde saker av ein bestemt art, er i hovudsak knytt til kor
960 arbeidskrevjande det vil vere å finne fram til dei aktuelle
961 dokumenta. I tillegg reknar vi med at vilkåret kan gje grunnlag for å
962 nekte innsyn i tilfelle der innsynskravet er så omfattande (gjeld så
963 mange dokument) at arbeidsmengda som ville gått med til å handsame
964 det, er større enn det ein `i rimeleg utstrekning&#39; kan krevje (sjølv
965 om det nok skal mykje til).»&lt;/em&gt;&lt;/p&gt;
966
967 &lt;p&gt;NRK har ikke noen egen sammenstilling over avtaler innenfor
968 bestemte områder som omtales i innsynsbegjæringen. De måtte søkes på
969 vanlig måte. I tillegg finnes ikke noen automatisert måte å finne
970 avtaler som «ikke er begrenset av de generelle bruksvilkårene som
971 gjelder for utstyr som bruker MPEG og/eller H.264». En slik
972 gjennomgang av avtaler måtte gjøres manuelt av en person med
973 spesialistkunnskap. Dette vil kreve at NRK avsetter omfattende
974 ressurser for å finne frem relevante avtaler og for deretter å vurdere
975 om de dekkes av det innsynsbegjæringen omfattes.&lt;/p&gt;
976
977 &lt;p&gt;På bakgrunn av dette nekter NRK innsyn, med den begrunnelsen at
978 innsynskravet er så omfattende at arbeidsmengden for å håndtere kravet
979 vil være langt større enn det som i rimelig utstrekning kan kreves i
980 henhold til offentleglova § 28 annet ledd.&lt;/p&gt;
981
982 &lt;p&gt;Avslag på deres innsynsbegjæring kan påklages til Kultur- og
983 kirkedepartementet innen tre uker fra det tidspunkt avslaget kommer
984 frem til mottakeren, i henhold til reglene i offentleglova § 32,
985 jf. forvaltningsloven kapittel VI. Klagen skal stiles til Kultur- og
986 kirkedepartementet, og sendes til NRK.&lt;/p&gt;
987
988 &lt;p&gt;NRK er imidlertid etter Offentleglova forpliktet å gi ut journaler,
989 slik at en eventuell søknad om innsyn kan tydeligere identifisere
990 hvilke dokumenter som det ønskes innsyn i. NRKs offentlige journaler
991 for inneværende og forrige måned ligger ute på
992 NRK.no/innsyn. Journaler som går lengre tilbake i tid, kan sendes ut
993 på forespørsel til innsyn (at) nrk.no.&lt;/p&gt;
994
995 &lt;p&gt;Med hilsen
996 &lt;br&gt;Dokumentarkivet i NRK
997 &lt;br&gt;v/ Elin Brandsrud
998 &lt;br&gt;Tel. direkte: 23 04 29 29
999 &lt;br&gt;Post: RBM3, Postboks 8500 Majorstuen, 0340 Oslo
1000 &lt;br&gt;innsyn (at) nrk.no&lt;/p&gt;
1001
1002 &lt;/blockquote&gt;&lt;/p&gt;
1003
1004 &lt;p&gt;Svaret kom
1005 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2012-06-25-video-mpegla-nrk.pdf&quot;&gt;i
1006 PDF-form som vedlegg på epost&lt;/a&gt;. Jeg er litt usikker på hvordan jeg
1007 best går videre for å bli klok, men jeg har jo i hvert fall tre uker
1008 på å vurdere om jeg skal klage. Enten må nok forespørselen
1009 reformuleres eller så må jeg vel klage. Synes jo det er merkelig at
1010 NRK ikke har bedre kontroll med hvilke avtaler de har inngått. Det
1011 burde jo være noen i ledelsen som vet om de har signert en avtale med
1012 MPEG-LA eller ikke...&lt;/p&gt;
1013
1014 &lt;p&gt;Oppdatering 2012-06-25 20:20: Et google-søk på &quot;2011/371 nrk&quot;
1015 sendte meg til postjournalen for
1016 &lt;a href=&quot;http://nrk.no/contentfile/file/1.8212365!offentligjournal19062012.pdf&quot;&gt;2012-06-19&lt;/a&gt;
1017 og
1018 &lt;a href=&quot;http://nrk.no/contentfile/file/1.8214156!offentligjournal20062012.pdf&quot;&gt;2012-06-20&lt;/a&gt;
1019 hos NRK som viser mine forespørsler og viser at sakens tittel hos NRK
1020 er &quot;Graphic Systems Regions MA 2378/10E&quot;. Videre søk etter &quot;Graphic
1021 Systems Regions&quot; viser at dette er saken til et anbud om
1022 &quot;&lt;a href=&quot;http://no.mercell.com/m/mts/Tender/27179412.aspx&quot;&gt;a graphics
1023 system for 12 or 13 sites broadcasting regional news&lt;/a&gt;&quot; hos Mercell
1024 Sourcing Service, også omtalt på
1025 &lt;a href=&quot;http://www.publictenders.net/tender/595705&quot;&gt;Public
1026 Tenders&lt;/a&gt; og
1027 &lt;a href=&quot;http://www.doffin.no/search/show/search_view.aspx?ID=JAN155521&quot;&gt;Doffin&lt;/a&gt;.
1028 Jeg er dog usikker på hvordan dette er relatert til min
1029 forespørsel.&lt;/p&gt;
1030
1031 &lt;p&gt;Oppdatering 2012-06-25 22:40: Ble tipset av Kieran Kunhya, fra
1032 miljøet rundt
1033 &lt;a href=&quot;http://code.google.com/p/open-broadcast-encoder/&quot;&gt;Open
1034 Broadcast Encoder&lt;/a&gt;, at listen over de som har lisensavtale med
1035 MPEG-LA er
1036 &lt;a href=&quot;http://www.mpeg-la.com/main/programs/AVC/Pages/Licensees.aspx&quot;&gt;tilgjengelig
1037 på web&lt;/a&gt;. Veldig fint å oppdage hvor den finnes, da jeg må ha lett
1038 etter feil ting da jeg forsøke å finne den. Der står ikke NRK, men
1039 flere andre &quot;Broadcasting Company&quot;-oppføringer. Lurer på om det betyr
1040 at NRK ikke trenger avtale, eller noe helt annet?&lt;/p&gt;
1041 </description>
1042 </item>
1043
1044 <item>
1045 <title>Song book for Computer Scientists</title>
1046 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
1047 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
1048 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
1049 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
1050 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
1051 collecting computer related songs for use at parties. The original
1052 version was written in LaTeX, but a few years ago I got help from
1053 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
1054 while keeping the ability to create a nice book in PDF format. I have
1055 not had time to maintain the book for a while now, and guess I should
1056 put it up on some public version control repository where others can
1057 help me extend and update the book. If anyone is volunteering to help
1058 me with this, send me an email. Also let me know if there are songs
1059 missing in my book.&lt;/p&gt;
1060
1061 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
1062 me today that I really should let all my readers share the joys of
1063 singing out load about programming, computers and computer networks.
1064 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
1065 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
1066 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
1067 Computer Science Songbook&lt;/a&gt;.
1068 </description>
1069 </item>
1070
1071 <item>
1072 <title>Trenger en avtale med MPEG-LA for å publisere og kringkaste H.264-video?</title>
1073 <link>http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html</link>
1074 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html</guid>
1075 <pubDate>Thu, 21 Jun 2012 13:40:00 +0200</pubDate>
1076 <description>&lt;p&gt;Trengs det avtale med MPEG-LA for å ha lovlig rett til å
1077 distribuere og kringkaste video i MPEG4 eller med videokodingen H.264?
1078 &lt;a href=&quot;http://webmink.com/essays/h-264/&quot;&gt;H.264 og MPEG4 er jo ikke en
1079 fri og åpen standard&lt;/a&gt; i henhold til
1080 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html&quot;&gt;definisjonen
1081 til Digistan&lt;/a&gt;, så i enkelte land er det ingen tvil om at du må ha
1082 en slik avtale, men jeg må innrømme at jeg ikke vet om det også
1083 gjelder Norge. Det ser uansett ut til å være en juridisk interessant
1084 problemstilling. Men jeg tenkte her om dagen som så, at hvis det er
1085 nødvendig, så har store aktører som
1086 &lt;a href=&quot;http://www.nrk.no/&quot;&gt;NRK&lt;/a&gt; og
1087 &lt;a href=&quot;http://www.regjeringen.no/&quot;&gt;regjeringen&lt;/a&gt; skaffet seg en
1088 slik avtale. Jeg har derfor sendt forespørsel til begge (for
1089 regjeringen sin del er det Departementenes Servicesenter som gjør
1090 jobben), og bedt om kopi av eventuelle avtaler de har om bruk av MPEG
1091 og/eller H.264 med MPEG-LA eller andre aktører som opererer på vegne
1092 av MPEG-LA. Her er kopi av eposten jeg har sendt til
1093 &lt;a href=&quot;http://www.dss.dep.no/&quot;&gt;Departementenes Servicesenter&lt;/a&gt;.
1094 Forespørselen til NRK er veldig lik.&lt;/p&gt;
1095
1096 &lt;p&gt;&lt;blockquote&gt;
1097
1098 &lt;p&gt;Date: Tue, 19 Jun 2012 15:18:33 +0200
1099 &lt;br&gt;From: Petter Reinholdtsen
1100 &lt;br&gt;To: postmottak@dss.dep.no
1101 &lt;br&gt;Subject: Innsynsbegjæring om MPEG/H.264-relaterte avtaler
1102
1103 &lt;p&gt;Hei. Jeg ber herved om innsyn og kopi av dokumenter i DSS relatert
1104 til avtaler rundt bruk av videoformatene MPEG og H.264. Jeg er
1105 spesielt interessert i å vite om DSS har lisensavtale med MPEG-LA
1106 eller noen som representerer MPEG-LA i Norge.&lt;/p&gt;
1107
1108 &lt;p&gt;MPEG og H.264 er videoformater som brukes både til kringkasting
1109 (f.eks. i bakkenett og kabel-TV) og videopublisering på web, deriblant
1110 via Adobe Flash. MPEG-LA, &amp;lt;URL:
1111 &lt;a href=&quot;http://www.mpeg-la.com/&quot;&gt;http://www.mpeg-la.com/&lt;/a&gt; &amp;gt;, er
1112 en organisasjon som har fått oppgaven, av de kjente rettighetshavere
1113 av immaterielle rettigheter knyttet til MPEG og H.264, å selge
1114 bruksrett for MPEG og H.264.&lt;/p&gt;
1115
1116 &lt;p&gt;Via regjeringen.no kringkastes med MPEG og H.264-baserte
1117 videoformater, og dette ser ut til å være organisert av DSS. Jeg
1118 antar dermed at DSS har avtale med en eller annen aktør om dette.&lt;/p&gt;
1119
1120 &lt;p&gt;F.eks. har Adobe Premiere Pro har følgende klausul i følge &amp;lt;URL:
1121 &lt;a href=&quot;http://news.cnet.com/8301-30685_3-20000101-264.html&quot;&gt;http://news.cnet.com/8301-30685_3-20000101-264.html&lt;/a&gt;
1122 &amp;gt;:&lt;/p&gt;
1123
1124 &lt;p&gt;&lt;blockquote&gt;
1125
1126 &lt;p&gt;6.17. AVC DISTRIBUTION. The following notice applies to software
1127 containing AVC import and export functionality: THIS PRODUCT IS
1128 LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND
1129 NON-COMMERCIAL USE OF A CONSUMER TO (a) ENCODE VIDEO IN COMPLIANCE
1130 WITH THE AVC STANDARD (&quot;AVC VIDEO&quot;) AND/OR (b) DECODE AVC VIDEO THAT
1131 WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL
1132 ACTIVITY AND/OR AVC VIDEO THAT WAS OBTAINED FROM A VIDEO PROVIDER
1133 LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
1134 IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED
1135 FROM MPEG LA L.L.C. SEE
1136 &lt;a href=&quot;http://www.mpegla.com&quot;&gt;http://www.mpegla.com&lt;/a&gt;.&lt;/p&gt;
1137
1138 &lt;/blockquote&gt;&lt;/p&gt;
1139
1140 &lt;p&gt;Her er det kun &quot;non-commercial&quot; og &quot;personal and non-commercial&quot;
1141 aktivitet som er tillatt uten ekstra avtale med MPEG-LA.&lt;/p&gt;
1142
1143 &lt;p&gt;Et annet tilsvarende eksempel er Apple Final Cut Pro, som har
1144 følgende klausul i følge &amp;lt;URL:
1145 &lt;a href=&quot;http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf&quot;&gt;http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf&lt;/a&gt;
1146 &amp;gt;:&lt;/p&gt;
1147
1148 &lt;p&gt;&lt;blockquote&gt;
1149
1150 &lt;p&gt;15. Merknad om H.264/AVC. Hvis Apple-programvaren inneholder
1151 funksjonalitet for AVC-koding og/eller AVC-dekoding, krever
1152 kommersiell bruk ekstra lisensiering og følgende gjelder:
1153 AVC-FUNKSJONALITETEN I DETTE PRODUKTET KAN KUN ANVENDES AV
1154 FORBRUKERE OG KUN FOR PERSONLIG OG IKKE- KOMMERSIELL BRUK TIL (i)
1155 KODING AV VIDEO I OVERENSSTEMMELSE MED AVC-STANDARDEN (&quot;AVC-VIDEO&quot;)
1156 OG/ELLER (ii) DEKODING AV AVC-VIDEO SOM ER KODET AV EN FORBRUKER TIL
1157 PERSONLIG OG IKKE-KOMMERSIELL BRUK OG/ELLER DEKODING AV AVC-VIDEO
1158 FRA EN VIDEOLEVERANDØR SOM HAR LISENS TIL Å TILBY
1159 AVC-VIDEO. INFORMASJON OM ANNEN BRUK OG LISENSIERING KAN INNHENTES
1160 FRA MPEG LA L.L.C. SE HTTP://WWW.MPEGLA.COM.&lt;/p&gt;
1161 &lt;/blockquote&gt;&lt;/p&gt;
1162
1163 &lt;p&gt;Tilsvarende gjelder for andre programvarepakker, kamera, etc som
1164 bruker MPEG og H.264, at en må ha en avtale med MPEG-LA for å ha lov
1165 til å bruke programmet/utstyret hvis en skal lage noe annet enn
1166 private filmer og i ikke-kommersiell virksomhet.&lt;/p&gt;
1167
1168 &lt;p&gt;Jeg er altså interessert i kopi av avtaler DSS har som gjør at en
1169 ikke er begrenset av de generelle bruksvilkårene som gjelder for
1170 utstyr som bruker MPEG og/eller H.264.&lt;/p&gt;
1171 &lt;/blockquote&gt;&lt;/p&gt;
1172
1173 &lt;p&gt;Nå venter jeg spent på svaret. Jeg planlegger å blogge om svaret
1174 her.&lt;/p&gt;
1175 </description>
1176 </item>
1177
1178 <item>
1179 <title>HTC One X - Your video? What do you mean?</title>
1180 <link>http://people.skolelinux.org/pere/blog/HTC_One_X___Your_video___What_do_you_mean_.html</link>
1181 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/HTC_One_X___Your_video___What_do_you_mean_.html</guid>
1182 <pubDate>Thu, 26 Apr 2012 13:20:00 +0200</pubDate>
1183 <description>&lt;p&gt;In &lt;a href=&quot;http://www.idg.no/computerworld/article243690.ece&quot;&gt;an
1184 article today&lt;/a&gt; published by Computerworld Norway, the photographer
1185 &lt;a href=&quot;http://www.urke.com/eirik/&quot;&gt;Eirik Helland Urke&lt;/a&gt; reports
1186 that the video editor application included with
1187 &lt;a href=&quot;http://www.htc.com/www/smartphones/htc-one-x/#specs&quot;&gt;HTC One
1188 X&lt;/a&gt; have some quite surprising terms of use. The article is mostly
1189 based on the twitter message from mister Urke, stating:
1190
1191 &lt;p&gt;&lt;blockquote&gt;
1192 &quot;&lt;a href=&quot;http://twitter.com/urke/status/194062269724897280&quot;&gt;Drøy
1193 brukeravtale: HTC kan bruke MINE redigerte videoer kommersielt. Selv
1194 kan jeg KUN bruke dem privat.&lt;/a&gt;&quot;
1195 &lt;/blockquote&gt;&lt;/p&gt;
1196
1197 &lt;p&gt;I quickly translated it to this English message:&lt;/p&gt;
1198
1199 &lt;p&gt;&lt;blockquote&gt;
1200 &quot;Arrogant user agreement: HTC can use MY edited videos
1201 commercially. Although I can ONLY use them privately.&quot;
1202 &lt;/blockquote&gt;&lt;/p&gt;
1203
1204 &lt;p&gt;I&#39;ve been unable to find the text of the license term myself, but
1205 suspect it is a variation of the MPEG-LA terms I
1206 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html&quot;&gt;discovered
1207 with my Canon IXUS 130&lt;/a&gt;. The HTC One X specification specifies that
1208 the recording format of the phone is .amr for audio and .mp3 for
1209 video. AMR is
1210 &lt;a href=&quot;http://en.wikipedia.org/wiki/Adaptive_Multi-Rate_audio_codec#Licensing_and_patent_issues&quot;&gt;Adaptive
1211 Multi-Rate audio codec&lt;/a&gt; with patents which according to the
1212 Wikipedia article require an license agreement with
1213 &lt;a href=&quot;http://www.voiceage.com/&quot;&gt;VoiceAge&lt;/a&gt;. MP4 is
1214 &lt;a href=&quot;http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Patent_licensing&quot;&gt;MPEG4 with
1215 H.264&lt;/a&gt;, which according to Wikipedia require a licence agreement
1216 with &lt;a href=&quot;http://www.mpegla.com/&quot;&gt;MPEG-LA&lt;/a&gt;.&lt;/p&gt;
1217
1218 &lt;p&gt;I know why I prefer
1219 &lt;a href=&quot;http://www.digistan.org/open-standard:definition&quot;&gt;free and open
1220 standards&lt;/a&gt; also for video.&lt;/p&gt;
1221 </description>
1222 </item>
1223
1224 <item>
1225 <title>RAND terms - non-reasonable and discriminatory</title>
1226 <link>http://people.skolelinux.org/pere/blog/RAND_terms___non_reasonable_and_discriminatory.html</link>
1227 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/RAND_terms___non_reasonable_and_discriminatory.html</guid>
1228 <pubDate>Thu, 19 Apr 2012 22:20:00 +0200</pubDate>
1229 <description>&lt;p&gt;Here in Norway, the
1230 &lt;a href=&quot;http://www.regjeringen.no/nb/dep/fad.html?id=339&quot;&gt; Ministry of
1231 Government Administration, Reform and Church Affairs&lt;/a&gt; is behind
1232 a &lt;a href=&quot;http://standard.difi.no/forvaltningsstandarder&quot;&gt;directory of
1233 standards&lt;/a&gt; that are recommended or mandatory for use by the
1234 government. When the directory was created, the people behind it made
1235 an effort to ensure that everyone would be able to implement the
1236 standards and compete on equal terms to supply software and solutions
1237 to the government. Free software and non-free software could compete
1238 on the same level.&lt;/p&gt;
1239
1240 &lt;p&gt;But recently, some standards with RAND
1241 (&lt;a href=&quot;http://en.wikipedia.org/wiki/Reasonable_and_non-discriminatory_licensing&quot;&gt;Reasonable
1242 And Non-Discriminatory&lt;/a&gt;) terms have made their way into the
1243 directory. And while this might not sound too bad, the fact is that
1244 standard specifications with RAND terms often block free software from
1245 implementing them. The reasonable part of RAND mean that the cost per
1246 user/unit is low,and the non-discriminatory part mean that everyone
1247 willing to pay will get a license. Both sound great in theory. In
1248 practice, to get such license one need to be able to count users, and
1249 be able to pay a small amount of money per unit or user. By
1250 definition, users of free software do not need to register their use.
1251 So counting users or units is not possible for free software projects.
1252 And given that people will use the software without handing any money
1253 to the author, it is not really economically possible for a free
1254 software author to pay a small amount of money to license the rights
1255 to implement a standard when the income available is zero. The result
1256 in these situations is that free software are locked out from
1257 implementing standards with RAND terms.&lt;/p&gt;
1258
1259 &lt;p&gt;Because of this, when I see someone claiming the terms of a
1260 standard is reasonable and non-discriminatory, all I can think of is
1261 how this really is non-reasonable and discriminatory. Because free
1262 software developers are working in a global market, it does not really
1263 help to know that software patents are not supposed to be enforceable
1264 in Norway. The patent regimes in other countries affect us even here.
1265 I really hope the people behind the standard directory will pay more
1266 attention to these issues in the future.&lt;/p&gt;
1267
1268 &lt;p&gt;You can find more on the issues with RAND, FRAND and RAND-Z terms
1269 from Simon Phipps
1270 (&lt;a href=&quot;http://blogs.computerworlduk.com/simon-says/2010/11/rand-not-so-reasonable/&quot;&gt;RAND:
1271 Not So Reasonable?&lt;/a&gt;).&lt;/p&gt;
1272
1273 &lt;p&gt;Update 2012-04-21: Just came across a
1274 &lt;a href=&quot;http://blogs.computerworlduk.com/open-enterprise/2012/04/of-microsoft-netscape-patents-and-open-standards/index.htm&quot;&gt;blog
1275 post from Glyn Moody&lt;/a&gt; over at Computer World UK warning about the
1276 same issue, and urging people to speak out to the UK government. I
1277 can only urge Norwegian users to do the same for
1278 &lt;a href=&quot;http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder&quot;&gt;the
1279 hearing taking place at the moment&lt;/a&gt; (respond before 2012-04-27).
1280 It proposes to require video conferencing standards including
1281 specifications with RAND terms.&lt;/p&gt;
1282 </description>
1283 </item>
1284
1285 <item>
1286 <title>Hvordan enkelt laste ned filmer fra NRK</title>
1287 <link>http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html</link>
1288 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html</guid>
1289 <pubDate>Sat, 5 Nov 2011 15:20:00 +0100</pubDate>
1290 <description>&lt;p&gt;Ofte har jeg lyst til å laste ned et innslag fra NRKs nettsted for
1291 å se det senere når jeg ikke er på nett, eller for å ha det
1292 tilgjengelig når jeg en gang i fremtiden ønsker å referere til
1293 innslaget selv om NRK har fjernet det fra sine nettsider. I dag fant
1294 jeg et lite script som fikser jobben.&lt;/p&gt;
1295
1296 &lt;p&gt;Scriptet er laget av Jan Henning Thorsen og tilgjengelig fra
1297 &lt;a href=&quot;http://jhthorsen.github.com/snippets/nrk-downloader/&quot;&gt;github&lt;/a&gt;,
1298 og gjør det veldig enkelt å laste ned. Kjør &lt;tt&gt;nrk-downloader.sh
1299 http://www1.nrk.no/nett-tv/klipp/582810&lt;/tt&gt; for å hente ned et enkelt
1300 innslag eller &lt;tt&gt;nrk-downloader.sh
1301 http://www1.nrk.no/nett-tv/kategori/3521&lt;/tt&gt; for å laste ned alle
1302 episodene i en serie.&lt;/p&gt;
1303
1304 &lt;p&gt;Det er ikke rakettforskning å laste ned NRK-&quot;strømmer&quot;, og
1305 tidligere gjorde jeg dette manuelt med mplayer. Scriptet til
1306 Hr. Thorsen gjør det raskere og enklere for meg, men jeg vil ikke si
1307 at det er en revolusjonerende løsning. Jeg mener jo fortsatt at
1308 påstanden fra NRKs ansatte om at det er
1309 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html&quot;&gt;vesensforskjellig
1310 å legge tilgjengelig for nedlasting og for streaming&lt;/a&gt; er
1311 meningsløs.&lt;/p&gt;
1312 </description>
1313 </item>
1314
1315 <item>
1316 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
1317 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
1318 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
1319 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
1320 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
1321 mentioned the issues I believe should be improved in Debian for its
1322 desktop to be useful for more people. The use case for this is my
1323 parents, which are currently running Kubuntu which solve the
1324 issues.&lt;/p&gt;
1325
1326 &lt;p&gt;I suspect these four missing features are not very hard to
1327 implement. After all, they are present in Ubuntu, so if we wanted to
1328 do this in Debian we would have a source.&lt;/p&gt;
1329
1330 &lt;ol&gt;
1331
1332 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
1333 are new packages available for upgrades, a icon in the KDE status bar
1334 indicate this, and clicking on it will activate the simple upgrade
1335 tool to handle it. I have no problem guiding both of my parents
1336 through the process over the phone. If a kernel reboot is required,
1337 this too is indicated by the status bars and the upgrade tool. Last
1338 time I checked, nothing with the same features was working in KDE in
1339 Debian.&lt;/li&gt;
1340
1341 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
1342 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
1343 currently have a handler for, it will ask the user if the system
1344 should search for a package that would add support for this MIME type,
1345 and if the user say yes, the APT sources will be searched for packages
1346 advertising the MIME type in their control file (visible in the
1347 Packages file in the APT archive). If one or more packages are found,
1348 it is a simple click of the mouse to add support for the missing mime
1349 type. If the package require the user to accept some non-free
1350 license, this is explained to the user. The entire process make it
1351 more clear to the user why something do not work in the browser, and
1352 make the chances higher for the user to blame the web page authors and
1353 not the browser for any missing features.&lt;/li&gt;
1354
1355 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
1356 handlers.&lt;/strong&gt; When the media players encounter a format or codec
1357 it is not supporting, a dialog pop up asking the user if the system
1358 should search for a package that would add support for it. This
1359 happen with things like MP3, Windows Media or H.264. The selection
1360 and installation procedure is very similar to the Firefox browser
1361 plugin handling. This is as far as I know implemented using a
1362 gstreamer hook. The end result is that the user easily get access to
1363 the codecs that are present from the APT archives available, while
1364 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
1365
1366 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
1367 displaying a text/plain file in my Debian browser, it will propose to
1368 start emacs to show it. If I remember correctly, when doing the same
1369 in Kunbutu it show the file as a text file in the browser. At least I
1370 know Opera will show text files within the browser. I much prefer the
1371 latter behaviour.&lt;/li&gt;
1372
1373 &lt;/ol&gt;
1374
1375 &lt;p&gt;There are other nice features as well, like the simplified suite
1376 upgrader, but given that I am the one mostly doing the dist-upgrade,
1377 it do not matter much.&lt;/p&gt;
1378
1379 &lt;p&gt;I really hope we could get these features in place for the next
1380 Debian release. It would require the coordinated effort of several
1381 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
1382 </description>
1383 </item>
1384
1385 <item>
1386 <title>Gnash enteres Google Summer of Code 2011</title>
1387 <link>http://people.skolelinux.org/pere/blog/Gnash_enteres_Google_Summer_of_Code_2011.html</link>
1388 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_enteres_Google_Summer_of_Code_2011.html</guid>
1389 <pubDate>Wed, 6 Apr 2011 09:00:00 +0200</pubDate>
1390 <description>&lt;p&gt;&lt;a href=&quot;http://www.getgnash.org/&quot;&gt;The Gnash project&lt;/a&gt; is still
1391 the most promising solution for a Free Software Flash implementation.
1392 A few days ago the project
1393 &lt;a href=&quot;http://lists.gnu.org/archive/html/gnash-dev/2011-04/msg00011.html&quot;&gt;announced&lt;/a&gt;
1394 that it will participate in Google Summer of Code. I hope many
1395 students apply, and that some of them succeed in getting AVM2 support
1396 into Gnash.&lt;/p&gt;
1397 </description>
1398 </item>
1399
1400 <item>
1401 <title>Why isn&#39;t Debian Edu using VLC?</title>
1402 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
1403 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
1404 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
1405 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
1406 presented, and the winner among the multimedia player were VLC.
1407 Personally, I like VLC, and it is my player of choice when I first try
1408 to play a video file or stream. Only if VLC fail will I drag out
1409 gmplayer to see if it can do better. The reason is mostly the failure
1410 model and trust. When VLC fail, it normally pop up a error message
1411 reporting the problem. When mplayer fail, it normally segfault or
1412 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
1413
1414 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
1415 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
1416 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
1417 plugin to play web videos seamlessly, and the VLC browser plugin is
1418 not very good. For example, it lack in-line control buttons, so there
1419 is no way for the user to pause the video. Also, when I
1420 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
1421 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
1422 failed on several video pages where mplayer based plugins worked. If
1423 the browser plugin for VLC was as good as the gecko-mediaplayer
1424 package (which uses mplayer), we would switch.&lt;/P&gt;
1425
1426 &lt;p&gt;While VLC is a good player, its user interface is slightly
1427 annoying. The most annoying feature is its inconsistent use of
1428 keyboard shortcuts. When the player is in full screen mode, its
1429 shortcuts are different from when it is playing the video in a window.
1430 For example, space only work as pause when in full screen mode. I
1431 wish it had consisten shortcuts and that space also would work when in
1432 window mode. Another nice shortcut in gmplayer is [enter] to restart
1433 the current video. It is very nice when playing short videos from the
1434 web and want to restart it when new people arrive to have a look at
1435 what is going on.&lt;/p&gt;
1436 </description>
1437 </item>
1438
1439 <item>
1440 <title>Best å ikke fortelle noen at streaming er nedlasting...</title>
1441 <link>http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html</link>
1442 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html</guid>
1443 <pubDate>Sat, 30 Oct 2010 11:20:00 +0200</pubDate>
1444 <description>&lt;p&gt;I dag la jeg inn en kommentar på en sak hos NRKBeta
1445 &lt;a href=&quot;http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/&quot;&gt;om
1446 hvordan TV-serien Blindpassasjer ble laget&lt;/a&gt; i forbindelse med at
1447 filmene NRK la ut ikke var tilgjengelig i et
1448 &lt;a href=&quot;http://www.digistan.org/open-standard:definition&quot;&gt;fritt og
1449 åpent format&lt;/a&gt;. Dette var det jeg skrev publiserte der 07:39.&lt;/p&gt;
1450
1451 &lt;p&gt;&lt;blockquote&gt;
1452 &lt;p&gt;&quot;Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
1453 nedlasting. Mange av oss som kan mer enn gjennomsnittet om systemer
1454 som dette, vet at det stort sett er mulig å lure ut ting med den
1455 nødvendige forkunnskapen.&quot;&lt;/p&gt;
1456
1457 &lt;p&gt;Haha. Å streame innhold er det samme som å laste ned innhold, så å
1458 beskytte en stream mot nedlasting er ikke mulig. Å skrive noe slikt
1459 er å forlede leseren.&lt;/p&gt;
1460
1461 &lt;p&gt;Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
1462 vil tillate streaming men ikke nedlasting meningsløs.&lt;/p&gt;
1463
1464 &lt;p&gt;Anbefaler forresten å lese
1465 &lt;a href=&quot;http://blogs.computerworlduk.com/simon-says/2010/10/drm-is-toxic-to-culture/index.htm&quot;&gt;http://blogs.computerworlduk.com/simon-says/2010/10/drm-is-toxic-to-culture/index.htm&lt;/a&gt;
1466 om hva som ville være konsekvensen hvis digitale avspillingssperrer
1467 (DRM) fungerte. Det gjør de naturligvis ikke teknisk - det er jo
1468 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
1469 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
1470 opp under.&lt;/p&gt;
1471 &lt;/blockquote&gt;&lt;/p&gt;
1472
1473 &lt;p&gt;Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
1474 NRKBeta:&lt;/p&gt;
1475
1476 &lt;p&gt;&lt;blockquote&gt;
1477 &lt;p&gt;From: Anders Hofseth &amp;lt;XXX@gmail.com&gt;
1478 &lt;br&gt;To: &quot;pere@hungry.com&quot; &amp;lt;pere@hungry.com&gt;
1479 &lt;br&gt;Cc: Eirik Solheim &amp;lt;XXX@gmail.com&gt;, Jon Ståle Carlsen &amp;lt;XXX@gmail.com&gt;, Henrik Lied &amp;lt;XXX@gmail.com&gt;
1480 &lt;br&gt;Subject: Re: [NRKbeta] Kommentar: &quot;Bakom Blindpassasjer: del 1&quot;
1481 &lt;br&gt;Date: Sat, 30 Oct 2010 07:58:44 +0200&lt;/p&gt;
1482
1483 &lt;p&gt;Hei Petter.
1484 &lt;br&gt;Det du forsøker dra igang er egentlig en interessant diskusjon,
1485 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
1486 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
1487 særlig lett å klarere ut noe annet arkivmateriale på lang tid.&lt;/p&gt;
1488
1489 &lt;p&gt;Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
1490 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
1491 konsekvensene vi beskriver ikke er noe du ønsker heller...&lt;/p&gt;
1492
1493 &lt;p&gt;Med hilsen,
1494 &lt;br&gt;-anders&lt;/p&gt;
1495
1496 &lt;p&gt;Ring meg om noe er uklart: 95XXXXXXX&lt;/p&gt;
1497 &lt;/blockquote&gt;&lt;/p&gt;
1498
1499 &lt;p&gt;Ble så fascinert over denne holdningen, at jeg forfattet og sendte
1500 over følgende svar. I og med at debatten er fjernet fra NRK Betas
1501 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
1502 Har fjernet epostadresser og telefonnummer til de involverte, for å
1503 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.&lt;/p&gt;
1504
1505 &lt;p&gt;&lt;blockquote&gt;
1506 &lt;p&gt;From: Petter Reinholdtsen &amp;lt;pere@hungry.com&gt;
1507 &lt;br&gt;To: Anders Hofseth &amp;lt;XXX@gmail.com&gt;
1508 &lt;br&gt;Cc: Eirik Solheim &amp;lt;XXX@gmail.com&gt;,
1509 &lt;br&gt; Jon Ståle Carlsen &amp;lt;XXX@gmail.com&gt;,
1510 &lt;br&gt; Henrik Lied &amp;lt;XXX@gmail.com&gt;
1511 &lt;br&gt;Subject: Re: [NRKbeta] Kommentar: &quot;Bakom Blindpassasjer: del 1&quot;
1512 &lt;br&gt;Date: Sat, 30 Oct 2010 08:24:34 +0200&lt;/p&gt;
1513
1514 &lt;p&gt;[Anders Hofseth]
1515 &lt;br&gt;&gt; Hei Petter.&lt;/p&gt;
1516
1517 &lt;p&gt;Hei.&lt;/p&gt;
1518
1519 &lt;p&gt;&gt; Det du forsøker dra igang er egentlig en interessant diskusjon, men
1520 &lt;br&gt;&gt; om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
1521 &lt;br&gt;&gt; å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
1522 &lt;br&gt;&gt; særlig lett å klarere ut noe annet arkivmateriale på lang tid.&lt;/p&gt;
1523
1524 &lt;p&gt;Godt å se at du er enig i at dette er en interessant diskusjon. Den
1525 vil nok fortsette en stund til. :)&lt;/p&gt;
1526
1527 &lt;p&gt;Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
1528 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
1529 fortsette å legge ut arkivmateriale.&lt;/p&gt;
1530
1531 &lt;p&gt;Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
1532 faktum, som er at streaming er det samme som nedlasting, og at innhold
1533 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
1534 det.&lt;/p&gt;
1535
1536 &lt;p&gt;Det du sier er jo at klarering av arkivmateriale for publisering på
1537 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
1538 Det er ikke et argument som holder vann. :)&lt;/p&gt;
1539
1540 &lt;p&gt;&gt; Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
1541 &lt;br&gt;&gt; og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
1542 &lt;br&gt;&gt; konsekvensene vi beskriver ikke er noe du ønsker heller...&lt;/p&gt;
1543
1544 &lt;p&gt;Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
1545 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
1546 mot de som vil låse kulturen inne. Jeg synes det er en skam at NRK
1547 godtar å forlede publikum. Ville heller at NRK krever at innhold som
1548 skal sendes skal være uten bruksbegresninger og kan publiseres i
1549 formater som heller ikke har bruksbegresninger (bruksbegresningene til
1550 H.264 burde få varselbjellene i NRK til å ringe).&lt;/p&gt;
1551
1552 &lt;p&gt;At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
1553 påstander om at &quot;streaming beskytter mot nedlasting&quot; som bare er egnet
1554 til å bygge opp om en myte som er skadelig for samfunnet som helhet.&lt;/p&gt;
1555
1556 &lt;p&gt;Anbefaler &amp;lt;URL:&lt;a href=&quot;http://webmink.com/2010/09/03/h-264-and-foss/&quot;&gt;http://webmink.com/2010/09/03/h-264-and-foss/&lt;/a&gt;&gt; og en
1557 titt på
1558 &amp;lt;URL: &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html&quot;&gt;http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html&lt;/a&gt; &gt;.
1559 for å se hva slags bruksbegresninger H.264 innebærer.&lt;/p&gt;
1560
1561 &lt;p&gt;Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
1562 kan brukes før rettighetshaverene også innser at de er med på å skade
1563 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
1564 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
1565 langt på overtid.&lt;/p&gt;
1566
1567 &lt;p&gt;&gt; Ring meg om noe er uklart: XXX&lt;/p&gt;
1568
1569 &lt;p&gt;Intet uklart, men ikke imponert over måten dere håndterer debatten på.
1570 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
1571 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
1572 for videre diskusjon hadde dere i mine øyne kommet fra det med
1573 ryggraden på plass.&lt;/p&gt;
1574
1575 &lt;p&gt;PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.&lt;/p&gt;
1576
1577 &lt;p&gt;Som en liten avslutning, her er noen litt morsomme innslag om temaet.
1578 &amp;lt;URL: &lt;a href=&quot;http://www.archive.org/details/CopyingIsNotTheft&quot;&gt;http://www.archive.org/details/CopyingIsNotTheft&lt;/a&gt; &gt; og
1579 &amp;lt;URL: &lt;a href=&quot;http://patentabsurdity.com/&quot;&gt;http://patentabsurdity.com/&lt;/a&gt; &gt; hadde vært noe å kringkaste på
1580 NRK1. :)&lt;/p&gt;
1581
1582 &lt;p&gt;Vennlig hilsen,
1583 &lt;br&gt;--
1584 &lt;br&gt;Petter Reinholdtsen&lt;/p&gt;
1585 </description>
1586 </item>
1587
1588 <item>
1589 <title>Software updates 2010-10-24</title>
1590 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
1591 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
1592 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
1593 <description>&lt;p&gt;Some updates.&lt;/p&gt;
1594
1595 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
1596 raise money for the project is going well. The lower limit of 10
1597 signers was reached in 24 hours, and so far 13 people have signed it.
1598 More signers and more funding is most welcome, and I am really curious
1599 how far we can get before the time limit of December 24 is reached.
1600 :)&lt;/p&gt;
1601
1602 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
1603 about what appear to be a great code coverage tool capable of
1604 generating code coverage stats without any changes to the source code.
1605 It is called
1606 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
1607 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
1608 It is missing in Debian, but the git source built just fine in Squeeze
1609 after I installed libelf-dev, libdwarf-dev, pkg-config and
1610 libglib2.0-dev. Failed to build in Lenny, but suspect that is
1611 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
1612
1613 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
1614 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
1615 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
1616 alpha test release of the Squeeze based Debian Edu /
1617 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
1618 release. Give it a try if you need a complete linux solution for your
1619 school, including central infrastructure server, workstations, thin
1620 client servers and diskless workstations. A nice touch added
1621 yesterday is RDP support on the thin client servers, for windows
1622 clients to get a Linux desktop on request.&lt;/p&gt;
1623 </description>
1624 </item>
1625
1626 <item>
1627 <title>Pledge for funding to the Gnash project to get AVM2 support</title>
1628 <link>http://people.skolelinux.org/pere/blog/Pledge_for_funding_to_the_Gnash_project_to_get_AVM2_support.html</link>
1629 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Pledge_for_funding_to_the_Gnash_project_to_get_AVM2_support.html</guid>
1630 <pubDate>Tue, 19 Oct 2010 14:45:00 +0200</pubDate>
1631 <description>&lt;p&gt;&lt;a href=&quot;http://www.getgnash.org/&quot;&gt;The Gnash project&lt;/a&gt; is the
1632 most promising solution for a Free Software Flash implementation. It
1633 has done great so far, but there is still far to go, and recently its
1634 funding has dried up. I believe AVM2 support in Gnash is vital to the
1635 continued progress of the project, as more and more sites show up with
1636 AVM2 flash files.&lt;/p&gt;
1637
1638 &lt;p&gt;To try to get funding for developing such support, I have started
1639 &lt;a href=&quot;http://www.pledgebank.com/gnash-avm2&quot;&gt;a pledge&lt;/a&gt; with the
1640 following text:&lt;/P&gt;
1641
1642 &lt;p&gt;&lt;blockquote&gt;
1643
1644 &lt;p&gt;&quot;I will pay 100$ to the Gnash project to develop AVM2 support but
1645 only if 10 other people will do the same.&quot;&lt;/p&gt;
1646
1647 &lt;p&gt;- Petter Reinholdtsen, free software developer&lt;/p&gt;
1648
1649 &lt;p&gt;Deadline to sign up by: 24th December 2010&lt;/p&gt;
1650
1651 &lt;p&gt;The Gnash project need to get support for the new Flash file
1652 format AVM2 to work with a lot of sites using Flash on the
1653 web. Gnash already work with a lot of Flash sites using the old AVM1
1654 format, but more and more sites are using the AVM2 format these
1655 days. The project web page is available from
1656 http://www.getgnash.org/ . Gnash is a free software implementation
1657 of Adobe Flash, allowing those of us that do not accept the terms of
1658 the Adobe Flash license to get access to Flash sites.&lt;/p&gt;
1659
1660 &lt;p&gt;The project need funding to get developers to put aside enough
1661 time to develop the AVM2 support, and this pledge is my way to try
1662 to get this to happen.&lt;/p&gt;
1663
1664 &lt;p&gt;The project accept donations via the OpenMediaNow foundation,
1665 &lt;a href=&quot;http://www.openmedianow.org/?q=node/32&quot;&gt;http://www.openmedianow.org/?q=node/32&lt;/a&gt; .&lt;/p&gt;
1666
1667 &lt;/blockquote&gt;&lt;/p&gt;
1668
1669 &lt;p&gt;I hope you will support this effort too. I hope more than 10
1670 people will participate to make this happen. The more money the
1671 project gets, the more features it can develop using these funds.
1672 :)&lt;/p&gt;
1673 </description>
1674 </item>
1675
1676 <item>
1677 <title>Terms of use for video produced by a Canon IXUS 130 digital camera</title>
1678 <link>http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html</link>
1679 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html</guid>
1680 <pubDate>Thu, 9 Sep 2010 23:55:00 +0200</pubDate>
1681 <description>&lt;p&gt;A few days ago I had the mixed pleasure of bying a new digital
1682 camera, a Canon IXUS 130. It was instructive and very disturbing to
1683 be able to verify that also this camera producer have the nerve to
1684 specify how I can or can not use the videos produced with the camera.
1685 Even thought I was aware of the issue, the options with new cameras
1686 are limited and I ended up bying the camera anyway. What is the
1687 problem, you might ask? It is software patents, MPEG-4, H.264 and the
1688 MPEG-LA that is the problem, and our right to record our experiences
1689 without asking for permissions that is at risk.
1690
1691 &lt;p&gt;On page 27 of the Danish instruction manual, this section is
1692 written:&lt;/p&gt;
1693
1694 &lt;blockquote&gt;
1695 &lt;p&gt;This product is licensed under AT&amp;T patents for the MPEG-4 standard
1696 and may be used for encoding MPEG-4 compliant video and/or decoding
1697 MPEG-4 compliant video that was encoded only (1) for a personal and
1698 non-commercial purpose or (2) by a video provider licensed under the
1699 AT&amp;T patents to provide MPEG-4 compliant video.&lt;/p&gt;
1700
1701 &lt;p&gt;No license is granted or implied for any other use for MPEG-4
1702 standard.&lt;/p&gt;
1703 &lt;/blockquote&gt;
1704
1705 &lt;p&gt;In short, the camera producer have chosen to use technology
1706 (MPEG-4/H.264) that is only provided if I used it for personal and
1707 non-commercial purposes, or ask for permission from the organisations
1708 holding the knowledge monopoly (patent) for technology used.&lt;/p&gt;
1709
1710 &lt;p&gt;This issue has been brewing for a while, and I recommend you to
1711 read
1712 &quot;&lt;a href=&quot;http://www.osnews.com/story/23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA&quot;&gt;Why
1713 Our Civilization&#39;s Video Art and Culture is Threatened by the
1714 MPEG-LA&lt;/a&gt;&quot; by Eugenia Loli-Queru and
1715 &quot;&lt;a href=&quot;http://webmink.com/2010/09/03/h-264-and-foss/&quot;&gt;H.264 Is Not
1716 The Sort Of Free That Matters&lt;/a&gt;&quot; by Simon Phipps to learn more about
1717 the issue. The solution is to support the
1718 &lt;a href=&quot;http://www.digistan.org/open-standard:definition&quot;&gt;free and
1719 open standards&lt;/a&gt; for video, like &lt;a href=&quot;http://www.theora.org/&quot;&gt;Ogg
1720 Theora&lt;/a&gt;, and avoid MPEG-4 and H.264 if you can.&lt;/p&gt;
1721 </description>
1722 </item>
1723
1724 <item>
1725 <title>Some notes on Flash in Debian and Debian Edu</title>
1726 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
1727 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
1728 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
1729 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
1730 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
1731 second most popular used package that is missing in Debian. The sixth
1732 most popular is flashplayer-mozilla. This is a clear indication that
1733 working flash is important for Debian users. Around 10 percent of the
1734 users submitting data to popcon.debian.org have this package
1735 installed.&lt;/p&gt;
1736
1737 &lt;p&gt;In the report written by Lars Risan in August 2008
1738&lt;a href=&quot;http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile&amp;do=view&amp;target=Skolelinux_i_bruk_rapport_1.0.pdf&quot;&gt;Skolelinux
1739 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
1740 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
1741 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
1742 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
1743 web sites require Flash to work, and lacking working Flash support in
1744 the web browser and the problems with installing it was perceived as a
1745 good reason to stay with Windows.&lt;/p&gt;
1746
1747 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
1748 said to be the retarded cousin that did not really understand
1749 everything you told him but could work fairly well. This was a
1750 comment regarding the problems Linux have with proprietary formats and
1751 non-standard web pages, and is sad because it exposes a fairly common
1752 understanding of whose fault it is if web pages that only work in for
1753 example Internet Explorer 6 fail to work on Firefox, and funny because
1754 it explain very well how annoying it is for users when Linux
1755 distributions do not work with the documents they receive or the web
1756 pages they want to visit.&lt;/p&gt;
1757
1758 &lt;p&gt;This is part of the reason why I believe it is important for Debian
1759 and Debian Edu to have a well working Flash implementation in the
1760 distribution, to get at least popular sites as Youtube and Google
1761 Video to working out of the box. For Squeeze, Debian have the chance
1762 to include the latest version of Gnash that will make this happen, as
1763 the new release 0.8.8 was published a few weeks ago and is resting in
1764 unstable. The new version work with more sites that version 0.8.7.
1765 The Gnash maintainers have asked for a freeze exception, but the
1766 release team have not had time to reply to it yet. I hope they agree
1767 with me that Flash is important for the Debian desktop users, and thus
1768 accept the new package into Squeeze.&lt;/p&gt;
1769 </description>
1770 </item>
1771
1772 <item>
1773 <title>Regjerningens oppsummering av høringen om standardkatalogen versjon 2</title>
1774 <link>http://people.skolelinux.org/pere/blog/Regjerningens_oppsummering_av_h_ringen_om_standardkatalogen_versjon_2.html</link>
1775 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Regjerningens_oppsummering_av_h_ringen_om_standardkatalogen_versjon_2.html</guid>
1776 <pubDate>Thu, 9 Jul 2009 14:40:00 +0200</pubDate>
1777 <description>&lt;p&gt;For å forstå mer om hvorfor standardkatalogens versjon 2 ble som
1778 den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
1779 for regjeringen da de tok sin avgjørelse. De er nå lagt ut på NUUGs
1780 wiki, direkte tilgjengelig via &quot;&lt;a
1781 href=&quot;http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&amp;do=get&amp;target=kongelig-resolusjon.pdf&quot;&gt;Referansekatalogen
1782 v2.0 - Oppsummering av høring&lt;/a&gt;&quot; og &quot;&lt;a
1783 href=&quot;http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&amp;do=get&amp;target=kongelig-resolusjon-katalogutkast.pdf&quot;&gt;Referansekatalog
1784 for IT-standarder i offentlig sektor Versjon 2.0, dd.mm.åååå -
1785 UTKAST&lt;/a&gt;&quot;.&lt;/p&gt;
1786
1787 &lt;p&gt;Det er tre ting jeg merker meg i oppsummeringen fra
1788 høringsuttalelsen da jeg skummet igjennom den. Det første er at
1789 forståelsen av hvordan programvarepatenter påvirker fri
1790 programvareutvikling også i Norge når en argumenterer med at
1791 royalty-betaling ikke er et relevant problem i Norge. Det andre er at
1792 FAD ikke har en prinsipiell forståelse av verdien av en enkelt
1793 standard innenfor hvert område. Det siste er at påstander i
1794 høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
1795 Microsoft om hvordan Ogg blir standardisert og påstanden fra
1796 politidirektoratet om patentproblemer i Theora).&lt;/p&gt;
1797 </description>
1798 </item>
1799
1800 <item>
1801 <title>Regjerningen forlater prinsippet om ingen royalty-betaling i standardkatalogen versjon 2</title>
1802 <link>http://people.skolelinux.org/pere/blog/Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html</link>
1803 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html</guid>
1804 <pubDate>Mon, 6 Jul 2009 21:00:00 +0200</pubDate>
1805 <description>&lt;p&gt;Jeg ble glad da regjeringen
1806 &lt;a href=&quot;http://www.digi.no/817635/her-er-statens-nye-it-standarder&quot;&gt;annonserte&lt;/a&gt;
1807 versjon 2 av
1808 &lt;a href=&quot;http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf&quot;&gt;statens
1809 referansekatalog over standarder&lt;/a&gt;, men trist da jeg leste hva som
1810 faktisk var vedtatt etter
1811 &lt;a href=&quot;http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html&quot;&gt;høringen&lt;/a&gt;.
1812 De fleste av de valgte åpne standardene er gode og vil bidra til at
1813 alle kan delta på like vilkår i å lage løsninger for staten, men
1814 noen av dem blokkerer for de som ikke har anledning til å benytte
1815 spesifikasjoner som krever betaling for bruk (såkalt
1816 royalty-betaling). Det gjelder spesifikt for H.264 for video og MP3
1817 for lyd. Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
1818 Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
1819 fra statens websider gjøre dette uten å måtte bruke programmer der
1820 betaling for bruk var nødvendig. Når det nå er gjort valgfritt for
1821 de statlige etatene å bruke enten H.264 eller Theora (og MP3 eler
1822 Vorbis), så vil en bli tvunget til å forholde seg til
1823 royalty-belastede standarder for å få tilgang til videoen og
1824 lyden.&lt;/p&gt;
1825
1826 &lt;p&gt;Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
1827 at alle standarder som ble valgt til å være påkrevd i katalogen skulle
1828 være uten royalty-betaling. Jeg håper det ikke betyr at en har mistet
1829 all forståelse for hvilke prinsipper som må følges for å oppnå
1830 likeverdig konkurranse mellom aktørene i IT-bransjen. NUUG advarte
1831 mot dette i
1832 &lt;a href=&quot;http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2&quot;&gt;sin
1833 høringsuttalelse&lt;/a&gt;, men ser ut til å ha blitt ignorert.&lt;/p&gt;
1834
1835 &lt;p&gt;Oppdatering 2012-06-29: Kom over &lt;ahref=&quot;
1836 http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf&quot;&gt;en
1837 rapport til FAD&lt;/a&gt; fra da versjon 1 av katalogen ble vedtatt, og der
1838 er det tydelig at problemstillingen var kjent og forstått.&lt;/p&gt;
1839 </description>
1840 </item>
1841
1842 <item>
1843 <title>Microsofts misvisende argumentasjon rundt multimediaformater</title>
1844 <link>http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html</link>
1845 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html</guid>
1846 <pubDate>Fri, 26 Jun 2009 13:30:00 +0200</pubDate>
1847 <description>&lt;p&gt;I
1848 &lt;a href=&quot;http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf&quot;&gt;Microsoft
1849 sin høringsuttalelse&lt;/a&gt; til
1850 &lt;a href=&quot;http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html?id=549422&quot;&gt;forslag
1851 til versjon 2 av statens referansekatalog over standarder&lt;/a&gt;, lirer
1852 de av seg følgende FUD-perle:&lt;/p&gt;
1853
1854 &lt;p&gt;&lt;blockquote&gt;&quot;Vorbis, OGG, Theora og FLAC er alle tekniske
1855 spesifikasjoner overordnet styrt av xiph.org, som er en
1856 ikke-kommersiell organisasjon. Etablerte og anerkjente
1857 standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
1858 innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
1859 Det er derimot helt opp til hver enkelt organisasjon å bestemme
1860 hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
1861 spesifikasjonene bør derfor ikke defineres som åpne
1862 standarder.&quot;&lt;/blockquote&gt;&lt;/p&gt;
1863
1864 &lt;p&gt;De vokter seg vel for å nevne den anerkjente
1865 standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
1866 IP og det meste av protokoller på Internet, og RFC-standardene som
1867 IETF står bak. Ogg er spesifisert i
1868 &lt;a href=&quot;http://ietf.org/rfc/rfc3533.txt&quot;&gt;RFC 3533&lt;/a&gt;, og er uten
1869 tvil å anse som en åpen standard. Vorbis er
1870 &lt;a href=&quot;http://ietf.org/rfc/rfc5215.txt&quot;&gt;RFC 5215&lt;/a&gt;. Theora er
1871
1872 under standardisering via IETF, med
1873 &lt;a href=&quot;http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt&quot;&gt;siste
1874 utkast publisert 2006-07-21&lt;/a&gt; (riktignok er dermed teksten ikke
1875 skrevet i stein ennå, men det blir neppe endringer som ikke er
1876 bakoverkompatibel). De kan være inne på noe når det gjelder FLAC da
1877 jeg ikke finner tegn til at &lt;a
1878 href=&quot;http://flac.sourceforge.net/format.html&quot;&gt;spesifikasjonen
1879 tilgjengelig på web&lt;/a&gt; er på tur via noen
1880 standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
1881 og Vorbis også har involvert seg i Flac siden 2003, så ser jeg ikke
1882 bort fra at også den organiseres via IETF. Jeg kjenner personlig lite
1883 til FLAC.&lt;/p&gt;
1884
1885 &lt;p&gt;Uredelig argumentasjon bør en holde seg for god til å komme med,
1886 spesielt når det er så enkelt i dagens Internet-hverdag å gå
1887 misvisende påstander etter i sømmene.&lt;/p&gt;
1888 </description>
1889 </item>
1890
1891 <item>
1892 <title>When web browser developers make a video player...</title>
1893 <link>http://people.skolelinux.org/pere/blog/When_web_browser_developers_make_a_video_player___.html</link>
1894 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/When_web_browser_developers_make_a_video_player___.html</guid>
1895 <pubDate>Sat, 17 Jan 2009 18:50:00 +0100</pubDate>
1896 <description>&lt;p&gt;As part of the work we do in &lt;a href=&quot;http://www.nuug.no&quot;&gt;NUUG&lt;/a&gt;
1897 to publish video recordings of our monthly presentations, we provide a
1898 page with embedded video for easy access to the recording. Putting a
1899 good set of HTML tags together to get working embedded video in all
1900 browsers and across all operating systems is not easy. I hope this
1901 will become easier when the &amp;lt;video&amp;gt; tag is implemented in all
1902 browsers, but I am not sure. We provide the recordings in several
1903 formats, MPEG1, Ogg Theora, H.264 and Quicktime, and want the
1904 browser/media plugin to pick one it support and use it to play the
1905 recording, using whatever embed mechanism the browser understand.
1906 There is at least four different tags to use for this, the new HTML5
1907 &amp;lt;video&amp;gt; tag, the &amp;lt;object&amp;gt; tag, the &amp;lt;embed&amp;gt; tag and
1908 the &amp;lt;applet&amp;gt; tag. All of these take a lot of options, and
1909 finding the best options is a major challenge.&lt;/p&gt;
1910
1911 &lt;p&gt;I just tested the experimental Opera browser available from &lt;a
1912 href=&quot;http://labs.opera.com&quot;&gt;labs.opera.com&lt;/a&gt;, to see how it handled
1913 a &amp;lt;video&amp;gt; tag with a few video sources and no extra attributes.
1914 I was not very impressed. The browser start by fetching a picture
1915 from the video stream. Not sure if it is the first frame, but it is
1916 definitely very early in the recording. So far, so good. Next,
1917 instead of streaming the 76 MiB video file, it start to download all
1918 of it, but do not start to play the video. This mean I have to wait
1919 for several minutes for the downloading to finish. When the download
1920 is done, the playing of the video do not start! Waiting for the
1921 download, but I do not get to see the video? Some testing later, I
1922 discover that I have to add the controls=&quot;true&quot; attribute to be able
1923 to get a play button to pres to start the video. Adding
1924 autoplay=&quot;true&quot; did not help. I sure hope this is a misfeature of the
1925 test version of Opera, and that future implementations of the
1926 &amp;lt;video&amp;gt; tag will stream recordings by default, or at least start
1927 playing when the download is done.&lt;/p&gt;
1928
1929 &lt;p&gt;The test page I used (since changed to add more attributes) is
1930 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20090113-foredrag-om-foredrag/&quot;&gt;available
1931 from the nuug site&lt;/a&gt;. Will have to test it with the new Firefox
1932 too.&lt;/p&gt;
1933
1934 &lt;p&gt;In the test process, I discovered a missing feature. I was unable
1935 to find a way to get the URL of the playing video out of Opera, so I
1936 am not quite sure it picked the Ogg Theora version of the video. I
1937 sure hope it was using the announced Ogg Theora support. :)&lt;/p&gt;
1938 </description>
1939 </item>
1940
1941 <item>
1942 <title>The sorry state of multimedia browser plugins in Debian</title>
1943 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
1944 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
1945 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
1946 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
1947 plugins available in Debian Lenny, to see which one we should use by
1948 default in Debian Edu. We need an embedded video playing plugin with
1949 control buttons to pause or stop the video, and capable of streaming
1950 all the multimedia content available on the web. The test results and
1951 notes are available on
1952 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
1953 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
1954 fill this need. My personal video player favorite, VLC, has a really
1955 bad plugin which fail on a lot of the test pages. A lot of the MIME
1956 types I would expect to work with any free software player (like
1957 video/ogg), just do not work. And simple formats like the
1958 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
1959 totem and vlc plugins. I hope the situation will improve soon. No
1960 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
1961
1962 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
1963 be the only one fitting our needs. :/&lt;/p&gt;
1964 </description>
1965 </item>
1966
1967 </channel>
1968 </rss>