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