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