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