]> pere.pagekite.me Git - homepage.git/blob - blog/tags/multimedia/multimedia.rss
8cc7eab3c2069fd88cbd3d49bfcd4aef9c43b13d
[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>youtube-dl for nedlasting fra NRK med undertekster - nice free software</title>
11 <link>http://people.skolelinux.org/pere/blog/youtube_dl_for_nedlasting_fra_NRK_med_undertekster___nice_free_software.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/youtube_dl_for_nedlasting_fra_NRK_med_undertekster___nice_free_software.html</guid>
13 <pubDate>Sat, 28 Apr 2018 10:30:00 +0200</pubDate>
14 <description>&lt;p&gt;I &lt;a href=&quot;https://no.wikipedia.org/wiki/VHS&quot;&gt;VHS-kassettenes&lt;/a&gt;
15 tid var det rett frem å ta vare på et TV-program en ønsket å kunne se
16 senere, uten å være avhengig av at programmet ble sendt på nytt.
17 Kanskje ønsket en å se programmet på hytten der det ikke var
18 TV-signal, eller av andre grunner ha det tilgjengelig for fremtidig
19 fornøyelse. Dette er blitt vanskeligere med introduksjon av
20 digital-TV og webstreaming, der opptak til harddisk er utenfor de
21 flestes kontroll. Men for NRK her i Norge, finnes det heldigvis flere
22 fri programvare-alternativer, som jeg har
23 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html&quot;&gt;skrevet&lt;/a&gt;
24 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html&quot;&gt;om&lt;/a&gt;
25 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html&quot;&gt;før&lt;/a&gt;.
26 Så lenge kilden for nedlastingen er lovlig lagt ut på nett (hvilket
27 jeg antar NRK gjør), så er slik lagring til privat bruk også lovlig i
28 Norge.&lt;/p&gt;
29
30 &lt;p&gt;Sist jeg så på saken, i 2016, nevnte jeg at
31 &lt;a href=&quot;https://rg3.github.com/youtube-dl/&quot;&gt;youtube-dl&lt;/a&gt; ikke kunne
32 bake undertekster fra NRK inn i videofilene, og at jeg derfor
33 foretrakk andre alternativer. Nylig oppdaget jeg at dette har endret
34 seg. Fordelen med youtube-dl er at den er tilgjengelig direkte fra
35 Linux-distribusjoner som &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
36 og &lt;a href=&quot;https://www.ubuntu.com/&quot;&gt;Ubuntu&lt;/a&gt;, slik at en slipper å
37 finne ut selv hvordan en skal få dem til å virke.&lt;/p&gt;
38
39 &lt;p&gt;For å laste ned et NRK-innslag med undertekster, og få den norske
40 underteksten pakket inn i videofilen, så kan følgende kommando
41 brukes:&lt;/p&gt;
42
43 &lt;p&gt;&lt;pre&gt;
44 youtube-dl --write-sub --sub-format ttml \
45 --convert-subtitles srt --embed-subs \
46 https://tv.nrk.no/serie/ramm-ferdig-gaa/MUHU11000316/27-04-2018
47 &lt;/pre&gt;&lt;/p&gt;
48
49 &lt;p&gt;URL-eksemplet er dagens toppsak på tv.nrk.no. Resultatet er en
50 MP4-fil med filmen og undertekster som kan spilles av med VLC. Merk
51 at VLC ikke viser frem undertekster før du aktiverer dem. For å gjøre
52 det, høyreklikk med musa i fremviservinduet, velg menyvalget for
53 undertekst og så norsk språk. Jeg testet også &#39;--write-auto-sub&#39;,
54 men det kommandolinjeargumentet ser ikke ut til å fungere, så jeg
55 endte opp med settet med argumentlisten over, som jeg fant i en
56 feilrapport i youtube-dl-prosjektets samling over feilrapporter.&lt;/p&gt;
57
58 &lt;p&gt;Denne støtten i youtube-dl gjør det svært enkelt å lagre
59 NRK-innslag, det være seg nyheter, filmer, serier eller dokumentater,
60 for å ha dem tilgjengelig for fremtidig referanse og bruk, uavhengig
61 av hvor lenge innslagene ligger tilgjengelig hos NRK. Så får det ikke
62 hjelpe at NRKs jurister mener at det er
63 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html&quot;&gt;vesensforskjellig
64 å legge tilgjengelig for nedlasting og for streaming&lt;/a&gt;, når det rent
65 teknisk er samme sak.&lt;/p&gt;
66
67 &lt;p&gt;Programmet youtube-dl støtter også en rekke andre nettsteder, se
68 prosjektoversikten for
69 &lt;a href=&quot;http://rg3.github.io/youtube-dl/supportedsites.html&quot;&gt;en
70 komplett liste&lt;/a&gt;.&lt;/p&gt;
71 </description>
72 </item>
73
74 <item>
75 <title>The new &quot;best&quot; multimedia player in Debian?</title>
76 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
77 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
78 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
79 <description>&lt;p&gt;When I set out a few weeks ago to figure out
80 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
81 multimedia player in Debian claimed to support most file formats /
82 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
83 the various players claimed support for. The range was from 55 to 130
84 MIME types. I suspect most media formats are supported by all
85 players, but this is not really reflected in the MimeTypes values in
86 their desktop files. There are probably also some bogus MIME types
87 listed, but it is hard to identify which one this is.&lt;/p&gt;
88
89 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
90 the players suggesting to add more MIME types to their desktop files,
91 and decided to spend some time myself improving the situation for my
92 favorite media player VLC. The fixes for VLC entered Debian unstable
93 yesterday. The complete list of MIME types can be seen on the
94 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
95 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
96
97 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
98 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
99 kmplayer. I am sure some of the other players desktop files support
100 several of the formats currently listed as working only with vlc,
101 toten and parole.&lt;/p&gt;
102
103 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
104 supported by all the tested multimedia players in Debian in their
105 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
106 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
107 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
108 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
109 it sad that video/ogg and video/webm is not supported by all the media
110 players in Debian. As far as I can tell, all of them can handle both
111 formats.&lt;/p&gt;
112 </description>
113 </item>
114
115 <item>
116 <title>What is the best multimedia player in Debian?</title>
117 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
118 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
119 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
120 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
121 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
122
123 &lt;p&gt;A few years ago, I had a look at the media support for Browser
124 plugins in Debian, to get an idea which plugins to include in Debian
125 Edu. I created a script to extract the set of supported MIME types
126 for each plugin, and used this to find out which multimedia browser
127 plugin supported most file formats / media types.
128 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
129 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
130 not been updated for a while. But browser plugins are less relevant
131 these days, so I thought it was time to look at standalone
132 players.&lt;/p&gt;
133
134 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
135 player when I wanted to play videos from the Norwegian National
136 Broadcasting Company, and decided to investigate why. The cause is a
137 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
138 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
139 of MIME types announced in the desktop file and the browser plugin,
140 only to discover that there is quite a large difference between the
141 two for VLC. This discovery made me dig up the script I used to
142 compare browser plugins, and adjust it to compare desktop files
143 instead, to try to figure out which multimedia player in Debian
144 support most file formats.&lt;/p&gt;
145
146 &lt;p&gt;The result can be seen on the Debian Wiki, as
147 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
148 table listing all MIME types supported by one of the packages included
149 in the table&lt;/a&gt;, with the package supporting most MIME types being
150 listed first in the table.&lt;/p&gt;
151
152 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
153 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
154 kmplayer. Time for the other players to update their announced MIME
155 support?&lt;/p&gt;
156 </description>
157 </item>
158
159 <item>
160 <title>Nedlasting fra NRK, som Matroska med undertekster</title>
161 <link>http://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html</link>
162 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html</guid>
163 <pubDate>Sat, 2 Jan 2016 13:50:00 +0100</pubDate>
164 <description>&lt;p&gt;Det kommer stadig nye løsninger for å ta lagre unna innslag fra NRK
165 for å se på det senere. For en stund tilbake kom jeg over et script
166 nrkopptak laget av Ingvar Hagelund. Han fjernet riktignok sitt script
167 etter forespørsel fra Erik Bolstad i NRK, men noen tok heldigvis og
168 gjorde det &lt;a href=&quot;https://github.com/liangqi/nrkopptak&quot;&gt;tilgjengelig
169 via github&lt;/a&gt;.&lt;/p&gt;
170
171 &lt;p&gt;Scriptet kan lagre som MPEG4 eller Matroska, og bake inn
172 undertekster i fila på et vis som blant annet VLC forstår. For å
173 bruke scriptet, kopier ned git-arkivet og kjør&lt;/p&gt;
174
175 &lt;p&gt;&lt;pre&gt;
176 nrkopptak/bin/nrk-opptak k &lt;ahref=&quot;https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-1/episode-1&quot;&gt;https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-1/episode-1&lt;/a&gt;
177 &lt;/pre&gt;&lt;/p&gt;
178
179 &lt;p&gt;URL-eksemplet er dagens toppsak på tv.nrk.no. Argument &#39;k&#39; ber
180 scriptet laste ned og lagre som Matroska. Det finnes en rekke andre
181 muligheter for valg av kvalitet og format.&lt;/p&gt;
182
183 &lt;p&gt;Jeg foretrekker dette scriptet fremfor youtube-dl, som
184 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html&quot;&gt;
185 nevnt i 2014 støtter NRK&lt;/a&gt; og en rekke andre videokilder, på grunn
186 av at nrkopptak samler undertekster og video i en enkelt fil, hvilket
187 gjør håndtering enklere på disk.&lt;/p&gt;
188 </description>
189 </item>
190
191 <item>
192 <title>MPEG LA on &quot;Internet Broadcast AVC Video&quot; licensing and non-private use</title>
193 <link>http://people.skolelinux.org/pere/blog/MPEG_LA_on__Internet_Broadcast_AVC_Video__licensing_and_non_private_use.html</link>
194 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/MPEG_LA_on__Internet_Broadcast_AVC_Video__licensing_and_non_private_use.html</guid>
195 <pubDate>Tue, 7 Jul 2015 09:50:00 +0200</pubDate>
196 <description>&lt;p&gt;After asking the Norwegian Broadcasting Company (NRK)
197 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Hva_gj_r_at_NRK_kan_distribuere_H_264_video_uten_patentavtale_med_MPEG_LA_.html&quot;&gt;why
198 they can broadcast and stream H.264 video without an agreement with
199 the MPEG LA&lt;/a&gt;, I was wiser, but still confused. So I asked MPEG LA
200 if their understanding matched that of NRK. As far as I can tell, it
201 does not.&lt;/p&gt;
202
203 &lt;p&gt;I started by asking for more information about the various
204 licensing classes and what exactly is covered by the &quot;Internet
205 Broadcast AVC Video&quot; class that NRK pointed me at to explain why NRK
206 did not need a license for streaming H.264 video:
207
208 &lt;p&gt;&lt;blockquote&gt;
209
210 &lt;p&gt;According to
211 &lt;a href=&quot;http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf&quot;&gt;a
212 MPEG LA press release dated 2010-02-02&lt;/a&gt;, there is no charge when
213 using MPEG AVC/H.264 according to the terms of &quot;Internet Broadcast AVC
214 Video&quot;. I am trying to understand exactly what the terms of &quot;Internet
215 Broadcast AVC Video&quot; is, and wondered if you could help me. What
216 exactly is covered by these terms, and what is not?&lt;/p&gt;
217
218 &lt;p&gt;The only source of more information I have been able to find is a
219 PDF named
220 &lt;a href=&quot;http://www.mpegla.com/main/programs/avc/Documents/avcweb.pdf&quot;&gt;AVC
221 Patent Portfolio License Briefing&lt;/a&gt;, which states this about the
222 fees:&lt;/p&gt;
223
224 &lt;ul&gt;
225 &lt;li&gt;Where End User pays for AVC Video
226 &lt;ul&gt;
227 &lt;li&gt;Subscription (not limited by title) – 100,000 or fewer
228 subscribers/yr = no royalty; &amp;gt; 100,000 to 250,000 subscribers/yr =
229 $25,000; &amp;gt;250,000 to 500,000 subscribers/yr = $50,000; &amp;gt;500,000 to
230 1M subscribers/yr = $75,000; &amp;gt;1M subscribers/yr = $100,000&lt;/li&gt;
231
232 &lt;li&gt;Title-by-Title - 12 minutes or less = no royalty; &amp;gt;12 minutes in
233 length = lower of (a) 2% or (b) $0.02 per title&lt;/li&gt;
234 &lt;/ul&gt;&lt;/li&gt;
235
236 &lt;li&gt;Where remuneration is from other sources
237 &lt;ul&gt;
238 &lt;li&gt;Free Television - (a) one-time $2,500 per transmission encoder or
239 (b) annual fee starting at $2,500 for &amp;gt; 100,000 HH rising to
240 maximum $10,000 for &amp;gt;1,000,000 HH&lt;/li&gt;
241
242 &lt;li&gt;Internet Broadcast AVC Video (not title-by-title, not subscription)
243 – no royalty for life of the AVC Patent Portfolio License&lt;/li&gt;
244 &lt;/ul&gt;&lt;/li&gt;
245 &lt;/ul&gt;
246
247 &lt;p&gt;Am I correct in assuming that the four categories listed is the
248 categories used when selecting licensing terms, and that &quot;Internet
249 Broadcast AVC Video&quot; is the category for things that do not fall into
250 one of the other three categories? Can you point me to a good source
251 explaining what is ment by &quot;title-by-title&quot; and &quot;Free Television&quot; in
252 the license terms for AVC/H.264?&lt;/p&gt;
253
254 &lt;p&gt;Will a web service providing H.264 encoded video content in a
255 &quot;video on demand&quot; fashing similar to Youtube and Vimeo, where no
256 subscription is required and no payment is required from end users to
257 get access to the videos, fall under the terms of the &quot;Internet
258 Broadcast AVC Video&quot;, ie no royalty for life of the AVC Patent
259 Portfolio license? Does it matter if some users are subscribed to get
260 access to personalized services?&lt;/p&gt;
261
262 &lt;p&gt;Note, this request and all answers will be published on the
263 Internet.&lt;/p&gt;
264 &lt;/blockquote&gt;&lt;/p&gt;
265
266 &lt;p&gt;The answer came quickly from Benjamin J. Myers, Licensing Associate
267 with the MPEG LA:&lt;/p&gt;
268
269 &lt;p&gt;&lt;blockquote&gt;
270 &lt;p&gt;Thank you for your message and for your interest in MPEG LA. We
271 appreciate hearing from you and I will be happy to assist you.&lt;/p&gt;
272
273 &lt;p&gt;As you are aware, MPEG LA offers our AVC Patent Portfolio License
274 which provides coverage under patents that are essential for use of
275 the AVC/H.264 Standard (MPEG-4 Part 10). Specifically, coverage is
276 provided for end products and video content that make use of AVC/H.264
277 technology. Accordingly, the party offering such end products and
278 video to End Users concludes the AVC License and is responsible for
279 paying the applicable royalties.&lt;/p&gt;
280
281 &lt;p&gt;Regarding Internet Broadcast AVC Video, the AVC License generally
282 defines such content to be video that is distributed to End Users over
283 the Internet free-of-charge. Therefore, if a party offers a service
284 which allows users to upload AVC/H.264 video to its website, and such
285 AVC Video is delivered to End Users for free, then such video would
286 receive coverage under the sublicense for Internet Broadcast AVC
287 Video, which is not subject to any royalties for the life of the AVC
288 License. This would also apply in the scenario where a user creates a
289 free online account in order to receive a customized offering of free
290 AVC Video content. In other words, as long as the End User is given
291 access to or views AVC Video content at no cost to the End User, then
292 no royalties would be payable under our AVC License.&lt;/p&gt;
293
294 &lt;p&gt;On the other hand, if End Users pay for access to AVC Video for a
295 specific period of time (e.g., one month, one year, etc.), then such
296 video would constitute Subscription AVC Video. In cases where AVC
297 Video is delivered to End Users on a pay-per-view basis, then such
298 content would constitute Title-by-Title AVC Video. If a party offers
299 Subscription or Title-by-Title AVC Video to End Users, then they would
300 be responsible for paying the applicable royalties you noted below.&lt;/p&gt;
301
302 &lt;p&gt;Finally, in the case where AVC Video is distributed for free
303 through an &quot;over-the-air, satellite and/or cable transmission&quot;, then
304 such content would constitute Free Television AVC Video and would be
305 subject to the applicable royalties.&lt;/p&gt;
306
307 &lt;p&gt;For your reference, I have attached
308 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-07-07-mpegla.pdf&quot;&gt;a
309 .pdf copy of the AVC License&lt;/a&gt;. You will find the relevant
310 sublicense information regarding AVC Video in Sections 2.2 through
311 2.5, and the corresponding royalties in Section 3.1.2 through 3.1.4.
312 You will also find the definitions of Title-by-Title AVC Video,
313 Subscription AVC Video, Free Television AVC Video, and Internet
314 Broadcast AVC Video in Section 1 of the License. Please note that the
315 electronic copy is provided for informational purposes only and cannot
316 be used for execution.&lt;/p&gt;
317
318 &lt;p&gt;I hope the above information is helpful. If you have additional
319 questions or need further assistance with the AVC License, please feel
320 free to contact me directly.&lt;/p&gt;
321 &lt;/blockquote&gt;&lt;/p&gt;
322
323 &lt;p&gt;Having a fresh copy of the license text was useful, and knowing
324 that the definition of Title-by-Title required payment per title made
325 me aware that my earlier understanding of that phrase had been wrong.
326 But I still had a few questions:&lt;/p&gt;
327
328 &lt;p&gt;&lt;blockquote&gt;
329 &lt;p&gt;I have a small followup question. Would it be possible for me to get
330 a license with MPEG LA even if there are no royalties to be paid? The
331 reason I ask, is that some video related products have a copyright
332 clause limiting their use without a license with MPEG LA. The clauses
333 typically look similar to this:
334
335 &lt;p&gt;&lt;blockquote&gt;
336 This product is licensed under the AVC patent portfolio license for
337 the personal and non-commercial use of a consumer to (a) encode
338 video in compliance with the AVC standard (&quot;AVC video&quot;) and/or (b)
339 decode AVC video that was encoded by a consumer engaged in a
340 personal and non-commercial activity and/or AVC video that was
341 obtained from a video provider licensed to provide AVC video. No
342 license is granted or shall be implied for any other use. additional
343 information may be obtained from MPEG LA L.L.C.
344 &lt;/blockquote&gt;&lt;/p&gt;
345
346 &lt;p&gt;It is unclear to me if this clause mean that I need to enter into
347 an agreement with MPEG LA to use the product in question, even if
348 there are no royalties to be paid to MPEG LA. I suspect it will
349 differ depending on the jurisdiction, and mine is Norway. What is
350 MPEG LAs view on this?&lt;/p&gt;
351 &lt;/blockquote&gt;&lt;/p&gt;
352
353 &lt;p&gt;According to the answer, MPEG LA believe those using such tools for
354 non-personal or commercial use need a license with them:&lt;/p&gt;
355
356 &lt;p&gt;&lt;blockquote&gt;
357
358 &lt;p&gt;With regard to the Notice to Customers, I would like to begin by
359 clarifying that the Notice from Section 7.1 of the AVC License
360 reads:&lt;/p&gt;
361
362 &lt;p&gt;THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR
363 THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT
364 RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC
365 STANDARD (&quot;AVC VIDEO&quot;) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED
366 BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM
367 A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED
368 OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE
369 OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM&lt;/p&gt;
370
371 &lt;p&gt;The Notice to Customers is intended to inform End Users of the
372 personal usage rights (for example, to watch video content) included
373 with the product they purchased, and to encourage any party using the
374 product for commercial purposes to contact MPEG LA in order to become
375 licensed for such use (for example, when they use an AVC Product to
376 deliver Title-by-Title, Subscription, Free Television or Internet
377 Broadcast AVC Video to End Users, or to re-Sell a third party&#39;s AVC
378 Product as their own branded AVC Product).&lt;/p&gt;
379
380 &lt;p&gt;Therefore, if a party is to be licensed for its use of an AVC
381 Product to Sell AVC Video on a Title-by-Title, Subscription, Free
382 Television or Internet Broadcast basis, that party would need to
383 conclude the AVC License, even in the case where no royalties were
384 payable under the License. On the other hand, if that party (either a
385 Consumer or business customer) simply uses an AVC Product for their
386 own internal purposes and not for the commercial purposes referenced
387 above, then such use would be included in the royalty paid for the AVC
388 Products by the licensed supplier.&lt;/p&gt;
389
390 &lt;p&gt;Finally, I note that our AVC License provides worldwide coverage in
391 countries that have AVC Patent Portfolio Patents, including
392 Norway.&lt;/p&gt;
393
394 &lt;p&gt;I hope this clarification is helpful. If I may be of any further
395 assistance, just let me know.&lt;/p&gt;
396 &lt;/blockquote&gt;&lt;/p&gt;
397
398 &lt;p&gt;The mentioning of Norwegian patents made me a bit confused, so I
399 asked for more information:&lt;/p&gt;
400
401 &lt;p&gt;&lt;blockquote&gt;
402
403 &lt;p&gt;But one minor question at the end. If I understand you correctly,
404 you state in the quote above that there are patents in the AVC Patent
405 Portfolio that are valid in Norway. This make me believe I read the
406 list available from &amp;lt;URL:
407 &lt;a href=&quot;http://www.mpegla.com/main/programs/AVC/Pages/PatentList.aspx&quot;&gt;http://www.mpegla.com/main/programs/AVC/Pages/PatentList.aspx&lt;/a&gt;
408 &amp;gt; incorrectly, as I believed the &quot;NO&quot; prefix in front of patents
409 were Norwegian patents, and the only one I could find under Mitsubishi
410 Electric Corporation expired in 2012. Which patents are you referring
411 to that are relevant for Norway?&lt;/p&gt;
412
413 &lt;/blockquote&gt;&lt;/p&gt;
414
415 &lt;p&gt;Again, the quick answer explained how to read the list of patents
416 in that list:&lt;/p&gt;
417
418 &lt;p&gt;&lt;blockquote&gt;
419
420 &lt;p&gt;Your understanding is correct that the last AVC Patent Portfolio
421 Patent in Norway expired on 21 October 2012. Therefore, where AVC
422 Video is both made and Sold in Norway after that date, then no
423 royalties would be payable for such AVC Video under the AVC License.
424 With that said, our AVC License provides historic coverage for AVC
425 Products and AVC Video that may have been manufactured or Sold before
426 the last Norwegian AVC patent expired. I would also like to clarify
427 that coverage is provided for the country of manufacture and the
428 country of Sale that has active AVC Patent Portfolio Patents.&lt;/p&gt;
429
430 &lt;p&gt;Therefore, if a party offers AVC Products or AVC Video for Sale in
431 a country with active AVC Patent Portfolio Patents (for example,
432 Sweden, Denmark, Finland, etc.), then that party would still need
433 coverage under the AVC License even if such products or video are
434 initially made in a country without active AVC Patent Portfolio
435 Patents (for example, Norway). Similarly, a party would need to
436 conclude the AVC License if they make AVC Products or AVC Video in a
437 country with active AVC Patent Portfolio Patents, but eventually Sell
438 such AVC Products or AVC Video in a country without active AVC Patent
439 Portfolio Patents.&lt;/p&gt;
440 &lt;/blockquote&gt;&lt;/p&gt;
441
442 &lt;p&gt;As far as I understand it, MPEG LA believe anyone using Adobe
443 Premiere and other video related software with a H.264 distribution
444 license need a license agreement with MPEG LA to use such tools for
445 anything non-private or commercial, while it is OK to set up a
446 Youtube-like service as long as no-one pays to get access to the
447 content. I still have no clear idea how this applies to Norway, where
448 none of the patents MPEG LA is licensing are valid. Will the
449 copyright terms take precedence or can those terms be ignored because
450 the patents are not valid in Norway?&lt;/p&gt;
451 </description>
452 </item>
453
454 <item>
455 <title>MakerCon Nordic videos now available on Frikanalen</title>
456 <link>http://people.skolelinux.org/pere/blog/MakerCon_Nordic_videos_now_available_on_Frikanalen.html</link>
457 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/MakerCon_Nordic_videos_now_available_on_Frikanalen.html</guid>
458 <pubDate>Thu, 2 Jul 2015 14:10:00 +0200</pubDate>
459 <description>&lt;p&gt;Last oktober I was involved on behalf of
460 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;NUUG&lt;/a&gt; with recording the talks at
461 &lt;a href=&quot;http://www.makercon.no/&quot;&gt;MakerCon Nordic&lt;/a&gt;, a conference for
462 the Maker movement. Since then it has been the plan to publish the
463 recordings on &lt;a href=&quot;http://www.frikanalen.no/&quot;&gt;Frikanalen&lt;/a&gt;, which
464 finally happened the last few days. A few talks are missing because
465 the speakers asked the organizers to not publish them, but most of the
466 talks are available. The talks are being broadcasted on RiksTV
467 channel 50 and using multicast on Uninett, as well as being available
468 from the Frikanalen web site. The unedited recordings are
469 &lt;a href=&quot;https://www.youtube.com/user/MakerConNordic/&quot;&gt;available on
470 Youtube too&lt;/a&gt;.&lt;/p&gt;
471
472 &lt;p&gt;This is the list of talks available at the moment. Visit the
473 &lt;a href=&quot;http://beta.frikanalen.no/video/?q=makercon&quot;&gt;Frikanalen video
474 pages&lt;/a&gt; to view them.&lt;/p&gt;
475
476 &lt;ul&gt;
477
478 &lt;li&gt;Evolutionary algorithms as a design tool - from art
479 to robotics (Kyrre Glette)&lt;/li&gt;
480
481 &lt;li&gt;Make and break (Hans Gerhard Meier)&lt;/li&gt;
482
483 &lt;li&gt;Making a one year school course for young makers
484 (Olav Helland)&lt;/li&gt;
485
486 &lt;li&gt;Innovation Inspiration - IPR Databases as a Source of
487 Inspiration (Hege Langlo)&lt;/li&gt;
488
489 &lt;li&gt;Making a toy for makers (Erik Torstensson)&lt;/li&gt;
490
491 &lt;li&gt;How to make 3D printer electronics (Elias Bakken)&lt;/li&gt;
492
493 &lt;li&gt;Hovering Clouds: Looking at online tool offerings for Product
494 Design and 3D Printing (William Kempton)&lt;/li&gt;
495
496 &lt;li&gt;Travelling maker stories (Øyvind Nydal Dahl)&lt;/li&gt;
497
498 &lt;li&gt;Making the first Maker Faire in Sweden (Nils Olander)&lt;/li&gt;
499
500 &lt;li&gt;Breaking the mold: Printing 1000’s of parts (Espen Sivertsen)&lt;/li&gt;
501
502 &lt;li&gt;Ultimaker — and open source 3D printing (Erik de Bruijn)&lt;/li&gt;
503
504 &lt;li&gt;Autodesk’s 3D Printing Platform: Sparking innovation (Hilde
505 Sevens)&lt;/li&gt;
506
507 &lt;li&gt;How Making is Changing the World – and How You Can Too!
508 (Jennifer Turliuk)&lt;/li&gt;
509
510 &lt;li&gt;Open-Source Adventuring: OpenROV, OpenExplorer and the Future of
511 Connected Exploration (David Lang)&lt;/li&gt;
512
513 &lt;li&gt;Making in Norway (Haakon Karlsen Jr., Graham Hayward and Jens
514 Dyvik)&lt;/li&gt;
515
516 &lt;li&gt;The Impact of the Maker Movement (Mike Senese)&lt;/li&gt;
517
518 &lt;/ul&gt;
519
520 &lt;p&gt;Part of the reason this took so long was that the scripts NUUG had
521 to prepare a recording for publication were five years old and no
522 longer worked with the current video processing tools (command line
523 argument changes). In addition, we needed better audio normalization,
524 which sent me on a detour to
525 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Measuring_and_adjusting_the_loudness_of_a_TV_channel_using_bs1770gain.html&quot;&gt;package
526 bs1770gain for Debian&lt;/a&gt;. Now this is in place and it became a lot
527 easier to publish NUUG videos on Frikanalen.&lt;/p&gt;
528 </description>
529 </item>
530
531 <item>
532 <title>Measuring and adjusting the loudness of a TV channel using bs1770gain</title>
533 <link>http://people.skolelinux.org/pere/blog/Measuring_and_adjusting_the_loudness_of_a_TV_channel_using_bs1770gain.html</link>
534 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Measuring_and_adjusting_the_loudness_of_a_TV_channel_using_bs1770gain.html</guid>
535 <pubDate>Thu, 11 Jun 2015 13:40:00 +0200</pubDate>
536 <description>&lt;p&gt;Television loudness is the source of frustration for viewers
537 everywhere. Some channels are very load, others are less loud, and
538 ads tend to shout very high to get the attention of the viewers, and
539 the viewers do not like this. This fact is well known to the TV
540 channels. See for example the BBC white paper
541 &quot;&lt;a href=&quot;http://downloads.bbc.co.uk/rd/pubs/whp/whp-pdf-files/WHP202.pdf&quot;&gt;Terminology
542 for loudness and level dBTP, LU, and all that&lt;/a&gt;&quot; from 2011 for a
543 summary of the problem domain. To better address the need for even
544 loadness, the TV channels got together several years ago to agree on a
545 new way to measure loudness in digital files as one step in
546 standardizing loudness. From this came the ITU-R standard BS.1770,
547 &quot;&lt;a href=&quot;http://www.itu.int/rec/R-REC-BS.1770/en&quot;&gt;Algorithms to
548 measure audio programme loudness and true-peak audio level&lt;/a&gt;&quot;.&lt;/p&gt;
549
550 &lt;p&gt;The ITU-R BS.1770 specification describe an algorithm to measure
551 loadness in LUFS (Loudness Units, referenced to Full Scale). But
552 having a way to measure is not enough. To get the same loudness
553 across TV channels, one also need to decide which value to standardize
554 on. For European TV channels, this was done in the EBU Recommondaton
555 R128, &quot;&lt;a href=&quot;https://tech.ebu.ch/docs/r/r128.pdf&quot;&gt;Loudness
556 normalisation and permitted maximum level of audio signals&lt;/a&gt;&quot;, which
557 specifies a recommended level of -23 LUFS. In Norway, I have been
558 told that NRK, TV2, MTG and SBS have decided among themselves to
559 follow the R128 recommondation for playout from 2016-03-01.&lt;/p&gt;
560
561 &lt;p&gt;There are free software available to measure and adjust the loudness
562 level using the LUFS. In Debian, I am aware of a library named
563 &lt;a href=&quot;https://tracker.debian.org/pkg/libebur128&quot;&gt;libebur128&lt;/a&gt;
564 able to measure the loudness and since yesterday morning a new binary
565 named &lt;a href=&quot;http://bs1770gain.sourceforge.net&quot;&gt;bs1770gain&lt;/a&gt;
566 capable of both measuring and adjusting was uploaded and is waiting
567 for NEW processing. I plan to maintain the latter in Debian under the
568 &lt;a href=&quot;https://qa.debian.org/developer.php?email=pkg-multimedia-maintainers%40lists.alioth.debian.org&quot;&gt;Debian
569 multimedia&lt;/a&gt; umbrella.&lt;/p&gt;
570
571 &lt;p&gt;The free software based TV channel I am involved in,
572 &lt;a href=&quot;http://www.frikanalen.no/&quot;&gt;Frikanalen&lt;/a&gt;, plan to follow the
573 R128 recommondation ourself as soon as we can adjust the software to
574 do so, and the bs1770gain tool seem like a good fit for that part of
575 the puzzle to measure loudness on new video uploaded to Frikanalen.
576 Personally, I plan to use bs1770gain to adjust the loudness of videos
577 I upload to Frikanalen on behalf of &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
578 NUUG member organisation&lt;/a&gt;. The program seem to be able to measure
579 the LUFS value of any media file handled by ffmpeg, but I&#39;ve only
580 successfully adjusted the LUFS value of WAV files. I suspect it
581 should be able to adjust it for all the formats handled by ffmpeg.&lt;/p&gt;
582 </description>
583 </item>
584
585 <item>
586 <title>Hva gjør at NRK kan distribuere H.264-video uten patentavtale med MPEG LA?</title>
587 <link>http://people.skolelinux.org/pere/blog/Hva_gj_r_at_NRK_kan_distribuere_H_264_video_uten_patentavtale_med_MPEG_LA_.html</link>
588 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hva_gj_r_at_NRK_kan_distribuere_H_264_video_uten_patentavtale_med_MPEG_LA_.html</guid>
589 <pubDate>Wed, 10 Jun 2015 15:20:00 +0200</pubDate>
590 <description>&lt;p&gt;Helt siden jeg i 2012 fikk beskjed fra MPEG LA om at
591 &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;NRK
592 trengte patentavtale med dem&lt;/a&gt; hvis de distribuerte H.264-video til
593 sluttbrukere, har jeg lurt på hva som gjør at NRK ikke har slik
594 avtale. For noen dager siden fikk jeg endelig gjort noe med min
595 undring, og sendte 2015-05-28 følgende epost til info (at) nrk.no med
596 tittel &quot;Hva gjør at NRK kan distribuere H.264-video uten patentavtale
597 med MPEG LA?&quot;:&lt;/p&gt;
598
599 &lt;p&gt;&lt;blockquote&gt;
600 &lt;p&gt;Jeg lurer på en ting rundt NRKs bruk av H.264-video på sine
601 websider samt distribusjon via RiksTV og kabel-TV. Har NRK vurdert om
602 det er behov for en patentavtale med
603 &lt;a href=&quot;http://www.mpegla.com/&quot;&gt;MPEG LA&lt;/a&gt; slik det står i
604 programvarelisensene til blant annet Apple Final Cut Studio, Adobe
605 Premiere Pro, Avid og Apples Final Cut Pro X?&lt;/p&gt;
606
607 &lt;p&gt;Hvis dere har vurdert dette, hva var utfallet av en slik vurdering?&lt;/p&gt;
608
609 &lt;p&gt;Hvis dere ikke har vurdert dette, har NRK planer om å vurdere behovet
610 for patentavtale?&lt;/p&gt;
611
612 &lt;p&gt;I følge en artikkel på
613 &lt;a href=&quot;https://nrkbeta.no/2012/02/01/siste-kutt-for-final-cut/&quot;&gt;NRK
614 Beta i 2012&lt;/a&gt; har NRK brukt eller testet både Apple Final Cut
615 Studio, Adobe Premiere Pro, Avid og Apples Final Cut Pro X til bruk
616 for å redigere video før sending. Alle disse har bruksvilkår
617 understøttet av opphavsretten som sier at de kun kan brukes til å lage
618 filmer til personlig og ikke-kommersiell bruk - med mindre en har en
619 lisensavtale med MPEG LA om bruk av patenter utstedt i USA for H.264.
620 Se f.eks. &lt;a href=&quot;http://www.avid.com/static/resources/common/documents/corporate/LICENSE.pdf&quot;&gt;bruksvilkårene for Avid&lt;/a&gt;, &lt;a href=&quot;http://news.cnet.com/8301-30685_3-20000101-264.html&quot;&gt;Adobe Premiere&lt;/a&gt; og &lt;a href=&quot;http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf&quot;&gt;Apple Final
621 Cut Studio&lt;/a&gt; og søk etter &quot;MPEG LA&quot;.&lt;/p&gt;
622
623 &lt;p&gt;Dette får meg til å lure på om det er brudd på opphavsretten å bruke
624 disse verktøyene i strid med bruksvilkårene uten patentavtale med MPEG
625 LA. Men NRK bruker jo tilsynelatende disse verktøyene uten patentavtale
626 med MPEG LA.&lt;/p&gt;
627
628 &lt;p&gt;I følge forfatteren av Open Broadcast Encoder finnes det to typer
629 H.264-relaterte avtaler en kan få med MPEG LA. Det er én for å lage
630 programvare og utstyr som produserer H.264-video, og en annen for å
631 kringkaste video som bruker H.264. Dette forteller meg at selv om
632 produsentene av utstyr og programvare som NRK bruker har en slik avtale
633 med MPEG LA, så trenges det en egen avtale for å kringkaste video på det
634 formatet.&lt;/p&gt;
635
636 &lt;p&gt;I følge Ryan Rodriguez hos MPEG LA, da jeg spurte ham på epost i
637 juni 2012, har NRK ikke en slik avtale med MPEG LA. Han sa videre at
638 NRK trenger en slik avtale hvis NRK tilbyr H.264-kodet video til
639 sluttbrukere. Jeg sjekket listen med
640 &lt;a href=&quot;http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx&quot;&gt;organisasjoner
641 med avtale med MPEG LA&lt;/a&gt; og NRK står fortsatt ikke der.&lt;/p&gt;
642
643 &lt;p&gt;Jeg lurer dermed på hva som gjør at NRK kan bruke de overnevnte
644 videoredigeringsverktøyene, som tilsynelatende har krav om avtale med
645 MPEG LA for å kunne brukes slik NRK bruker dem, til å lage videofiler
646 for distribusjon uten å ha en avtale med MPEG LA om distribusjon av
647 H.264-video? Dette er spesielt interessant å vite for oss andre som
648 også vurderer å spre H.264-video etter å ha redigert dem med disse mye
649 brukte videoredigeringsverktøyene.&lt;/p&gt;
650 &lt;/blockquote&gt;&lt;/p&gt;
651
652 &lt;p&gt;Samme dag fikk jeg automatisk svar om at min henvendelse hadde fått
653 saksid 1294699. Jeg fikk deretter følgende respons fra NRK
654 2015-06-09:&lt;/p&gt;
655
656 &lt;p&gt;&lt;blockquote&gt;
657 &lt;p&gt;Hei, beklager lang svartid, men det tok litt tid å finne ut hvem som kunne
658 svare på dette.&lt;/p&gt;
659
660 &lt;p&gt;For selskaper som leverer h.264 til sluttbrukere på nett (f.eks
661 NRKs nett- tv utgaver som bruker h.264) - og som leverer slike
662 tjenester uten betaling fra forbrukere – er det heller ikke påkrevd
663 noen patentavtale.&lt;/p&gt;
664
665 &lt;p&gt;&lt;a href=&quot;http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y&quot;&gt;http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y&lt;/a&gt;&lt;/p&gt;
666
667 &lt;p&gt;Med vennlig hilsen
668 &lt;br&gt;Gunn Helen Berg
669 &lt;br&gt;Informasjonskonsulent, Publikumsservice&lt;/p&gt;
670
671 &lt;p&gt;NRK
672 &lt;br&gt;Strategidivisjonen
673 &lt;Br&gt;Sentralbord: +47 23 04 70 00
674 &lt;br&gt;Post: NRK Publikumsservice, 8608 Mo i Rana
675 &lt;br&gt;nrk.no / info (at) nrk.no&lt;/p&gt;
676 &lt;/blockquote&gt;&lt;/p&gt;
677
678 Da dette ikke helt var svar på det jeg lurte på, sendte jeg samme dag
679 oppfølgerepost tilbake:
680
681 &lt;p&gt;&lt;blockquote&gt;
682 &lt;p&gt;[Gunn Helen Berg]
683 &lt;br&gt;&gt; Hei, beklager lang svartid, men det tok litt tid å finne ut hvem som
684 &lt;br&gt;&gt; kunne svare på dette.&lt;/p&gt;
685
686 &lt;p&gt;Takk for svar. Men det besvarte ikke helt det jeg spurte om.&lt;/p&gt;
687
688 &lt;p&gt;&gt; For selskaper som leverer h.264 til sluttbrukere på nett (f.eks NRKs
689 &lt;br&gt;&gt; nett- tv utgaver som bruker h.264) - og som leverer slike tjenester
690 &lt;br&gt;&gt; uten betaling fra forbrukere – er det heller ikke påkrevd noen
691 &lt;br&gt;&gt; patentavtale.
692 &lt;br&gt;&gt;
693 &lt;br&gt;&gt; http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y&lt;/p&gt;
694
695 &lt;p&gt;Spørsmålet er ikke kun om MPEG LA krever patentavtale eller ikke
696 (hvilket ikke helt besvares av pressemeldingen omtalt over, gitt at
697 pressemeldingen kom i 2010, to år før MPEG LA ansvarlige for
698 internasjonal lisensiering egen Ryan Rodriguez fortalte meg på epost
699 at NRK trenger en lisens.&lt;/p&gt;
700
701 &lt;p&gt;Det er uklart fra pressemeldingen hva &quot;Internet Broadcast AVC
702 Video&quot; konkret betyr, men i følge en
703 &lt;a href=&quot;http://www.mpegla.com/main/programs/avc/Documents/avcweb.pdf&quot;&gt;presentasjon
704 fra MPEG LA med tema &quot;AVC PAtent Portfoli License Briefing&quot; datert
705 2015-05-15&lt;/a&gt; gjelder &quot;Internet Broadcast AVC Video&quot; kun kringkasting
706 på Internet som ikke tilbyr valg av enkeltinnslag (&quot;not
707 title-by-title&quot;), hvilket jo NRK gjør på sine nettsider. I tillegg
708 kringkaster jo NRK H.264-video også utenom Internet (RiksTV, kabel,
709 satelitt), hvilket helt klart ikke er dekket av vilkårene omtalt i
710 pressemeldingen.&lt;/p&gt;
711
712 &lt;p&gt;Spørsmålet mitt er hvordan NRK kan bruke verktøy med bruksvilkår
713 som krever avtale med MPEG LA for det NRK bruker dem til, når NRK ikke
714 har avtale med MPEG LA. Hvis jeg forsto spørsmålet riktig, så mener
715 NRK at dere ikke trenger avtale med MPEG LA, men uten slik avtale kan
716 dere vel ikke bruke hverken Apple Final Cut Studio, Adobe Premiere
717 Pro, Avid eller Apples Final Cut Pro X for å redigere video før
718 sending?&lt;/p&gt;
719
720 &lt;p&gt;Mine konkrete spørsmål var altså:&lt;/p&gt;
721
722 &lt;ul&gt;
723
724 &lt;li&gt;Hvis NRK har vurdert om det er behov for en patentavtale med MPEG LA
725 slik det er krav om i programvarelisensene til blant annet Apple
726 Final Cut Studio, Adobe Premiere Pro, Avid og Apples Final Cut Pro X,
727 hva var utfallet av en slik vurdering? Kan jeg få kopi av vurderingen
728 hvis den er gjort skriftlig?&lt;/li&gt;
729
730 &lt;li&gt;Hvis NRK ikke har vurdert dette, har NRK planer om å vurdere behovet
731 for patentavtale?&lt;/li&gt;
732
733 &lt;li&gt;Hva slags saksnummer fikk min henvendelse i NRKs offentlige
734 postjournal? Jeg ser at postjournalen ikke er publisert for den
735 aktuelle perioden ennå, så jeg fikk ikke sjekket selv.&lt;/li&gt;
736
737 &lt;/ul&gt;
738 &lt;/blockquote&gt;&lt;/p&gt;
739
740 &lt;p&gt;Det hjelper å ha funnet rette vedkommende i NRK, for denne gangen
741 fikk jeg svar tilbake dagen etter (2015-06-10), fra Geir Børdalen i
742 NRK:&lt;/p&gt;
743
744 &lt;p&gt;&lt;blockquote&gt;
745 &lt;p&gt;Hei Petter Reinholdtsen&lt;/p&gt;
746
747 &lt;p&gt;Jeg har sjekket saken med distribusjonssjef for tv, Arild Hellgren
748 (som var teknologidirektør da bakkenettet ble satt opp). NRK v/
749 Hellgren hadde møte med MPEG LA sammen med den europeiske
750 kringkastingsunionen EBU før bakkenettet for TV ble satt opp
751 (igangsatt høsten 2007). I dette møtet ble det avklart at NRK/EBU ikke
752 trengte noen patentavtale for h.264 i forbindelse med oppsett av
753 bakkenettet eller bruk av MPEG4 h.264 som kompresjonsalgoritme fordi
754 tjenesten «in full»(nor: helt) var betalt av utsendelseselskapene og
755 ikke av forbrukerne.&lt;/p&gt;
756
757 &lt;p&gt;&lt;a href=&quot;http://www.nrk.no/oppdrag/digitalt-bakkenett-1.3214555&quot;&gt;http://www.nrk.no/oppdrag/digitalt-bakkenett-1.3214555&lt;/a&gt;&lt;/p&gt;
758
759 &lt;p&gt;Det er også klart slått fast at selskaper som leverer video basert
760 på MPEG4 h.264 til sluttbrukere på nett, heller ikke påkrevd noen
761 patentavtale – så lenge de leverer slike tjenester uten betaling fra
762 sluttbrukere.&lt;/p&gt;
763
764 &lt;a href=&quot;http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y&quot;&gt;http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y&lt;/a&gt;
765
766 &lt;p&gt;“MPEG LA announced today that its AVC Patent Portfolio License will
767 continue not to charge royalties for Internet Video that is free to
768 end users (known as “Internet Broadcast AVC Video”) during the entire
769 life of this License. MPEG LA previously announced it would not charge
770 royalties for such video through December 31, 2015 (see
771 &lt;a href=&quot;http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf&quot;&gt;http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf&lt;/a&gt;),
772 and today’s announcement makes clear that royalties will continue not
773 to be charged for such video beyond that time. Products and services
774 other than Internet Broadcast AVC Video continue to be
775 royalty-bearing.”&lt;/p&gt;
776
777 &lt;p&gt;Vi har derfor ikke noe behov for å vurdere noen patentavtale med
778 MPEG LA.&lt;/p&gt;
779
780 &lt;p&gt;Understreker for øvrig at NRK ikke er låst til MPEG4 – h.264 som
781 utsendelsesformat – og at vi har brukt og bruker flere andre
782 alternativer i våre tjenester. Ulike «devicer» har ofte behov for
783 forskjellige løsninger – og NRK har forsøkt å levere med best mulig
784 kvalitet /økonomi /stabilitet avhengig av
785 plattform. Produksjonsformater i NRK spenner for øvrig over en rekke
786 forskjellige formater – hvor MPEG4 bare er en av disse. Når NRK kjøper
787 teknisk utstyr er betaling for kodekstøtte ofte en del av
788 anskaffelsesprisen for denne maskinvaren (enten dette er spesialiserte
789 enkodere eller forskjellige typer produksjonsutstyr).&lt;/p&gt;
790
791 &lt;p&gt;Vennlig hilsen
792 &lt;br&gt;Geir Børdalen&lt;/p&gt;
793
794 &lt;p&gt;________________________________________
795 &lt;br&gt;Geir Børdalen
796 &lt;br&gt;Investeringsansvarlig NRK / Hovedprosjektleder - Origo
797 &lt;br&gt;Avdeling for utvikling, innovasjon, investering og eiendom
798 &lt;br&gt;NRK medietjenester
799 &lt;br&gt;Sentralbord: +47 23 04 70 00
800 &lt;br&gt;Post: NRK, AUTV (RBM5), Pb. 8500 Majorstuen, 0340 Oslo
801 &lt;br&gt;nrk.no
802 &lt;/blockquote&gt;&lt;/p&gt;
803
804 &lt;p&gt;Et godt og grundig svar, som var informativt om hvordan NRK tenker
805 rundt patentavtale med MPEG LA, men heller ikke helt besvarte det jeg
806 lurte på, så jeg sendte epostoppfølging samme dag.&lt;/p&gt;
807
808 &lt;p&gt;&lt;blockquote&gt;
809 &lt;p&gt;[Geir Børdalen]
810 &lt;br&gt;&gt; Hei Petter Reinholdtsen&lt;/p&gt;
811
812 &lt;p&gt;Hei, og takk for raskt svar. Er min henvendelse journalført slik
813 at den dukker opp i NRKs postjournal?&lt;/p&gt;
814
815 &lt;p&gt;Svaret ditt var meget nyttig, og jeg forstår ut fra det du skriver
816 at avklaringen med MPEG LA rundt H.264-distribusjon via bakkenettet
817 gjelder alle TV-kanaler i Norge. Hvilke saksnummer fikk dokumenter
818 som ble opprettet i forbindelse med det omtalte møtet NRK v/Hellgren
819 og EBU hadde med MPEG LA (dvs. referater, avtaler, etc),
820 f.eks. dokumentet der formuleringen &quot;in full&quot; som du omtaler
821 finnes?&lt;p&gt;
822
823 &lt;p&gt;Men det er et par ting jeg fortsatt ikke forstår. Det ene er
824 hvorfor NRKs forståelse av hva &quot;Internet Broadcast AVC Video&quot; dekker
825 ser ut til å avvike fra det som presenteres i
826 &lt;a href=&quot;http://www.mpegla.com/main/programs/avc/Documents/avcweb.pdf&quot;&gt;lysark
827 fra MPEG LA&lt;/a&gt; i mai, der MPEG LA på lysark med overskriften
828 &quot;AVC/H.264 License Terms Participation Fees&quot; og undertittel &quot;Where
829 remuneration is from other sources&quot; skriver &quot;Internet Broadcast AVC
830 Video (not title-by-title, not subscription) – no royalty for life of
831 the AVC Patent Portfolio License&quot;.&lt;/p&gt;
832
833 &lt;p&gt;Her leser jeg MPEG LA dithen at det kun er kringkasting uten
834 abonnement via Internet som er dekket at vilkårne omtalt i
835 pressemeldingen, mens jeg forstår deg dithen at NRK mener NRKs
836 nettsider som også har enkeltfilmer og innslag (som jeg forstår dekket
837 av formuleringen &quot;title-by-title&quot;) dekkes av &quot;Internet Broadcast AVC
838 Video&quot; fra MPEG LA. Hva baserer dere denne tolkningen på? Jeg har
839 ikke sett noe skriftlig fra MPEG LA som støtter NRKs tolkning, og
840 lurer på om dere har andre kilder enn den pressemeldingen fra 5 år
841 tilbake, der NRKS forståelse av hva &quot;Internet Broadcast AVC Video&quot;
842 dekker er beskrevet?&lt;/p&gt;
843
844 &lt;p&gt;Det andre er at eposten din ikke nevnte spørsmålet mitt om
845 bruksvilkårene til videoredigeringsverktøyene som NRK bruker. Disse
846 har som tidligere nevnt krav om at de kun skal brukes til private og
847 ikke-kommersielle formål med mindre en har avtale med MPEG LA, og uten
848 avtale med MPEG LA kan det jo virke som om NRK bruker verktøyene i
849 strid med bruksvilkårene. Hva gjør at disse bruksvilkårene ikke
850 gjelder for NRK?&lt;/p&gt;
851 &lt;/blockquote&gt;&lt;/p&gt;
852
853 &lt;p&gt;Noen minutter senere får jeg foreløpig siste svar i
854 føljetongen:&lt;/p&gt;
855
856 &lt;p&gt;&lt;blockquote&gt;
857 &lt;p&gt;Hei igjen&lt;/p&gt;
858
859 &lt;p&gt;Vårt dokumentarkiv har fått en kopi (journalføringsnr kan jeg
860 dessverre ikke gi deg).&lt;p&gt;
861
862 &lt;p&gt;&gt; Svaret ditt var meget nyttig, og jeg forstår ut fra det du
863 &lt;br&gt;&gt; skriver at avklaringen med MPEG LA rundt H.264-distribusjon via
864 &lt;br&gt;&gt; bakkenettet gjelder alle TV-kanaler i Norge.&lt;/p&gt;
865
866 &lt;p&gt;Svar: Kan ikke svare for andre enn for NRK/EBU - og for bakkenettet
867 i Norge er det kun NRK som er et lisensbasert selskap. Kan ikke gi noe
868 svar på saksnr på dokumenter eller ytterligere informasjon da jeg selv
869 ikke var del i dette.&lt;/p&gt;
870
871 &lt;p&gt;&gt; Men det er et par ting jeg fortsatt ikke forstår. ...&lt;/p&gt;
872
873 &lt;p&gt;Svar: Kan ikke gå ytterligere inn i dette fra min side og mitt
874 fagfelt som er produksjon/publisering og systemstrukturene bak
875 disse. For øvrig ligger det etter vår formening ingen begrensninger
876 for NRK i mulighetene til publisering mht til kodek i
877 produksjonssystemer. Som tidligere skrevet mener vi at NRK ikke
878 trenger noen avtale med MPEG LA og støtter oss til det vi allerede har
879 kommunisert i forrige epost.&lt;/p&gt;
880
881 &lt;p&gt;Mvh
882 &lt;br&gt;Geir Børdalen&lt;/p&gt;
883 &lt;/blockquote&gt;&lt;/p&gt;
884
885 &lt;p&gt;Det syntes vanskelig å komme videre når NRK ikke ønsker å gå inn i
886 problemstillingen rundt bruksvilkårene til videoredigeringsverktøyene
887 NRK bruker, så jeg sendte takk for svarene og avsluttet utvekslingen
888 så langt:&lt;/p&gt;
889
890 &lt;p&gt;&lt;blockquote&gt;
891 &lt;p&gt;Tusen takk for rask respons, og oppklarende forklaring om hvordan
892 NRK tenker rundt MPEG LA.&lt;/p&gt;
893
894 &lt;p&gt;Jeg vil høre med NRK-arkivet for å se om de kan spore opp de
895 omtalte dokumentene. Jeg setter pris på om du kan dele titler, dato
896 eller annen informasjon som kan gjøre det enklere for arkivet å finne
897 dem.&lt;/p&gt;
898
899 &lt;p&gt;Når det gjelder hvordan bruksvilkårene til
900 videoredigeringsverktøyene skal tolkes, så skal jeg høre med MPEG LA
901 og produsentene av verktøyene for å forsøke å få klarhet i hva de
902 mener er rikgig rettstilstand.&lt;/p&gt;
903 &lt;/blockquote&gt;&lt;/p&gt;
904
905 &lt;p&gt;Jeg ble litt klokere, men fortsatt er det uklart for meg hva som er
906 grunnlaget til NRK for å se bort fra bruksvilkår i
907 videoredigeringsprogramvare som krever MPEG LA-avtale til alt annet
908 enn privat og ikke-kommersiell bruk.&lt;/p&gt;
909 </description>
910 </item>
911
912 <item>
913 <title>Hvordan vurderer regjeringen H.264-patentutfordringen?</title>
914 <link>http://people.skolelinux.org/pere/blog/Hvordan_vurderer_regjeringen_H_264_patentutfordringen_.html</link>
915 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hvordan_vurderer_regjeringen_H_264_patentutfordringen_.html</guid>
916 <pubDate>Sun, 16 Nov 2014 10:30:00 +0100</pubDate>
917 <description>&lt;p&gt;For en stund tilbake spurte jeg Fornyingsdepartementet om hvilke
918 juridiske vurderinger rundt patentproblemstillingen som var gjort da
919 H.264 ble tatt inn i &lt;a href=&quot;http://standard.difi.no/&quot;&gt;statens
920 referansekatalog over standarder&lt;/a&gt;. Stig Hornnes i FAD tipset meg
921 om følgende som står i oppsumeringen til høringen om
922 referansekatalogen versjon 2.0, som jeg siden ved hjelp av en
923 innsynsforespørsel fikk tak i
924 &lt;a href=&quot;http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&amp;do=get&amp;target=kongelig-resolusjon.pdf&quot;&gt;PDF-utgaven av&lt;/a&gt;
925 datert 2009-06-03 (saksnummer 200803291, saksbehandler Henrik
926 Linnestad).&lt;/p&gt;
927
928 &lt;p&gt;Der står det følgende om problemstillingen:&lt;/p&gt;
929
930 &lt;p&gt;&lt;blockquote&gt;
931 &lt;strong&gt;4.4 Patentproblematikk&lt;/strong&gt;
932
933 &lt;p&gt;NUUG og Opera ser det som særlig viktig at forslagene knyttet til
934 lyd og video baserer seg på de royalty-frie standardene Vorbis, Theora
935 og FLAC.&lt;/p&gt;
936
937 &lt;p&gt;Kommentarene relaterer seg til at enkelte standarder er åpne, men
938 inneholder tekniske prosedyrer som det i USA (og noen andre land som
939 Japan) er gitt patentrettigheter til. I vårt tilfelle berører dette
940 spesielt standardene Mp3 og H.264, selv om Politidirektoratet peker på
941 at det muligens kan være tilsvarende problematikk også for Theora og
942 Vorbis. Dette medfører at det i USA kan kreves royalties for bruk av
943 tekniske løsninger knyttet til standardene, et krav som også
944 håndheves. Patenter kan imidlertid bare hevdes i de landene hvor
945 patentet er gitt, så amerikanske patenter gjelder ikke andre steder
946 enn USA.&lt;/p&gt;
947
948 &lt;p&gt;Spesielt for utvikling av fri programvare er patenter
949 problematisk. GPL, en &quot;grunnleggende&quot; lisens for distribusjon av fri
950 programvare, avviser at programvare kan distribueres under denne
951 lisensen hvis det inneholder referanser til patenterte rutiner som
952 utløser krav om royalties. Det er imidlertid uproblematisk å
953 distribuere fri programvareløsninger under GPL som benytter de
954 aktuelle standardene innen eller mellom land som ikke anerkjenner
955 patentene. Derfor finner vi også flere implementeringer av Mp3 og
956 H.264 som er fri programvare, lisensiert under GPL.&lt;/p&gt;
957
958 &lt;p&gt;I Norge og EU er patentlovgivningen langt mer restriktiv enn i USA,
959 men det er også her mulig å få patentert metoder for løsning av et
960 problem som relaterer seg til databehandling. Det er AIF bekjent ikke
961 relevante patenter i EU eller Norge hva gjelder H.264 og Mp3, men
962 muligheten for at det finnes patenter uten at det er gjort krav om
963 royalties eller at det senere vil gis slike patenter kan ikke helt
964 avvises.&lt;/p&gt;
965
966 &lt;p&gt;AIF mener det er et behov for å gi offentlige virksomheter mulighet
967 til å benytte antatt royaltyfrie åpne standarder som et likeverdig
968 alternativ eller i tillegg til de markedsledende åpne standardene.&lt;/p&gt;
969
970 &lt;/blockquote&gt;&lt;/p&gt;
971
972 &lt;p&gt;Det ser dermed ikke ut til at de har vurdert patentspørsmålet i
973 sammenheng med opphavsrettsvilkår slik de er formulert for f.eks.
974 Apple Final Cut Pro, Adobe Premiere Pro, Avid og Sorenson-verktøyene,
975 der det kreves brukstillatelse for patenter som ikke er gyldige i
976 Norge for å bruke disse verktøyene til annet en personlig og ikke
977 kommersiell aktivitet når det gjelder H.264-video. Jeg må nok lete
978 videre etter svar på det spørsmålet.&lt;/p&gt;
979 </description>
980 </item>
981
982 <item>
983 <title>New lsdvd release version 0.17 is ready</title>
984 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
985 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
986 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
987 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
988 got a new set of developers a few weeks ago, after the original
989 developer decided to step down and pass the project to fresh blood.
990 This project is now maintained by Petter Reinholdtsen and Steve
991 Dibb.&lt;/p&gt;
992
993 &lt;p&gt;I just wrapped up
994 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
995 new lsdvd release&lt;/a&gt;, available in git or from
996 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
997 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
998 0.17.&lt;/p&gt;
999
1000 &lt;ul&gt;
1001
1002 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
1003 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
1004 non-existant, to work around additional copy protection&lt;/li&gt;
1005 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
1006 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
1007 &lt;li&gt;Fix include orders&lt;/li&gt;
1008 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
1009 &lt;li&gt;Fix the chapter count&lt;/li&gt;
1010 &lt;li&gt;Make sure the array size and the array limit used when initialising
1011 the palette size is the same.&lt;/li&gt;
1012 &lt;li&gt;Fix array printing.&lt;/li&gt;
1013 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
1014 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
1015 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
1016 with more GCC compiler warnings.&lt;/li&gt;
1017
1018 &lt;/ul&gt;
1019
1020 &lt;p&gt;This change bring together patches for lsdvd in use in various
1021 Linux and Unix distributions, as well as patches submitted to the
1022 project the last nine years. Please check it out. :)&lt;/p&gt;
1023 </description>
1024 </item>
1025
1026 <item>
1027 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
1028 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
1029 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
1030 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
1031 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
1032 to handle my fairly large DVD collection. It is a nice command line
1033 tool to get details about a DVD, like title, tracks, track length,
1034 etc, in XML, Perl or human readable format. But lsdvd have not seen
1035 any new development since 2006 and had a few irritating bugs affecting
1036 its use with some DVDs. Upstream seemed to be dead, and in January I
1037 sent a small probe asking for a version control repository for the
1038 project, without any reply. But I use it regularly and would like to
1039 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
1040 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
1041 the project admin, and after getting a reply from him explaining that
1042 he was no longer interested in the project, I asked if I could take
1043 over. And yesterday, I became project admin.&lt;/p&gt;
1044
1045 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
1046 maintainer interested in joining forces to maintain the upstream
1047 project, and I hope we can get a new release out fairly quickly,
1048 collecting the patches spread around on the internet into on place.
1049 I&#39;ve added the relevant Debian patches to the freshly created git
1050 repository, and expect the Gentoo patches to make it too. If you got
1051 a DVD collection and care about command line tools, check out
1052 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
1053 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
1054 list&lt;/a&gt;. :)&lt;/p&gt;
1055 </description>
1056 </item>
1057
1058 <item>
1059 <title>Do you need an agreement with MPEG-LA to publish and broadcast H.264 video in Norway?</title>
1060 <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>
1061 <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>
1062 <pubDate>Mon, 25 Aug 2014 22:10:00 +0200</pubDate>
1063 <description>&lt;p&gt;Two years later, I am still not sure if it is legal here in Norway
1064 to use or publish a video in H.264 or MPEG4 format edited by the
1065 commercially licensed video editors, without limiting the use to
1066 create &quot;personal&quot; or &quot;non-commercial&quot; videos or get a license
1067 agreement with &lt;a href=&quot;http://www.mpegla.com&quot;&gt;MPEG LA&lt;/a&gt;. If one
1068 want to publish and broadcast video in a non-personal or commercial
1069 setting, it might be that those tools can not be used, or that video
1070 format can not be used, without breaking their copyright license. I
1071 am not sure.
1072 &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
1073 then&lt;/a&gt;, I found that the copyright license terms for Adobe Premiere
1074 and Apple Final Cut Pro both specified that one could not use the
1075 program to produce anything else without a patent license from MPEG
1076 LA. The issue is not limited to those two products, though. Other
1077 much used products like those from Avid and Sorenson Media have terms
1078 of use are similar to those from Adobe and Apple. The complicating
1079 factor making me unsure if those terms have effect in Norway or not is
1080 that the patents in question are not valid in Norway, but copyright
1081 licenses are.&lt;/p&gt;
1082
1083 &lt;p&gt;These are the terms for Avid Artist Suite, according to their
1084 &lt;a href=&quot;http://www.avid.com/US/about-avid/legal-notices/legal-enduserlicense2&quot;&gt;published
1085 end user&lt;/a&gt;
1086 &lt;a href=&quot;http://www.avid.com/static/resources/common/documents/corporate/LICENSE.pdf&quot;&gt;license
1087 text&lt;/a&gt; (converted to lower case text for easier reading):&lt;/p&gt;
1088
1089 &lt;p&gt;&lt;blockquote&gt;
1090 &lt;p&gt;18.2. MPEG-4. MPEG-4 technology may be included with the
1091 software. MPEG LA, L.L.C. requires this notice: &lt;/p&gt;
1092
1093 &lt;p&gt;This product is licensed under the MPEG-4 visual patent portfolio
1094 license for the personal and non-commercial use of a consumer for (i)
1095 encoding video in compliance with the MPEG-4 visual standard (“MPEG-4
1096 video”) and/or (ii) decoding MPEG-4 video that was encoded by a
1097 consumer engaged in a personal and non-commercial activity and/or was
1098 obtained from a video provider licensed by MPEG LA to provide MPEG-4
1099 video. No license is granted or shall be implied for any other
1100 use. Additional information including that relating to promotional,
1101 internal and commercial uses and licensing may be obtained from MPEG
1102 LA, LLC. See http://www.mpegla.com. This product is licensed under
1103 the MPEG-4 systems patent portfolio license for encoding in compliance
1104 with the MPEG-4 systems standard, except that an additional license
1105 and payment of royalties are necessary for encoding in connection with
1106 (i) data stored or replicated in physical media which is paid for on a
1107 title by title basis and/or (ii) data which is paid for on a title by
1108 title basis and is transmitted to an end user for permanent storage
1109 and/or use, such additional license may be obtained from MPEG LA,
1110 LLC. See http://www.mpegla.com for additional details.&lt;/p&gt;
1111
1112 &lt;p&gt;18.3. H.264/AVC. H.264/AVC technology may be included with the
1113 software. MPEG LA, L.L.C. requires this notice:&lt;/p&gt;
1114
1115 &lt;p&gt;This product is licensed under the AVC patent portfolio license for
1116 the personal use of a consumer or other uses in which it does not
1117 receive remuneration to (i) encode video in compliance with the AVC
1118 standard (“AVC video”) and/or (ii) decode AVC video that was encoded
1119 by a consumer engaged in a personal activity and/or was obtained from
1120 a video provider licensed to provide AVC video. No license is granted
1121 or shall be implied for any other use. Additional information may be
1122 obtained from MPEG LA, L.L.C. See http://www.mpegla.com.&lt;/p&gt;
1123 &lt;/blockquote&gt;&lt;/p&gt;
1124
1125 &lt;p&gt;Note the requirement that the videos created can only be used for
1126 personal or non-commercial purposes.&lt;/p&gt;
1127
1128 &lt;p&gt;The Sorenson Media software have
1129 &lt;a href=&quot;http://www.sorensonmedia.com/terms/&quot;&gt;similar terms&lt;/a&gt;:&lt;/p&gt;
1130
1131 &lt;p&gt;&lt;blockquote&gt;
1132
1133 &lt;p&gt;With respect to a license from Sorenson pertaining to MPEG-4 Video
1134 Decoders and/or Encoders: Any such product is licensed under the
1135 MPEG-4 visual patent portfolio license for the personal and
1136 non-commercial use of a consumer for (i) encoding video in compliance
1137 with the MPEG-4 visual standard (“MPEG-4 video”) and/or (ii) decoding
1138 MPEG-4 video that was encoded by a consumer engaged in a personal and
1139 non-commercial activity and/or was obtained from a video provider
1140 licensed by MPEG LA to provide MPEG-4 video. No license is granted or
1141 shall be implied for any other use. Additional information including
1142 that relating to promotional, internal and commercial uses and
1143 licensing may be obtained from MPEG LA, LLC. See
1144 http://www.mpegla.com.&lt;/p&gt;
1145
1146 &lt;p&gt;With respect to a license from Sorenson pertaining to MPEG-4
1147 Consumer Recorded Data Encoder, MPEG-4 Systems Internet Data Encoder,
1148 MPEG-4 Mobile Data Encoder, and/or MPEG-4 Unique Use Encoder: Any such
1149 product is licensed under the MPEG-4 systems patent portfolio license
1150 for encoding in compliance with the MPEG-4 systems standard, except
1151 that an additional license and payment of royalties are necessary for
1152 encoding in connection with (i) data stored or replicated in physical
1153 media which is paid for on a title by title basis and/or (ii) data
1154 which is paid for on a title by title basis and is transmitted to an
1155 end user for permanent storage and/or use. Such additional license may
1156 be obtained from MPEG LA, LLC. See http://www.mpegla.com for
1157 additional details.&lt;/p&gt;
1158
1159 &lt;/blockquote&gt;&lt;/p&gt;
1160
1161 &lt;p&gt;Some free software like
1162 &lt;a href=&quot;https://handbrake.fr/&quot;&gt;Handbrake&lt;/A&gt; and
1163 &lt;a href=&quot;http://ffmpeg.org/&quot;&gt;FFMPEG&lt;/a&gt; uses GPL/LGPL licenses and do
1164 not have any such terms included, so for those, there is no
1165 requirement to limit the use to personal and non-commercial.&lt;/p&gt;
1166 </description>
1167 </item>
1168
1169 <item>
1170 <title>Hvordan enkelt laste ned filmer fra NRK med den &quot;nye&quot; løsningen</title>
1171 <link>http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html</link>
1172 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html</guid>
1173 <pubDate>Mon, 16 Jun 2014 19:20:00 +0200</pubDate>
1174 <description>&lt;p&gt;Jeg har fortsatt behov for å kunne laste ned innslag fra NRKs
1175 nettsted av og til for å se senere når jeg ikke er på nett, men
1176 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html&quot;&gt;min
1177 oppskrift fra 2011&lt;/a&gt; sluttet å fungere da NRK byttet
1178 avspillermetode. I dag fikk jeg endelig lett etter oppdatert løsning,
1179 og jeg er veldig glad for å fortelle at den enkleste måten å laste ned
1180 innslag er å bruke siste versjon 2014.06.07 av
1181 &lt;a href=&quot;http://rg3.github.io/youtube-dl/&quot;&gt;youtube-dl&lt;/a&gt;. Støtten i
1182 youtube-dl &lt;a href=&quot;https://github.com/rg3/youtube-dl/issues/2980&quot;&gt;kom
1183 inn for 23 dager siden&lt;/a&gt; og
1184 &lt;a href=&quot;http://packages.qa.debian.org/y/youtube-dl.html&quot;&gt;versjonen i
1185 Debian&lt;/a&gt; fungerer fint også som backport til Debian Wheezy. Det er
1186 et lite problem, det håndterer kun URLer med små bokstaver, men hvis
1187 en har en URL med store bokstaver kan en bare gjøre alle store om til
1188 små bokstaver for å få youtube-dl til å laste ned. Rapporterte
1189 nettopp
1190 &lt;a href=&quot;https://github.com/rg3/youtube-dl/issues/2980&quot;&gt;problemet til
1191 utviklerne&lt;/a&gt;, og antar de får fikset det snart.&lt;/p&gt;
1192
1193 &lt;p&gt;Dermed er alt klart til å laste ned dokumentarene om
1194 &lt;a href=&quot;http://tv.nrk.no/program/KOID23005014/usas-hemmelige-avlytting&quot;&gt;USAs
1195 hemmelige avlytting&lt;/a&gt; og
1196 &lt;a href=&quot;http://tv.nrk.no/program/KOID23005114/selskapene-bak-usas-avlytting&quot;&gt;Selskapene
1197 bak USAs avlytting&lt;/a&gt;, i tillegg til
1198 &lt;a href=&quot;http://tv.nrk.no/program/KOID20005814/et-moete-med-edward-snowden&quot;&gt;intervjuet
1199 med Edward Snowden gjort av den tyske tv-kanalen ARD&lt;/a&gt;. Anbefaler
1200 alle å se disse, sammen med
1201 &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
1202 til Jacob Appelbaum på siste CCC-konferanse&lt;/a&gt;, for å forstå mer om
1203 hvordan overvåkningen av borgerne brer om seg.&lt;/p&gt;
1204
1205 &lt;p&gt;Takk til gode venner på foreningen NUUGs IRC-kanal
1206 &lt;a href=&quot;irc://irc.freenode.net/%23nuug&quot;&gt;#nuug på irc.freenode.net&lt;/a&gt;
1207 for tipsene som fikk meg i mål&lt;/a&gt;.&lt;/p&gt;
1208
1209 &lt;p&gt;&lt;strong&gt;Oppdatering 2014-06-17&lt;/strong&gt;: Etter at jeg publiserte
1210 denne, ble jeg tipset om bloggposten
1211 &quot;&lt;a href=&quot;http://ingvar.blog.redpill-linpro.com/2012/05/31/downloading-hd-content-from-tv-nrk-no/&quot;&gt;Downloading
1212 HD content from tv.nrk.no&lt;/a&gt;&quot; av Ingvar Hagelund, som har alternativ
1213 implementasjon og tips for å lage mkv-fil med undertekstene inkludert.
1214 Kanskje den passer bedre for deg? I tillegg ble feilen i youtube-dl
1215 ble fikset litt senere ut på dagen i går, samt at youtube-dl fikk
1216 støtte for å laste ned undertitler. Takk til Anders Einar Hilden for
1217 god innsats og youtube-dl-utviklerne for rask respons.&lt;/p&gt;
1218 </description>
1219 </item>
1220
1221 <item>
1222 <title>Half the Coverity issues in Gnash fixed in the next release</title>
1223 <link>http://people.skolelinux.org/pere/blog/Half_the_Coverity_issues_in_Gnash_fixed_in_the_next_release.html</link>
1224 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Half_the_Coverity_issues_in_Gnash_fixed_in_the_next_release.html</guid>
1225 <pubDate>Tue, 29 Apr 2014 14:20:00 +0200</pubDate>
1226 <description>&lt;p&gt;I&#39;ve been following &lt;a href=&quot;http://www.getgnash.org/&quot;&gt;the Gnash
1227 project&lt;/a&gt; for quite a while now. It is a free software
1228 implementation of Adobe Flash, both a standalone player and a browser
1229 plugin. Gnash implement support for the AVM1 format (and not the
1230 newer AVM2 format - see
1231 &lt;a href=&quot;http://lightspark.github.io/&quot;&gt;Lightspark&lt;/a&gt; for that one),
1232 allowing several flash based sites to work. Thanks to the friendly
1233 developers at Youtube, it also work with Youtube videos, because the
1234 Javascript code at Youtube detect Gnash and serve a AVM1 player to
1235 those users. :) Would be great if someone found time to implement AVM2
1236 support, but it has not happened yet. If you install both Lightspark
1237 and Gnash, Lightspark will invoke Gnash if it find a AVM1 flash file,
1238 so you can get both handled as free software. Unfortunately,
1239 Lightspark so far only implement a small subset of AVM2, and many
1240 sites do not work yet.&lt;/p&gt;
1241
1242 &lt;p&gt;A few months ago, I started looking at
1243 &lt;a href=&quot;http://scan.coverity.com/&quot;&gt;Coverity&lt;/a&gt;, the static source
1244 checker used to find heaps and heaps of bugs in free software (thanks
1245 to the donation of a scanning service to free software projects by the
1246 company developing this non-free code checker), and Gnash was one of
1247 the projects I decided to check out. Coverity is able to find lock
1248 errors, memory errors, dead code and more. A few days ago they even
1249 extended it to also be able to find the heartbleed bug in OpenSSL.
1250 There are heaps of checks being done on the instrumented code, and the
1251 amount of bogus warnings is quite low compared to the other static
1252 code checkers I have tested over the years.&lt;/p&gt;
1253
1254 &lt;p&gt;Since a few weeks ago, I&#39;ve been working with the other Gnash
1255 developers squashing bugs discovered by Coverity. I was quite happy
1256 today when I checked the current status and saw that of the 777 issues
1257 detected so far, 374 are marked as fixed. This make me confident that
1258 the next Gnash release will be more stable and more dependable than
1259 the previous one. Most of the reported issues were and are in the
1260 test suite, but it also found a few in the rest of the code.&lt;/p&gt;
1261
1262 &lt;p&gt;If you want to help out, you find us on
1263 &lt;a href=&quot;https://lists.gnu.org/mailman/listinfo/gnash-dev&quot;&gt;the
1264 gnash-dev mailing list&lt;/a&gt; and on
1265 &lt;a href=&quot;irc://irc.freenode.net/#gnash&quot;&gt;the #gnash channel on
1266 irc.freenode.net IRC server&lt;/a&gt;.&lt;/p&gt;
1267 </description>
1268 </item>
1269
1270 <item>
1271 <title>Video DVD reader library / python-dvdvideo - nice free software</title>
1272 <link>http://people.skolelinux.org/pere/blog/Video_DVD_reader_library___python_dvdvideo___nice_free_software.html</link>
1273 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Video_DVD_reader_library___python_dvdvideo___nice_free_software.html</guid>
1274 <pubDate>Fri, 21 Mar 2014 15:25:00 +0100</pubDate>
1275 <description>&lt;p&gt;Keeping your DVD collection safe from scratches and curious
1276 children fingers while still having it available when you want to see a
1277 movie is not straight forward. My preferred method at the moment is
1278 to store a full copy of the ISO on a hard drive, and use VLC, Popcorn
1279 Hour or other useful players to view the resulting file. This way the
1280 subtitles and bonus material are still available and using the ISO is
1281 just like inserting the original DVD record in the DVD player.&lt;/p&gt;
1282
1283 &lt;p&gt;Earlier I used dd for taking security copies, but it do not handle
1284 DVDs giving read errors (which are quite a few of them). I&#39;ve also
1285 tried using
1286 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html&quot;&gt;dvdbackup
1287 and genisoimage&lt;/a&gt;, but these days I use the marvellous python library
1288 and program
1289 &lt;a href=&quot;http://bblank.thinkmo.de/blog/new-software-python-dvdvideo&quot;&gt;python-dvdvideo&lt;/a&gt;
1290 written by Bastian Blank. It is
1291 &lt;a href=&quot;http://packages.qa.debian.org/p/python-dvdvideo.html&quot;&gt;in Debian
1292 already&lt;/a&gt; and the binary package name is python3-dvdvideo. Instead
1293 of trying to read every block from the DVD, it parses the file
1294 structure and figure out which block on the DVD is actually in used,
1295 and only read those blocks from the DVD. This work surprisingly well,
1296 and I have been able to almost backup my entire DVD collection using
1297 this method.&lt;/p&gt;
1298
1299 &lt;p&gt;So far, python-dvdvideo have failed on between 10 and
1300 20 DVDs, which is a small fraction of my collection. The most common
1301 problem is
1302 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720831&quot;&gt;DVDs
1303 using UTF-16 instead of UTF-8 characters&lt;/a&gt;, which according to
1304 Bastian is against the DVD specification (and seem to cause some
1305 players to fail too). A rarer problem is what seem to be inconsistent
1306 DVD structures, as the python library
1307 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723079&quot;&gt;claim
1308 there is a overlap between objects&lt;/a&gt;. An equally rare problem claim
1309 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741878&quot;&gt;some
1310 value is out of range&lt;/a&gt;. No idea what is going on there. I wish I
1311 knew enough about the DVD format to fix these, to ensure my movie
1312 collection will stay with me in the future.&lt;/p&gt;
1313
1314 &lt;p&gt;So, if you need to keep your DVDs safe, back them up using
1315 python-dvdvideo. :)&lt;/p&gt;
1316 </description>
1317 </item>
1318
1319 <item>
1320 <title>IETF activity to standardise video codec</title>
1321 <link>http://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html</link>
1322 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html</guid>
1323 <pubDate>Sat, 15 Sep 2012 20:00:00 +0200</pubDate>
1324 <description>&lt;p&gt;After the
1325 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html&quot;&gt;Opus
1326 codec made&lt;/a&gt; it into &lt;a href=&quot;http://www.ietf.org/&quot;&gt;IETF&lt;/a&gt; as
1327 &lt;a href=&quot;http://tools.ietf.org/html/rfc6716&quot;&gt;RFC 6716&lt;/a&gt;, I had a look
1328 to see if there is any activity in IETF to standardise a video codec
1329 too, and I was happy to discover that there is some activity in this
1330 area. A non-&quot;working group&quot; mailing list
1331 &lt;a href=&quot;https://www.ietf.org/mailman/listinfo/video-codec&quot;&gt;video-codec&lt;/a&gt;
1332 was
1333 &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
1334 formal working group should be formed.&lt;/p&gt;
1335
1336 &lt;p&gt;I look forward to see how this plays out. There is already
1337 &lt;a href=&quot;http://www.ietf.org/mail-archive/web/video-codec/current/msg00003.html&quot;&gt;an
1338 email from someone&lt;/a&gt; in the MPEG group at ISO asking people to
1339 participate in the ISO group. Given how ISO failed with OOXML and given
1340 that it so far (as far as I can remember) only have produced
1341 multimedia formats requiring royalty payments, I suspect
1342 joining the ISO group would be a complete waste of time, but I am not
1343 involved in any codec work and my opinion will not matter much.&lt;/p&gt;
1344
1345 &lt;p&gt;If one of my readers is involved with codec work, I hope she will
1346 join this work to standardise a royalty free video codec within
1347 IETF.&lt;/p&gt;
1348 </description>
1349 </item>
1350
1351 <item>
1352 <title>IETF standardize its first multimedia codec: Opus</title>
1353 <link>http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html</link>
1354 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html</guid>
1355 <pubDate>Wed, 12 Sep 2012 13:50:00 +0200</pubDate>
1356 <description>&lt;p&gt;Yesterday, &lt;a href=&quot;http://www.ietf.org/&quot;&gt;IETF&lt;/a&gt; announced the
1357 publication of of
1358 &lt;a href=&quot;http://tools.ietf.org/html/rfc6716&quot;&gt;RFC 6716, the Definition
1359 of the Opus Audio Codec&lt;/a&gt;, a low latency, variable bandwidth, codec
1360 intended for both VoIP, film and music. This is the first time, as
1361 far as I know, that IETF have standardized a multimedia codec. In
1362 &lt;a href=&quot;http://tools.ietf.org/html/rfc3533&quot;&gt;RFC 3533&lt;/a&gt;, IETF
1363 standardized the OGG container format, and it has proven to be a great
1364 royalty free container for audio, video and movies. I hope IETF will
1365 continue to standardize more royalty free codeces, after ISO and MPEG
1366 have proven incapable of securing everyone equal rights to publish
1367 multimedia content on the Internet.&lt;/p&gt;
1368
1369 &lt;p&gt;IETF require two interoperating independent implementations to
1370 ratify a standard, and have so far ensured to only standardize royalty
1371 free specifications. Both are key factors to allow everyone (rich and
1372 poor), to compete on equal terms on the Internet.&lt;/p&gt;
1373
1374 &lt;p&gt;Visit the &lt;a href=&quot;http://opus-codec.org/&quot;&gt;Opus project page&lt;/a&gt; if
1375 you want to learn more about the solution.&lt;/p&gt;
1376 </description>
1377 </item>
1378
1379 <item>
1380 <title>Git repository for song book for Computer Scientists</title>
1381 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
1382 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
1383 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
1384 <description>&lt;p&gt;As I
1385 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
1386 this summer&lt;/a&gt;, I have created a Computer Science song book a few
1387 years ago, and today I finally found time to create a public
1388 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
1389 repository for the project&lt;/a&gt;.&lt;/p&gt;
1390
1391 &lt;p&gt;If you want to help out, please clone the source and submit patches
1392 to the HTML version. To generate the PDF and PostScript version,
1393 please use prince XML, or let me know about a useful free software
1394 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
1395
1396 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
1397 PostScript formats at
1398 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
1399 Science Songbook&lt;/a&gt;.&lt;/p&gt;
1400 </description>
1401 </item>
1402
1403 <item>
1404 <title>Mer oppfølging fra MPEG-LA om avtale med dem for å kringkaste og publisere H.264-video</title>
1405 <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>
1406 <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>
1407 <pubDate>Thu, 5 Jul 2012 23:50:00 +0200</pubDate>
1408 <description>&lt;p&gt;I føljetongen om H.264
1409 &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
1410 jeg leserne i undring&lt;/a&gt; om hvor pakken fra MPEG-LA tok veien, og om
1411 hvilke selskaper i Norge som har avtale med MPEG-LA. Da Ryan hos
1412 MPEG-LA dro på ferie sendte jeg min melding videre til hans kollega,
1413 og dagen etter fikk jeg følgende svar derfra:&lt;/p&gt;
1414
1415 &lt;p&gt;&lt;blockquote&gt;
1416 &lt;p&gt;Date: Fri, 29 Jun 2012 18:32:34 +0000
1417 &lt;br&gt;From: Sidney Wolf &amp;lt;SWolf (at) mpegla.com&amp;gt;
1418 &lt;br&gt;To: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
1419 &lt;br&gt;Cc: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
1420 &lt;br&gt;Subject: RE: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
1421
1422 &lt;p&gt;Dear Mr. Reinholdtsen,&lt;/p&gt;
1423
1424 &lt;p&gt;Thank you for your message. As you know, Ryan is currently our of the
1425 office, so it will be my pleasure to assist you.&lt;/p&gt;
1426
1427 &lt;p&gt;Per your request, attached please find an electronic copy of the
1428 AVC Patent Portfolio License. Please note that the electronic copy of
1429 the License is provided as a convenience and for informational
1430 purposes only. When concluding the Licenses, only the hard copies
1431 provided by MPEG LA may be used.&lt;/p&gt;
1432
1433 &lt;p&gt;To your question, MPEG LA lists our Licensees on our website
1434 according to each program. The lists are in alphabetical order, so it
1435 is very easy to search.&lt;/p&gt;
1436
1437 &lt;p&gt;I hope that this was helpful. If we can be of additional
1438 assistance, please let me know.&lt;/p&gt;
1439
1440 &lt;p&gt;Kind regards,&lt;/p&gt;
1441
1442 &lt;p&gt;Sidney A. Wolf
1443 &lt;br&gt;Manager, Global Licensing
1444 &lt;br&gt;MPEG LA&lt;/p&gt;
1445 &lt;/blockquote&gt;&lt;/p&gt;
1446
1447 &lt;p&gt;Selv om et epostvedlegg er nyttig for mottakeren, så håpet jeg å få
1448 et dokument jeg kunne dele med alle leserne av bloggen min, og ikke et
1449 som må deles på individuell basis. Opphavsretten krever godkjenning
1450 fra rettighetsinnehaver før en kan gjøre slikt, så dermed fulgte jeg
1451 opp med et spørsmål om dette var greit.&lt;/p&gt;
1452
1453 &lt;p&gt;&lt;blockquote&gt;
1454 &lt;p&gt;Date: Wed, 4 Jul 2012 20:25:06 +0200
1455 &lt;br&gt;From: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
1456 &lt;br&gt;To: Sidney Wolf &amp;lt;SWolf (at) mpegla.com&amp;gt;
1457 &lt;br&gt;Cc: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
1458 &lt;br&gt;Subject: Re: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
1459
1460 &lt;p&gt;Thank you for your reply.&lt;/p&gt;
1461
1462 &lt;p&gt;[Sidney Wolf]
1463 &lt;br&gt;&amp;gt; Per your request, attached please find an electronic copy of the AVC
1464 &lt;br&gt;&amp;gt; Patent Portfolio License. Please note that the electronic copy of
1465 &lt;br&gt;&amp;gt; the License is provided as a convenience and for informational
1466 &lt;br&gt;&amp;gt; purposes only. When concluding the Licenses, only the hard copies
1467 &lt;br&gt;&amp;gt; provided by MPEG LA may be used.&lt;/p&gt;
1468
1469 &lt;p&gt;This is useful for me to learn, but the reason I asked for the
1470 Internet address of the licensing document was to ensure I could
1471 publish a link to it when I discuss the topic of H.264 licensing here
1472 in Norway, and allow others to verify my observations. I can not do
1473 the same with an email attachment. Thus I would like to ask you if it
1474 is OK with MPEG LA that I publish this document on the Internet for
1475 others to read?&lt;/p&gt;
1476
1477 &lt;p&gt;&amp;gt; To your question, MPEG LA lists our Licensees on our website
1478 &lt;br&gt;&amp;gt; according to each program. The lists are in alphabetical order, so
1479 &lt;br&gt;&amp;gt; it is very easy to search.&lt;/p&gt;
1480
1481 &lt;p&gt;I am afraid this do not help me locate Norwegian companies in the
1482 list of Licensees. I do not know the name of all companies and
1483 organisations in Norway, and thus do not know how to locate the
1484 Norwegian ones on that list.&lt;/p&gt;
1485
1486 &lt;p&gt;&amp;gt; I hope that this was helpful. If we can be of additional assistance,
1487 &lt;br&gt;&amp;gt; please let me know.&lt;/p&gt;
1488
1489 &lt;p&gt;Absoutely helpful to learn more about how MPEG LA handle licensing.&lt;/p&gt;
1490
1491 &lt;p&gt;--
1492 &lt;br&gt;Happy hacking
1493 &lt;br&gt;Petter Reinholdtsen&lt;/p&gt;
1494 &lt;/blockquote&gt;&lt;/p&gt;
1495
1496 &lt;p&gt;Jeg håpet også at det skulle være mulig å få vite hvilke av de
1497 mange hundre som har avtale med MPEG-LA om bruk av H.264 som holdt til
1498 i Norge. Begge mine håp falt i grus med svaret fra MPEG-LA.
1499
1500 &lt;p&gt;&lt;blockquote&gt;
1501 &lt;p&gt;Date: Thu, 5 Jul 2012 17:42:39 +0000
1502 &lt;br&gt;From: Sidney Wolf &amp;lt;SWolf (at) mpegla.com&amp;gt;
1503 &lt;br&gt;To: &#39;Petter Reinholdtsen&#39; &amp;lt;pere (at) hungry.com&amp;gt;
1504 &lt;br&gt;Cc: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
1505 &lt;br&gt;Subject: RE: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
1506
1507 &lt;p&gt;Dear Mr. Reinholdtsen,&lt;/p&gt;
1508
1509 &lt;p&gt;Thank you for your reply.&lt;/p&gt;
1510
1511 &lt;p&gt;We appreciate the additional explanation you have provided and for
1512 asking our permission to publish the electronic copy of the License in
1513 advance of doing so. Typically, MPEG LA prefers to distribute the
1514 electronic copies of our Licenses to interested parties. Therefore,
1515 please feel free to send interested parties to the AVC portion of our
1516 website, http://www.mpegla.com/main/programs/AVC/Pages/Intro.aspx for
1517 their further reference.&lt;/p&gt;
1518
1519 &lt;p&gt;As previously mentioned, MPEG LA maintains a list of Licensees in good
1520 standing on our website according to each program. Due to the large
1521 volume of Licensees, it would be administratively impractical to
1522 provide this level of detail to interested parties. Therefore, I am
1523 afraid we are not in a position to assist you with your request.&lt;/p&gt;
1524
1525 &lt;p&gt;Kind regards,&lt;/p&gt;
1526
1527 &lt;p&gt;Sidney A. Wolf
1528 &lt;br&gt;Manager, Global Licensing
1529 &lt;br&gt;MPEG LA&lt;/p&gt;
1530 &lt;/blockquote&gt;&lt;/p&gt;
1531
1532 &lt;p&gt;Men takket være epostvedlegget kunne jeg søke på Google etter
1533 setningen &quot;WHEREAS, a video standard commonly referred to as AVC has
1534 been defined and is referred to in this Agreement as the “AVC
1535 Standard” (as more fully defined herein below)&quot; som finnes i avtalen,
1536 og lokalisere en kopi fra 2007 av
1537 &lt;a href=&quot;http://www.sec.gov/Archives/edgar/data/1342960/000119312509050004/dex1024.htm&quot;&gt;lisensavtalen
1538 mellom MPEG-LA og DivX, Inc.&lt;/a&gt;, slik at mine lesere kan se hvordan
1539 avtalen så ut da. Jeg har ikke sammenlignet tekstene for å se om noe
1540 har endret seg siden den tid, men satser på at teksten er representativ.&lt;/p&gt;
1541
1542 &lt;p&gt;Jeg aner fortsatt ikke hvor FedEx tok veien med pakken fra
1543 MPEG-LA.&lt;/p&gt;
1544
1545 &lt;p&gt;Update 2012-07-06: Jeg er visst ikke den første som forsøker å få
1546 klarhet i problemstillinger rundt H.264, og kom nettopp over en veldig
1547 interessant bloggpost fra 2010 hos LibreVideo med tittelen
1548 &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
1549 answers some questions about AVC/H.264 licensing&lt;/a&gt;. Anbefales!&lt;/p&gt;
1550 </description>
1551 </item>
1552
1553 <item>
1554 <title>Departementenes servicesenter har ingen avtale om bruk av H.264 med MPEG-LA</title>
1555 <link>http://people.skolelinux.org/pere/blog/Departementenes_servicesenter_har_ingen_avtale_om_bruk_av_H_264_med_MPEG_LA.html</link>
1556 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Departementenes_servicesenter_har_ingen_avtale_om_bruk_av_H_264_med_MPEG_LA.html</guid>
1557 <pubDate>Fri, 29 Jun 2012 09:40:00 +0200</pubDate>
1558 <description>&lt;p&gt;Da fikk jeg nettopp svar fra
1559 &lt;a href=&quot;http://www.dss.dep.no/&quot;&gt;Departementenes servicesenter&lt;/a&gt;
1560 (DSS) på
1561 &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
1562 spørsmål om avtale rundt bruk av H.264&lt;/a&gt;. De har ingen avtale med
1563 MPEG LA eller dets representanter. Her er svaret.
1564
1565 &lt;p&gt;&lt;blockquote&gt;
1566
1567 &lt;p&gt;Date: Fri, 29 Jun 2012 07:04:42 +0000
1568 &lt;br&gt;From: Nielsen Mette Haga &amp;lt;Mette-Haga.Nielsen (at) dss.dep.no&amp;gt;
1569 &lt;br&gt;To: Petter Reinholdtsen &amp;lt;petter.reinholdtsen (at) ...&amp;gt;
1570 &lt;br&gt;CC: Postmottak &amp;lt;Postmottak (at) dss.dep.no&amp;gt;
1571 &lt;br&gt;Subject: SV: Innsynsbegjæring om MPEG/H.264-relaterte avtaler&lt;/p&gt;
1572
1573 &lt;p&gt;DSS har ikke inngått noen egen lisensavtale med MPEG-LA eller noen som
1574 representerer MPEG-LA i Norge. Videoløsningen på regjeringen.no er
1575 levert av Smartcom:tv. Lisensforholdet rundt H.264 er ikke omtalt i
1576 vår avtale med Smartcom.&lt;/p&gt;
1577
1578 &lt;p&gt;Vennlig hilsen&lt;/p&gt;
1579
1580 &lt;p&gt;Mette Haga Nielsen
1581 &lt;br&gt;Fung. seksjonssjef&lt;/p&gt;
1582
1583 &lt;p&gt;Departementenes servicesenter&lt;/p&gt;
1584
1585 &lt;p&gt;Informasjonsforvaltning
1586
1587 &lt;p&gt;Mobil 93 09 83 51
1588 &lt;br&gt;E-post mette-haga.nielsen (at) dss.dep.no&lt;/p&gt;
1589 &lt;/blockquote&gt;&lt;/p&gt;
1590
1591 &lt;p&gt;Hvis den norske regjeringen representert ved DSS ikke har slik
1592 avtale, så kan en kanskje konkludere med at det ikke trengs? Jeg er
1593 ikke trygg på at det er god juridisk grunn å stå på, men det er i det
1594 minste interessant å vite at hverken NRK eller DSS har funnet det
1595 nødvendig å ha avtale om bruk av H.264.&lt;/p&gt;
1596
1597 &lt;p&gt;Det forklarer ikke hvordan de kan ignorere bruksvilkårene knyttet
1598 til bruk av opphavsrettsbeskyttet materiale de bruker til
1599 videoproduksjon, med mindre slike vilkår kan ignoreres av selskaper og
1600 privatpersoner i Norge. Har de lov til å bryte vilkårene, eller har
1601 de brutt dem og så langt sluppet unna med det? Jeg aner ikke.&lt;/p&gt;
1602 </description>
1603 </item>
1604
1605 <item>
1606 <title>MPEG-LA mener NRK må ha avtale med dem for å kringkaste og publisere H.264-video</title>
1607 <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>
1608 <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>
1609 <pubDate>Thu, 28 Jun 2012 20:00:00 +0200</pubDate>
1610 <description>&lt;p&gt;Etter at NRK
1611 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html&quot;&gt;nektet
1612 å spore opp eventuell avtale med MPEG-LA&lt;/a&gt; eller andre om bruk av
1613 MPEG/H.264-video etter at jeg &lt;a
1614 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
1615 om innsyn i slike avtaler&lt;/a&gt;, tenkte jeg at i stedet for å forsøke å
1616 få NRK til å finne en slik avtale, så burde det være like enkelt å
1617 spørre MPEG-LA om de hadde avtale med NRK. Spørsmålet ble sendt før
1618 jeg fikk tips fra Kieran Kunhya om hvor listen over lisensinnehavere
1619 &quot;in Good Standing&quot; befant seg. MPEG-LA svarte meg i dag, og kan
1620 fortelle at NRK ikke har noen avtale med dem, så da er i det minste det
1621 slått fast. Ikke overraskende mener MPEG-LA at det trengs en avtale
1622 med MPEG-LA for å streame H.264, men deres rammer er jo
1623 rettstilstanden i USA og ikke Norge. Jeg tar dermed den delen av
1624 svaret med en klype salt. Jeg er dermed fortsatt ikke klok på om det
1625 trengs en avtale, og hvis det trengs en avtale her i Norge, heller
1626 ikke sikker på om NRK har en avtale med noen andre enn MPEG-LA som
1627 gjør at de ikke trenger avtale direkte med MPEG-LA. Jeg håper NRKs
1628 jurister har vurdert dette, og at det er mulig å få tilgang til
1629 vurderingen uansett om de trenger en avtale eller ikke.&lt;/p&gt;
1630
1631 &lt;p&gt;Her er epostutvekslingen med MPEG-LA så langt. Håper ikke
1632 utvekslingen fører til NRK plutselig får en litt uventet pakke fra
1633 MPEG-LA.&lt;/p&gt;
1634
1635 &lt;p&gt;&lt;blockquote&gt;
1636 &lt;p&gt;Date: Mon, 25 Jun 2012 15:29:37 +0200
1637 &lt;br&gt;From: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
1638 &lt;br&gt;To: licensing-web (at) mpegla.com
1639 &lt;br&gt;Subject: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
1640
1641 &lt;p&gt;Hi. I have a small question for you, that I hope it is OK that I
1642 ask.&lt;/p&gt;
1643
1644 &lt;p&gt;Is there any license agreements between MPEG-LA and NRK, &amp;lt;URL:
1645 &lt;a href=&quot;http://www.nrk.no/&quot;&gt;http://www.nrk.no/&lt;/a&gt; &amp;gt;, the
1646 Norwegian national broadcasting cooperation? I am not sure if they
1647 need one, and am just curious if such agreeement exist.&lt;/p&gt;
1648
1649 &lt;p&gt;The postal address is&lt;/p&gt;
1650
1651 &lt;p&gt;&lt;blockquote&gt;
1652 NRK
1653 &lt;br&gt;Postbox 8500, Majorstuen
1654 &lt;br&gt;0340 Oslo
1655 &lt;br&gt;Norway
1656 &lt;/blockquote&gt;&lt;/p&gt;
1657
1658 &lt;p&gt;if it make it easier for you to locate such agreement.&lt;/p&gt;
1659
1660 &lt;p&gt;Can you tell me how many entities in Norway have an agreement with
1661 MPEG-LA, and the name of these entities?&lt;/p&gt;
1662
1663 &lt;p&gt;--
1664 &lt;br&gt;Happy hacking
1665 &lt;br&gt;Petter Reinholdtsen
1666 &lt;/blockquote&gt;&lt;/p&gt;
1667
1668 &lt;p&gt;I dag, to dager senere, fikk jeg følgende svar:&lt;/p&gt;
1669
1670 &lt;p&gt;&lt;blockquote&gt;
1671 &lt;p&gt;Date: Thu, 28 Jun 2012 14:11:17 +0000
1672 &lt;br&gt;From: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&gt;
1673 &lt;br&gt;To: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&gt;
1674 &lt;br&gt;CC: MD Administration &amp;lt;MDAdministration (at) mpegla.com&gt;
1675 &lt;br&gt;Subject: RE: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
1676
1677 &lt;p&gt;Dear Mr. Reinholdtsen,&lt;/p&gt;
1678
1679 &lt;p&gt;Thank you for your message and for your interest in MPEG LA. We
1680 appreciate hearing from you and I will be happy to assist you.&lt;/p&gt;
1681
1682 &lt;p&gt;To begin, I will assume that you are referring to AVC/H.264
1683 technology in your message below, as this technology is commonly used
1684 in the transmission of video content. In that case, please allow me
1685 to briefly summarize the coverage provided by our AVC Patent Portfolio
1686 License.&lt;/p&gt;
1687
1688 &lt;P&gt;Our AVC License provides coverage for end products and video
1689 services that make use of AVC/H.264 technology. Accordingly, the
1690 party offering such end products and video to End Users concludes the
1691 AVC License and is responsible for paying the applicable royalties
1692 associated with the end products/video they offer.&lt;/p&gt;
1693
1694 &lt;p&gt;While the Norwegian Broadcast Corporation (NRK) is not currently a
1695 Licensee to MPEG LA&#39;s AVC License (or any other Portfolio License
1696 offered by MPEG LA), if NRK offers AVC Video to End Users for
1697 remuneration (for example, Title-by-Title, Subscription, Free
1698 Television, or Internet Broadcast AVC Video), then NRK will need to
1699 conclude the AVC License and may be responsible for paying applicable
1700 royalties associated with the AVC Video it distributes.&lt;/p&gt;
1701
1702 &lt;p&gt;Today I will send you a FedEx package containing a copy of our AVC
1703 License for your review. You should receive the License document
1704 within the next few days.&lt;/p&gt;
1705
1706 &lt;p&gt;Meanwhile, MPEG LA currently has several Norwegian Licensees that
1707 can be found under the &quot;Licensees&quot; header within the respective
1708 portion of our website. For example, you may find our list of
1709 Licensees in Good Standing to our AVC License in the AVC portion of
1710 our website,
1711 &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;
1712
1713 &lt;p&gt;I hope the above information is helpful. If you have additional
1714 questions or need further assistance with the AVC License, please feel
1715 free to contact me directly. I look forward to hearing from you again
1716 soon.&lt;/p&gt;
1717
1718 &lt;p&gt;Best regards,&lt;/p&gt;
1719
1720 &lt;p&gt;Ryan&lt;/p&gt;
1721
1722 &lt;p&gt;Ryan M. Rodriguez
1723 &lt;br&gt;Licensing Associate
1724 &lt;br&gt;MPEG LA
1725 &lt;br&gt;5425 Wisconsin Avenue
1726 &lt;br&gt;Suite 801
1727 &lt;br&gt;Chevy Chase, MD 20815
1728 &lt;br&gt;U.S.A.
1729 &lt;br&gt;Phone: +1 (301) 986-6660 x211
1730 &lt;br&gt;Fax: +1 (301) 986-8575
1731 &lt;br&gt;Email: rrodriguez (at) mpegla.com&lt;/p&gt;
1732
1733 &lt;/blockquote&gt;&lt;/p&gt;
1734
1735 &lt;p&gt;Meldingen om utsendt FedEx-pakke var så merkelig at jeg
1736 øyeblikkelig sendte svar tilbake og spurte hva i alle dager han mente,
1737 da han jo ikke hadde fått noen postadresse som nådde meg.&lt;/p&gt;
1738
1739 &lt;p&gt;&lt;blockquote&gt;
1740
1741 &lt;p&gt;Date: Thu, 28 Jun 2012 16:36:15 +0200
1742 &lt;br&gt;From: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
1743 &lt;br&gt;To: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
1744 &lt;br&gt;Cc: MD Administration &amp;lt;MDAdministration (at) mpegla.com&amp;gt;
1745 &lt;br&gt;Subject: Re: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
1746
1747 &lt;p&gt;[Ryan Rodriguez]
1748 &lt;br&gt;&amp;gt; Dear Mr. Reinholdtsen,&lt;/p&gt;
1749
1750 &lt;p&gt;Thank you for your quick reply.&lt;/p&gt;
1751
1752 &lt;p&gt;&amp;gt; Today I will send you a FedEx package containing a copy of our AVC
1753 &lt;br&gt;&amp;gt; License for your review. You should receive the License document
1754 &lt;br&gt;&amp;gt; within the next few days.&lt;/p&gt;
1755
1756 &lt;p&gt;The part about sending a FedEx package confused me, though. I did not
1757 &lt;br&gt;give you my address, nor am I associated with NRK in any way, so I hope
1758 &lt;br&gt;you did not try to send me a package using the address of NRK. If you
1759 &lt;br&gt;would send me the Internet address of to the document, it would be more
1760 &lt;br&gt;useful to me to be able to download it as an electronic document.&lt;/p&gt;
1761
1762 &lt;p&gt;&amp;gt; Meanwhile, MPEG LA currently has several Norwegian Licensees that can
1763 &lt;br&gt;&amp;gt; be found under the &quot;Licensees&quot; header within the respective portion
1764 &lt;br&gt;&amp;gt; of our website. For example, you may find our list of Licensees in
1765 &lt;br&gt;&amp;gt; Good Standing to our AVC License in the AVC portion of our website,
1766 &lt;br&gt;&amp;gt; http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx&lt;/p&gt;
1767
1768 &lt;p&gt;How can I recognize the Norwegian licensees?&lt;/p&gt;
1769
1770 &lt;p&gt;--
1771 &lt;br&gt;Happy hacking
1772 &lt;br&gt;Petter Reinholdtsen&lt;/p&gt;
1773 &lt;/blockquote&gt;&lt;/p&gt;
1774
1775 &lt;p&gt;Selv om jeg svarte kun noen minutter etter at jeg fikk eposten fra
1776 MPEG-LA, fikk jeg eposten under som automatisk var beskjed på min
1777 siste epost. Får håpe noen likevel følger opp &quot;FedEx-pakken&quot;. For å
1778 øke sjansen for at noen revurderer utsending av pakke uten mottaker,
1779 videresendte jeg min epost til swolf (at) mpegla.com, så får vi se.
1780 Har ikke hørt noe mer 3 timer senere, så jeg mistenker at ingen leste
1781 min epost tidsnok.&lt;/p&gt;
1782
1783 &lt;p&gt;&lt;blockquote&gt;
1784
1785 &lt;p&gt;Date: Thu, 28 Jun 2012 14:36:20 +0000
1786 &lt;br&gt;From: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
1787 &lt;br&gt;To: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
1788 &lt;br&gt;Subject: Automatic reply: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
1789
1790 &lt;p&gt;Thank you for your message.&lt;/p&gt;
1791
1792 &lt;p&gt;I will be out of the office until Thursday, July 5 and will respond
1793 to all messages upon my return. If this is a matter that requires
1794 immediate attention, please contact Sidney Wolf (swolf (at)
1795 mpegla.com)&lt;/p&gt;
1796
1797 &lt;p&gt;Best regards,&lt;/p&gt;
1798
1799 &lt;p&gt;Ryan&lt;/p&gt;
1800
1801 &lt;p&gt;Ryan M. Rodriguez
1802 &lt;br&gt;Licensing Associate
1803 &lt;br&gt;MPEG LA&lt;/p&gt;
1804
1805 &lt;/blockquote&gt;&lt;/p&gt;
1806
1807 &lt;p&gt;Litt klokere, men fortsatt ikke klok på mitt opprinnelige spørsmål,
1808 som er om en trenger avtale med MPEG-LA for å publisere eller
1809 kringkaste H.264-video i Norge.&lt;/p&gt;
1810 </description>
1811 </item>
1812
1813 <item>
1814 <title>NRK nekter å finne og utlevere eventuell avtale med MPEG-LA</title>
1815 <link>http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html</link>
1816 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html</guid>
1817 <pubDate>Mon, 25 Jun 2012 15:10:00 +0200</pubDate>
1818 <description>&lt;p&gt;Jeg fikk nettopp svar fra NRK på
1819 &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
1820 forespørsel om kopi av avtale&lt;/a&gt; med MPEG-LA eller andre om bruk av
1821 MPEG og/eller H.264. Svaret har fått saksreferanse 2011/371 (mon tro
1822 hva slags sak fra 2011 dette er?) hos NRK og lyder som følger:&lt;/p&gt;
1823
1824 &lt;p&gt;&lt;blockquote&gt;
1825
1826 &lt;p&gt;&lt;strong&gt;Svar på innsynsbegjæring i MPEG / H.264-relaterte
1827 avtaler&lt;/strong&gt;&lt;/p&gt;
1828
1829 &lt;p&gt;Viser til innsynsbegjæring av 19. juni 2012. Kravet om innsyn
1830 gjelder avtale som gjør at NRK «ikke er begrenset av de generelle
1831 bruksvilkårene som gjelder for utstyr som bruker MPEG og/eller
1832 H.264».&lt;/p&gt;
1833
1834 &lt;p&gt;I henhold til offentleglova § 28 annet ledd må innsynskravet gjelde
1835 en bestemt sak eller i rimelig utstrekning saker av en bestemt
1836 sak. Det er på det rene at det aktuelle innsynskravet ikke gjelder en
1837 bestemt sak. Spørsmålet som reiser seg er om identifiseringsgraden er
1838 tilstrekkelig. I Justisdepartementets «Rettleiar til offentleglova»
1839 står følgende:&lt;/p&gt;
1840
1841 &lt;p&gt;«Kravet om at innsynskravet må gjelde ei bestemt sak er til hinder
1842 for at eit innsynskrav kan gjelde alle saker av ein bestemt art, utan
1843 at den enkelte saka blir identifisert. Ein kan med andre ord i
1844 utgangspunktet ikkje krevje innsyn i til dømes alle saker om
1845 utsleppsløyve hos Statens forureiningstilsyn frå dei siste tre åra,
1846 med mindre ein identifiserer kvar enkelt sak, til dømes med tilvising
1847 til dato, partar eller liknande.»&lt;/p&gt;
1848
1849 &lt;p&gt;Vedrørende denne begrensningen har Justisdepartementet uttalt
1850 følgende (Lovavdelingens uttalelser JDLOV-2010-3295):&lt;/p&gt;
1851
1852 &lt;p&gt;&lt;em&gt;«Bakgrunnen for avgrensinga av kva innsynskravet kan gjelde,
1853 er fyrst og fremst at meir generelle innsynskrav, utan noka form for
1854 identifikasjon av kva ein eigentleg ynskjer, ville vere svært
1855 vanskelege å handsame for forvaltninga.»&lt;/em&gt;&lt;/p&gt;
1856
1857 &lt;p&gt;I samme sak uttaler Lovavdelingen følgende:&lt;/p&gt;
1858
1859 &lt;p&gt;&lt;em&gt;«Det følgjer vidare av offentleglova § 28 andre ledd at det `i
1860 rimeleg utstrekning&#39; kan krevjast innsyn i `saker av ein bestemt
1861 art&#39;. Vilkåret om at eit innsynskrav berre `i rimeleg utstrekning&#39; kan
1862 gjelde saker av ein bestemt art, er i hovudsak knytt til kor
1863 arbeidskrevjande det vil vere å finne fram til dei aktuelle
1864 dokumenta. I tillegg reknar vi med at vilkåret kan gje grunnlag for å
1865 nekte innsyn i tilfelle der innsynskravet er så omfattande (gjeld så
1866 mange dokument) at arbeidsmengda som ville gått med til å handsame
1867 det, er større enn det ein `i rimeleg utstrekning&#39; kan krevje (sjølv
1868 om det nok skal mykje til).»&lt;/em&gt;&lt;/p&gt;
1869
1870 &lt;p&gt;NRK har ikke noen egen sammenstilling over avtaler innenfor
1871 bestemte områder som omtales i innsynsbegjæringen. De måtte søkes på
1872 vanlig måte. I tillegg finnes ikke noen automatisert måte å finne
1873 avtaler som «ikke er begrenset av de generelle bruksvilkårene som
1874 gjelder for utstyr som bruker MPEG og/eller H.264». En slik
1875 gjennomgang av avtaler måtte gjøres manuelt av en person med
1876 spesialistkunnskap. Dette vil kreve at NRK avsetter omfattende
1877 ressurser for å finne frem relevante avtaler og for deretter å vurdere
1878 om de dekkes av det innsynsbegjæringen omfattes.&lt;/p&gt;
1879
1880 &lt;p&gt;På bakgrunn av dette nekter NRK innsyn, med den begrunnelsen at
1881 innsynskravet er så omfattende at arbeidsmengden for å håndtere kravet
1882 vil være langt større enn det som i rimelig utstrekning kan kreves i
1883 henhold til offentleglova § 28 annet ledd.&lt;/p&gt;
1884
1885 &lt;p&gt;Avslag på deres innsynsbegjæring kan påklages til Kultur- og
1886 kirkedepartementet innen tre uker fra det tidspunkt avslaget kommer
1887 frem til mottakeren, i henhold til reglene i offentleglova § 32,
1888 jf. forvaltningsloven kapittel VI. Klagen skal stiles til Kultur- og
1889 kirkedepartementet, og sendes til NRK.&lt;/p&gt;
1890
1891 &lt;p&gt;NRK er imidlertid etter Offentleglova forpliktet å gi ut journaler,
1892 slik at en eventuell søknad om innsyn kan tydeligere identifisere
1893 hvilke dokumenter som det ønskes innsyn i. NRKs offentlige journaler
1894 for inneværende og forrige måned ligger ute på
1895 NRK.no/innsyn. Journaler som går lengre tilbake i tid, kan sendes ut
1896 på forespørsel til innsyn (at) nrk.no.&lt;/p&gt;
1897
1898 &lt;p&gt;Med hilsen
1899 &lt;br&gt;Dokumentarkivet i NRK
1900 &lt;br&gt;v/ Elin Brandsrud
1901 &lt;br&gt;Tel. direkte: 23 04 29 29
1902 &lt;br&gt;Post: RBM3, Postboks 8500 Majorstuen, 0340 Oslo
1903 &lt;br&gt;innsyn (at) nrk.no&lt;/p&gt;
1904
1905 &lt;/blockquote&gt;&lt;/p&gt;
1906
1907 &lt;p&gt;Svaret kom
1908 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2012-06-25-video-mpegla-nrk.pdf&quot;&gt;i
1909 PDF-form som vedlegg på epost&lt;/a&gt;. Jeg er litt usikker på hvordan jeg
1910 best går videre for å bli klok, men jeg har jo i hvert fall tre uker
1911 på å vurdere om jeg skal klage. Enten må nok forespørselen
1912 reformuleres eller så må jeg vel klage. Synes jo det er merkelig at
1913 NRK ikke har bedre kontroll med hvilke avtaler de har inngått. Det
1914 burde jo være noen i ledelsen som vet om de har signert en avtale med
1915 MPEG-LA eller ikke...&lt;/p&gt;
1916
1917 &lt;p&gt;Oppdatering 2012-06-25 20:20: Et google-søk på &quot;2011/371 nrk&quot;
1918 sendte meg til postjournalen for
1919 &lt;a href=&quot;http://nrk.no/contentfile/file/1.8212365!offentligjournal19062012.pdf&quot;&gt;2012-06-19&lt;/a&gt;
1920 og
1921 &lt;a href=&quot;http://nrk.no/contentfile/file/1.8214156!offentligjournal20062012.pdf&quot;&gt;2012-06-20&lt;/a&gt;
1922 hos NRK som viser mine forespørsler og viser at sakens tittel hos NRK
1923 er &quot;Graphic Systems Regions MA 2378/10E&quot;. Videre søk etter &quot;Graphic
1924 Systems Regions&quot; viser at dette er saken til et anbud om
1925 &quot;&lt;a href=&quot;http://no.mercell.com/m/mts/Tender/27179412.aspx&quot;&gt;a graphics
1926 system for 12 or 13 sites broadcasting regional news&lt;/a&gt;&quot; hos Mercell
1927 Sourcing Service, også omtalt på
1928 &lt;a href=&quot;http://www.publictenders.net/tender/595705&quot;&gt;Public
1929 Tenders&lt;/a&gt; og
1930 &lt;a href=&quot;http://www.doffin.no/search/show/search_view.aspx?ID=JAN155521&quot;&gt;Doffin&lt;/a&gt;.
1931 Jeg er dog usikker på hvordan dette er relatert til min
1932 forespørsel.&lt;/p&gt;
1933
1934 &lt;p&gt;Oppdatering 2012-06-25 22:40: Ble tipset av Kieran Kunhya, fra
1935 miljøet rundt
1936 &lt;a href=&quot;http://code.google.com/p/open-broadcast-encoder/&quot;&gt;Open
1937 Broadcast Encoder&lt;/a&gt;, at listen over de som har lisensavtale med
1938 MPEG-LA er
1939 &lt;a href=&quot;http://www.mpeg-la.com/main/programs/AVC/Pages/Licensees.aspx&quot;&gt;tilgjengelig
1940 på web&lt;/a&gt;. Veldig fint å oppdage hvor den finnes, da jeg må ha lett
1941 etter feil ting da jeg forsøke å finne den. Der står ikke NRK, men
1942 flere andre &quot;Broadcasting Company&quot;-oppføringer. Lurer på om det betyr
1943 at NRK ikke trenger avtale, eller noe helt annet?&lt;/p&gt;
1944 </description>
1945 </item>
1946
1947 <item>
1948 <title>Song book for Computer Scientists</title>
1949 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
1950 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
1951 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
1952 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
1953 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
1954 collecting computer related songs for use at parties. The original
1955 version was written in LaTeX, but a few years ago I got help from
1956 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
1957 while keeping the ability to create a nice book in PDF format. I have
1958 not had time to maintain the book for a while now, and guess I should
1959 put it up on some public version control repository where others can
1960 help me extend and update the book. If anyone is volunteering to help
1961 me with this, send me an email. Also let me know if there are songs
1962 missing in my book.&lt;/p&gt;
1963
1964 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
1965 me today that I really should let all my readers share the joys of
1966 singing out load about programming, computers and computer networks.
1967 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
1968 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
1969 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
1970 Computer Science Songbook&lt;/a&gt;.
1971 </description>
1972 </item>
1973
1974 <item>
1975 <title>Trenger en avtale med MPEG-LA for å publisere og kringkaste H.264-video?</title>
1976 <link>http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html</link>
1977 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html</guid>
1978 <pubDate>Thu, 21 Jun 2012 13:40:00 +0200</pubDate>
1979 <description>&lt;p&gt;Trengs det avtale med MPEG-LA for å ha lovlig rett til å
1980 distribuere og kringkaste video i MPEG4 eller med videokodingen H.264?
1981 &lt;a href=&quot;http://webmink.com/essays/h-264/&quot;&gt;H.264 og MPEG4 er jo ikke en
1982 fri og åpen standard&lt;/a&gt; i henhold til
1983 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html&quot;&gt;definisjonen
1984 til Digistan&lt;/a&gt;, så i enkelte land er det ingen tvil om at du må ha
1985 en slik avtale, men jeg må innrømme at jeg ikke vet om det også
1986 gjelder Norge. Det ser uansett ut til å være en juridisk interessant
1987 problemstilling. Men jeg tenkte her om dagen som så, at hvis det er
1988 nødvendig, så har store aktører som
1989 &lt;a href=&quot;http://www.nrk.no/&quot;&gt;NRK&lt;/a&gt; og
1990 &lt;a href=&quot;http://www.regjeringen.no/&quot;&gt;regjeringen&lt;/a&gt; skaffet seg en
1991 slik avtale. Jeg har derfor sendt forespørsel til begge (for
1992 regjeringen sin del er det Departementenes Servicesenter som gjør
1993 jobben), og bedt om kopi av eventuelle avtaler de har om bruk av MPEG
1994 og/eller H.264 med MPEG-LA eller andre aktører som opererer på vegne
1995 av MPEG-LA. Her er kopi av eposten jeg har sendt til
1996 &lt;a href=&quot;http://www.dss.dep.no/&quot;&gt;Departementenes Servicesenter&lt;/a&gt;.
1997 Forespørselen til NRK er veldig lik.&lt;/p&gt;
1998
1999 &lt;p&gt;&lt;blockquote&gt;
2000
2001 &lt;p&gt;Date: Tue, 19 Jun 2012 15:18:33 +0200
2002 &lt;br&gt;From: Petter Reinholdtsen
2003 &lt;br&gt;To: postmottak@dss.dep.no
2004 &lt;br&gt;Subject: Innsynsbegjæring om MPEG/H.264-relaterte avtaler
2005
2006 &lt;p&gt;Hei. Jeg ber herved om innsyn og kopi av dokumenter i DSS relatert
2007 til avtaler rundt bruk av videoformatene MPEG og H.264. Jeg er
2008 spesielt interessert i å vite om DSS har lisensavtale med MPEG-LA
2009 eller noen som representerer MPEG-LA i Norge.&lt;/p&gt;
2010
2011 &lt;p&gt;MPEG og H.264 er videoformater som brukes både til kringkasting
2012 (f.eks. i bakkenett og kabel-TV) og videopublisering på web, deriblant
2013 via Adobe Flash. MPEG-LA, &amp;lt;URL:
2014 &lt;a href=&quot;http://www.mpeg-la.com/&quot;&gt;http://www.mpeg-la.com/&lt;/a&gt; &amp;gt;, er
2015 en organisasjon som har fått oppgaven, av de kjente rettighetshavere
2016 av immaterielle rettigheter knyttet til MPEG og H.264, å selge
2017 bruksrett for MPEG og H.264.&lt;/p&gt;
2018
2019 &lt;p&gt;Via regjeringen.no kringkastes med MPEG og H.264-baserte
2020 videoformater, og dette ser ut til å være organisert av DSS. Jeg
2021 antar dermed at DSS har avtale med en eller annen aktør om dette.&lt;/p&gt;
2022
2023 &lt;p&gt;F.eks. har Adobe Premiere Pro har følgende klausul i følge &amp;lt;URL:
2024 &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;
2025 &amp;gt;:&lt;/p&gt;
2026
2027 &lt;p&gt;&lt;blockquote&gt;
2028
2029 &lt;p&gt;6.17. AVC DISTRIBUTION. The following notice applies to software
2030 containing AVC import and export functionality: THIS PRODUCT IS
2031 LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND
2032 NON-COMMERCIAL USE OF A CONSUMER TO (a) ENCODE VIDEO IN COMPLIANCE
2033 WITH THE AVC STANDARD (&quot;AVC VIDEO&quot;) AND/OR (b) DECODE AVC VIDEO THAT
2034 WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL
2035 ACTIVITY AND/OR AVC VIDEO THAT WAS OBTAINED FROM A VIDEO PROVIDER
2036 LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
2037 IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED
2038 FROM MPEG LA L.L.C. SEE
2039 &lt;a href=&quot;http://www.mpegla.com&quot;&gt;http://www.mpegla.com&lt;/a&gt;.&lt;/p&gt;
2040
2041 &lt;/blockquote&gt;&lt;/p&gt;
2042
2043 &lt;p&gt;Her er det kun &quot;non-commercial&quot; og &quot;personal and non-commercial&quot;
2044 aktivitet som er tillatt uten ekstra avtale med MPEG-LA.&lt;/p&gt;
2045
2046 &lt;p&gt;Et annet tilsvarende eksempel er Apple Final Cut Pro, som har
2047 følgende klausul i følge &amp;lt;URL:
2048 &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;
2049 &amp;gt;:&lt;/p&gt;
2050
2051 &lt;p&gt;&lt;blockquote&gt;
2052
2053 &lt;p&gt;15. Merknad om H.264/AVC. Hvis Apple-programvaren inneholder
2054 funksjonalitet for AVC-koding og/eller AVC-dekoding, krever
2055 kommersiell bruk ekstra lisensiering og følgende gjelder:
2056 AVC-FUNKSJONALITETEN I DETTE PRODUKTET KAN KUN ANVENDES AV
2057 FORBRUKERE OG KUN FOR PERSONLIG OG IKKE- KOMMERSIELL BRUK TIL (i)
2058 KODING AV VIDEO I OVERENSSTEMMELSE MED AVC-STANDARDEN (&quot;AVC-VIDEO&quot;)
2059 OG/ELLER (ii) DEKODING AV AVC-VIDEO SOM ER KODET AV EN FORBRUKER TIL
2060 PERSONLIG OG IKKE-KOMMERSIELL BRUK OG/ELLER DEKODING AV AVC-VIDEO
2061 FRA EN VIDEOLEVERANDØR SOM HAR LISENS TIL Å TILBY
2062 AVC-VIDEO. INFORMASJON OM ANNEN BRUK OG LISENSIERING KAN INNHENTES
2063 FRA MPEG LA L.L.C. SE HTTP://WWW.MPEGLA.COM.&lt;/p&gt;
2064 &lt;/blockquote&gt;&lt;/p&gt;
2065
2066 &lt;p&gt;Tilsvarende gjelder for andre programvarepakker, kamera, etc som
2067 bruker MPEG og H.264, at en må ha en avtale med MPEG-LA for å ha lov
2068 til å bruke programmet/utstyret hvis en skal lage noe annet enn
2069 private filmer og i ikke-kommersiell virksomhet.&lt;/p&gt;
2070
2071 &lt;p&gt;Jeg er altså interessert i kopi av avtaler DSS har som gjør at en
2072 ikke er begrenset av de generelle bruksvilkårene som gjelder for
2073 utstyr som bruker MPEG og/eller H.264.&lt;/p&gt;
2074 &lt;/blockquote&gt;&lt;/p&gt;
2075
2076 &lt;p&gt;Nå venter jeg spent på svaret. Jeg planlegger å blogge om svaret
2077 her.&lt;/p&gt;
2078 </description>
2079 </item>
2080
2081 <item>
2082 <title>HTC One X - Your video? What do you mean?</title>
2083 <link>http://people.skolelinux.org/pere/blog/HTC_One_X___Your_video___What_do_you_mean_.html</link>
2084 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/HTC_One_X___Your_video___What_do_you_mean_.html</guid>
2085 <pubDate>Thu, 26 Apr 2012 13:20:00 +0200</pubDate>
2086 <description>&lt;p&gt;In &lt;a href=&quot;http://www.idg.no/computerworld/article243690.ece&quot;&gt;an
2087 article today&lt;/a&gt; published by Computerworld Norway, the photographer
2088 &lt;a href=&quot;http://www.urke.com/eirik/&quot;&gt;Eirik Helland Urke&lt;/a&gt; reports
2089 that the video editor application included with
2090 &lt;a href=&quot;http://www.htc.com/www/smartphones/htc-one-x/#specs&quot;&gt;HTC One
2091 X&lt;/a&gt; have some quite surprising terms of use. The article is mostly
2092 based on the twitter message from mister Urke, stating:
2093
2094 &lt;p&gt;&lt;blockquote&gt;
2095 &quot;&lt;a href=&quot;http://twitter.com/urke/status/194062269724897280&quot;&gt;Drøy
2096 brukeravtale: HTC kan bruke MINE redigerte videoer kommersielt. Selv
2097 kan jeg KUN bruke dem privat.&lt;/a&gt;&quot;
2098 &lt;/blockquote&gt;&lt;/p&gt;
2099
2100 &lt;p&gt;I quickly translated it to this English message:&lt;/p&gt;
2101
2102 &lt;p&gt;&lt;blockquote&gt;
2103 &quot;Arrogant user agreement: HTC can use MY edited videos
2104 commercially. Although I can ONLY use them privately.&quot;
2105 &lt;/blockquote&gt;&lt;/p&gt;
2106
2107 &lt;p&gt;I&#39;ve been unable to find the text of the license term myself, but
2108 suspect it is a variation of the MPEG-LA terms I
2109 &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
2110 with my Canon IXUS 130&lt;/a&gt;. The HTC One X specification specifies that
2111 the recording format of the phone is .amr for audio and .mp3 for
2112 video. AMR is
2113 &lt;a href=&quot;http://en.wikipedia.org/wiki/Adaptive_Multi-Rate_audio_codec#Licensing_and_patent_issues&quot;&gt;Adaptive
2114 Multi-Rate audio codec&lt;/a&gt; with patents which according to the
2115 Wikipedia article require an license agreement with
2116 &lt;a href=&quot;http://www.voiceage.com/&quot;&gt;VoiceAge&lt;/a&gt;. MP4 is
2117 &lt;a href=&quot;http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Patent_licensing&quot;&gt;MPEG4 with
2118 H.264&lt;/a&gt;, which according to Wikipedia require a licence agreement
2119 with &lt;a href=&quot;http://www.mpegla.com/&quot;&gt;MPEG-LA&lt;/a&gt;.&lt;/p&gt;
2120
2121 &lt;p&gt;I know why I prefer
2122 &lt;a href=&quot;http://www.digistan.org/open-standard:definition&quot;&gt;free and open
2123 standards&lt;/a&gt; also for video.&lt;/p&gt;
2124 </description>
2125 </item>
2126
2127 <item>
2128 <title>RAND terms - non-reasonable and discriminatory</title>
2129 <link>http://people.skolelinux.org/pere/blog/RAND_terms___non_reasonable_and_discriminatory.html</link>
2130 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/RAND_terms___non_reasonable_and_discriminatory.html</guid>
2131 <pubDate>Thu, 19 Apr 2012 22:20:00 +0200</pubDate>
2132 <description>&lt;p&gt;Here in Norway, the
2133 &lt;a href=&quot;http://www.regjeringen.no/nb/dep/fad.html?id=339&quot;&gt; Ministry of
2134 Government Administration, Reform and Church Affairs&lt;/a&gt; is behind
2135 a &lt;a href=&quot;http://standard.difi.no/forvaltningsstandarder&quot;&gt;directory of
2136 standards&lt;/a&gt; that are recommended or mandatory for use by the
2137 government. When the directory was created, the people behind it made
2138 an effort to ensure that everyone would be able to implement the
2139 standards and compete on equal terms to supply software and solutions
2140 to the government. Free software and non-free software could compete
2141 on the same level.&lt;/p&gt;
2142
2143 &lt;p&gt;But recently, some standards with RAND
2144 (&lt;a href=&quot;http://en.wikipedia.org/wiki/Reasonable_and_non-discriminatory_licensing&quot;&gt;Reasonable
2145 And Non-Discriminatory&lt;/a&gt;) terms have made their way into the
2146 directory. And while this might not sound too bad, the fact is that
2147 standard specifications with RAND terms often block free software from
2148 implementing them. The reasonable part of RAND mean that the cost per
2149 user/unit is low,and the non-discriminatory part mean that everyone
2150 willing to pay will get a license. Both sound great in theory. In
2151 practice, to get such license one need to be able to count users, and
2152 be able to pay a small amount of money per unit or user. By
2153 definition, users of free software do not need to register their use.
2154 So counting users or units is not possible for free software projects.
2155 And given that people will use the software without handing any money
2156 to the author, it is not really economically possible for a free
2157 software author to pay a small amount of money to license the rights
2158 to implement a standard when the income available is zero. The result
2159 in these situations is that free software are locked out from
2160 implementing standards with RAND terms.&lt;/p&gt;
2161
2162 &lt;p&gt;Because of this, when I see someone claiming the terms of a
2163 standard is reasonable and non-discriminatory, all I can think of is
2164 how this really is non-reasonable and discriminatory. Because free
2165 software developers are working in a global market, it does not really
2166 help to know that software patents are not supposed to be enforceable
2167 in Norway. The patent regimes in other countries affect us even here.
2168 I really hope the people behind the standard directory will pay more
2169 attention to these issues in the future.&lt;/p&gt;
2170
2171 &lt;p&gt;You can find more on the issues with RAND, FRAND and RAND-Z terms
2172 from Simon Phipps
2173 (&lt;a href=&quot;http://blogs.computerworlduk.com/simon-says/2010/11/rand-not-so-reasonable/&quot;&gt;RAND:
2174 Not So Reasonable?&lt;/a&gt;).&lt;/p&gt;
2175
2176 &lt;p&gt;Update 2012-04-21: Just came across a
2177 &lt;a href=&quot;http://blogs.computerworlduk.com/open-enterprise/2012/04/of-microsoft-netscape-patents-and-open-standards/index.htm&quot;&gt;blog
2178 post from Glyn Moody&lt;/a&gt; over at Computer World UK warning about the
2179 same issue, and urging people to speak out to the UK government. I
2180 can only urge Norwegian users to do the same for
2181 &lt;a href=&quot;http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder&quot;&gt;the
2182 hearing taking place at the moment&lt;/a&gt; (respond before 2012-04-27).
2183 It proposes to require video conferencing standards including
2184 specifications with RAND terms.&lt;/p&gt;
2185 </description>
2186 </item>
2187
2188 <item>
2189 <title>Hvordan enkelt laste ned filmer fra NRK</title>
2190 <link>http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html</link>
2191 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html</guid>
2192 <pubDate>Sat, 5 Nov 2011 15:20:00 +0100</pubDate>
2193 <description>&lt;p&gt;Ofte har jeg lyst til å laste ned et innslag fra NRKs nettsted for
2194 å se det senere når jeg ikke er på nett, eller for å ha det
2195 tilgjengelig når jeg en gang i fremtiden ønsker å referere til
2196 innslaget selv om NRK har fjernet det fra sine nettsider. I dag fant
2197 jeg et lite script som fikser jobben.&lt;/p&gt;
2198
2199 &lt;p&gt;Scriptet er laget av Jan Henning Thorsen og tilgjengelig fra
2200 &lt;a href=&quot;http://jhthorsen.github.com/snippets/nrk-downloader/&quot;&gt;github&lt;/a&gt;,
2201 og gjør det veldig enkelt å laste ned. Kjør &lt;tt&gt;nrk-downloader.sh
2202 http://www1.nrk.no/nett-tv/klipp/582810&lt;/tt&gt; for å hente ned et enkelt
2203 innslag eller &lt;tt&gt;nrk-downloader.sh
2204 http://www1.nrk.no/nett-tv/kategori/3521&lt;/tt&gt; for å laste ned alle
2205 episodene i en serie.&lt;/p&gt;
2206
2207 &lt;p&gt;Det er ikke rakettforskning å laste ned NRK-&quot;strømmer&quot;, og
2208 tidligere gjorde jeg dette manuelt med mplayer. Scriptet til
2209 Hr. Thorsen gjør det raskere og enklere for meg, men jeg vil ikke si
2210 at det er en revolusjonerende løsning. Jeg mener jo fortsatt at
2211 påstanden fra NRKs ansatte om at det er
2212 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html&quot;&gt;vesensforskjellig
2213 å legge tilgjengelig for nedlasting og for streaming&lt;/a&gt; er
2214 meningsløs.&lt;/p&gt;
2215 </description>
2216 </item>
2217
2218 <item>
2219 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
2220 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
2221 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
2222 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
2223 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
2224 mentioned the issues I believe should be improved in Debian for its
2225 desktop to be useful for more people. The use case for this is my
2226 parents, which are currently running Kubuntu which solve the
2227 issues.&lt;/p&gt;
2228
2229 &lt;p&gt;I suspect these four missing features are not very hard to
2230 implement. After all, they are present in Ubuntu, so if we wanted to
2231 do this in Debian we would have a source.&lt;/p&gt;
2232
2233 &lt;ol&gt;
2234
2235 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
2236 are new packages available for upgrades, a icon in the KDE status bar
2237 indicate this, and clicking on it will activate the simple upgrade
2238 tool to handle it. I have no problem guiding both of my parents
2239 through the process over the phone. If a kernel reboot is required,
2240 this too is indicated by the status bars and the upgrade tool. Last
2241 time I checked, nothing with the same features was working in KDE in
2242 Debian.&lt;/li&gt;
2243
2244 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
2245 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
2246 currently have a handler for, it will ask the user if the system
2247 should search for a package that would add support for this MIME type,
2248 and if the user say yes, the APT sources will be searched for packages
2249 advertising the MIME type in their control file (visible in the
2250 Packages file in the APT archive). If one or more packages are found,
2251 it is a simple click of the mouse to add support for the missing mime
2252 type. If the package require the user to accept some non-free
2253 license, this is explained to the user. The entire process make it
2254 more clear to the user why something do not work in the browser, and
2255 make the chances higher for the user to blame the web page authors and
2256 not the browser for any missing features.&lt;/li&gt;
2257
2258 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
2259 handlers.&lt;/strong&gt; When the media players encounter a format or codec
2260 it is not supporting, a dialog pop up asking the user if the system
2261 should search for a package that would add support for it. This
2262 happen with things like MP3, Windows Media or H.264. The selection
2263 and installation procedure is very similar to the Firefox browser
2264 plugin handling. This is as far as I know implemented using a
2265 gstreamer hook. The end result is that the user easily get access to
2266 the codecs that are present from the APT archives available, while
2267 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
2268
2269 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
2270 displaying a text/plain file in my Debian browser, it will propose to
2271 start emacs to show it. If I remember correctly, when doing the same
2272 in Kunbutu it show the file as a text file in the browser. At least I
2273 know Opera will show text files within the browser. I much prefer the
2274 latter behaviour.&lt;/li&gt;
2275
2276 &lt;/ol&gt;
2277
2278 &lt;p&gt;There are other nice features as well, like the simplified suite
2279 upgrader, but given that I am the one mostly doing the dist-upgrade,
2280 it do not matter much.&lt;/p&gt;
2281
2282 &lt;p&gt;I really hope we could get these features in place for the next
2283 Debian release. It would require the coordinated effort of several
2284 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
2285 </description>
2286 </item>
2287
2288 <item>
2289 <title>Gnash enteres Google Summer of Code 2011</title>
2290 <link>http://people.skolelinux.org/pere/blog/Gnash_enteres_Google_Summer_of_Code_2011.html</link>
2291 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_enteres_Google_Summer_of_Code_2011.html</guid>
2292 <pubDate>Wed, 6 Apr 2011 09:00:00 +0200</pubDate>
2293 <description>&lt;p&gt;&lt;a href=&quot;http://www.getgnash.org/&quot;&gt;The Gnash project&lt;/a&gt; is still
2294 the most promising solution for a Free Software Flash implementation.
2295 A few days ago the project
2296 &lt;a href=&quot;http://lists.gnu.org/archive/html/gnash-dev/2011-04/msg00011.html&quot;&gt;announced&lt;/a&gt;
2297 that it will participate in Google Summer of Code. I hope many
2298 students apply, and that some of them succeed in getting AVM2 support
2299 into Gnash.&lt;/p&gt;
2300 </description>
2301 </item>
2302
2303 <item>
2304 <title>Why isn&#39;t Debian Edu using VLC?</title>
2305 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
2306 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
2307 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
2308 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
2309 presented, and the winner among the multimedia player were VLC.
2310 Personally, I like VLC, and it is my player of choice when I first try
2311 to play a video file or stream. Only if VLC fail will I drag out
2312 gmplayer to see if it can do better. The reason is mostly the failure
2313 model and trust. When VLC fail, it normally pop up a error message
2314 reporting the problem. When mplayer fail, it normally segfault or
2315 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
2316
2317 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
2318 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
2319 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
2320 plugin to play web videos seamlessly, and the VLC browser plugin is
2321 not very good. For example, it lack in-line control buttons, so there
2322 is no way for the user to pause the video. Also, when I
2323 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
2324 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
2325 failed on several video pages where mplayer based plugins worked. If
2326 the browser plugin for VLC was as good as the gecko-mediaplayer
2327 package (which uses mplayer), we would switch.&lt;/P&gt;
2328
2329 &lt;p&gt;While VLC is a good player, its user interface is slightly
2330 annoying. The most annoying feature is its inconsistent use of
2331 keyboard shortcuts. When the player is in full screen mode, its
2332 shortcuts are different from when it is playing the video in a window.
2333 For example, space only work as pause when in full screen mode. I
2334 wish it had consisten shortcuts and that space also would work when in
2335 window mode. Another nice shortcut in gmplayer is [enter] to restart
2336 the current video. It is very nice when playing short videos from the
2337 web and want to restart it when new people arrive to have a look at
2338 what is going on.&lt;/p&gt;
2339 </description>
2340 </item>
2341
2342 <item>
2343 <title>Best å ikke fortelle noen at streaming er nedlasting...</title>
2344 <link>http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html</link>
2345 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html</guid>
2346 <pubDate>Sat, 30 Oct 2010 11:20:00 +0200</pubDate>
2347 <description>&lt;p&gt;I dag la jeg inn en kommentar på en sak hos NRKBeta
2348 &lt;a href=&quot;http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/&quot;&gt;om
2349 hvordan TV-serien Blindpassasjer ble laget&lt;/a&gt; i forbindelse med at
2350 filmene NRK la ut ikke var tilgjengelig i et
2351 &lt;a href=&quot;http://www.digistan.org/open-standard:definition&quot;&gt;fritt og
2352 åpent format&lt;/a&gt;. Dette var det jeg skrev publiserte der 07:39.&lt;/p&gt;
2353
2354 &lt;p&gt;&lt;blockquote&gt;
2355 &lt;p&gt;&quot;Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
2356 nedlasting. Mange av oss som kan mer enn gjennomsnittet om systemer
2357 som dette, vet at det stort sett er mulig å lure ut ting med den
2358 nødvendige forkunnskapen.&quot;&lt;/p&gt;
2359
2360 &lt;p&gt;Haha. Å streame innhold er det samme som å laste ned innhold, så å
2361 beskytte en stream mot nedlasting er ikke mulig. Å skrive noe slikt
2362 er å forlede leseren.&lt;/p&gt;
2363
2364 &lt;p&gt;Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
2365 vil tillate streaming men ikke nedlasting meningsløs.&lt;/p&gt;
2366
2367 &lt;p&gt;Anbefaler forresten å lese
2368 &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;
2369 om hva som ville være konsekvensen hvis digitale avspillingssperrer
2370 (DRM) fungerte. Det gjør de naturligvis ikke teknisk - det er jo
2371 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
2372 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
2373 opp under.&lt;/p&gt;
2374 &lt;/blockquote&gt;&lt;/p&gt;
2375
2376 &lt;p&gt;Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
2377 NRKBeta:&lt;/p&gt;
2378
2379 &lt;p&gt;&lt;blockquote&gt;
2380 &lt;p&gt;From: Anders Hofseth &amp;lt;XXX@gmail.com&gt;
2381 &lt;br&gt;To: &quot;pere@hungry.com&quot; &amp;lt;pere@hungry.com&gt;
2382 &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;
2383 &lt;br&gt;Subject: Re: [NRKbeta] Kommentar: &quot;Bakom Blindpassasjer: del 1&quot;
2384 &lt;br&gt;Date: Sat, 30 Oct 2010 07:58:44 +0200&lt;/p&gt;
2385
2386 &lt;p&gt;Hei Petter.
2387 &lt;br&gt;Det du forsøker dra igang er egentlig en interessant diskusjon,
2388 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
2389 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
2390 særlig lett å klarere ut noe annet arkivmateriale på lang tid.&lt;/p&gt;
2391
2392 &lt;p&gt;Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
2393 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
2394 konsekvensene vi beskriver ikke er noe du ønsker heller...&lt;/p&gt;
2395
2396 &lt;p&gt;Med hilsen,
2397 &lt;br&gt;-anders&lt;/p&gt;
2398
2399 &lt;p&gt;Ring meg om noe er uklart: 95XXXXXXX&lt;/p&gt;
2400 &lt;/blockquote&gt;&lt;/p&gt;
2401
2402 &lt;p&gt;Ble så fascinert over denne holdningen, at jeg forfattet og sendte
2403 over følgende svar. I og med at debatten er fjernet fra NRK Betas
2404 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
2405 Har fjernet epostadresser og telefonnummer til de involverte, for å
2406 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.&lt;/p&gt;
2407
2408 &lt;p&gt;&lt;blockquote&gt;
2409 &lt;p&gt;From: Petter Reinholdtsen &amp;lt;pere@hungry.com&gt;
2410 &lt;br&gt;To: Anders Hofseth &amp;lt;XXX@gmail.com&gt;
2411 &lt;br&gt;Cc: Eirik Solheim &amp;lt;XXX@gmail.com&gt;,
2412 &lt;br&gt; Jon Ståle Carlsen &amp;lt;XXX@gmail.com&gt;,
2413 &lt;br&gt; Henrik Lied &amp;lt;XXX@gmail.com&gt;
2414 &lt;br&gt;Subject: Re: [NRKbeta] Kommentar: &quot;Bakom Blindpassasjer: del 1&quot;
2415 &lt;br&gt;Date: Sat, 30 Oct 2010 08:24:34 +0200&lt;/p&gt;
2416
2417 &lt;p&gt;[Anders Hofseth]
2418 &lt;br&gt;&gt; Hei Petter.&lt;/p&gt;
2419
2420 &lt;p&gt;Hei.&lt;/p&gt;
2421
2422 &lt;p&gt;&gt; Det du forsøker dra igang er egentlig en interessant diskusjon, men
2423 &lt;br&gt;&gt; om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
2424 &lt;br&gt;&gt; å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
2425 &lt;br&gt;&gt; særlig lett å klarere ut noe annet arkivmateriale på lang tid.&lt;/p&gt;
2426
2427 &lt;p&gt;Godt å se at du er enig i at dette er en interessant diskusjon. Den
2428 vil nok fortsette en stund til. :)&lt;/p&gt;
2429
2430 &lt;p&gt;Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
2431 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
2432 fortsette å legge ut arkivmateriale.&lt;/p&gt;
2433
2434 &lt;p&gt;Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
2435 faktum, som er at streaming er det samme som nedlasting, og at innhold
2436 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
2437 det.&lt;/p&gt;
2438
2439 &lt;p&gt;Det du sier er jo at klarering av arkivmateriale for publisering på
2440 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
2441 Det er ikke et argument som holder vann. :)&lt;/p&gt;
2442
2443 &lt;p&gt;&gt; Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
2444 &lt;br&gt;&gt; og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
2445 &lt;br&gt;&gt; konsekvensene vi beskriver ikke er noe du ønsker heller...&lt;/p&gt;
2446
2447 &lt;p&gt;Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
2448 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
2449 mot de som vil låse kulturen inne. Jeg synes det er en skam at NRK
2450 godtar å forlede publikum. Ville heller at NRK krever at innhold som
2451 skal sendes skal være uten bruksbegresninger og kan publiseres i
2452 formater som heller ikke har bruksbegresninger (bruksbegresningene til
2453 H.264 burde få varselbjellene i NRK til å ringe).&lt;/p&gt;
2454
2455 &lt;p&gt;At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
2456 påstander om at &quot;streaming beskytter mot nedlasting&quot; som bare er egnet
2457 til å bygge opp om en myte som er skadelig for samfunnet som helhet.&lt;/p&gt;
2458
2459 &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
2460 titt på
2461 &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;.
2462 for å se hva slags bruksbegresninger H.264 innebærer.&lt;/p&gt;
2463
2464 &lt;p&gt;Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
2465 kan brukes før rettighetshaverene også innser at de er med på å skade
2466 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
2467 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
2468 langt på overtid.&lt;/p&gt;
2469
2470 &lt;p&gt;&gt; Ring meg om noe er uklart: XXX&lt;/p&gt;
2471
2472 &lt;p&gt;Intet uklart, men ikke imponert over måten dere håndterer debatten på.
2473 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
2474 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
2475 for videre diskusjon hadde dere i mine øyne kommet fra det med
2476 ryggraden på plass.&lt;/p&gt;
2477
2478 &lt;p&gt;PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.&lt;/p&gt;
2479
2480 &lt;p&gt;Som en liten avslutning, her er noen litt morsomme innslag om temaet.
2481 &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
2482 &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å
2483 NRK1. :)&lt;/p&gt;
2484
2485 &lt;p&gt;Vennlig hilsen,
2486 &lt;br&gt;--
2487 &lt;br&gt;Petter Reinholdtsen&lt;/p&gt;
2488 </description>
2489 </item>
2490
2491 <item>
2492 <title>Software updates 2010-10-24</title>
2493 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
2494 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
2495 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
2496 <description>&lt;p&gt;Some updates.&lt;/p&gt;
2497
2498 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
2499 raise money for the project is going well. The lower limit of 10
2500 signers was reached in 24 hours, and so far 13 people have signed it.
2501 More signers and more funding is most welcome, and I am really curious
2502 how far we can get before the time limit of December 24 is reached.
2503 :)&lt;/p&gt;
2504
2505 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
2506 about what appear to be a great code coverage tool capable of
2507 generating code coverage stats without any changes to the source code.
2508 It is called
2509 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
2510 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
2511 It is missing in Debian, but the git source built just fine in Squeeze
2512 after I installed libelf-dev, libdwarf-dev, pkg-config and
2513 libglib2.0-dev. Failed to build in Lenny, but suspect that is
2514 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
2515
2516 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
2517 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
2518 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
2519 alpha test release of the Squeeze based Debian Edu /
2520 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
2521 release. Give it a try if you need a complete linux solution for your
2522 school, including central infrastructure server, workstations, thin
2523 client servers and diskless workstations. A nice touch added
2524 yesterday is RDP support on the thin client servers, for windows
2525 clients to get a Linux desktop on request.&lt;/p&gt;
2526 </description>
2527 </item>
2528
2529 <item>
2530 <title>Pledge for funding to the Gnash project to get AVM2 support</title>
2531 <link>http://people.skolelinux.org/pere/blog/Pledge_for_funding_to_the_Gnash_project_to_get_AVM2_support.html</link>
2532 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Pledge_for_funding_to_the_Gnash_project_to_get_AVM2_support.html</guid>
2533 <pubDate>Tue, 19 Oct 2010 14:45:00 +0200</pubDate>
2534 <description>&lt;p&gt;&lt;a href=&quot;http://www.getgnash.org/&quot;&gt;The Gnash project&lt;/a&gt; is the
2535 most promising solution for a Free Software Flash implementation. It
2536 has done great so far, but there is still far to go, and recently its
2537 funding has dried up. I believe AVM2 support in Gnash is vital to the
2538 continued progress of the project, as more and more sites show up with
2539 AVM2 flash files.&lt;/p&gt;
2540
2541 &lt;p&gt;To try to get funding for developing such support, I have started
2542 &lt;a href=&quot;http://www.pledgebank.com/gnash-avm2&quot;&gt;a pledge&lt;/a&gt; with the
2543 following text:&lt;/P&gt;
2544
2545 &lt;p&gt;&lt;blockquote&gt;
2546
2547 &lt;p&gt;&quot;I will pay 100$ to the Gnash project to develop AVM2 support but
2548 only if 10 other people will do the same.&quot;&lt;/p&gt;
2549
2550 &lt;p&gt;- Petter Reinholdtsen, free software developer&lt;/p&gt;
2551
2552 &lt;p&gt;Deadline to sign up by: 24th December 2010&lt;/p&gt;
2553
2554 &lt;p&gt;The Gnash project need to get support for the new Flash file
2555 format AVM2 to work with a lot of sites using Flash on the
2556 web. Gnash already work with a lot of Flash sites using the old AVM1
2557 format, but more and more sites are using the AVM2 format these
2558 days. The project web page is available from
2559 http://www.getgnash.org/ . Gnash is a free software implementation
2560 of Adobe Flash, allowing those of us that do not accept the terms of
2561 the Adobe Flash license to get access to Flash sites.&lt;/p&gt;
2562
2563 &lt;p&gt;The project need funding to get developers to put aside enough
2564 time to develop the AVM2 support, and this pledge is my way to try
2565 to get this to happen.&lt;/p&gt;
2566
2567 &lt;p&gt;The project accept donations via the OpenMediaNow foundation,
2568 &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;
2569
2570 &lt;/blockquote&gt;&lt;/p&gt;
2571
2572 &lt;p&gt;I hope you will support this effort too. I hope more than 10
2573 people will participate to make this happen. The more money the
2574 project gets, the more features it can develop using these funds.
2575 :)&lt;/p&gt;
2576 </description>
2577 </item>
2578
2579 <item>
2580 <title>Terms of use for video produced by a Canon IXUS 130 digital camera</title>
2581 <link>http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html</link>
2582 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html</guid>
2583 <pubDate>Thu, 9 Sep 2010 23:55:00 +0200</pubDate>
2584 <description>&lt;p&gt;A few days ago I had the mixed pleasure of bying a new digital
2585 camera, a Canon IXUS 130. It was instructive and very disturbing to
2586 be able to verify that also this camera producer have the nerve to
2587 specify how I can or can not use the videos produced with the camera.
2588 Even thought I was aware of the issue, the options with new cameras
2589 are limited and I ended up bying the camera anyway. What is the
2590 problem, you might ask? It is software patents, MPEG-4, H.264 and the
2591 MPEG-LA that is the problem, and our right to record our experiences
2592 without asking for permissions that is at risk.
2593
2594 &lt;p&gt;On page 27 of the Danish instruction manual, this section is
2595 written:&lt;/p&gt;
2596
2597 &lt;blockquote&gt;
2598 &lt;p&gt;This product is licensed under AT&amp;T patents for the MPEG-4 standard
2599 and may be used for encoding MPEG-4 compliant video and/or decoding
2600 MPEG-4 compliant video that was encoded only (1) for a personal and
2601 non-commercial purpose or (2) by a video provider licensed under the
2602 AT&amp;T patents to provide MPEG-4 compliant video.&lt;/p&gt;
2603
2604 &lt;p&gt;No license is granted or implied for any other use for MPEG-4
2605 standard.&lt;/p&gt;
2606 &lt;/blockquote&gt;
2607
2608 &lt;p&gt;In short, the camera producer have chosen to use technology
2609 (MPEG-4/H.264) that is only provided if I used it for personal and
2610 non-commercial purposes, or ask for permission from the organisations
2611 holding the knowledge monopoly (patent) for technology used.&lt;/p&gt;
2612
2613 &lt;p&gt;This issue has been brewing for a while, and I recommend you to
2614 read
2615 &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
2616 Our Civilization&#39;s Video Art and Culture is Threatened by the
2617 MPEG-LA&lt;/a&gt;&quot; by Eugenia Loli-Queru and
2618 &quot;&lt;a href=&quot;http://webmink.com/2010/09/03/h-264-and-foss/&quot;&gt;H.264 Is Not
2619 The Sort Of Free That Matters&lt;/a&gt;&quot; by Simon Phipps to learn more about
2620 the issue. The solution is to support the
2621 &lt;a href=&quot;http://www.digistan.org/open-standard:definition&quot;&gt;free and
2622 open standards&lt;/a&gt; for video, like &lt;a href=&quot;http://www.theora.org/&quot;&gt;Ogg
2623 Theora&lt;/a&gt;, and avoid MPEG-4 and H.264 if you can.&lt;/p&gt;
2624 </description>
2625 </item>
2626
2627 <item>
2628 <title>Some notes on Flash in Debian and Debian Edu</title>
2629 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
2630 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
2631 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
2632 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
2633 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
2634 second most popular used package that is missing in Debian. The sixth
2635 most popular is flashplayer-mozilla. This is a clear indication that
2636 working flash is important for Debian users. Around 10 percent of the
2637 users submitting data to popcon.debian.org have this package
2638 installed.&lt;/p&gt;
2639
2640 &lt;p&gt;In the report written by Lars Risan in August 2008
2641&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
2642 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
2643 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
2644 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
2645 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
2646 web sites require Flash to work, and lacking working Flash support in
2647 the web browser and the problems with installing it was perceived as a
2648 good reason to stay with Windows.&lt;/p&gt;
2649
2650 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
2651 said to be the retarded cousin that did not really understand
2652 everything you told him but could work fairly well. This was a
2653 comment regarding the problems Linux have with proprietary formats and
2654 non-standard web pages, and is sad because it exposes a fairly common
2655 understanding of whose fault it is if web pages that only work in for
2656 example Internet Explorer 6 fail to work on Firefox, and funny because
2657 it explain very well how annoying it is for users when Linux
2658 distributions do not work with the documents they receive or the web
2659 pages they want to visit.&lt;/p&gt;
2660
2661 &lt;p&gt;This is part of the reason why I believe it is important for Debian
2662 and Debian Edu to have a well working Flash implementation in the
2663 distribution, to get at least popular sites as Youtube and Google
2664 Video to working out of the box. For Squeeze, Debian have the chance
2665 to include the latest version of Gnash that will make this happen, as
2666 the new release 0.8.8 was published a few weeks ago and is resting in
2667 unstable. The new version work with more sites that version 0.8.7.
2668 The Gnash maintainers have asked for a freeze exception, but the
2669 release team have not had time to reply to it yet. I hope they agree
2670 with me that Flash is important for the Debian desktop users, and thus
2671 accept the new package into Squeeze.&lt;/p&gt;
2672 </description>
2673 </item>
2674
2675 <item>
2676 <title>Regjerningens oppsummering av høringen om standardkatalogen versjon 2</title>
2677 <link>http://people.skolelinux.org/pere/blog/Regjerningens_oppsummering_av_h_ringen_om_standardkatalogen_versjon_2.html</link>
2678 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Regjerningens_oppsummering_av_h_ringen_om_standardkatalogen_versjon_2.html</guid>
2679 <pubDate>Thu, 9 Jul 2009 14:40:00 +0200</pubDate>
2680 <description>&lt;p&gt;For å forstå mer om hvorfor standardkatalogens versjon 2 ble som
2681 den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
2682 for regjeringen da de tok sin avgjørelse. De er nå lagt ut på NUUGs
2683 wiki, direkte tilgjengelig via &quot;&lt;a
2684 href=&quot;http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&amp;do=get&amp;target=kongelig-resolusjon.pdf&quot;&gt;Referansekatalogen
2685 v2.0 - Oppsummering av høring&lt;/a&gt;&quot; og &quot;&lt;a
2686 href=&quot;http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&amp;do=get&amp;target=kongelig-resolusjon-katalogutkast.pdf&quot;&gt;Referansekatalog
2687 for IT-standarder i offentlig sektor Versjon 2.0, dd.mm.åååå -
2688 UTKAST&lt;/a&gt;&quot;.&lt;/p&gt;
2689
2690 &lt;p&gt;Det er tre ting jeg merker meg i oppsummeringen fra
2691 høringsuttalelsen da jeg skummet igjennom den. Det første er at
2692 forståelsen av hvordan programvarepatenter påvirker fri
2693 programvareutvikling også i Norge når en argumenterer med at
2694 royalty-betaling ikke er et relevant problem i Norge. Det andre er at
2695 FAD ikke har en prinsipiell forståelse av verdien av en enkelt
2696 standard innenfor hvert område. Det siste er at påstander i
2697 høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
2698 Microsoft om hvordan Ogg blir standardisert og påstanden fra
2699 politidirektoratet om patentproblemer i Theora).&lt;/p&gt;
2700 </description>
2701 </item>
2702
2703 <item>
2704 <title>Regjerningen forlater prinsippet om ingen royalty-betaling i standardkatalogen versjon 2</title>
2705 <link>http://people.skolelinux.org/pere/blog/Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html</link>
2706 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html</guid>
2707 <pubDate>Mon, 6 Jul 2009 21:00:00 +0200</pubDate>
2708 <description>&lt;p&gt;Jeg ble glad da regjeringen
2709 &lt;a href=&quot;http://www.digi.no/817635/her-er-statens-nye-it-standarder&quot;&gt;annonserte&lt;/a&gt;
2710 versjon 2 av
2711 &lt;a href=&quot;http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf&quot;&gt;statens
2712 referansekatalog over standarder&lt;/a&gt;, men trist da jeg leste hva som
2713 faktisk var vedtatt etter
2714 &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;.
2715 De fleste av de valgte åpne standardene er gode og vil bidra til at
2716 alle kan delta på like vilkår i å lage løsninger for staten, men
2717 noen av dem blokkerer for de som ikke har anledning til å benytte
2718 spesifikasjoner som krever betaling for bruk (såkalt
2719 royalty-betaling). Det gjelder spesifikt for H.264 for video og MP3
2720 for lyd. Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
2721 Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
2722 fra statens websider gjøre dette uten å måtte bruke programmer der
2723 betaling for bruk var nødvendig. Når det nå er gjort valgfritt for
2724 de statlige etatene å bruke enten H.264 eller Theora (og MP3 eler
2725 Vorbis), så vil en bli tvunget til å forholde seg til
2726 royalty-belastede standarder for å få tilgang til videoen og
2727 lyden.&lt;/p&gt;
2728
2729 &lt;p&gt;Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
2730 at alle standarder som ble valgt til å være påkrevd i katalogen skulle
2731 være uten royalty-betaling. Jeg håper det ikke betyr at en har mistet
2732 all forståelse for hvilke prinsipper som må følges for å oppnå
2733 likeverdig konkurranse mellom aktørene i IT-bransjen. NUUG advarte
2734 mot dette i
2735 &lt;a href=&quot;http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2&quot;&gt;sin
2736 høringsuttalelse&lt;/a&gt;, men ser ut til å ha blitt ignorert.&lt;/p&gt;
2737
2738 &lt;p&gt;Oppdatering 2012-06-29: Kom over &lt;a href=&quot;http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf&quot;&gt;en
2739 rapport til FAD&lt;/a&gt; fra da versjon 1 av katalogen ble vedtatt, og der
2740 er det tydelig at problemstillingen var kjent og forstått.&lt;/p&gt;
2741 </description>
2742 </item>
2743
2744 <item>
2745 <title>Microsofts misvisende argumentasjon rundt multimediaformater</title>
2746 <link>http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html</link>
2747 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html</guid>
2748 <pubDate>Fri, 26 Jun 2009 13:30:00 +0200</pubDate>
2749 <description>&lt;p&gt;I
2750 &lt;a href=&quot;http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf&quot;&gt;Microsoft
2751 sin høringsuttalelse&lt;/a&gt; til
2752 &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
2753 til versjon 2 av statens referansekatalog over standarder&lt;/a&gt;, lirer
2754 de av seg følgende FUD-perle:&lt;/p&gt;
2755
2756 &lt;p&gt;&lt;blockquote&gt;&quot;Vorbis, OGG, Theora og FLAC er alle tekniske
2757 spesifikasjoner overordnet styrt av xiph.org, som er en
2758 ikke-kommersiell organisasjon. Etablerte og anerkjente
2759 standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
2760 innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
2761 Det er derimot helt opp til hver enkelt organisasjon å bestemme
2762 hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
2763 spesifikasjonene bør derfor ikke defineres som åpne
2764 standarder.&quot;&lt;/blockquote&gt;&lt;/p&gt;
2765
2766 &lt;p&gt;De vokter seg vel for å nevne den anerkjente
2767 standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
2768 IP og det meste av protokoller på Internet, og RFC-standardene som
2769 IETF står bak. Ogg er spesifisert i
2770 &lt;a href=&quot;http://ietf.org/rfc/rfc3533.txt&quot;&gt;RFC 3533&lt;/a&gt;, og er uten
2771 tvil å anse som en åpen standard. Vorbis er
2772 &lt;a href=&quot;http://ietf.org/rfc/rfc5215.txt&quot;&gt;RFC 5215&lt;/a&gt;. Theora er
2773
2774 under standardisering via IETF, med
2775 &lt;a href=&quot;http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt&quot;&gt;siste
2776 utkast publisert 2006-07-21&lt;/a&gt; (riktignok er dermed teksten ikke
2777 skrevet i stein ennå, men det blir neppe endringer som ikke er
2778 bakoverkompatibel). De kan være inne på noe når det gjelder FLAC da
2779 jeg ikke finner tegn til at &lt;a
2780 href=&quot;http://flac.sourceforge.net/format.html&quot;&gt;spesifikasjonen
2781 tilgjengelig på web&lt;/a&gt; er på tur via noen
2782 standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
2783 og Vorbis også har involvert seg i Flac siden 2003, så ser jeg ikke
2784 bort fra at også den organiseres via IETF. Jeg kjenner personlig lite
2785 til FLAC.&lt;/p&gt;
2786
2787 &lt;p&gt;Uredelig argumentasjon bør en holde seg for god til å komme med,
2788 spesielt når det er så enkelt i dagens Internet-hverdag å gå
2789 misvisende påstander etter i sømmene.&lt;/p&gt;
2790 </description>
2791 </item>
2792
2793 <item>
2794 <title>When web browser developers make a video player...</title>
2795 <link>http://people.skolelinux.org/pere/blog/When_web_browser_developers_make_a_video_player___.html</link>
2796 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/When_web_browser_developers_make_a_video_player___.html</guid>
2797 <pubDate>Sat, 17 Jan 2009 18:50:00 +0100</pubDate>
2798 <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;
2799 to publish video recordings of our monthly presentations, we provide a
2800 page with embedded video for easy access to the recording. Putting a
2801 good set of HTML tags together to get working embedded video in all
2802 browsers and across all operating systems is not easy. I hope this
2803 will become easier when the &amp;lt;video&amp;gt; tag is implemented in all
2804 browsers, but I am not sure. We provide the recordings in several
2805 formats, MPEG1, Ogg Theora, H.264 and Quicktime, and want the
2806 browser/media plugin to pick one it support and use it to play the
2807 recording, using whatever embed mechanism the browser understand.
2808 There is at least four different tags to use for this, the new HTML5
2809 &amp;lt;video&amp;gt; tag, the &amp;lt;object&amp;gt; tag, the &amp;lt;embed&amp;gt; tag and
2810 the &amp;lt;applet&amp;gt; tag. All of these take a lot of options, and
2811 finding the best options is a major challenge.&lt;/p&gt;
2812
2813 &lt;p&gt;I just tested the experimental Opera browser available from &lt;a
2814 href=&quot;http://labs.opera.com&quot;&gt;labs.opera.com&lt;/a&gt;, to see how it handled
2815 a &amp;lt;video&amp;gt; tag with a few video sources and no extra attributes.
2816 I was not very impressed. The browser start by fetching a picture
2817 from the video stream. Not sure if it is the first frame, but it is
2818 definitely very early in the recording. So far, so good. Next,
2819 instead of streaming the 76 MiB video file, it start to download all
2820 of it, but do not start to play the video. This mean I have to wait
2821 for several minutes for the downloading to finish. When the download
2822 is done, the playing of the video do not start! Waiting for the
2823 download, but I do not get to see the video? Some testing later, I
2824 discover that I have to add the controls=&quot;true&quot; attribute to be able
2825 to get a play button to pres to start the video. Adding
2826 autoplay=&quot;true&quot; did not help. I sure hope this is a misfeature of the
2827 test version of Opera, and that future implementations of the
2828 &amp;lt;video&amp;gt; tag will stream recordings by default, or at least start
2829 playing when the download is done.&lt;/p&gt;
2830
2831 &lt;p&gt;The test page I used (since changed to add more attributes) is
2832 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20090113-foredrag-om-foredrag/&quot;&gt;available
2833 from the nuug site&lt;/a&gt;. Will have to test it with the new Firefox
2834 too.&lt;/p&gt;
2835
2836 &lt;p&gt;In the test process, I discovered a missing feature. I was unable
2837 to find a way to get the URL of the playing video out of Opera, so I
2838 am not quite sure it picked the Ogg Theora version of the video. I
2839 sure hope it was using the announced Ogg Theora support. :)&lt;/p&gt;
2840 </description>
2841 </item>
2842
2843 <item>
2844 <title>The sorry state of multimedia browser plugins in Debian</title>
2845 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
2846 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
2847 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
2848 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
2849 plugins available in Debian Lenny, to see which one we should use by
2850 default in Debian Edu. We need an embedded video playing plugin with
2851 control buttons to pause or stop the video, and capable of streaming
2852 all the multimedia content available on the web. The test results and
2853 notes are available on
2854 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
2855 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
2856 fill this need. My personal video player favorite, VLC, has a really
2857 bad plugin which fail on a lot of the test pages. A lot of the MIME
2858 types I would expect to work with any free software player (like
2859 video/ogg), just do not work. And simple formats like the
2860 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
2861 totem and vlc plugins. I hope the situation will improve soon. No
2862 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
2863
2864 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
2865 be the only one fitting our needs. :/&lt;/p&gt;
2866 </description>
2867 </item>
2868
2869 </channel>
2870 </rss>