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