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