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