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 video
</title>
5 <description>Entries tagged video
</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>Software video mixer on a USB stick
</title>
11 <link>http://people.skolelinux.org/pere/blog/Software_video_mixer_on_a_USB_stick.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_video_mixer_on_a_USB_stick.html
</guid>
13 <pubDate>Sun,
28 Dec
2008 15:
40:
00 +
0100</pubDate>
14 <description><p
>The
<a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> is
15 recording our montly presentation on video, and recently we have
16 worked on improving the quality of the recordings by mixing the slides
17 directly with the video stream. For this, we use the
18 <a href=
"http://dvswitch.alioth.debian.org/
">dvswitch
</a
> package from
19 the Debian video team. As this require quite one computer per video
20 source, and NUUG do not have enough laptops available, we need to
21 borrow laptops. And to avoid having to install extra software on
22 these borrwed laptops, I have wrapped up all the programs needed on a
23 bootable USB stick. The software required is dvswitch with assosiated
24 source, sink and mixer applications and
25 <a href=
"http://www.kinodv.org/
">dvgrab
</a
>. To allow this setup to
26 work without any configuration, I
've patched dvswitch to use
27 <a href=
"http://www.avahi.org/
">avahi
</a
> to connect the various parts
28 together. And to allow us to use laptops without firewire plugs, I
29 upgraded dvgrab to the one from Debian/unstable to get one that work
30 with USB sources. We have not yet tested this setup in a production
31 setup, but I hope it will work properly, and allow us to set up a
32 video mixer in a very short time frame. We will need it for
33 <a href=
"http://www.goopen.no/
">Go Open
2009</a
>.
</p
>
35 <p
><a href=
"http://www.nuug.no/pub/video/bin/usbstick-dvswitch.img.gz
">The
36 USB image
</a
> is for a
1 GB memory stick, but can be used on any
37 larger stick as well.
</p
>
42 <title>When web browser developers make a video player...
</title>
43 <link>http://people.skolelinux.org/pere/blog/When_web_browser_developers_make_a_video_player___.html
</link>
44 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/When_web_browser_developers_make_a_video_player___.html
</guid>
45 <pubDate>Sat,
17 Jan
2009 18:
50:
00 +
0100</pubDate>
46 <description><p
>As part of the work we do in
<a href=
"http://www.nuug.no
">NUUG
</a
>
47 to publish video recordings of our monthly presentations, we provide a
48 page with embedded video for easy access to the recording. Putting a
49 good set of HTML tags together to get working embedded video in all
50 browsers and across all operating systems is not easy. I hope this
51 will become easier when the
&lt;video
&gt; tag is implemented in all
52 browsers, but I am not sure. We provide the recordings in several
53 formats, MPEG1, Ogg Theora, H
.264 and Quicktime, and want the
54 browser/media plugin to pick one it support and use it to play the
55 recording, using whatever embed mechanism the browser understand.
56 There is at least four different tags to use for this, the new HTML5
57 &lt;video
&gt; tag, the
&lt;object
&gt; tag, the
&lt;embed
&gt; tag and
58 the
&lt;applet
&gt; tag. All of these take a lot of options, and
59 finding the best options is a major challenge.
</p
>
61 <p
>I just tested the experimental Opera browser available from
<a
62 href=
"http://labs.opera.com
">labs.opera.com
</a
>, to see how it handled
63 a
&lt;video
&gt; tag with a few video sources and no extra attributes.
64 I was not very impressed. The browser start by fetching a picture
65 from the video stream. Not sure if it is the first frame, but it is
66 definitely very early in the recording. So far, so good. Next,
67 instead of streaming the
76 MiB video file, it start to download all
68 of it, but do not start to play the video. This mean I have to wait
69 for several minutes for the downloading to finish. When the download
70 is done, the playing of the video do not start! Waiting for the
71 download, but I do not get to see the video? Some testing later, I
72 discover that I have to add the controls=
"true
" attribute to be able
73 to get a play button to pres to start the video. Adding
74 autoplay=
"true
" did not help. I sure hope this is a misfeature of the
75 test version of Opera, and that future implementations of the
76 &lt;video
&gt; tag will stream recordings by default, or at least start
77 playing when the download is done.
</p
>
79 <p
>The test page I used (since changed to add more attributes) is
80 <a href=
"http://www.nuug.no/aktiviteter/
20090113-foredrag-om-foredrag/
">available
81 from the nuug site
</a
>. Will have to test it with the new Firefox
84 <p
>In the test process, I discovered a missing feature. I was unable
85 to find a way to get the URL of the playing video out of Opera, so I
86 am not quite sure it picked the Ogg Theora version of the video. I
87 sure hope it was using the announced Ogg Theora support. :)
</p
>
92 <title>Første vellykkede videostrøm fra NUUG
</title>
93 <link>http://people.skolelinux.org/pere/blog/F_rste_vellykkede_videostr_m_fra_NUUG.html
</link>
94 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/F_rste_vellykkede_videostr_m_fra_NUUG.html
</guid>
95 <pubDate>Wed,
11 Feb
2009 06:
30:
00 +
0100</pubDate>
96 <description><p
>Jeg ble glad for å se under
97 <a href=
"http://www.nuug.no/aktiviteter/
20090210-compiz/
">gårdagens
98 medlemsmøte
</a
> i NUUG Oslo at utsending av live-video fra møtet
99 fungerte for første gang. Forrige gang ble det ved en teknisk tabbe
100 sendt video uten lyd. Vi kan takke Ole Kristian Lien og resten av
101 videogruppen i NUUG for at nå NUUG-medlemmer over det ganske land
102 kunne se foredraget samtidig med oss i Oslo. Vi opplevde til og med
103 under møtet å motta spørsmål via IRC som ble besvart der og da.
104 Opptaket publiseres så snart det er kopiert over til NUUGs
105 webserver og komprimert.
</p
>
110 <title>Lisensvalg for NUUG-opptakene endelig på plass
</title>
111 <link>http://people.skolelinux.org/pere/blog/Lisensvalg_for_NUUG_opptakene_endelig_p__plass.html
</link>
112 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lisensvalg_for_NUUG_opptakene_endelig_p__plass.html
</guid>
113 <pubDate>Fri,
6 Mar
2009 21:
20:
00 +
0100</pubDate>
114 <description><p
>Etter mange års meditasjon over temaet, har NUUG endelig klart å
115 bestemme seg for hvilken lisens vi skal bruke på videoopptakene som
116 gjøres av NUUGs videogruppe. Ole Kristian har annonsert at lisensen
117 blir
<a href=
"http://creativecommons.org/licenses/by-sa/
3.0/no/
">Creative
118 Commons Navngivelse-Del på samme vilkår
3.0 Norge
</a
>. Jeg er veldig
119 glad for at denne saken endelig er landet. Lisensen for opptaket til
120 Stallman-foredraget ble en annen pga. at lisensvalget ikke var avklart
121 på forhånd og IFI og PING ønsket CC-BY-ND, og må ses på som et unntak
122 i denne sammenhengen.
</p
>
127 <title>Frikanalen og jul i studentrådet
</title>
128 <link>http://people.skolelinux.org/pere/blog/Frikanalen_og_jul_i_studentr_det.html
</link>
129 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Frikanalen_og_jul_i_studentr_det.html
</guid>
130 <pubDate>Wed,
11 Mar
2009 23:
40:
00 +
0100</pubDate>
131 <description><p
>I går
132 <a href=
"http://lists.nuug.no/pipermail/interesserte/
2009-March/
000387.html
">lanserte
</a
>
134 <a href=
"http://www.frikanalen.no
">Frikanalen
</a
> med
135 <a href=
"http://www.nuug.no/pub/video/frikanalen/frontpage.cgi
">åpne
136 standarder
</a
>, og resultatet av noen intense uker med arbeide kunne
137 endelig presenteres. Jeg har tro på åpen kanalkonseptet som
138 Frikanalen er et eksempel på, der borgerne får anledning til å
139 kringkaste sitt syn på en åpen og demokratisk måte. Jeg er veldig
140 glad vi har fått gjort kanalen tilgjengelig i Ogg Theora, slik at alle
141 kan få tilgang til opptakene på web, og slipper å måtte installere MS
142 Silverlight for å spille av opptakene.
</p
>
144 <p
>Frikanalen har en brokete historie, og dagens inkarnasjon er ikke
145 helt slik foreningen Åpen kanal planla det for mange år siden, noe som
146 er bakgrunnen for at det fredag
13. mars
2009 kl
09:
00 starter en
147 rettsak i Oslo tingrett der Kringkasterforeningen (tidligere
148 foreningen Åpen kanal) har saksøkt kulturdepartementet over
149 konsesjonsvilkårene til Frikanalen. Jeg er spent på resultatet.
</p
>
151 <p
>I arbeidet med Frikanalen med åpne standarder, så har vi hatt glede
152 av å se en rekke av innslagene som er tilgjengelig. Her er mye
153 religiøst sludder, fra
154 <a href=
"http://www.nuug.no/pub/video/frikanalen/fetchvideo.cgi?videoId=
720">vandring
155 i jerusalem
</a
> via
156 <a href=
"http://www.nuug.no/pub/video/frikanalen/fetchvideo.cgi?videoId=
779">religiøst
157 vinklede nyheter
</a
> til
159 href=
"http://www.nuug.no/pub/video/frikanalen/fetchvideo.cgi?videoId=
2077">kreasjonisk
160 retorikk
</a
>, men også fine
161 <a href=
"http://www.nuug.no/pub/video/frikanalen/fetchvideo.cgi?videoId=
407">dokumentarer
162 om redningsselskapet
</a
> og
163 <a href=
"http://www.nuug.no/pub/video/frikanalen/fetchvideo.cgi?videoId=
2204">interessante
164 tegneserieanmeldelser
</a
>. Det jeg derimot har hatt størst glede av,
167 <a href=
"http://www.nuug.no/pub/video/frikanalen/fetchvideo.cgi?videoId=
1556">jul
168 i studentrådet
</a
>, der hver episode var en fest å se på. Jeg håper
169 NUUG lykkes med å få ut sine opptak med like stor suksess.
</p
>
174 <title>Recording video from cron using VLC
</title>
175 <link>http://people.skolelinux.org/pere/blog/Recording_video_from_cron_using_VLC.html
</link>
176 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recording_video_from_cron_using_VLC.html
</guid>
177 <pubDate>Sun,
5 Apr
2009 10:
00:
00 +
0200</pubDate>
178 <description><p
>One think I have wanted to figure out for a along time is how to
179 run vlc from cron to do recording of video streams on the net. The
180 task is trivial with mplayer, but I do not really trust the security
181 of mplayer (it crashes too often on strange input), and thus prefer
182 vlc. I finally found a way to do it today. I spent an hour or so
183 searching the web for recipes and reading the documentation. The
184 hardest part was to get rid of the GUI window, but after finding the
185 dummy interface, the command line finally presented itself:
</p
>
187 <blockquote
><pre
>URL=http://www.ping.uio.no/video/rms-oslo_2009.ogg
189 DISPLAY= vlc -q $URL \
190 --sout=
"#duplicate{dst=std{access=file,url=
'$SAVEFILE
'},dst=nodisplay}
" \
191 --intf=dummy
</pre
></blockquote
>
193 <p
>The command stream the URL and store it in the SAVEFILE by
194 duplicating the output stream to
"nodisplay
" and the file, using the
195 dummy interface. The dummy interface and the nodisplay output make
196 sure no X interface is needed.
</p
>
198 <p
>The cron job then need to start this job with the appropriate URL
199 and file name to save, sleep for the duration wanted, and then kill
200 the vlc process with SIGTERM. Here is a complete script
201 <tt
>vlc-record
</tt
> to use from
<tt
>at
</tt
> or
<tt
>cron
</tt
>:
</p
>
203 <blockquote
><pre
>#!/bin/sh
206 SAVEFILE=
"$
2"
207 DURATION=
"$
3"
208 DISPLAY= vlc -q
"$URL
" \
209 --sout=
"#duplicate{dst=std{access=file,url=
'$SAVEFILE
'},dst=nodisplay}
" \
210 --intf=dummy
< /dev/null
> /dev/null
2>&1 &
214 wait $pid
</pre
></blockquote
>
219 <title>Microsofts misvisende argumentasjon rundt multimediaformater
</title>
220 <link>http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html
</link>
221 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html
</guid>
222 <pubDate>Fri,
26 Jun
2009 13:
30:
00 +
0200</pubDate>
223 <description><p
>I
224 <a href=
"http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf
">Microsoft
225 sin høringsuttalelse
</a
> til
226 <a href=
"http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/
2009/horing---referansekatalog-versjon-
2.html?id=
549422">forslag
227 til versjon
2 av statens referansekatalog over standarder
</a
>, lirer
228 de av seg følgende FUD-perle:
</p
>
230 <p
><blockquote
>"Vorbis, OGG, Theora og FLAC er alle tekniske
231 spesifikasjoner overordnet styrt av xiph.org, som er en
232 ikke-kommersiell organisasjon. Etablerte og anerkjente
233 standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
234 innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
235 Det er derimot helt opp til hver enkelt organisasjon å bestemme
236 hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
237 spesifikasjonene bør derfor ikke defineres som åpne
238 standarder.
"</blockquote
></p
>
240 <p
>De vokter seg vel for å nevne den anerkjente
241 standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
242 IP og det meste av protokoller på Internet, og RFC-standardene som
243 IETF står bak. Ogg er spesifisert i
244 <a href=
"http://ietf.org/rfc/rfc3533.txt
">RFC
3533</a
>, og er uten
245 tvil å anse som en åpen standard. Vorbis er
246 <a href=
"http://ietf.org/rfc/rfc5215.txt
">RFC
5215</a
>. Theora er
248 under standardisering via IETF, med
249 <a href=
"http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-
00.txt
">siste
250 utkast publisert
2006-
07-
21</a
> (riktignok er dermed teksten ikke
251 skrevet i stein ennå, men det blir neppe endringer som ikke er
252 bakoverkompatibel). De kan være inne på noe når det gjelder FLAC da
253 jeg ikke finner tegn til at
<a
254 href=
"http://flac.sourceforge.net/format.html
">spesifikasjonen
255 tilgjengelig på web
</a
> er på tur via noen
256 standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
257 og Vorbis også har involvert seg i Flac siden
2003, så ser jeg ikke
258 bort fra at også den organiseres via IETF. Jeg kjenner personlig lite
261 <p
>Uredelig argumentasjon bør en holde seg for god til å komme med,
262 spesielt når det er så enkelt i dagens Internet-hverdag å gå
263 misvisende påstander etter i sømmene.
</p
>
268 <title>Regjerningen forlater prinsippet om ingen royalty-betaling i standardkatalogen versjon
2</title>
269 <link>http://people.skolelinux.org/pere/blog/Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html
</link>
270 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html
</guid>
271 <pubDate>Mon,
6 Jul
2009 21:
00:
00 +
0200</pubDate>
272 <description><p
>Jeg ble glad da regjeringen
273 <a href=
"http://www.digi.no/
817635/her-er-statens-nye-it-standarder
">annonserte
</a
>
275 <a href=
"http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf
">statens
276 referansekatalog over standarder
</a
>, men trist da jeg leste hva som
277 faktisk var vedtatt etter
278 <a href=
"http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/
2009/horing---referansekatalog-versjon-
2.html
">høringen
</a
>.
279 De fleste av de valgte åpne standardene er gode og vil bidra til at
280 alle kan delta på like vilkår i å lage løsninger for staten, men
281 noen av dem blokkerer for de som ikke har anledning til å benytte
282 spesifikasjoner som krever betaling for bruk (såkalt
283 royalty-betaling). Det gjelder spesifikt for H
.264 for video og MP3
284 for lyd. Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
285 Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
286 fra statens websider gjøre dette uten å måtte bruke programmer der
287 betaling for bruk var nødvendig. Når det nå er gjort valgfritt for
288 de statlige etatene å bruke enten H
.264 eller Theora (og MP3 eler
289 Vorbis), så vil en bli tvunget til å forholde seg til
290 royalty-belastede standarder for å få tilgang til videoen og
293 <p
>Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
294 at alle standarder som ble valgt til å være påkrevd i katalogen skulle
295 være uten royalty-betaling. Jeg håper det ikke betyr at en har mistet
296 all forståelse for hvilke prinsipper som må følges for å oppnå
297 likeverdig konkurranse mellom aktørene i IT-bransjen. NUUG advarte
299 <a href=
"http://wiki.nuug.no/uttalelser/
200901-standardkatalog-v2
">sin
300 høringsuttalelse
</a
>, men ser ut til å ha blitt ignorert.
</p
>
305 <title>Regjerningens oppsummering av høringen om standardkatalogen versjon
2</title>
306 <link>http://people.skolelinux.org/pere/blog/Regjerningens_oppsummering_av_h_ringen_om_standardkatalogen_versjon_2.html
</link>
307 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Regjerningens_oppsummering_av_h_ringen_om_standardkatalogen_versjon_2.html
</guid>
308 <pubDate>Thu,
9 Jul
2009 14:
40:
00 +
0200</pubDate>
309 <description><p
>For å forstå mer om hvorfor standardkatalogens versjon
2 ble som
310 den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
311 for regjeringen da de tok sin avgjørelse. De er nå lagt ut på NUUGs
312 wiki, direkte tilgjengelig via
"<a
313 href=
"http://wiki.nuug.no/uttalelser/
200901-standardkatalog-v2?action=AttachFile
&do=get
&target=kongelig-resolusjon.pdf
">Referansekatalogen
314 v2.0 - Oppsummering av høring
</a
>" og
"<a
315 href=
"http://wiki.nuug.no/uttalelser/
200901-standardkatalog-v2?action=AttachFile
&do=get
&target=kongelig-resolusjon-katalogutkast.pdf
">Referansekatalog
316 for IT-standarder i offentlig sektor Versjon
2.0, dd.mm.åååå -
317 UTKAST
</a
>".
</p
>
319 <p
>Det er tre ting jeg merker meg i oppsummeringen fra
320 høringsuttalelsen da jeg skummet igjennom den. Det første er at
321 forståelsen av hvordan programvarepatenter påvirker fri
322 programvareutvikling også i Norge når en argumenterer med at
323 royalty-betaling ikke er et relevant problem i Norge. Det andre er at
324 FAD ikke har en prinsipiell forståelse av verdien av en enkelt
325 standard innenfor hvert område. Det siste er at påstander i
326 høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
327 Microsoft om hvordan Ogg blir standardisert og påstanden fra
328 politidirektoratet om patentproblemer i Theora).
</p
>
333 <title>Første NUUG-fordrag sendt på TV
</title>
334 <link>http://people.skolelinux.org/pere/blog/F_rste_NUUG_fordrag_sendt_p__TV.html
</link>
335 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/F_rste_NUUG_fordrag_sendt_p__TV.html
</guid>
336 <pubDate>Tue,
8 Dec
2009 12:
00:
00 +
0100</pubDate>
337 <description><p
>Endelig har NUUG klart å få kringkastet ut et av sine fordrag på
339 <a href=
"http://www.nuug.no/aktiviteter/
20090512-bifrost/
">utskriftsløsningen
340 Biforst
</a
> var først ute, pga. at det var det nyeste foredraget som
341 var holdt på norsk, og dermed slapp vi å finne ut av hvordan
342 teksting av video skulle gjøres.
</p
>
344 <p
>NUUG har vært involvert i
345 <a href=
"http://www.frikanalen.no/
">Frikanalen
</a
> en stund nå, for å
346 forsøke å få ut budskapet vårt også på TV, og dette første foredraget
347 er en sped start på det vi har planlagt.
</p
>
349 <p
>NUUGs første foredrag sendes ut via frikanelen på digitalt
350 bakkenett, og alle abonnenter av riks-TV skal dermed ha mulighet til å
351 ta inn sendingen. Slå på TVen
5/
12 16:
05 (for sent),
12/
12 14:
00,
352 19/
12 16:
00,
24/
12 15:
37 eller
26/
12 16:
11 i år, så skal du få se
353 meg, Tollef og alle andre de som deltok på møtet på TV.
<p
>
358 <title>Some notes on Flash in Debian and Debian Edu
</title>
359 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
360 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
361 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
362 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
363 popularity-contest numbers
</a
>, the adobe-flashplugin package the
364 second most popular used package that is missing in Debian. The sixth
365 most popular is flashplayer-mozilla. This is a clear indication that
366 working flash is important for Debian users. Around
10 percent of the
367 users submitting data to popcon.debian.org have this package
370 <p
>In the report written by Lars Risan in August
2008
371 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
372 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
373 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
374 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
375 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
376 web sites require Flash to work, and lacking working Flash support in
377 the web browser and the problems with installing it was perceived as a
378 good reason to stay with Windows.
</p
>
380 <p
>I once saw a funny and sad comment in a web forum, where Linux was
381 said to be the retarded cousin that did not really understand
382 everything you told him but could work fairly well. This was a
383 comment regarding the problems Linux have with proprietary formats and
384 non-standard web pages, and is sad because it exposes a fairly common
385 understanding of whose fault it is if web pages that only work in for
386 example Internet Explorer
6 fail to work on Firefox, and funny because
387 it explain very well how annoying it is for users when Linux
388 distributions do not work with the documents they receive or the web
389 pages they want to visit.
</p
>
391 <p
>This is part of the reason why I believe it is important for Debian
392 and Debian Edu to have a well working Flash implementation in the
393 distribution, to get at least popular sites as Youtube and Google
394 Video to working out of the box. For Squeeze, Debian have the chance
395 to include the latest version of Gnash that will make this happen, as
396 the new release
0.8.8 was published a few weeks ago and is resting in
397 unstable. The new version work with more sites that version
0.8.7.
398 The Gnash maintainers have asked for a freeze exception, but the
399 release team have not had time to reply to it yet. I hope they agree
400 with me that Flash is important for the Debian desktop users, and thus
401 accept the new package into Squeeze.
</p
>
406 <title>Terms of use for video produced by a Canon IXUS
130 digital camera
</title>
407 <link>http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html
</link>
408 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html
</guid>
409 <pubDate>Thu,
9 Sep
2010 23:
55:
00 +
0200</pubDate>
410 <description><p
>A few days ago I had the mixed pleasure of bying a new digital
411 camera, a Canon IXUS
130. It was instructive and very disturbing to
412 be able to verify that also this camera producer have the nerve to
413 specify how I can or can not use the videos produced with the camera.
414 Even thought I was aware of the issue, the options with new cameras
415 are limited and I ended up bying the camera anyway. What is the
416 problem, you might ask? It is software patents, MPEG-
4, H
.264 and the
417 MPEG-LA that is the problem, and our right to record our experiences
418 without asking for permissions that is at risk.
420 <p
>On page
27 of the Danish instruction manual, this section is
424 <p
>This product is licensed under AT
&T patents for the MPEG-
4 standard
425 and may be used for encoding MPEG-
4 compliant video and/or decoding
426 MPEG-
4 compliant video that was encoded only (
1) for a personal and
427 non-commercial purpose or (
2) by a video provider licensed under the
428 AT
&T patents to provide MPEG-
4 compliant video.
</p
>
430 <p
>No license is granted or implied for any other use for MPEG-
4
434 <p
>In short, the camera producer have chosen to use technology
435 (MPEG-
4/H
.264) that is only provided if I used it for personal and
436 non-commercial purposes, or ask for permission from the organisations
437 holding the knowledge monopoly (patent) for technology used.
</p
>
439 <p
>This issue has been brewing for a while, and I recommend you to
441 "<a href=
"http://www.osnews.com/story/
23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA
">Why
442 Our Civilization
's Video Art and Culture is Threatened by the
443 MPEG-LA
</a
>" by Eugenia Loli-Queru and
444 "<a href=
"http://webmink.com/
2010/
09/
03/h-
264-and-foss/
">H
.264 Is Not
445 The Sort Of Free That Matters
</a
>" by Simon Phipps to learn more about
446 the issue. The solution is to support the
447 <a href=
"http://www.digistan.org/open-standard:definition
">free and
448 open standards
</a
> for video, like
<a href=
"http://www.theora.org/
">Ogg
449 Theora
</a
>, and avoid MPEG-
4 and H
.264 if you can.
</p
>
454 <title>TED talks på norsk og NUUG-foredrag - frivillige trengs til teksting
</title>
455 <link>http://people.skolelinux.org/pere/blog/TED_talks_p__norsk_og_NUUG_foredrag___frivillige_trengs_til_teksting.html
</link>
456 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/TED_talks_p__norsk_og_NUUG_foredrag___frivillige_trengs_til_teksting.html
</guid>
457 <pubDate>Fri,
1 Oct
2010 11:
00:
00 +
0200</pubDate>
458 <description><p
>Frikanalen og NUUG jobber for å få
<a href=
"http://www.ted.com
">TED
459 talks
</a
> kringkastet på
460 <a href=
"http://www.frikanalen.no/
">Frikanalen
</a
>, for å gi et mer
461 variert innhold på kanalen som i dag sendes på RiksTV, Lyse og
462 Uninett. Før innslagene kan sendes må det lages norske undertekster,
463 og dette her trengs det frivillige. Det er hundrevis av innslag, men
465 <a href=
"http://www.ted.com/talks/james_randi.html
">James Randi
</a
> og
466 <a href=
"http://www.ted.com/talks/lang/eng/michael_specter_the_danger_of_science_denial.html
">Michael
467 Specter
</a
>. Hvis du har litt tid til overs, bli med på å oversette
468 TED-foredragene til norsk og få på plass undertekster. TED har
469 allerede opplegg på plass for å håndtere oversettelser og
470 undertekster. Registrer deg på
471 <a href=
"http://www.ted.com/translate/forted
">sidene til TED
</a
> i
474 <p
>NUUG holder også på å få alle opptakene fra NUUG-presentasjonene
475 <a href=
"http://www.nuug.no/pub/video/frikanalen/frontpage.cgi?organization=NUUG
">publisert
476 på Frikanalen
</a
>. Foredrag på engelsk må også her tekstes og
477 oversettes. Ta kontakt med video@nuug.no hvis du vil bidra med
478 teksting og oversetting. Arbeidet koordineres på epostlisten og på
479 IRC (#nuug-video på irc.oftc.org), og
<a
480 href=
"http://wiki.nuug.no/grupper/video/frikanalen
">en wikiside
</a
>
481 brukes som notatblokk for arbeidet. Mest lovende verktøy for dette
482 ser i dag ut til å være
483 <a href=
"http://universalsubtitles.org/
">Universal Subtitles
</a
>, som
484 lar en bidra med teksting via en nettleser.
</p
>
489 <title>Pledge for funding to the Gnash project to get AVM2 support
</title>
490 <link>http://people.skolelinux.org/pere/blog/Pledge_for_funding_to_the_Gnash_project_to_get_AVM2_support.html
</link>
491 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Pledge_for_funding_to_the_Gnash_project_to_get_AVM2_support.html
</guid>
492 <pubDate>Tue,
19 Oct
2010 14:
45:
00 +
0200</pubDate>
493 <description><p
><a href=
"http://www.getgnash.org/
">The Gnash project
</a
> is the
494 most promising solution for a Free Software Flash implementation. It
495 has done great so far, but there is still far to go, and recently its
496 funding has dried up. I believe AVM2 support in Gnash is vital to the
497 continued progress of the project, as more and more sites show up with
498 AVM2 flash files.
</p
>
500 <p
>To try to get funding for developing such support, I have started
501 <a href=
"http://www.pledgebank.com/gnash-avm2
">a pledge
</a
> with the
502 following text:
</P
>
504 <p
><blockquote
>
506 <p
>"I will pay
100$ to the Gnash project to develop AVM2 support but
507 only if
10 other people will do the same.
"</p
>
509 <p
>- Petter Reinholdtsen, free software developer
</p
>
511 <p
>Deadline to sign up by:
24th December
2010</p
>
513 <p
>The Gnash project need to get support for the new Flash file
514 format AVM2 to work with a lot of sites using Flash on the
515 web. Gnash already work with a lot of Flash sites using the old AVM1
516 format, but more and more sites are using the AVM2 format these
517 days. The project web page is available from
518 http://www.getgnash.org/ . Gnash is a free software implementation
519 of Adobe Flash, allowing those of us that do not accept the terms of
520 the Adobe Flash license to get access to Flash sites.
</p
>
522 <p
>The project need funding to get developers to put aside enough
523 time to develop the AVM2 support, and this pledge is my way to try
524 to get this to happen.
</p
>
526 <p
>The project accept donations via the OpenMediaNow foundation,
527 <a href=
"http://www.openmedianow.org/?q=node/
32">http://www.openmedianow.org/?q=node/
32</a
> .
</p
>
529 </blockquote
></p
>
531 <p
>I hope you will support this effort too. I hope more than
10
532 people will participate to make this happen. The more money the
533 project gets, the more features it can develop using these funds.
539 <title>Best å ikke fortelle noen at streaming er nedlasting...
</title>
540 <link>http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html
</link>
541 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html
</guid>
542 <pubDate>Sat,
30 Oct
2010 11:
20:
00 +
0200</pubDate>
543 <description><p
>I dag la jeg inn en kommentar på en sak hos NRKBeta
544 <a href=
"http://nrkbeta.no/
2010/
10/
27/bakom-blindpassasjer-del-
1/
">om
545 hvordan TV-serien Blindpassasjer ble laget
</a
> i forbindelse med at
546 filmene NRK la ut ikke var tilgjengelig i et
547 <a href=
"http://www.digistan.org/open-standard:definition
">fritt og
548 åpent format
</a
>. Dette var det jeg skrev publiserte der
07:
39.
</p
>
550 <p
><blockquote
>
551 <p
>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
552 nedlasting. Mange av oss som kan mer enn gjennomsnittet om systemer
553 som dette, vet at det stort sett er mulig å lure ut ting med den
554 nødvendige forkunnskapen.
"</p
>
556 <p
>Haha. Å streame innhold er det samme som å laste ned innhold, så å
557 beskytte en stream mot nedlasting er ikke mulig. Å skrive noe slikt
558 er å forlede leseren.
</p
>
560 <p
>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
561 vil tillate streaming men ikke nedlasting meningsløs.
</p
>
563 <p
>Anbefaler forresten å lese
564 <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
>
565 om hva som ville være konsekvensen hvis digitale avspillingssperrer
566 (DRM) fungerte. Det gjør de naturligvis ikke teknisk - det er jo
567 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
568 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
570 </blockquote
></p
>
572 <p
>Ca.
20 minutter senere får jeg følgende epost fra Anders Hofseth i
575 <p
><blockquote
>
576 <p
>From: Anders Hofseth
&lt;XXX@gmail.com
>
577 <br
>To:
"pere@hungry.com
" &lt;pere@hungry.com
>
578 <br
>Cc: Eirik Solheim
&lt;XXX@gmail.com
>, Jon Ståle Carlsen
&lt;XXX@gmail.com
>, Henrik Lied
&lt;XXX@gmail.com
>
579 <br
>Subject: Re: [NRKbeta] Kommentar:
"Bakom Blindpassasjer: del
1"
580 <br
>Date: Sat,
30 Oct
2010 07:
58:
44 +
0200</p
>
583 <br
>Det du forsøker dra igang er egentlig en interessant diskusjon,
584 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
585 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
586 særlig lett å klarere ut noe annet arkivmateriale på lang tid.
</p
>
588 <p
>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
589 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
590 konsekvensene vi beskriver ikke er noe du ønsker heller...
</p
>
593 <br
>-anders
</p
>
595 <p
>Ring meg om noe er uklart:
95XXXXXXX
</p
>
596 </blockquote
></p
>
598 <p
>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
599 over følgende svar. I og med at debatten er fjernet fra NRK Betas
600 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
601 Har fjernet epostadresser og telefonnummer til de involverte, for å
602 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.
</p
>
604 <p
><blockquote
>
605 <p
>From: Petter Reinholdtsen
&lt;pere@hungry.com
>
606 <br
>To: Anders Hofseth
&lt;XXX@gmail.com
>
607 <br
>Cc: Eirik Solheim
&lt;XXX@gmail.com
>,
608 <br
> Jon Ståle Carlsen
&lt;XXX@gmail.com
>,
609 <br
> Henrik Lied
&lt;XXX@gmail.com
>
610 <br
>Subject: Re: [NRKbeta] Kommentar:
"Bakom Blindpassasjer: del
1"
611 <br
>Date: Sat,
30 Oct
2010 08:
24:
34 +
0200</p
>
613 <p
>[Anders Hofseth]
614 <br
>> Hei Petter.
</p
>
616 <p
>Hei.
</p
>
618 <p
>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
619 <br
>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
620 <br
>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
621 <br
>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.
</p
>
623 <p
>Godt å se at du er enig i at dette er en interessant diskusjon. Den
624 vil nok fortsette en stund til. :)
</p
>
626 <p
>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
627 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
628 fortsette å legge ut arkivmateriale.
</p
>
630 <p
>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
631 faktum, som er at streaming er det samme som nedlasting, og at innhold
632 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
635 <p
>Det du sier er jo at klarering av arkivmateriale for publisering på
636 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
637 Det er ikke et argument som holder vann. :)
</p
>
639 <p
>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
640 <br
>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
641 <br
>> konsekvensene vi beskriver ikke er noe du ønsker heller...
</p
>
643 <p
>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
644 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
645 mot de som vil låse kulturen inne. Jeg synes det er en skam at NRK
646 godtar å forlede publikum. Ville heller at NRK krever at innhold som
647 skal sendes skal være uten bruksbegresninger og kan publiseres i
648 formater som heller ikke har bruksbegresninger (bruksbegresningene til
649 H
.264 burde få varselbjellene i NRK til å ringe).
</p
>
651 <p
>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
652 påstander om at
"streaming beskytter mot nedlasting
" som bare er egnet
653 til å bygge opp om en myte som er skadelig for samfunnet som helhet.
</p
>
655 <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
657 &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
> >.
658 for å se hva slags bruksbegresninger H
.264 innebærer.
</p
>
660 <p
>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
661 kan brukes før rettighetshaverene også innser at de er med på å skade
662 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
663 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
664 langt på overtid.
</p
>
666 <p
>> Ring meg om noe er uklart: XXX
</p
>
668 <p
>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
669 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
670 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
671 for videre diskusjon hadde dere i mine øyne kommet fra det med
672 ryggraden på plass.
</p
>
674 <p
>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.
</p
>
676 <p
>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
677 &lt;URL:
<a href=
"http://www.archive.org/details/CopyingIsNotTheft
">http://www.archive.org/details/CopyingIsNotTheft
</a
> > og
678 &lt;URL:
<a href=
"http://patentabsurdity.com/
">http://patentabsurdity.com/
</a
> > hadde vært noe å kringkaste på
681 <p
>Vennlig hilsen,
683 <br
>Petter Reinholdtsen
</p
>
688 <title>Why isn
't Debian Edu using VLC?
</title>
689 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
690 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
691 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
692 <description><p
>In the latest issue of Linux Journal, the readers choices were
693 presented, and the winner among the multimedia player were VLC.
694 Personally, I like VLC, and it is my player of choice when I first try
695 to play a video file or stream. Only if VLC fail will I drag out
696 gmplayer to see if it can do better. The reason is mostly the failure
697 model and trust. When VLC fail, it normally pop up a error message
698 reporting the problem. When mplayer fail, it normally segfault or
699 just hangs. The latter failure mode drain my trust in the program.
<p
>
701 <p
>But even if VLC is my player of choice, we have choosen to use
702 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
703 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
704 plugin to play web videos seamlessly, and the VLC browser plugin is
705 not very good. For example, it lack in-line control buttons, so there
706 is no way for the user to pause the video. Also, when I
707 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
708 tested the browser plugins
</a
> available in Debian, the VLC plugin
709 failed on several video pages where mplayer based plugins worked. If
710 the browser plugin for VLC was as good as the gecko-mediaplayer
711 package (which uses mplayer), we would switch.
</P
>
713 <p
>While VLC is a good player, its user interface is slightly
714 annoying. The most annoying feature is its inconsistent use of
715 keyboard shortcuts. When the player is in full screen mode, its
716 shortcuts are different from when it is playing the video in a window.
717 For example, space only work as pause when in full screen mode. I
718 wish it had consisten shortcuts and that space also would work when in
719 window mode. Another nice shortcut in gmplayer is [enter] to restart
720 the current video. It is very nice when playing short videos from the
721 web and want to restart it when new people arrive to have a look at
722 what is going on.
</p
>
727 <title>Is Ogg Theora a free and open standard?
</title>
728 <link>http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html
</link>
729 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html
</guid>
730 <pubDate>Sat,
25 Dec
2010 20:
25:
00 +
0100</pubDate>
731 <description><p
><a href=
"http://www.digistan.org/open-standard:definition
">The
732 Digistan definition
</a
> of a free and open standard reads like this:
</p
>
736 <p
>The Digital Standards Organization defines free and open standard
737 as follows:
</p
>
741 <li
>A free and open standard is immune to vendor capture at all stages
742 in its life-cycle. Immunity from vendor capture makes it possible to
743 freely use, improve upon, trust, and extend a standard over time.
</li
>
745 <li
>The standard is adopted and will be maintained by a not-for-profit
746 organisation, and its ongoing development occurs on the basis of an
747 open decision-making procedure available to all interested
750 <li
>The standard has been published and the standard specification
751 document is available freely. It must be permissible to all to copy,
752 distribute, and use it freely.
</li
>
754 <li
>The patents possibly present on (parts of) the standard are made
755 irrevocably available on a royalty-free basis.
</li
>
757 <li
>There are no constraints on the re-use of the standard.
</li
>
761 <p
>The economic outcome of a free and open standard, which can be
762 measured, is that it enables perfect competition between suppliers of
763 products based on the standard.
</p
>
766 <p
>For a while now I have tried to figure out of Ogg Theora is a free
767 and open standard according to this definition. Here is a short
768 writeup of what I have been able to gather so far. I brought up the
769 topic on the Xiph advocacy mailing list
770 <a href=
"http://lists.xiph.org/pipermail/advocacy/
2009-July/
001632.html
">in
771 July
2009</a
>, for those that want to see some background information.
772 According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
773 the Ogg Theora specification fulfils the Digistan definition.
</p
>
775 <p
><strong
>Free from vendor capture?
</strong
></p
>
777 <p
>As far as I can see, there is no single vendor that can control the
778 Ogg Theora specification. It can be argued that the
779 <a href=
"http://www.xiph.org/
">Xiph foundation
</A
> is such vendor, but
780 given that it is a non-profit foundation with the expressed goal
781 making free and open protocols and standards available, it is not
782 obvious that this is a real risk. One issue with the Xiph
783 foundation is that its inner working (as in board member list, or who
784 control the foundation) are not easily available on the web. I
've
785 been unable to find out who is in the foundation board, and have not
786 seen any accounting information documenting how money is handled nor
787 where is is spent in the foundation. It is thus not obvious for an
788 external observer who control The Xiph foundation, and for all I know
789 it is possible for a single vendor to take control over the
790 specification. But it seem unlikely.
</p
>
792 <p
><strong
>Maintained by open not-for-profit organisation?
</strong
></p
>
794 <p
>Assuming that the Xiph foundation is the organisation its web pages
795 claim it to be, this point is fulfilled. If Xiph foundation is
796 controlled by a single vendor, it isn
't, but I have not found any
797 documentation indicating this.
</p
>
799 <p
>According to
800 <a href=
"http://media.hiof.no/diverse/fad/rapport_4.pdf
">a report
</a
>
801 prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
802 government, the Xiph foundation is a non-commercial organisation and
803 the development process is open, transparent and non-Discrimatory.
804 Until proven otherwise, I believe it make most sense to believe the
805 report is correct.
</p
>
807 <p
><strong
>Specification freely available?
</strong
></p
>
809 <p
>The specification for the
<a href=
"http://www.xiph.org/ogg/doc/
">Ogg
810 container format
</a
> and both the
811 <a href=
"http://www.xiph.org/vorbis/doc/
">Vorbis
</a
> and
812 <a href=
"http://theora.org/doc/
">Theora
</a
> codeces are available on
813 the web. This are the terms in the Vorbis and Theora specification:
817 Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
818 specifications, whether in private, public, or corporate
819 capacity. However, the Xiph.Org Foundation and the Ogg project reserve
820 the right to set the Ogg [Vorbis/Theora] specification and certify
821 specification compliance.
825 <p
>The Ogg container format is specified in IETF
826 <a href=
"http://www.xiph.org/ogg/doc/rfc3533.txt
">RFC
3533</a
>, and
827 this is the term:
<p
>
831 <p
>This document and translations of it may be copied and furnished to
832 others, and derivative works that comment on or otherwise explain it
833 or assist in its implementation may be prepared, copied, published and
834 distributed, in whole or in part, without restriction of any kind,
835 provided that the above copyright notice and this paragraph are
836 included on all such copies and derivative works. However, this
837 document itself may not be modified in any way, such as by removing
838 the copyright notice or references to the Internet Society or other
839 Internet organizations, except as needed for the purpose of developing
840 Internet standards in which case the procedures for copyrights defined
841 in the Internet Standards process must be followed, or as required to
842 translate it into languages other than English.
</p
>
844 <p
>The limited permissions granted above are perpetual and will not be
845 revoked by the Internet Society or its successors or assigns.
</p
>
848 <p
>All these terms seem to allow unlimited distribution and use, an
849 this term seem to be fulfilled. There might be a problem with the
850 missing permission to distribute modified versions of the text, and
851 thus reuse it in other specifications. Not quite sure if that is a
852 requirement for the Digistan definition.
</p
>
854 <p
><strong
>Royalty-free?
</strong
></p
>
856 <p
>There are no known patent claims requiring royalties for the Ogg
858 <a href=
"http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=
65782">MPEG-LA
</a
>
860 <a href=
"http://yro.slashdot.org/story/
10/
04/
30/
237238/Steve-Jobs-Hints-At-Theora-Lawsuit
">Steve
861 Jobs
</a
> in Apple claim to know about some patent claims (submarine
862 patents) against the Theora format, but no-one else seem to believe
863 them. Both Opera Software and the Mozilla Foundation have looked into
864 this and decided to implement Ogg Theora support in their browsers
865 without paying any royalties. For now the claims from MPEG-LA and
866 Steve Jobs seem more like FUD to scare people to use the H
.264 codec
867 than any real problem with Ogg Theora.
</p
>
869 <p
><strong
>No constraints on re-use?
</strong
></p
>
871 <p
>I am not aware of any constraints on re-use.
</p
>
873 <p
><strong
>Conclusion
</strong
></p
>
875 <p
>3 of
5 requirements seem obviously fulfilled, and the remaining
2
876 depend on the governing structure of the Xiph foundation. Given the
877 background report used by the Norwegian government, I believe it is
878 safe to assume the last two requirements are fulfilled too, but it
879 would be nice if the Xiph foundation web site made it easier to verify
882 <p
>It would be nice to see other analysis of other specifications to
883 see if they are free and open standards.
</p
>
888 <title>Chrome plan to drop H
.264 support for HTML5
&lt;video
&gt;
</title>
889 <link>http://people.skolelinux.org/pere/blog/Chrome_plan_to_drop_H_264_support_for_HTML5__lt_video_gt_.html
</link>
890 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Chrome_plan_to_drop_H_264_support_for_HTML5__lt_video_gt_.html
</guid>
891 <pubDate>Wed,
12 Jan
2011 22:
10:
00 +
0100</pubDate>
892 <description><p
>Today I discovered
893 <a href=
"http://www.digi.no/
860070/google-dropper-h264-stotten-i-chrome
">via
894 digi.no
</a
> that the Chrome developers, in a surprising announcement,
895 <a href=
"http://blog.chromium.org/
2011/
01/html-video-codec-support-in-chrome.html
">yesterday
896 announced
</a
> plans to drop H
.264 support for HTML5
&lt;video
&gt; in
897 the browser. The argument used is that H
.264 is not a
"completely
898 open
" codec technology. If you believe H
.264 was free for everyone
899 to use, I recommend having a look at the essay
900 "<a href=
"http://webmink.com/essays/h-
264/
">H
.264 – Not The Kind Of
901 Free That Matters
</a
>". It is not free of cost for creators of video
902 tools, nor those of us that want to publish on the Internet, and the
903 terms provided by MPEG-LA excludes free software projects from
904 licensing the patents needed for H
.264. Some background information
905 on the Google announcement is available from
906 <a href=
"http://www.osnews.com/story/
24243/Google_To_Drop_H264_Support_from_Chrome
">OSnews
</a
>.
907 A good read. :)
</p
>
909 <p
>Personally, I believe it is great that Google is taking a stand to
910 promote equal terms for everyone when it comes to video publishing on
911 the Internet. This can only be done by publishing using free and open
912 standards, which is only possible if the web browsers provide support
913 for these free and open standards. At the moment there seem to be two
914 camps in the web browser world when it come to video support. Some
915 browsers support H
.264, and others support
916 <a href=
"http://www.theora.org/
">Ogg Theora
</a
> and
917 <a href=
"http://www.webmproject.org/
">WebM
</a
>
918 (
<a href=
"http://www.diracvideo.org/
">Dirac
</a
> is not really an option
919 yet), forcing those of us that want to publish video on the Internet
920 and which can not accept the terms of use presented by MPEG-LA for
921 H
.264 to not reach all potential viewers.
922 Wikipedia keep
<a href=
"http://en.wikipedia.org/wiki/HTML5_video
">an
923 updated summary
</a
> of the current browser support.
</p
>
925 <p
>Not surprising, several people would prefer Google to keep
926 promoting H
.264, and John Gruber
927 <a href=
"http://daringfireball.net/
2011/
01/simple_questions
">presents
928 the mind set
</a
> of these people quite well. His rhetorical questions
929 provoked a reply from Thom Holwerda with another set of questions
930 <a href=
"http://www.osnews.com/story/
24245/
10_Questions_for_John_Gruber_Regarding_H_264_WebM
">presenting
931 the issues with H
.264</a
>. Both are worth a read.
</p
>
933 <p
>Some argue that if Google is dropping H
.264 because it isn
't free,
934 they should also drop support for the Adobe Flash plugin. This
935 argument was covered by Simon Phipps in
936 <a href=
"http://blogs.computerworlduk.com/simon-says/
2011/
01/google-and-h264---far-from-hypocritical/index.htm
">todays
937 blog post
</a
>, which I find to put the issue in context. To me it
938 make perfect sense to drop native H
.264 support for HTML5 in the
939 browser while still allowing plugins.
</p
>
941 <p
>I suspect the reason this announcement make so many people protest,
942 is that all the users and promoters of H
.264 suddenly get an uneasy
943 feeling that they might be backing the wrong horse. A lot of TV
944 broadcasters have been moving to H
.264 the last few years, and a lot
945 of money has been invested in hardware based on the belief that they
946 could use the same video format for both broadcasting and web
947 publishing. Suddenly this belief is shaken.
</p
>
949 <p
>An interesting question is why Google is doing this. While the
950 presented argument might be true enough, I believe Google would only
951 present the argument if the change make sense from a business
952 perspective. One reason might be that they are currently negotiating
953 with MPEG-LA over royalties or usage terms, and giving MPEG-LA the
954 feeling that dropping H
.264 completely from Chroome, Youtube and
955 Google Video would improve the negotiation position of Google.
956 Another reason might be that Google want to save money by not having
957 to pay the video tax to MPEG-LA at all, and thus want to move to a
958 video format not requiring royalties at all. A third reason might be
959 that the Chrome development team simply want to avoid the
960 Chrome/Chromium split to get more help with the development of Chrome.
961 I guess time will tell.
</p
>
963 <p
>Update
2011-
01-
15: The Google Chrome team provided
964 <a href=
"http://blog.chromium.org/
2011/
01/more-about-chrome-html-video-codec.html
">more
965 background and information on the move
</a
> it a blog post yesterday.
</p
>
970 <title>The video format most supported in web browsers?
</title>
971 <link>http://people.skolelinux.org/pere/blog/The_video_format_most_supported_in_web_browsers_.html
</link>
972 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_video_format_most_supported_in_web_browsers_.html
</guid>
973 <pubDate>Sun,
16 Jan
2011 00:
20:
00 +
0100</pubDate>
974 <description><p
>The video format struggle on the web continues, and the three
975 contenders seem to be Ogg Theora, H
.264 and WebM. Most video sites
976 seem to use H
.264, while others use Ogg Theora. Interestingly enough,
977 the comments I see give me the feeling that a lot of people believe
978 H
.264 is the most supported video format in browsers, but according to
979 the Wikipedia article on
980 <a href=
"http://en.wikipedia.org/wiki/HTML5_video
">HTML5 video
</a
>,
981 this is not true. Check out the nice table of supprted formats in
982 different browsers there. The format supported by most browsers is
983 Ogg Theora, supported by released versions of Mozilla Firefox, Google
984 Chrome, Chromium, Opera, Konqueror, Epiphany, Origyn Web Browser and
985 BOLT browser, while not supported by Internet Explorer nor Safari.
986 The runner up is WebM supported by released versions of Google Chrome
987 Chromium Opera and Origyn Web Browser, and test versions of Mozilla
988 Firefox. H
.264 is supported by released versions of Safari, Origyn
989 Web Browser and BOLT browser, and the test version of Internet
990 Explorer. Those wanting Ogg Theora support in Internet Explorer and
991 Safari can install plugins to get it.
</p
>
993 <p
>To me, the simple conclusion from this is that to reach most users
994 without any extra software installed, one uses Ogg Theora with the
995 HTML5 video tag. Of course to reach all those without a browser
996 handling HTML5, one need fallback mechanisms. In
997 <a href=
"http://www.nuug.no/
">NUUG
</a
>, we provide first fallback to a
998 plugin capable of playing MPEG1 video, and those without such support
999 we have a second fallback to the Cortado java applet playing Ogg
1000 Theora. This seem to work quite well, as can be seen in an
<a
1001 href=
"http://www.nuug.no/aktiviteter/
20110111-semantic-web/
">example
1002 from last week
</a
>.
</p
>
1004 <p
>The reason Ogg Theora is the most supported format, and H
.264 is
1005 the least supported is simple. Implementing and using H
.264
1006 require royalty payment to MPEG-LA, and the terms of use from MPEG-LA
1007 are incompatible with free software licensing. If you believed H
.264
1008 was without royalties and license terms, check out
1009 "<a href=
"http://webmink.com/essays/h-
264/
">H
.264 – Not The Kind Of
1010 Free That Matters
</a
>" by Simon Phipps.
</p
>
1012 <p
>A incomplete list of sites providing video in Ogg Theora is
1014 <a href=
"http://wiki.xiph.org/index.php/List_of_Theora_videos
">the
1015 Xiph.org wiki
</a
>, if you want to have a look. I
'm not aware of a
1016 similar list for WebM nor H
.264.
</p
>
1018 <p
>Update
2011-
01-
16 09:
40: A question from Tollef on IRC made me
1019 realise that I failed to make it clear enough this text is about the
1020 &lt;video
&gt; tag support in browsers and not the video support
1021 provided by external plugins like the Flash plugins.
</p
>
1026 <title>Gnash enteres Google Summer of Code
2011</title>
1027 <link>http://people.skolelinux.org/pere/blog/Gnash_enteres_Google_Summer_of_Code_2011.html
</link>
1028 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_enteres_Google_Summer_of_Code_2011.html
</guid>
1029 <pubDate>Wed,
6 Apr
2011 09:
00:
00 +
0200</pubDate>
1030 <description><p
><a href=
"http://www.getgnash.org/
">The Gnash project
</a
> is still
1031 the most promising solution for a Free Software Flash implementation.
1032 A few days ago the project
1033 <a href=
"http://lists.gnu.org/archive/html/gnash-dev/
2011-
04/msg00011.html
">announced
</a
>
1034 that it will participate in Google Summer of Code. I hope many
1035 students apply, and that some of them succeed in getting AVM2 support
1036 into Gnash.
</p
>
1041 <title>Ripping problematic DVDs using dvdbackup and genisoimage
</title>
1042 <link>http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html
</link>
1043 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html
</guid>
1044 <pubDate>Sat,
17 Sep
2011 20:
20:
00 +
0200</pubDate>
1045 <description><p
>For convenience, I want to store copies of all my DVDs on my file
1046 server. It allow me to save shelf space flat while still having my
1047 movie collection easily available. It also make it possible to let
1048 the kids see their favourite DVDs without wearing the physical copies
1049 down. I prefer to store the DVDs as ISOs to keep the DVD menu and
1050 subtitle options intact. It also ensure that the entire film is one
1051 file on the disk. As this is for personal use, the ripping is
1052 perfectly legal here in Norway.
</p
>
1054 <p
>Normally I rip the DVDs using dd like this:
</p
>
1056 <blockquote
><pre
>
1058 # apt-get install lsdvd
1059 title=$(lsdvd
2>/dev/null|awk
'/Disc Title: / {print $
3}
')
1060 dd if=/dev/dvd of=/storage/dvds/$title.iso bs=
1M
1061 </pre
></blockquote
>
1063 <p
>But some DVDs give a input/output error when I read it, and I have
1064 been looking for a better alternative. I have no idea why this I/O
1065 error occur, but suspect my DVD drive, the Linux kernel driver or
1066 something fishy with the DVDs in question. Or perhaps all three.
</p
>
1068 <p
>Anyway, I believe I found a solution today using dvdbackup and
1069 genisoimage. This script gave me a working ISO for a problematic
1070 movie by first extracting the DVD file system and then re-packing it
1073 <blockquote
><pre
>
1075 # apt-get install lsdvd dvdbackup genisoimage
1077 tmpdir=/storage/dvds/
1078 title=$(lsdvd
2>/dev/null|awk
'/Disc Title: / {print $
3}
')
1079 dvdbackup -i /dev/dvd -M -o $tmpdir -n$title
1080 genisoimage -dvd-video -o $tmpdir/$title.iso $tmpdir/$title
1081 rm -rf $tmpdir/$title
1082 </pre
></blockquote
>
1084 <p
>Anyone know of a better way available in Debian/Squeeze?
</p
>
1086 <p
>Update
2011-
09-
18: I got a tip from Konstantin Khomoutov about the
1087 readom program from the wodim package. It is specially written to
1088 read optical media, and is called like this:
<tt
>readom dev=/dev/dvd
1089 f=image.iso
</tt
>. It got
6 GB along with the problematic Cars DVD
1090 before it failed, and failed right away with a Timmy Time DVD.
</p
>
1092 <p
>Next, I got a tip from Bastian Blank about
1093 <a href=
"http://bblank.thinkmo.de/blog/new-software-python-dvdvideo
">his
1094 program python-dvdvideo
</a
>, which seem to be just what I am looking
1095 for. Tested it with my problematic Timmy Time DVD, and it succeeded
1096 creating a ISO image. The git source built and installed just fine in
1097 Squeeze, so I guess this will be my tool of choice in the future.
</p
>
1102 <title>Hvordan enkelt laste ned filmer fra NRK
</title>
1103 <link>http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html
</link>
1104 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html
</guid>
1105 <pubDate>Sat,
5 Nov
2011 15:
20:
00 +
0100</pubDate>
1106 <description><p
>Ofte har jeg lyst til å laste ned et innslag fra NRKs nettsted for
1107 å se det senere når jeg ikke er på nett, eller for å ha det
1108 tilgjengelig når jeg en gang i fremtiden ønsker å referere til
1109 innslaget selv om NRK har fjernet det fra sine nettsider. I dag fant
1110 jeg et lite script som fikser jobben.
</p
>
1112 <p
>Scriptet er laget av Jan Henning Thorsen og tilgjengelig fra
1113 <a href=
"http://jhthorsen.github.com/snippets/nrk-downloader/
">github
</a
>,
1114 og gjør det veldig enkelt å laste ned. Kjør
<tt
>nrk-downloader.sh
1115 http://www1.nrk.no/nett-tv/klipp/
582810</tt
> for å hente ned et enkelt
1116 innslag eller
<tt
>nrk-downloader.sh
1117 http://www1.nrk.no/nett-tv/kategori/
3521</tt
> for å laste ned alle
1118 episodene i en serie.
</p
>
1120 <p
>Det er ikke rakettforskning å laste ned NRK-
"strømmer
", og
1121 tidligere gjorde jeg dette manuelt med mplayer. Scriptet til
1122 Hr. Thorsen gjør det raskere og enklere for meg, men jeg vil ikke si
1123 at det er en revolusjonerende løsning. Jeg mener jo fortsatt at
1124 påstanden fra NRKs ansatte om at det er
1125 <a href=
"http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html
">vesensforskjellig
1126 å legge tilgjengelig for nedlasting og for streaming
</a
> er
1127 meningsløs.
</p
>
1132 <title>Stopmotion for making stop motion animations on Linux - reloaded
</title>
1133 <link>http://people.skolelinux.org/pere/blog/Stopmotion_for_making_stop_motion_animations_on_Linux___reloaded.html
</link>
1134 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Stopmotion_for_making_stop_motion_animations_on_Linux___reloaded.html
</guid>
1135 <pubDate>Sat,
3 Mar
2012 12:
50:
00 +
0100</pubDate>
1136 <description><p
>Many years ago, the
<a href=
"http://www.skolelinux.org/
">Skolelinux
1137 / Debian Edu project
</a
> initiated a student project to create a tool
1138 for making stop motion movies. The proposal came from a teacher
1139 needing such tool on Skolelinux. The project, called
"stopmotion
",
1140 was manned by two extraordinary students and won a school award and a
1141 national aware with this great project. The project was initiated and
1142 mentored by Herman Robak, and manned by the students Bjørn Erik Nilsen
1143 and Fredrik Berg Kjølstad. They got in touch with people at Aardman
1144 Animation studio and received feedback on how professionals would like
1145 such stopmotion tool to work, and the end result was and is used by
1146 animators around the globe. But as is usual after studying, both got
1147 jobs and went elsewhere, and did not have time to properly tend to the
1148 project, and it has been lingering for a few years now. Until last
1151 <p
>Last year some of the users got together with Herman, and moved the
1152 project to Sourceforge and in effect restarted the project under a new
1154 <a href=
"http://sourceforge.net/projects/linuxstopmotion/
">linuxstopmotion
</a
>.
1155 The name change was done to make it possible to find the project using
1156 Internet search engines (try to search for
'stopmotion
' to see what I
1157 mean). I
've been following
1158 <a href=
"https://lists.sourceforge.net/lists/listinfo/linuxstopmotion-community
">the
1159 mailing list
</a
> and the improvement already in place and planned for
1160 the future is encouraging. If you want to make stop motion movies.
1161 Check it out. :)
</p
>