From Wiki

This is the beginning of the DebConf8 videoteam pages... :)

Contents 1 feature wishlist 2 Hardware to buy wishlist 2.1 suggestions from hermanr 2.1.1 Wishes to the DC8 orga team: 2.1.2 Goals for the DC8 video team: 2.1.3 Suggestions: 2.1.4 Wishes: 3 daily todo

[edit] feature wishlist

needs to be grepped from IRC logs...

[edit] Hardware to buy wishlist

1. laters/manana/debconf8
   1. monitoring machine
   2. svn commit mails for debconf-video
   3. debconf8: rename group video (1008) to videoteam
   4. grab for "**DC8 wishlist" in #debconf-video logs

1. Paul van Tilburg <paulvt@debian.org> offered a video mirror - do we want it? -- **NO** mirrors needed, we have enough
2. find more space for meetings-archive (for ftp.acc.umu.se, they're currently looking at buying a new backend server, that could take a few sata drives, so throwing a bit of money (for 2-5 500gb drives including the appropriate hot-swap caddies ) towards ACC would be one solution. getting hw donations would be another.) -- meetings archive master has multiple hundred gigabytes unallocated in lvm

[edit] suggestions from hermanr

todo-item: move this to a better suited page

[edit] Wishes to the DC8 orga team:

1. Have a complete schedule ready by the beginning of Debcamp
   1. Rescheduling must be communicated to the video team in due time
2. Good video tripods for all the cameras that need to move during talks (tripods are bulky; I can only bring one...)
3. Be ready to provide one cameraperson for each BoF. The video team will strive to reduce BoF coverage to panning, zooming and the push of a button on a grabbing laptop.
4. Don't throw parties in the talk rooms, unless you want to induce ulcers and fury among video team members next morning!

[edit] Goals for the DC8 video team:

1. To top DC7's coverage ;-)
2. Simplified recording workflow, more failsafe.
3. A better way of capturing the presenter's screen (software or hardware)
4. Training video and/or courses for the cam-ops.
5. Talk-back from the director to cam-ops.
6. Audience cams that can get good close-ups of _everyone_ in the audience.

[edit] Suggestions:

1. Constant recording by default. Recording is the "safe" operation, stopping it is risky.
   1. reply from Womble2: We had constant recording, except when there was too much contention for the file server's disk. (To avoid this, I think we should record to local disk during the day and transfer to a file server later.) Constant recording made more work for reviewers, and the lack of feedback from the 'cut' command was itself a problem.
2. Archiving the streams remotely, for extra redundancy.
3. Extending dvswitch to remote-control the sources and the sinks, and monitor them for status.
   1. Womble2 replied: Yes, I think it would be useful to allow some sources and sinks to work as daemons and have dvswitch connect to them instead of vice versa.
4. "Playout"/"autopilot" in dvswitch, that instructs the banner dvsource to play a banner specific for the upcoming talk, and switches to preset sources (e.g. speaker cam) when the talk is due.
   1. Womble2 replied: This is a bit risky as we cannot rely on events to start on time.

[edit] Wishes:

1. Remote-controlled cameras, so we can get by with fewer cam-ops
2. Full-resolution streams, ensuring legible slides (optional, of course)
   1. Womble2 said: If a slide is not readable at 320x240, it probably isn't readable at the back of the room either. Speakers should be reminded to use large text.
3. Dedicated documentary equipment, sufficiently shiny for the wannabe film-maker. Maybe a full-blown documentary team.

[edit] daily todo

• not anymore but we used to have:
  • RL meeting to keep in sync, discuss problems & solutions, make schedules
  • one in the lunch break, one after the talks at 18oo. both short, 10min