[Debconf-video-commits] r274 - in talks: . DebConf8
holger at alioth.debian.org
holger at alioth.debian.org
Mon Feb 2 11:57:49 UTC 2009
Author: holger
Date: 2009-02-02 11:57:49 +0000 (Mon, 02 Feb 2009)
New Revision: 274
Added:
talks/DebConf8/
talks/DebConf8/dc8-videoteam_abs.txt
talks/DebConf8/dc8-videoteam_outline.txt
Removed:
talks/dc8-videoteam_abs.txt
talks/dc8-videoteam_outline.txt
Log:
move stuff into subdir for dc8
Copied: talks/DebConf8/dc8-videoteam_abs.txt (from rev 249, talks/dc8-videoteam_abs.txt)
===================================================================
--- talks/DebConf8/dc8-videoteam_abs.txt (rev 0)
+++ talks/DebConf8/dc8-videoteam_abs.txt 2009-02-02 11:57:49 UTC (rev 274)
@@ -0,0 +1,41 @@
+ ABSTRACT
+
+Since 2005, the talks at Debconf have been recorded on video, to be
+published online. Beginning in 2006, talks have also been streamed
+live. One of the goals is to get recordings in high quality online
+immediately, with little or no post-production work. The video
+switcher dvswitch, realized in software, and a disk-based recording
+workflow is bringing us closer to that goal. Tape is still used as
+backup in case of failures, but we expect those to become rarer as
+the system matures. A large part of the post production work is
+restoring failed recordings.
+
+Dvswitch was developed by Ben Hutchings just in time for the Debconf7
+in Edinburgh. It enabled a multi-camera live production using cheap
+cameras and modest laptops. The laptops relays DV streams over
+TCP/IP. This avoids any degradation due to long cable stretches, and
+makes cabling cheap and convenient. The output is DV straight from
+the cameras, producing a very crisp master video.
+
+Dvswitch works with sources and sinks. The sources send video from a
+file or a firewire port to a listening instance of dvswitch, which can
+run on a remote machine.
+dvswitch listens to several sources and displays a scaled down black
+and white preview image of each one. One of the sources is displayed
+at full resolution in colour; this is the outgoing stream, which is
+sent to the listening sinks. Each sink may send the stream to disk or
+to an encoder for live streaming. It is common to do both; store the
+raw master to disk, and forward the master to an encoder, and
+subsequently to a streaming server.
+
+While dvswitch saves us a bundle in hardware, the video team is still
+heavy on manpower. Remotely operated cameras would help, and we are
+still looking for affordable solutions that work well on Linux.
+
+
+ The talk will cover the hardware, software and manpower required for
+a typical dvswitch usecase. Some caveats and challenges regarding
+sound, lighting and rigging will be discussed. A live demonstration
+of dvswitch in use will be given. We would also like to offer
+rehearsal sessions with the demo rig for those who are interested.
+
Property changes on: talks/DebConf8/dc8-videoteam_abs.txt
___________________________________________________________________
Name: svn:mergeinfo
+
Copied: talks/DebConf8/dc8-videoteam_outline.txt (from rev 249, talks/dc8-videoteam_outline.txt)
===================================================================
--- talks/DebConf8/dc8-videoteam_outline.txt (rev 0)
+++ talks/DebConf8/dc8-videoteam_outline.txt 2009-02-02 11:57:49 UTC (rev 274)
@@ -0,0 +1,97 @@
+ The video team,
+ people, hardware and software
+
+
+ People
+
+We would like to bind up as few people as possible in the video team.
+Our activity is a service, not a playful hacking thing.
+
+Post production takes for ever, if it ever happens. We strive to get
+as much as possible done instantly.
+
+
+ Hardware
+
+The hardware should be cheap and light. Commodity hardware is more
+convenient than specialty hardware. Two non-commodity pieces that we
+now consider "must have": Scan converter (VGA to DV) and wireless
+mic. The laptops and the DV cameras can be borrowed by/from participants
+or the local team.
+
+
+ Software
+
+The software should be a minimal set of packages running on Debian
+Stable. Dvswitch fits that bill.
+
+
+ TODO
+
+Talkback: The camera operators should have headsets, and receive oral
+instructions from the mixer operator/producer.
+
+Tally lights: The cameras should have a red lamp telling everyone
+(especially the camera operator) when they are "on".
+
+
+ Caveats
+
+Lighting problems. Good room lighting should provide a comfortable light
+level and adequate light for cheap cameras, and still not wash out the
+projector screen. More often than not, this is not the case.
+
+Lighting workarounds. Spot light on the speaker, turn off the rest
+during the talk. Turn the lights on again for the Q&A session,
+assuming the screen won't be much needed then.
+
+Recording the sound from the audience takes some care. We want
+reactions from the audience to be audible, but general murmur and air
+condition noise should be cut out.
+
+The crowd cam should see _everyone_ in the audience. This may require
+a tall platform, or (fancy!) a jib arm.
+
+
+
+ *** What the software does
+
+ * dvsource
+
+Grabs video from a DV camera over firewire, and sends it over TCP to
+the *dvswitch*. Dvswitch may run on a different computer, usually
+nearby.
+
+
+ * dvswitch
+
+The heart of the system is dvswitch.
+
+
+ * dvsink
+
+Receives the output from dvswitch
+
+
+ *** Live demo
+
+* Show the hardware
+ Laptops
+ Cameras, tripods, firewire
+ Scan converter
+ Switch, ethernet cable
+ Sound mixer
+
+* Show the setup
+ Speaker cam, head mic
+ Crowd cam, crowd mic
+ Cabling (gaffa, gaffa, gaffa)
+
+* Demonstrate editing
+ Recursive video (gag)
+ Cutaways (let the cam-op frame the shot)
+ Eye direction (when two shots won't intercut well...)
+ Sound level (open and fade out crowd mic)
+ PiP? Text overlays?
+ Disorienting each other and the stream team (gag)
+ "Do you have goatse there?"
Property changes on: talks/DebConf8/dc8-videoteam_outline.txt
___________________________________________________________________
Name: svn:mergeinfo
+
Deleted: talks/dc8-videoteam_abs.txt
===================================================================
--- talks/dc8-videoteam_abs.txt 2008-08-23 18:48:36 UTC (rev 273)
+++ talks/dc8-videoteam_abs.txt 2009-02-02 11:57:49 UTC (rev 274)
@@ -1,41 +0,0 @@
- ABSTRACT
-
-Since 2005, the talks at Debconf have been recorded on video, to be
-published online. Beginning in 2006, talks have also been streamed
-live. One of the goals is to get recordings in high quality online
-immediately, with little or no post-production work. The video
-switcher dvswitch, realized in software, and a disk-based recording
-workflow is bringing us closer to that goal. Tape is still used as
-backup in case of failures, but we expect those to become rarer as
-the system matures. A large part of the post production work is
-restoring failed recordings.
-
-Dvswitch was developed by Ben Hutchings just in time for the Debconf7
-in Edinburgh. It enabled a multi-camera live production using cheap
-cameras and modest laptops. The laptops relays DV streams over
-TCP/IP. This avoids any degradation due to long cable stretches, and
-makes cabling cheap and convenient. The output is DV straight from
-the cameras, producing a very crisp master video.
-
-Dvswitch works with sources and sinks. The sources send video from a
-file or a firewire port to a listening instance of dvswitch, which can
-run on a remote machine.
-dvswitch listens to several sources and displays a scaled down black
-and white preview image of each one. One of the sources is displayed
-at full resolution in colour; this is the outgoing stream, which is
-sent to the listening sinks. Each sink may send the stream to disk or
-to an encoder for live streaming. It is common to do both; store the
-raw master to disk, and forward the master to an encoder, and
-subsequently to a streaming server.
-
-While dvswitch saves us a bundle in hardware, the video team is still
-heavy on manpower. Remotely operated cameras would help, and we are
-still looking for affordable solutions that work well on Linux.
-
-
- The talk will cover the hardware, software and manpower required for
-a typical dvswitch usecase. Some caveats and challenges regarding
-sound, lighting and rigging will be discussed. A live demonstration
-of dvswitch in use will be given. We would also like to offer
-rehearsal sessions with the demo rig for those who are interested.
-
Deleted: talks/dc8-videoteam_outline.txt
===================================================================
--- talks/dc8-videoteam_outline.txt 2008-08-23 18:48:36 UTC (rev 273)
+++ talks/dc8-videoteam_outline.txt 2009-02-02 11:57:49 UTC (rev 274)
@@ -1,97 +0,0 @@
- The video team,
- people, hardware and software
-
-
- People
-
-We would like to bind up as few people as possible in the video team.
-Our activity is a service, not a playful hacking thing.
-
-Post production takes for ever, if it ever happens. We strive to get
-as much as possible done instantly.
-
-
- Hardware
-
-The hardware should be cheap and light. Commodity hardware is more
-convenient than specialty hardware. Two non-commodity pieces that we
-now consider "must have": Scan converter (VGA to DV) and wireless
-mic. The laptops and the DV cameras can be borrowed by/from participants
-or the local team.
-
-
- Software
-
-The software should be a minimal set of packages running on Debian
-Stable. Dvswitch fits that bill.
-
-
- TODO
-
-Talkback: The camera operators should have headsets, and receive oral
-instructions from the mixer operator/producer.
-
-Tally lights: The cameras should have a red lamp telling everyone
-(especially the camera operator) when they are "on".
-
-
- Caveats
-
-Lighting problems. Good room lighting should provide a comfortable light
-level and adequate light for cheap cameras, and still not wash out the
-projector screen. More often than not, this is not the case.
-
-Lighting workarounds. Spot light on the speaker, turn off the rest
-during the talk. Turn the lights on again for the Q&A session,
-assuming the screen won't be much needed then.
-
-Recording the sound from the audience takes some care. We want
-reactions from the audience to be audible, but general murmur and air
-condition noise should be cut out.
-
-The crowd cam should see _everyone_ in the audience. This may require
-a tall platform, or (fancy!) a jib arm.
-
-
-
- *** What the software does
-
- * dvsource
-
-Grabs video from a DV camera over firewire, and sends it over TCP to
-the *dvswitch*. Dvswitch may run on a different computer, usually
-nearby.
-
-
- * dvswitch
-
-The heart of the system is dvswitch.
-
-
- * dvsink
-
-Receives the output from dvswitch
-
-
- *** Live demo
-
-* Show the hardware
- Laptops
- Cameras, tripods, firewire
- Scan converter
- Switch, ethernet cable
- Sound mixer
-
-* Show the setup
- Speaker cam, head mic
- Crowd cam, crowd mic
- Cabling (gaffa, gaffa, gaffa)
-
-* Demonstrate editing
- Recursive video (gag)
- Cutaways (let the cam-op frame the shot)
- Eye direction (when two shots won't intercut well...)
- Sound level (open and fade out crowd mic)
- PiP? Text overlays?
- Disorienting each other and the stream team (gag)
- "Do you have goatse there?"
More information about the Debconf-video-commits
mailing list