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