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