blog/tags/video/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen: Entries Tagged video</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="video.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21     <h3>Entries tagged "video".</h3>
  22
  23     <div class="entry">
  24       <div class="title">
  25         <a href="http://people.skolelinux.org/pere/blog/Software_video_mixer_on_a_USB_stick.html">Software video mixer on a USB stick</a>
  26       </div>
  27       <div class="date">
  28         28th December 2008
  29       </div>
  30       <div class="body">
  31         <p>The <a href="http://www.nuug.no/">Norwegian Unix User Group</a> is
  32 recording our montly presentation on video, and recently we have
  33 worked on improving the quality of the recordings by mixing the slides
  34 directly with the video stream.  For this, we use the
  35 <a href="http://dvswitch.alioth.debian.org/">dvswitch</a> package from
  36 the Debian video team.  As this require quite one computer per video
  37 source, and NUUG do not have enough laptops available, we need to
  38 borrow laptops.  And to avoid having to install extra software on
  39 these borrwed laptops, I have wrapped up all the programs needed on a
  40 bootable USB stick.  The software required is dvswitch with assosiated
  41 source, sink and mixer applications and
  42 <a href="http://www.kinodv.org/">dvgrab</a>.  To allow this setup to
  43 work without any configuration, I've patched dvswitch to use
  44 <a href="http://www.avahi.org/">avahi</a> to connect the various parts
  45 together.  And to allow us to use laptops without firewire plugs, I
  46 upgraded dvgrab to the one from Debian/unstable to get one that work
  47 with USB sources.  We have not yet tested this setup in a production
  48 setup, but I hope it will work properly, and allow us to set up a
  49 video mixer in a very short time frame.  We will need it for
  50 <a href="http://www.goopen.no/">Go Open 2009</a>.</p>
  51
  52 <p><a href="http://www.nuug.no/pub/video/bin/usbstick-dvswitch.img.gz">The
  53 USB image</a> is for a 1 GB memory stick, but can be used on any
  54 larger stick as well.</p>
  55
  56       </div>
  57       <div class="tags">
  58
  59
  60         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
  61
  62
  63       </div>
  64     </div>
  65     <div class="padding"></div>
  66
  67     <div class="entry">
  68       <div class="title">
  69         <a href="http://people.skolelinux.org/pere/blog/When_web_browser_developers_make_a_video_player___.html">When web browser developers make a video player...</a>
  70       </div>
  71       <div class="date">
  72         17th January 2009
  73       </div>
  74       <div class="body">
  75         <p>As part of the work we do in <a href="http://www.nuug.no">NUUG</a>
  76 to publish video recordings of our monthly presentations, we provide a
  77 page with embedded video for easy access to the recording.  Putting a
  78 good set of HTML tags together to get working embedded video in all
  79 browsers and across all operating systems is not easy.  I hope this
  80 will become easier when the &lt;video&gt; tag is implemented in all
  81 browsers, but I am not sure.  We provide the recordings in several
  82 formats, MPEG1, Ogg Theora, H.264 and Quicktime, and want the
  83 browser/media plugin to pick one it support and use it to play the
  84 recording, using whatever embed mechanism the browser understand.
  85 There is at least four different tags to use for this, the new HTML5
  86 &lt;video&gt; tag, the &lt;object&gt; tag, the &lt;embed&gt; tag and
  87 the &lt;applet&gt; tag.  All of these take a lot of options, and
  88 finding the best options is a major challenge.</p>
  89
  90 <p>I just tested the experimental Opera browser available from <a
  91 href="http://labs.opera.com">labs.opera.com</a>, to see how it handled
  92 a &lt;video&gt; tag with a few video sources and no extra attributes.
  93 I was not very impressed.  The browser start by fetching a picture
  94 from the video stream.  Not sure if it is the first frame, but it is
  95 definitely very early in the recording.  So far, so good. Next,
  96 instead of streaming the 76 MiB video file, it start to download all
  97 of it, but do not start to play the video.  This mean I have to wait
  98 for several minutes for the downloading to finish.  When the download
  99 is done, the playing of the video do not start!  Waiting for the
 100 download, but I do not get to see the video?  Some testing later, I
 101 discover that I have to add the controls="true" attribute to be able
 102 to get a play button to pres to start the video.  Adding
 103 autoplay="true" did not help.  I sure hope this is a misfeature of the
 104 test version of Opera, and that future implementations of the
 105 &lt;video&gt; tag will stream recordings by default, or at least start
 106 playing when the download is done.</p>
 107
 108 <p>The test page I used (since changed to add more attributes) is
 109 <a href="http://www.nuug.no/aktiviteter/20090113-foredrag-om-foredrag/">available
 110 from the nuug site</a>.  Will have to test it with the new Firefox
 111 too.</p>
 112
 113 <p>In the test process, I discovered a missing feature.  I was unable
 114 to find a way to get the URL of the playing video out of Opera, so I
 115 am not quite sure it picked the Ogg Theora version of the video.  I
 116 sure hope it was using the announced Ogg Theora support. :)</p>
 117
 118       </div>
 119       <div class="tags">
 120
 121
 122         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 123
 124
 125       </div>
 126     </div>
 127     <div class="padding"></div>
 128
 129     <div class="entry">
 130       <div class="title">
 131         <a href="http://people.skolelinux.org/pere/blog/F_rste_vellykkede_videostr_m_fra_NUUG.html">Første vellykkede videostrøm fra NUUG</a>
 132       </div>
 133       <div class="date">
 134         11th February 2009
 135       </div>
 136       <div class="body">
 137         <p>Jeg ble glad for å se under
 138 <a href="http://www.nuug.no/aktiviteter/20090210-compiz/">gårdagens
 139 medlemsmøte</a> i NUUG Oslo at utsending av live-video fra møtet
 140 fungerte for første gang.  Forrige gang ble det ved en teknisk tabbe
 141 sendt video uten lyd.  Vi kan takke Ole Kristian Lien og resten av
 142 videogruppen i NUUG for at nå NUUG-medlemmer over det ganske land
 143 kunne se foredraget samtidig med oss i Oslo.  Vi opplevde til og med
 144 under møtet å motta spørsmål via IRC som ble besvart der og da.
 145 Opptaket publiseres så snart det er kopiert over til NUUGs
 146 webserver og komprimert.</p>
 147
 148       </div>
 149       <div class="tags">
 150
 151
 152         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 153
 154
 155       </div>
 156     </div>
 157     <div class="padding"></div>
 158
 159     <div class="entry">
 160       <div class="title">
 161         <a href="http://people.skolelinux.org/pere/blog/Lisensvalg_for_NUUG_opptakene_endelig_p__plass.html">Lisensvalg for NUUG-opptakene endelig på plass</a>
 162       </div>
 163       <div class="date">
 164          6th March 2009
 165       </div>
 166       <div class="body">
 167         <p>Etter mange års meditasjon over temaet, har NUUG endelig klart å
 168 bestemme seg for hvilken lisens vi skal bruke på videoopptakene som
 169 gjøres av NUUGs videogruppe.  Ole Kristian har annonsert at lisensen
 170 blir <a href="http://creativecommons.org/licenses/by-sa/3.0/no/">Creative
 171 Commons Navngivelse-Del på samme vilkår 3.0 Norge</a>.  Jeg er veldig
 172 glad for at denne saken endelig er landet.  Lisensen for opptaket til
 173 Stallman-foredraget ble en annen pga. at lisensvalget ikke var avklart
 174 på forhånd og IFI og PING ønsket CC-BY-ND, og må ses på som et unntak
 175 i denne sammenhengen.</p>
 176
 177       </div>
 178       <div class="tags">
 179
 180
 181         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 182
 183
 184       </div>
 185     </div>
 186     <div class="padding"></div>
 187
 188     <div class="entry">
 189       <div class="title">
 190         <a href="http://people.skolelinux.org/pere/blog/Frikanalen_og_jul_i_studentr_det.html">Frikanalen og jul i studentrådet</a>
 191       </div>
 192       <div class="date">
 193         11th March 2009
 194       </div>
 195       <div class="body">
 196         <p>I går
 197 <a href="http://lists.nuug.no/pipermail/interesserte/2009-March/000387.html">lanserte</a>
 198 NUUGs videogruppe
 199 <a href="http://www.frikanalen.no">Frikanalen</a> med
 200 <a href="http://www.nuug.no/pub/video/frikanalen/frontpage.cgi">åpne
 201 standarder</a>, og resultatet av noen intense uker med arbeide kunne
 202 endelig presenteres.  Jeg har tro på åpen kanalkonseptet som
 203 Frikanalen er et eksempel på, der borgerne får anledning til å
 204 kringkaste sitt syn på en åpen og demokratisk måte.  Jeg er veldig
 205 glad vi har fått gjort kanalen tilgjengelig i Ogg Theora, slik at alle
 206 kan få tilgang til opptakene på web, og slipper å måtte installere MS
 207 Silverlight for å spille av opptakene.</p>
 208
 209 <p>Frikanalen har en brokete historie, og dagens inkarnasjon er ikke
 210 helt slik foreningen Åpen kanal planla det for mange år siden, noe som
 211 er bakgrunnen for at det fredag 13. mars 2009 kl 09:00 starter en
 212 rettsak i Oslo tingrett der Kringkasterforeningen (tidligere
 213 foreningen Åpen kanal) har saksøkt kulturdepartementet over
 214 konsesjonsvilkårene til Frikanalen.  Jeg er spent på resultatet.</p>
 215
 216 <p>I arbeidet med Frikanalen med åpne standarder, så har vi hatt glede
 217 av å se en rekke av innslagene som er tilgjengelig.  Her er mye
 218 religiøst sludder, fra
 219 <a href="http://www.nuug.no/pub/video/frikanalen/fetchvideo.cgi?videoId=720">vandring
 220 i jerusalem</a> via
 221 <a href="http://www.nuug.no/pub/video/frikanalen/fetchvideo.cgi?videoId=779">religiøst
 222 vinklede nyheter</a> til
 223 <a
 224 href="http://www.nuug.no/pub/video/frikanalen/fetchvideo.cgi?videoId=2077">kreasjonisk
 225 retorikk</a>, men også fine
 226 <a href="http://www.nuug.no/pub/video/frikanalen/fetchvideo.cgi?videoId=407">dokumentarer
 227 om redningsselskapet</a> og
 228 <a href="http://www.nuug.no/pub/video/frikanalen/fetchvideo.cgi?videoId=2204">interessante
 229 tegneserieanmeldelser</a>.  Det jeg derimot har hatt størst glede av,
 230 er
 231
 232 <a href="http://www.nuug.no/pub/video/frikanalen/fetchvideo.cgi?videoId=1556">jul
 233 i studentrådet</a>, der hver episode var en fest å se på.  Jeg håper
 234 NUUG lykkes med å få ut sine opptak med like stor suksess.</p>
 235
 236       </div>
 237       <div class="tags">
 238
 239
 240         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 241
 242
 243       </div>
 244     </div>
 245     <div class="padding"></div>
 246
 247     <div class="entry">
 248       <div class="title">
 249         <a href="http://people.skolelinux.org/pere/blog/Recording_video_from_cron_using_VLC.html">Recording video from cron using VLC</a>
 250       </div>
 251       <div class="date">
 252          5th April 2009
 253       </div>
 254       <div class="body">
 255         <p>One think I have wanted to figure out for a along time is how to
 256 run vlc from cron to do recording of video streams on the net.  The
 257 task is trivial with mplayer, but I do not really trust the security
 258 of mplayer (it crashes too often on strange input), and thus prefer
 259 vlc.  I finally found a way to do it today.  I spent an hour or so
 260 searching the web for recipes and reading the documentation.  The
 261 hardest part was to get rid of the GUI window, but after finding the
 262 dummy interface, the command line finally presented itself:</p>
 263
 264 <blockquote><pre>URL=http://www.ping.uio.no/video/rms-oslo_2009.ogg
 265 SAVEFILE=rms.ogg
 266 DISPLAY= vlc -q $URL \
 267   --sout="#duplicate{dst=std{access=file,url='$SAVEFILE'},dst=nodisplay}" \
 268   --intf=dummy</pre></blockquote>
 269
 270 <p>The command stream the URL and store it in the SAVEFILE by
 271 duplicating the output stream to "nodisplay" and the file, using the
 272 dummy interface.  The dummy interface and the nodisplay output make
 273 sure no X interface is needed.</p>
 274
 275 <p>The cron job then need to start this job with the appropriate URL
 276 and file name to save, sleep for the duration wanted, and then kill
 277 the vlc process with SIGTERM.  Here is a complete script
 278 <tt>vlc-record</tt> to use from <tt>at</tt> or <tt>cron</tt>:</p>
 279
 280 <blockquote><pre>#!/bin/sh
 281 set -e
 282 URL="$1"
 283 SAVEFILE="$2"
 284 DURATION="$3"
 285 DISPLAY= vlc -q "$URL" \
 286   --sout="#duplicate{dst=std{access=file,url='$SAVEFILE'},dst=nodisplay}" \
 287   --intf=dummy < /dev/null > /dev/null 2>&1 &
 288 pid=$!
 289 sleep $DURATION
 290 kill $pid
 291 wait $pid</pre></blockquote>
 292
 293       </div>
 294       <div class="tags">
 295
 296
 297         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 298
 299
 300       </div>
 301     </div>
 302     <div class="padding"></div>
 303
 304     <div class="entry">
 305       <div class="title">
 306         <a href="http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html">Microsofts misvisende argumentasjon rundt multimediaformater</a>
 307       </div>
 308       <div class="date">
 309         26th June 2009
 310       </div>
 311       <div class="body">
 312         <p>I
 313 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf">Microsoft
 314 sin høringsuttalelse</a> til
 315 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html?id=549422">forslag
 316 til versjon 2 av statens referansekatalog over standarder</a>, lirer
 317 de av seg følgende FUD-perle:</p>
 318
 319 <p><blockquote>"Vorbis, OGG, Theora og FLAC er alle tekniske
 320   spesifikasjoner overordnet styrt av xiph.org, som er en
 321   ikke-kommersiell organisasjon.  Etablerte og anerkjente
 322   standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
 323   innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
 324   Det er derimot helt opp til hver enkelt organisasjon å bestemme
 325   hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
 326   spesifikasjonene bør derfor ikke defineres som åpne
 327   standarder."</blockquote></p>
 328
 329 <p>De vokter seg vel for å nevne den anerkjente
 330 standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
 331 IP og det meste av protokoller på Internet, og RFC-standardene som
 332 IETF står bak.  Ogg er spesifisert i
 333 <a href="http://ietf.org/rfc/rfc3533.txt">RFC 3533</a>, og er uten
 334 tvil å anse som en åpen standard.  Vorbis er
 335 <a href="http://ietf.org/rfc/rfc5215.txt">RFC 5215</a>.  Theora er
 336
 337 under standardisering via IETF, med
 338 <a href="http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt">siste
 339 utkast publisert 2006-07-21</a> (riktignok er dermed teksten ikke
 340 skrevet i stein ennå, men det blir neppe endringer som ikke er
 341 bakoverkompatibel).  De kan være inne på noe når det gjelder FLAC da
 342 jeg ikke finner tegn til at <a
 343 href="http://flac.sourceforge.net/format.html">spesifikasjonen
 344 tilgjengelig på web</a> er på tur via noen
 345 standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
 346 og Vorbis også har involvert seg i Flac siden 2003, så ser jeg ikke
 347 bort fra at også den organiseres via IETF.  Jeg kjenner personlig lite
 348 til FLAC.</p>
 349
 350 <p>Uredelig argumentasjon bør en holde seg for god til å komme med,
 351 spesielt når det er så enkelt i dagens Internet-hverdag å gå
 352 misvisende påstander etter i sømmene.</p>
 353
 354       </div>
 355       <div class="tags">
 356
 357
 358         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 359
 360
 361       </div>
 362     </div>
 363     <div class="padding"></div>
 364
 365     <div class="entry">
 366       <div class="title">
 367         <a href="http://people.skolelinux.org/pere/blog/Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html">Regjerningen forlater prinsippet om ingen royalty-betaling i standardkatalogen versjon 2</a>
 368       </div>
 369       <div class="date">
 370          6th July 2009
 371       </div>
 372       <div class="body">
 373         <p>Jeg ble glad da regjeringen
 374 <a href="http://www.digi.no/817635/her-er-statens-nye-it-standarder">annonserte</a>
 375 versjon 2 av
 376 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf">statens
 377 referansekatalog over standarder</a>, men trist da jeg leste hva som
 378 faktisk var vedtatt etter
 379 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html">høringen</a>.
 380 De fleste av de valgte åpne standardene er gode og vil bidra til at
 381 alle kan delta på like vilkår i å lage løsninger for staten, men
 382 noen av dem blokkerer for de som ikke har anledning til å benytte
 383 spesifikasjoner som krever betaling for bruk (såkalt
 384 royalty-betaling).  Det gjelder spesifikt for H.264 for video og MP3
 385 for lyd.  Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
 386 Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
 387 fra statens websider gjøre dette uten å måtte bruke programmer der
 388 betaling for bruk var nødvendig.  Når det nå er gjort valgfritt for
 389 de statlige etatene å bruke enten H.264 eller Theora (og MP3 eler
 390 Vorbis), så vil en bli tvunget til å forholde seg til
 391 royalty-belastede standarder for å få tilgang til videoen og
 392 lyden.</p>
 393
 394 <p>Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
 395 at alle standarder som ble valgt til å være påkrevd i katalogen skulle
 396 være uten royalty-betaling.  Jeg håper det ikke betyr at en har mistet
 397 all forståelse for hvilke prinsipper som må følges for å oppnå
 398 likeverdig konkurranse mellom aktørene i IT-bransjen.  NUUG advarte
 399 mot dette i
 400 <a href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2">sin
 401 høringsuttalelse</a>, men ser ut til å ha blitt ignorert.</p>
 402
 403       </div>
 404       <div class="tags">
 405
 406
 407         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 408
 409
 410       </div>
 411     </div>
 412     <div class="padding"></div>
 413
 414     <div class="entry">
 415       <div class="title">
 416         <a href="http://people.skolelinux.org/pere/blog/Regjerningens_oppsummering_av_h_ringen_om_standardkatalogen_versjon_2.html">Regjerningens oppsummering av høringen om standardkatalogen versjon 2</a>
 417       </div>
 418       <div class="date">
 419          9th July 2009
 420       </div>
 421       <div class="body">
 422         <p>For å forstå mer om hvorfor standardkatalogens versjon 2 ble som
 423 den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
 424 for regjeringen da de tok sin avgjørelse.  De er nå lagt ut på NUUGs
 425 wiki, direkte tilgjengelig via "<a
 426 href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon.pdf">Referansekatalogen
 427 v2.0 - Oppsummering av høring</a>" og "<a
 428 href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon-katalogutkast.pdf">Referansekatalog
 429 for IT-standarder i offentlig sektor Versjon 2.0, dd.mm.åååå -
 430 UTKAST</a>".</p>
 431
 432 <p>Det er tre ting jeg merker meg i oppsummeringen fra
 433 høringsuttalelsen da jeg skummet igjennom den.  Det første er at
 434 forståelsen av hvordan programvarepatenter påvirker fri
 435 programvareutvikling også i Norge når en argumenterer med at
 436 royalty-betaling ikke er et relevant problem i Norge.  Det andre er at
 437 FAD ikke har en prinsipiell forståelse av verdien av en enkelt
 438 standard innenfor hvert område.  Det siste er at påstander i
 439 høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
 440 Microsoft om hvordan Ogg blir standardisert og påstanden fra
 441 politidirektoratet om patentproblemer i Theora).</p>
 442
 443       </div>
 444       <div class="tags">
 445
 446
 447         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 448
 449
 450       </div>
 451     </div>
 452     <div class="padding"></div>
 453
 454     <div class="entry">
 455       <div class="title">
 456         <a href="http://people.skolelinux.org/pere/blog/F_rste_NUUG_fordrag_sendt_p__TV.html">Første NUUG-fordrag sendt på TV</a>
 457       </div>
 458       <div class="date">
 459          8th December 2009
 460       </div>
 461       <div class="body">
 462         <p>Endelig har NUUG klart å få kringkastet ut et av sine fordrag på
 463 TV.  Foredraget om
 464 <a href="http://www.nuug.no/aktiviteter/20090512-bifrost/">utskriftsløsningen
 465 Biforst</a> var først ute, pga. at det var det nyeste foredraget som
 466 var holdt på norsk, og dermed slapp vi å finne ut av hvordan
 467 teksting av video skulle gjøres.</p>
 468
 469 <p>NUUG har vært involvert i
 470 <a href="http://www.frikanalen.no/">Frikanalen</a> en stund nå, for å
 471 forsøke å få ut budskapet vårt også på TV, og dette første foredraget
 472 er en sped start på det vi har planlagt.</p>
 473
 474 <p>NUUGs første foredrag sendes ut via frikanelen på digitalt
 475 bakkenett, og alle abonnenter av riks-TV skal dermed ha mulighet til å
 476 ta inn sendingen.  Slå på TVen 5/12 16:05 (for sent), 12/12 14:00,
 477 19/12 16:00, 24/12 15:37 eller 26/12 16:11 i år, så skal du få se
 478 meg, Tollef og alle andre de som deltok på møtet på TV.<p>
 479
 480       </div>
 481       <div class="tags">
 482
 483
 484         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 485
 486
 487       </div>
 488     </div>
 489     <div class="padding"></div>
 490
 491     <div class="entry">
 492       <div class="title">
 493         <a href="http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html">Some notes on Flash in Debian and Debian Edu</a>
 494       </div>
 495       <div class="date">
 496          4th September 2010
 497       </div>
 498       <div class="body">
 499         <p>In the <a href="http://popcon.debian.org/unknown/by_vote">Debian
 500 popularity-contest numbers</a>, the adobe-flashplugin package the
 501 second most popular used package that is missing in Debian.  The sixth
 502 most popular is flashplayer-mozilla.  This is a clear indication that
 503 working flash is important for Debian users.  Around 10 percent of the
 504 users submitting data to popcon.debian.org have this package
 505 installed.</p>
 506
 507 <p>In the report written by Lars Risan in August 2008
 508 («<a href="http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile&do=view&target=Skolelinux_i_bruk_rapport_1.0.pdf">Skolelinux
 509 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
 510 stiftelsen SLX Debian Labs</a>»), one of the most important problems
 511 schools experienced with <a href="http://www.skolelinux.org/">Debian
 512 Edu/Skolelinux</a> was the lack of working Flash.  A lot of educational
 513 web sites require Flash to work, and lacking working Flash support in
 514 the web browser and the problems with installing it was perceived as a
 515 good reason to stay with Windows.</p>
 516
 517 <p>I once saw a funny and sad comment in a web forum, where Linux was
 518 said to be the retarded cousin that did not really understand
 519 everything you told him but could work fairly well.  This was a
 520 comment regarding the problems Linux have with proprietary formats and
 521 non-standard web pages, and is sad because it exposes a fairly common
 522 understanding of whose fault it is if web pages that only work in for
 523 example Internet Explorer 6 fail to work on Firefox, and funny because
 524 it explain very well how annoying it is for users when Linux
 525 distributions do not work with the documents they receive or the web
 526 pages they want to visit.</p>
 527
 528 <p>This is part of the reason why I believe it is important for Debian
 529 and Debian Edu to have a well working Flash implementation in the
 530 distribution, to get at least popular sites as Youtube and Google
 531 Video to working out of the box.  For Squeeze, Debian have the chance
 532 to include the latest version of Gnash that will make this happen, as
 533 the new release 0.8.8 was published a few weeks ago and is resting in
 534 unstable.  The new version work with more sites that version 0.8.7.
 535 The Gnash maintainers have asked for a freeze exception, but the
 536 release team have not had time to reply to it yet.  I hope they agree
 537 with me that Flash is important for the Debian desktop users, and thus
 538 accept the new package into Squeeze.</p>
 539
 540       </div>
 541       <div class="tags">
 542
 543
 544         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 545
 546
 547       </div>
 548     </div>
 549     <div class="padding"></div>
 550
 551     <div class="entry">
 552       <div class="title">
 553         <a href="http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">Terms of use for video produced by a Canon IXUS 130 digital camera</a>
 554       </div>
 555       <div class="date">
 556          9th September 2010
 557       </div>
 558       <div class="body">
 559         <p>A few days ago I had the mixed pleasure of bying a new digital
 560 camera, a Canon IXUS 130.  It was instructive and very disturbing to
 561 be able to verify that also this camera producer have the nerve to
 562 specify how I can or can not use the videos produced with the camera.
 563 Even thought I was aware of the issue, the options with new cameras
 564 are limited and I ended up bying the camera anyway.  What is the
 565 problem, you might ask?  It is software patents, MPEG-4, H.264 and the
 566 MPEG-LA that is the problem, and our right to record our experiences
 567 without asking for permissions that is at risk.
 568
 569 <p>On page 27 of the Danish instruction manual, this section is
 570 written:</p>
 571
 572 <blockquote>
 573 <p>This product is licensed under AT&T patents for the MPEG-4 standard
 574 and may be used for encoding MPEG-4 compliant video and/or decoding
 575 MPEG-4 compliant video that was encoded only (1) for a personal and
 576 non-commercial purpose or (2) by a video provider licensed under the
 577 AT&T patents to provide MPEG-4 compliant video.</p>
 578
 579 <p>No license is granted or implied for any other use for MPEG-4
 580 standard.</p>
 581 </blockquote>
 582
 583 <p>In short, the camera producer have chosen to use technology
 584 (MPEG-4/H.264) that is only provided if I used it for personal and
 585 non-commercial purposes, or ask for permission from the organisations
 586 holding the knowledge monopoly (patent) for technology used.</p>
 587
 588 <p>This issue has been brewing for a while, and I recommend you to
 589 read
 590 "<a href="http://www.osnews.com/story/23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA">Why
 591 Our Civilization's Video Art and Culture is Threatened by the
 592 MPEG-LA</a>" by Eugenia Loli-Queru and
 593 "<a href="http://webmink.com/2010/09/03/h-264-and-foss/">H.264 Is Not
 594 The Sort Of Free That Matters</a>" by Simon Phipps to learn more about
 595 the issue.  The solution is to support the
 596 <a href="http://www.digistan.org/open-standard:definition">free and
 597 open standards</a> for video, like <a href="http://www.theora.org/">Ogg
 598 Theora</a>, and avoid MPEG-4 and H.264 if you can.</p>
 599
 600       </div>
 601       <div class="tags">
 602
 603
 604         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 605
 606
 607       </div>
 608     </div>
 609     <div class="padding"></div>
 610
 611     <div class="entry">
 612       <div class="title">
 613         <a href="http://people.skolelinux.org/pere/blog/TED_talks_p__norsk_og_NUUG_foredrag___frivillige_trengs_til_teksting.html">TED talks på norsk og NUUG-foredrag - frivillige trengs til teksting</a>
 614       </div>
 615       <div class="date">
 616          1st October 2010
 617       </div>
 618       <div class="body">
 619         <p>Frikanalen og NUUG jobber for å få <a href="http://www.ted.com">TED
 620 talks</a> kringkastet på
 621 <a href="http://www.frikanalen.no/">Frikanalen</a>, for å gi et mer
 622 variert innhold på kanalen som i dag sendes på RiksTV, Lyse og
 623 Uninett.  Før innslagene kan sendes må det lages norske undertekster,
 624 og dette her trengs det frivillige.  Det er hundrevis av innslag, men
 625 mine favoritter er
 626 <a href="http://www.ted.com/talks/james_randi.html">James Randi</a> og
 627 <a href="http://www.ted.com/talks/lang/eng/michael_specter_the_danger_of_science_denial.html">Michael
 628 Specter</a>.  Hvis du har litt tid til overs, bli med på å oversette
 629 TED-foredragene til norsk og få på plass undertekster.  TED har
 630 allerede opplegg på plass for å håndtere oversettelser og
 631 undertekster.  Registrer deg på
 632 <a href="http://www.ted.com/translate/forted">sidene til TED</a> i
 633 dag!</p>
 634
 635 <p>NUUG holder også på å få alle opptakene fra NUUG-presentasjonene
 636 <a href="http://www.nuug.no/pub/video/frikanalen/frontpage.cgi?organization=NUUG">publisert
 637 på Frikanalen</a>.  Foredrag på engelsk må også her tekstes og
 638 oversettes.  Ta kontakt med video@nuug.no hvis du vil bidra med
 639 teksting og oversetting.  Arbeidet koordineres på epostlisten og på
 640 IRC (#nuug-video på irc.oftc.org), og <a
 641 href="http://wiki.nuug.no/grupper/video/frikanalen">en wikiside</a>
 642 brukes som notatblokk for arbeidet.  Mest lovende verktøy for dette
 643 ser i dag ut til å være
 644 <a href="http://universalsubtitles.org/">Universal Subtitles</a>, som
 645 lar en bidra med teksting via en nettleser.</p>
 646
 647       </div>
 648       <div class="tags">
 649
 650
 651         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 652
 653
 654       </div>
 655     </div>
 656     <div class="padding"></div>
 657
 658     <div class="entry">
 659       <div class="title">
 660         <a href="http://people.skolelinux.org/pere/blog/Pledge_for_funding_to_the_Gnash_project_to_get_AVM2_support.html">Pledge for funding to the Gnash project to get AVM2 support</a>
 661       </div>
 662       <div class="date">
 663         19th October 2010
 664       </div>
 665       <div class="body">
 666         <p><a href="http://www.getgnash.org/">The Gnash project</a> is the
 667 most promising solution for a Free Software Flash implementation. It
 668 has done great so far, but there is still far to go, and recently its
 669 funding has dried up.  I believe AVM2 support in Gnash is vital to the
 670 continued progress of the project, as more and more sites show up with
 671 AVM2 flash files.</p>
 672
 673 <p>To try to get funding for developing such support, I have started
 674 <a href="http://www.pledgebank.com/gnash-avm2">a pledge</a> with the
 675 following text:</P>
 676
 677 <p><blockquote>
 678
 679   <p>"I will pay 100$ to the Gnash project to develop AVM2 support but
 680   only if 10 other people will do the same."</p>
 681
 682   <p>- Petter Reinholdtsen, free software developer</p>
 683
 684   <p>Deadline to sign up by: 24th December 2010</p>
 685
 686   <p>The Gnash project need to get support for the new Flash file
 687   format AVM2 to work with a lot of sites using Flash on the
 688   web. Gnash already work with a lot of Flash sites using the old AVM1
 689   format, but more and more sites are using the AVM2 format these
 690   days. The project web page is available from
 691   http://www.getgnash.org/ . Gnash is a free software implementation
 692   of Adobe Flash, allowing those of us that do not accept the terms of
 693   the Adobe Flash license to get access to Flash sites.</p>
 694
 695   <p>The project need funding to get developers to put aside enough
 696   time to develop the AVM2 support, and this pledge is my way to try
 697   to get this to happen.</p>
 698
 699   <p>The project accept donations via the OpenMediaNow foundation,
 700   <a href="http://www.openmedianow.org/?q=node/32">http://www.openmedianow.org/?q=node/32</a> .</p>
 701
 702 </blockquote></p>
 703
 704 <p>I hope you will support this effort too.  I hope more than 10
 705 people will participate to make this happen.  The more money the
 706 project gets, the more features it can develop using these funds.
 707 :)</p>
 708
 709       </div>
 710       <div class="tags">
 711
 712
 713         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 714
 715
 716       </div>
 717     </div>
 718     <div class="padding"></div>
 719
 720     <div class="entry">
 721       <div class="title">
 722         <a href="http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html">Best å ikke fortelle noen at streaming er nedlasting...</a>
 723       </div>
 724       <div class="date">
 725         30th October 2010
 726       </div>
 727       <div class="body">
 728         <p>I dag la jeg inn en kommentar på en sak hos NRKBeta
 729 <a href="http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/">om
 730 hvordan TV-serien Blindpassasjer ble laget</a> i forbindelse med at
 731 filmene NRK la ut ikke var tilgjengelig i et
 732 <a href="http://www.digistan.org/open-standard:definition">fritt og
 733 åpent format</a>.  Dette var det jeg skrev publiserte der 07:39.</p>
 734
 735 <p><blockquote>
 736 <p>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
 737 nedlasting.  Mange av oss som kan mer enn gjennomsnittet om systemer
 738 som dette, vet at det stort sett er mulig å lure ut ting med den
 739 nødvendige forkunnskapen."</p>
 740
 741 <p>Haha.  Å streame innhold er det samme som å laste ned innhold, så å
 742 beskytte en stream mot nedlasting er ikke mulig.  Å skrive noe slikt
 743 er å forlede leseren.</p>
 744
 745 <p>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
 746 vil tillate streaming men ikke nedlasting meningsløs.</p>
 747
 748 <p>Anbefaler forresten å lese
 749 <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>
 750 om hva som ville være konsekvensen hvis digitale avspillingssperrer
 751 (DRM) fungerte.  Det gjør de naturligvis ikke teknisk - det er jo
 752 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
 753 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
 754 opp under.</p>
 755 </blockquote></p>
 756
 757 <p>Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
 758 NRKBeta:</p>
 759
 760 <p><blockquote>
 761 <p>From: Anders Hofseth &lt;XXX@gmail.com>
 762 <br>To: "pere@hungry.com" &lt;pere@hungry.com>
 763 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>, Jon Ståle Carlsen &lt;XXX@gmail.com>, Henrik Lied &lt;XXX@gmail.com>
 764 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
 765 <br>Date: Sat, 30 Oct 2010 07:58:44 +0200</p>
 766
 767 <p>Hei Petter.
 768 <br>Det du forsøker dra igang er egentlig en interessant diskusjon,
 769 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
 770 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
 771 særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
 772
 773 <p>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
 774 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
 775 konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
 776
 777 <p>Med hilsen,
 778 <br>-anders</p>
 779
 780 <p>Ring meg om noe er uklart: 95XXXXXXX</p>
 781 </blockquote></p>
 782
 783 <p>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
 784 over følgende svar.  I og med at debatten er fjernet fra NRK Betas
 785 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
 786 Har fjernet epostadresser og telefonnummer til de involverte, for å
 787 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.</p>
 788
 789 <p><blockquote>
 790 <p>From: Petter Reinholdtsen &lt;pere@hungry.com>
 791 <br>To: Anders Hofseth &lt;XXX@gmail.com>
 792 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>,
 793 <br>        Jon Ståle Carlsen &lt;XXX@gmail.com>,
 794 <br>        Henrik Lied &lt;XXX@gmail.com>
 795 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
 796 <br>Date: Sat, 30 Oct 2010 08:24:34 +0200</p>
 797
 798 <p>[Anders Hofseth]
 799 <br>> Hei Petter.</p>
 800
 801 <p>Hei.</p>
 802
 803 <p>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
 804 <br>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
 805 <br>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
 806 <br>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
 807
 808 <p>Godt å se at du er enig i at dette er en interessant diskusjon.  Den
 809 vil nok fortsette en stund til.  :)</p>
 810
 811 <p>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
 812 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
 813 fortsette å legge ut arkivmateriale.</p>
 814
 815 <p>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
 816 faktum, som er at streaming er det samme som nedlasting, og at innhold
 817 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
 818 det.</p>
 819
 820 <p>Det du sier er jo at klarering av arkivmateriale for publisering på
 821 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
 822 Det er ikke et argument som holder vann. :)</p>
 823
 824 <p>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
 825 <br>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
 826 <br>> konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
 827
 828 <p>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
 829 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
 830 mot de som vil låse kulturen inne.  Jeg synes det er en skam at NRK
 831 godtar å forlede publikum.  Ville heller at NRK krever at innhold som
 832 skal sendes skal være uten bruksbegresninger og kan publiseres i
 833 formater som heller ikke har bruksbegresninger (bruksbegresningene til
 834 H.264 burde få varselbjellene i NRK til å ringe).</p>
 835
 836 <p>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
 837 påstander om at "streaming beskytter mot nedlasting" som bare er egnet
 838 til å bygge opp om en myte som er skadelig for samfunnet som helhet.</p>
 839
 840 <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
 841 titt på
 842 &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> >.
 843 for å se hva slags bruksbegresninger H.264 innebærer.</p>
 844
 845 <p>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
 846 kan brukes før rettighetshaverene også innser at de er med på å skade
 847 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
 848 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
 849 langt på overtid.</p>
 850
 851 <p>> Ring meg om noe er uklart: XXX</p>
 852
 853 <p>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
 854 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
 855 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
 856 for videre diskusjon hadde dere i mine øyne kommet fra det med
 857 ryggraden på plass.</p>
 858
 859 <p>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.</p>
 860
 861 <p>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
 862 &lt;URL: <a href="http://www.archive.org/details/CopyingIsNotTheft">http://www.archive.org/details/CopyingIsNotTheft</a> > og
 863 &lt;URL: <a href="http://patentabsurdity.com/">http://patentabsurdity.com/</a> > hadde vært noe å kringkaste på
 864 NRK1. :)</p>
 865
 866 <p>Vennlig hilsen,
 867 <br>--
 868 <br>Petter Reinholdtsen</p>
 869
 870       </div>
 871       <div class="tags">
 872
 873
 874         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 875
 876
 877       </div>
 878     </div>
 879     <div class="padding"></div>
 880
 881     <div class="entry">
 882       <div class="title">
 883         <a href="http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html">Why isn't Debian Edu using VLC?</a>
 884       </div>
 885       <div class="date">
 886         27th November 2010
 887       </div>
 888       <div class="body">
 889         <p>In the latest issue of Linux Journal, the readers choices were
 890 presented, and the winner among the multimedia player were VLC.
 891 Personally, I like VLC, and it is my player of choice when I first try
 892 to play a video file or stream.  Only if VLC fail will I drag out
 893 gmplayer to see if it can do better.  The reason is mostly the failure
 894 model and trust.  When VLC fail, it normally pop up a error message
 895 reporting the problem.  When mplayer fail, it normally segfault or
 896 just hangs.  The latter failure mode drain my trust in the program.<p>
 897
 898 <p>But even if VLC is my player of choice, we have choosen to use
 899 mplayer in <a href="http://www.skolelinux.org/">Debian
 900 Edu/Skolelinux</a>.  The reason is simple.  We need a good browser
 901 plugin to play web videos seamlessly, and the VLC browser plugin is
 902 not very good.  For example, it lack in-line control buttons, so there
 903 is no way for the user to pause the video.  Also, when I
 904 <a href="http://wiki.debian.org/DebianEdu/BrowserMultimedia">last
 905 tested the browser plugins</a> available in Debian, the VLC plugin
 906 failed on several video pages where mplayer based plugins worked.  If
 907 the browser plugin for VLC was as good as the gecko-mediaplayer
 908 package (which uses mplayer), we would switch.</P>
 909
 910 <p>While VLC is a good player, its user interface is slightly
 911 annoying.  The most annoying feature is its inconsistent use of
 912 keyboard shortcuts.  When the player is in full screen mode, its
 913 shortcuts are different from when it is playing the video in a window.
 914 For example, space only work as pause when in full screen mode.  I
 915 wish it had consisten shortcuts and that space also would work when in
 916 window mode.  Another nice shortcut in gmplayer is [enter] to restart
 917 the current video.  It is very nice when playing short videos from the
 918 web and want to restart it when new people arrive to have a look at
 919 what is going on.</p>
 920
 921       </div>
 922       <div class="tags">
 923
 924
 925         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 926
 927
 928       </div>
 929     </div>
 930     <div class="padding"></div>
 931
 932     <div class="entry">
 933       <div class="title">
 934         <a href="http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">Is Ogg Theora a free and open standard?</a>
 935       </div>
 936       <div class="date">
 937         25th December 2010
 938       </div>
 939       <div class="body">
 940         <p><a href="http://www.digistan.org/open-standard:definition">The
 941 Digistan definition</a> of a free and open standard reads like this:</p>
 942
 943 <blockquote>
 944
 945 <p>The Digital Standards Organization defines free and open standard
 946 as follows:</p>
 947
 948 <ol>
 949
 950 <li>A free and open standard is immune to vendor capture at all stages
 951 in its life-cycle. Immunity from vendor capture makes it possible to
 952 freely use, improve upon, trust, and extend a standard over time.</li>
 953
 954 <li>The standard is adopted and will be maintained by a not-for-profit
 955 organisation, and its ongoing development occurs on the basis of an
 956 open decision-making procedure available to all interested
 957 parties.</li>
 958
 959 <li>The standard has been published and the standard specification
 960 document is available freely. It must be permissible to all to copy,
 961 distribute, and use it freely.</li>
 962
 963 <li>The patents possibly present on (parts of) the standard are made
 964 irrevocably available on a royalty-free basis.</li>
 965
 966 <li>There are no constraints on the re-use of the standard.</li>
 967
 968 </ol>
 969
 970 <p>The economic outcome of a free and open standard, which can be
 971 measured, is that it enables perfect competition between suppliers of
 972 products based on the standard.</p>
 973 </blockquote>
 974
 975 <p>For a while now I have tried to figure out of Ogg Theora is a free
 976 and open standard according to this definition.  Here is a short
 977 writeup of what I have been able to gather so far.  I brought up the
 978 topic on the Xiph advocacy mailing list
 979 <a href="http://lists.xiph.org/pipermail/advocacy/2009-July/001632.html">in
 980 July 2009</a>, for those that want to see some background information.
 981 According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
 982 the Ogg Theora specification fulfils the Digistan definition.</p>
 983
 984 <p><strong>Free from vendor capture?</strong></p>
 985
 986 <p>As far as I can see, there is no single vendor that can control the
 987 Ogg Theora specification.  It can be argued that the
 988 <a href="http://www.xiph.org/">Xiph foundation</A> is such vendor, but
 989 given that it is a non-profit foundation with the expressed goal
 990 making free and open protocols and standards available, it is not
 991 obvious that this is a real risk.  One issue with the Xiph
 992 foundation is that its inner working (as in board member list, or who
 993 control the foundation) are not easily available on the web.  I've
 994 been unable to find out who is in the foundation board, and have not
 995 seen any accounting information documenting how money is handled nor
 996 where is is spent in the foundation.  It is thus not obvious for an
 997 external observer who control The Xiph foundation, and for all I know
 998 it is possible for a single vendor to take control over the
 999 specification.  But it seem unlikely.</p>
1000
1001 <p><strong>Maintained by open not-for-profit organisation?</strong></p>
1002
1003 <p>Assuming that the Xiph foundation is the organisation its web pages
1004 claim it to be, this point is fulfilled.  If Xiph foundation is
1005 controlled by a single vendor, it isn't, but I have not found any
1006 documentation indicating this.</p>
1007
1008 <p>According to
1009 <a href="http://media.hiof.no/diverse/fad/rapport_4.pdf">a report</a>
1010 prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
1011 government, the Xiph foundation is a non-commercial organisation and
1012 the development process is open, transparent and non-Discrimatory.
1013 Until proven otherwise, I believe it make most sense to believe the
1014 report is correct.</p>
1015
1016 <p><strong>Specification freely available?</strong></p>
1017
1018 <p>The specification for the <a href="http://www.xiph.org/ogg/doc/">Ogg
1019 container format</a> and both the
1020 <a href="http://www.xiph.org/vorbis/doc/">Vorbis</a> and
1021 <a href="http://theora.org/doc/">Theora</a> codeces are available on
1022 the web.  This are the terms in the Vorbis and Theora specification:
1023
1024 <blockquote>
1025
1026 Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
1027 specifications, whether in private, public, or corporate
1028 capacity. However, the Xiph.Org Foundation and the Ogg project reserve
1029 the right to set the Ogg [Vorbis/Theora] specification and certify
1030 specification compliance.
1031
1032 </blockquote>
1033
1034 <p>The Ogg container format is specified in IETF
1035 <a href="http://www.xiph.org/ogg/doc/rfc3533.txt">RFC 3533</a>, and
1036 this is the term:<p>
1037
1038 <blockquote>
1039
1040 <p>This document and translations of it may be copied and furnished to
1041 others, and derivative works that comment on or otherwise explain it
1042 or assist in its implementation may be prepared, copied, published and
1043 distributed, in whole or in part, without restriction of any kind,
1044 provided that the above copyright notice and this paragraph are
1045 included on all such copies and derivative works.  However, this
1046 document itself may not be modified in any way, such as by removing
1047 the copyright notice or references to the Internet Society or other
1048 Internet organizations, except as needed for the purpose of developing
1049 Internet standards in which case the procedures for copyrights defined
1050 in the Internet Standards process must be followed, or as required to
1051 translate it into languages other than English.</p>
1052
1053 <p>The limited permissions granted above are perpetual and will not be
1054 revoked by the Internet Society or its successors or assigns.</p>
1055 </blockquote>
1056
1057 <p>All these terms seem to allow unlimited distribution and use, an
1058 this term seem to be fulfilled.  There might be a problem with the
1059 missing permission to distribute modified versions of the text, and
1060 thus reuse it in other specifications.  Not quite sure if that is a
1061 requirement for the Digistan definition.</p>
1062
1063 <p><strong>Royalty-free?</strong></p>
1064
1065 <p>There are no known patent claims requiring royalties for the Ogg
1066 Theora format.
1067 <a href="http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65782">MPEG-LA</a>
1068 and
1069 <a href="http://yro.slashdot.org/story/10/04/30/237238/Steve-Jobs-Hints-At-Theora-Lawsuit">Steve
1070 Jobs</a> in Apple claim to know about some patent claims (submarine
1071 patents) against the Theora format, but no-one else seem to believe
1072 them.  Both Opera Software and the Mozilla Foundation have looked into
1073 this and decided to implement Ogg Theora support in their browsers
1074 without paying any royalties.  For now the claims from MPEG-LA and
1075 Steve Jobs seem more like FUD to scare people to use the H.264 codec
1076 than any real problem with Ogg Theora.</p>
1077
1078 <p><strong>No constraints on re-use?</strong></p>
1079
1080 <p>I am not aware of any constraints on re-use.</p>
1081
1082 <p><strong>Conclusion</strong></p>
1083
1084 <p>3 of 5 requirements seem obviously fulfilled, and the remaining 2
1085 depend on the governing structure of the Xiph foundation.  Given the
1086 background report used by the Norwegian government, I believe it is
1087 safe to assume the last two requirements are fulfilled too, but it
1088 would be nice if the Xiph foundation web site made it easier to verify
1089 this.</p>
1090
1091 <p>It would be nice to see other analysis of other specifications to
1092 see if they are free and open standards.</p>
1093
1094       </div>
1095       <div class="tags">
1096
1097
1098         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
1099
1100
1101       </div>
1102     </div>
1103     <div class="padding"></div>
1104
1105     <div class="entry">
1106       <div class="title">
1107         <a href="http://people.skolelinux.org/pere/blog/Chrome_plan_to_drop_H_264_support_for_HTML5__lt_video_gt_.html">Chrome plan to drop H.264 support for HTML5 &lt;video&gt;</a>
1108       </div>
1109       <div class="date">
1110         12th January 2011
1111       </div>
1112       <div class="body">
1113         <p>Today I discovered
1114 <a href="http://www.digi.no/860070/google-dropper-h264-stotten-i-chrome">via
1115 digi.no</a> that the Chrome developers, in a surprising announcement,
1116 <a href="http://blog.chromium.org/2011/01/html-video-codec-support-in-chrome.html">yesterday
1117 announced</a> plans to drop H.264 support for HTML5 &lt;video&gt; in
1118 the browser.  The argument used is that H.264 is not a "completely
1119 open" codec technology.  If you believe H.264 was free for everyone
1120 to use, I recommend having a look at the essay
1121 "<a href="http://webmink.com/essays/h-264/">H.264 – Not The Kind Of
1122 Free That Matters</a>".  It is not free of cost for creators of video
1123 tools, nor those of us that want to publish on the Internet, and the
1124 terms provided by MPEG-LA excludes free software projects from
1125 licensing the patents needed for H.264.  Some background information
1126 on the Google announcement is available from
1127 <a href="http://www.osnews.com/story/24243/Google_To_Drop_H264_Support_from_Chrome">OSnews</a>.
1128 A good read. :)</p>
1129
1130 <p>Personally, I believe it is great that Google is taking a stand to
1131 promote equal terms for everyone when it comes to video publishing on
1132 the Internet.  This can only be done by publishing using free and open
1133 standards, which is only possible if the web browsers provide support
1134 for these free and open standards.  At the moment there seem to be two
1135 camps in the web browser world when it come to video support.  Some
1136 browsers support H.264, and others support
1137 <a href="http://www.theora.org/">Ogg Theora</a> and
1138 <a href="http://www.webmproject.org/">WebM</a>
1139 (<a href="http://www.diracvideo.org/">Dirac</a> is not really an option
1140 yet), forcing those of us that want to publish video on the Internet
1141 and which can not accept the terms of use presented by MPEG-LA for
1142 H.264 to not reach all potential viewers.
1143 Wikipedia keep <a href="http://en.wikipedia.org/wiki/HTML5_video">an
1144 updated summary</a> of the current browser support.</p>
1145
1146 <p>Not surprising, several people would prefer Google to keep
1147 promoting H.264, and John Gruber
1148 <a href="http://daringfireball.net/2011/01/simple_questions">presents
1149 the mind set</a> of these people quite well.  His rhetorical questions
1150 provoked a reply from Thom Holwerda with another set of questions
1151 <a href="http://www.osnews.com/story/24245/10_Questions_for_John_Gruber_Regarding_H_264_WebM">presenting
1152 the issues with H.264</a>. Both are worth a read.</p>
1153
1154 <p>Some argue that if Google is dropping H.264 because it isn't free,
1155 they should also drop support for the Adobe Flash plugin.  This
1156 argument was covered by Simon Phipps in
1157 <a href="http://blogs.computerworlduk.com/simon-says/2011/01/google-and-h264---far-from-hypocritical/index.htm">todays
1158 blog post</a>, which I find to put the issue in context.  To me it
1159 make perfect sense to drop native H.264 support for HTML5 in the
1160 browser while still allowing plugins.</p>
1161
1162 <p>I suspect the reason this announcement make so many people protest,
1163 is that all the users and promoters of H.264 suddenly get an uneasy
1164 feeling that they might be backing the wrong horse.  A lot of TV
1165 broadcasters have been moving to H.264 the last few years, and a lot
1166 of money has been invested in hardware based on the belief that they
1167 could use the same video format for both broadcasting and web
1168 publishing.  Suddenly this belief is shaken.</p>
1169
1170 <p>An interesting question is why Google is doing this.  While the
1171 presented argument might be true enough, I believe Google would only
1172 present the argument if the change make sense from a business
1173 perspective.  One reason might be that they are currently negotiating
1174 with MPEG-LA over royalties or usage terms, and giving MPEG-LA the
1175 feeling that dropping H.264 completely from Chroome, Youtube and
1176 Google Video would improve the negotiation position of Google.
1177 Another reason might be that Google want to save money by not having
1178 to pay the video tax to MPEG-LA at all, and thus want to move to a
1179 video format not requiring royalties at all.  A third reason might be
1180 that the Chrome development team simply want to avoid the
1181 Chrome/Chromium split to get more help with the development of Chrome.
1182 I guess time will tell.</p>
1183
1184 <p>Update 2011-01-15: The Google Chrome team provided
1185 <a href="http://blog.chromium.org/2011/01/more-about-chrome-html-video-codec.html">more
1186 background and information on the move</a> it a blog post yesterday.</p>
1187
1188       </div>
1189       <div class="tags">
1190
1191
1192         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
1193
1194
1195       </div>
1196     </div>
1197     <div class="padding"></div>
1198
1199     <div class="entry">
1200       <div class="title">
1201         <a href="http://people.skolelinux.org/pere/blog/The_video_format_most_supported_in_web_browsers_.html">The video format most supported in web browsers?</a>
1202       </div>
1203       <div class="date">
1204         16th January 2011
1205       </div>
1206       <div class="body">
1207         <p>The video format struggle on the web continues, and the three
1208 contenders seem to be Ogg Theora, H.264 and WebM.  Most video sites
1209 seem to use H.264, while others use Ogg Theora.  Interestingly enough,
1210 the comments I see give me the feeling that a lot of people believe
1211 H.264 is the most supported video format in browsers, but according to
1212 the Wikipedia article on
1213 <a href="http://en.wikipedia.org/wiki/HTML5_video">HTML5 video</a>,
1214 this is not true.  Check out the nice table of supprted formats in
1215 different browsers there.  The format supported by most browsers is
1216 Ogg Theora, supported by released versions of Mozilla Firefox, Google
1217 Chrome, Chromium, Opera, Konqueror, Epiphany, Origyn Web Browser and
1218 BOLT browser, while not supported by Internet Explorer nor Safari.
1219 The runner up is WebM supported by released versions of Google Chrome
1220 Chromium Opera and Origyn Web Browser, and test versions of Mozilla
1221 Firefox.  H.264 is supported by released versions of Safari, Origyn
1222 Web Browser and BOLT browser, and the test version of Internet
1223 Explorer.  Those wanting Ogg Theora support in Internet Explorer and
1224 Safari can install plugins to get it.</p>
1225
1226 <p>To me, the simple conclusion from this is that to reach most users
1227 without any extra software installed, one uses Ogg Theora with the
1228 HTML5 video tag.   Of course to reach all those without a browser
1229 handling HTML5, one need fallback mechanisms.  In
1230 <a href="http://www.nuug.no/">NUUG</a>, we provide first fallback to a
1231 plugin capable of playing MPEG1 video, and those without such support
1232 we have a second fallback to the Cortado java applet playing Ogg
1233 Theora.  This seem to work quite well, as can be seen in an <a
1234 href="http://www.nuug.no/aktiviteter/20110111-semantic-web/">example
1235 from last week</a>.</p>
1236
1237 <p>The reason Ogg Theora is the most supported format, and H.264 is
1238 the least supported is simple.  Implementing and using H.264
1239 require royalty payment to MPEG-LA, and the terms of use from MPEG-LA
1240 are incompatible with free software licensing.  If you believed H.264
1241 was without royalties and license terms, check out
1242 "<a href="http://webmink.com/essays/h-264/">H.264 – Not The Kind Of
1243 Free That Matters</a>" by Simon Phipps.</p>
1244
1245 <p>A incomplete list of sites providing video in Ogg Theora is
1246 available from
1247 <a href="http://wiki.xiph.org/index.php/List_of_Theora_videos">the
1248 Xiph.org wiki</a>, if you want to have a look.  I'm not aware of a
1249 similar list for WebM nor H.264.</p>
1250
1251 <p>Update 2011-01-16 09:40: A question from Tollef on IRC made me
1252 realise that I failed to make it clear enough this text is about the
1253 &lt;video&gt; tag support in browsers and not the video support
1254 provided by external plugins like the Flash plugins.</p>
1255
1256       </div>
1257       <div class="tags">
1258
1259
1260         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
1261
1262
1263       </div>
1264     </div>
1265     <div class="padding"></div>
1266
1267     <div class="entry">
1268       <div class="title">
1269         <a href="http://people.skolelinux.org/pere/blog/Gnash_enteres_Google_Summer_of_Code_2011.html">Gnash enteres Google Summer of Code 2011</a>
1270       </div>
1271       <div class="date">
1272          6th April 2011
1273       </div>
1274       <div class="body">
1275         <p><a href="http://www.getgnash.org/">The Gnash project</a> is still
1276 the most promising solution for a Free Software Flash implementation.
1277 A few days ago the project
1278 <a href="http://lists.gnu.org/archive/html/gnash-dev/2011-04/msg00011.html">announced</a>
1279 that it will participate in Google Summer of Code.  I hope many
1280 students apply, and that some of them succeed in getting AVM2 support
1281 into Gnash.</p>
1282
1283       </div>
1284       <div class="tags">
1285
1286
1287         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1288
1289
1290       </div>
1291     </div>
1292     <div class="padding"></div>
1293
1294     <div class="entry">
1295       <div class="title">
1296         <a href="http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html">Ripping problematic DVDs using dvdbackup and genisoimage</a>
1297       </div>
1298       <div class="date">
1299         17th September 2011
1300       </div>
1301       <div class="body">
1302         <p>For convenience, I want to store copies of all my DVDs on my file
1303 server.  It allow me to save shelf space flat while still having my
1304 movie collection easily available.  It also make it possible to let
1305 the kids see their favourite DVDs without wearing the physical copies
1306 down.  I prefer to store the DVDs as ISOs to keep the DVD menu and
1307 subtitle options intact.  It also ensure that the entire film is one
1308 file on the disk.  As this is for personal use, the ripping is
1309 perfectly legal here in Norway.</p>
1310
1311 <p>Normally I rip the DVDs using dd like this:</p>
1312
1313 <blockquote><pre>
1314 #!/bin/sh
1315 # apt-get install lsdvd
1316 title=$(lsdvd 2>/dev/null|awk '/Disc Title: / {print $3}')
1317 dd if=/dev/dvd of=/storage/dvds/$title.iso bs=1M
1318 </pre></blockquote>
1319
1320 <p>But some DVDs give a input/output error when I read it, and I have
1321 been looking for a better alternative.  I have no idea why this I/O
1322 error occur, but suspect my DVD drive, the Linux kernel driver or
1323 something fishy with the DVDs in question.  Or perhaps all three.</p>
1324
1325 <p>Anyway, I believe I found a solution today using dvdbackup and
1326 genisoimage.  This script gave me a working ISO for a problematic
1327 movie by first extracting the DVD file system and then re-packing it
1328 back as an ISO.
1329
1330 <blockquote><pre>
1331 #!/bin/sh
1332 # apt-get install lsdvd dvdbackup genisoimage
1333 set -e
1334 tmpdir=/storage/dvds/
1335 title=$(lsdvd 2>/dev/null|awk '/Disc Title: / {print $3}')
1336 dvdbackup -i /dev/dvd -M -o $tmpdir -n$title
1337 genisoimage -dvd-video -o $tmpdir/$title.iso $tmpdir/$title
1338 rm -rf $tmpdir/$title
1339 </pre></blockquote>
1340
1341 <p>Anyone know of a better way available in Debian/Squeeze?</p>
1342
1343 <p>Update 2011-09-18: I got a tip from Konstantin Khomoutov about the
1344 readom program from the wodim package.  It is specially written to
1345 read optical media, and is called like this: <tt>readom dev=/dev/dvd
1346 f=image.iso</tt>.  It got 6 GB along with the problematic Cars DVD
1347 before it failed, and failed right away with a Timmy Time DVD.</p>
1348
1349 <p>Next, I got a tip from Bastian Blank about
1350 <a href="http://bblank.thinkmo.de/blog/new-software-python-dvdvideo">his
1351 program python-dvdvideo</a>, which seem to be just what I am looking
1352 for.  Tested it with my problematic Timmy Time DVD, and it succeeded
1353 creating a ISO image.  The git source built and installed just fine in
1354 Squeeze, so I guess this will be my tool of choice in the future.</p>
1355
1356       </div>
1357       <div class="tags">
1358
1359
1360         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
1361
1362
1363       </div>
1364     </div>
1365     <div class="padding"></div>
1366
1367     <div class="entry">
1368       <div class="title">
1369         <a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html">Hvordan enkelt laste ned filmer fra NRK</a>
1370       </div>
1371       <div class="date">
1372          5th November 2011
1373       </div>
1374       <div class="body">
1375         <p>Ofte har jeg lyst til å laste ned et innslag fra NRKs nettsted for
1376 å se det senere når jeg ikke er på nett, eller for å ha det
1377 tilgjengelig når jeg en gang i fremtiden ønsker å referere til
1378 innslaget selv om NRK har fjernet det fra sine nettsider.  I dag fant
1379 jeg et lite script som fikser jobben.</p>
1380
1381 <p>Scriptet er laget av Jan Henning Thorsen og tilgjengelig fra
1382 <a href="http://jhthorsen.github.com/snippets/nrk-downloader/">github</a>,
1383 og gjør det veldig enkelt å laste ned.  Kjør <tt>nrk-downloader.sh
1384 http://www1.nrk.no/nett-tv/klipp/582810</tt> for å hente ned et enkelt
1385 innslag eller <tt>nrk-downloader.sh
1386 http://www1.nrk.no/nett-tv/kategori/3521</tt> for å laste ned alle
1387 episodene i en serie.</p>
1388
1389 <p>Det er ikke rakettforskning å laste ned NRK-"strømmer", og
1390 tidligere gjorde jeg dette manuelt med mplayer.  Scriptet til
1391 Hr. Thorsen gjør det raskere og enklere for meg, men jeg vil ikke si
1392 at det er en revolusjonerende løsning.  Jeg mener jo fortsatt at
1393 påstanden fra NRKs ansatte om at det er
1394 <a href="http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html">vesensforskjellig
1395 å legge tilgjengelig for nedlasting og for streaming</a> er
1396 meningsløs.</p>
1397
1398       </div>
1399       <div class="tags">
1400
1401
1402         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1403
1404
1405       </div>
1406     </div>
1407     <div class="padding"></div>
1408
1409     <div class="entry">
1410       <div class="title">
1411         <a href="http://people.skolelinux.org/pere/blog/Stopmotion_for_making_stop_motion_animations_on_Linux___reloaded.html">Stopmotion for making stop motion animations on Linux - reloaded</a>
1412       </div>
1413       <div class="date">
1414          3rd March 2012
1415       </div>
1416       <div class="body">
1417         <p>Many years ago, the <a href="http://www.skolelinux.org/">Skolelinux
1418 / Debian Edu project</a> initiated a student project to create a tool
1419 for making stop motion movies.  The proposal came from a teacher
1420 needing such tool on Skolelinux.  The project, called "stopmotion",
1421 was manned by two extraordinary students and won a school award and a
1422 national aware with this great project.  The project was initiated and
1423 mentored by Herman Robak, and manned by the students Bjørn Erik Nilsen
1424 and Fredrik Berg Kjølstad.  They got in touch with people at Aardman
1425 Animation studio and received feedback on how professionals would like
1426 such stopmotion tool to work, and the end result was and is used by
1427 animators around the globe.  But as is usual after studying, both got
1428 jobs and went elsewhere, and did not have time to properly tend to the
1429 project, and it has been lingering for a few years now.  Until last
1430 year...</p>
1431
1432 <p>Last year some of the users got together with Herman, and moved the
1433 project to Sourceforge and in effect restarted the project under a new
1434 name,
1435 <a href="http://sourceforge.net/projects/linuxstopmotion/">linuxstopmotion</a>.
1436 The name change was done to make it possible to find the project using
1437 Internet search engines (try to search for 'stopmotion' to see what I
1438 mean). I've been following
1439 <a href="https://lists.sourceforge.net/lists/listinfo/linuxstopmotion-community">the
1440 mailing list</a> and the improvement already in place and planned for
1441 the future is encouraging.  If you want to make stop motion movies.
1442 Check it out. :)</p>
1443
1444       </div>
1445       <div class="tags">
1446
1447
1448         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
1449
1450
1451       </div>
1452     </div>
1453     <div class="padding"></div>
1454
1455     <p style="text-align: right;"><a href="video.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
1456     <div id="sidebar">
1457
1458
1459
1460 <h2>Archive</h2>
1461 <ul>
1462
1463 <li>2012
1464 <ul>
1465
1466 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1467
1468 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1469
1470 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1471
1472 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (4)</a></li>
1473
1474 </ul></li>
1475
1476 <li>2011
1477 <ul>
1478
1479 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1480
1481 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1482
1483 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1484
1485 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1486
1487 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1488
1489 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1490
1491 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1492
1493 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1494
1495 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1496
1497 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1498
1499 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1500
1501 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1502
1503 </ul></li>
1504
1505 <li>2010
1506 <ul>
1507
1508 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1509
1510 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1511
1512 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1513
1514 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1515
1516 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1517
1518 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1519
1520 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1521
1522 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1523
1524 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1525
1526 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1527
1528 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1529
1530 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1531
1532 </ul></li>
1533
1534 <li>2009
1535 <ul>
1536
1537 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1538
1539 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1540
1541 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1542
1543 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1544
1545 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1546
1547 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1548
1549 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1550
1551 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1552
1553 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1554
1555 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1556
1557 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1558
1559 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1560
1561 </ul></li>
1562
1563 <li>2008
1564 <ul>
1565
1566 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1567
1568 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1569
1570 </ul></li>
1571
1572 </ul>
1573
1574
1575
1576 <h2>Tags</h2>
1577 <ul>
1578
1579  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1580
1581  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1582
1583  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1584
1585  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (2)</a></li>
1586
1587  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (12)</a></li>
1588
1589  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1590
1591  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (54)</a></li>
1592
1593  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (97)</a></li>
1594
1595  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (7)</a></li>
1596
1597  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (121)</a></li>
1598
1599  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (15)</a></li>
1600
1601  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1602
1603  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (22)</a></li>
1604
1605  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (15)</a></li>
1606
1607  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
1608
1609  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (4)</a></li>
1610
1611  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1612
1613  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (14)</a></li>
1614
1615  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (156)</a></li>
1616
1617  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (120)</a></li>
1618
1619  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1620
1621  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (24)</a></li>
1622
1623  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (46)</a></li>
1624
1625  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1626
1627  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1628
1629  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1630
1631  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (4)</a></li>
1632
1633  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1634
1635  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1636
1637  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (23)</a></li>
1638
1639  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1640
1641  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (24)</a></li>
1642
1643  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (1)</a></li>
1644
1645  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (3)</a></li>
1646
1647  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (9)</a></li>
1648
1649  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (6)</a></li>
1650
1651  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (23)</a></li>
1652
1653  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (1)</a></li>
1654
1655  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (18)</a></li>
1656
1657 </ul>
1658
1659
1660     </div>
1661     <p style="text-align: right">
1662  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.4</a>
1663 </p>
1664
1665   </body>
1666 </html>