Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Hi,

    make sure your talk is recorded and made availlable online for all of us who can't come.

    Steffen
    • My company is planning to do the presentation capture and production for YAPC::NA this year. Here's an early sample of what the content might look like:

      http://www.media-landscape.com/demos/YAPC/ [media-landscape.com]
      • by Alias (5735) on 2006.04.21 7:19 (#47301) Homepage Journal
        That looks really interesting.

        How does it handle being overloaded?

        For example, my current generation of talks (one big one, and three or four lightning talks) average out at around a "slide" every 6 seconds. So that's something like 220 slides for the 50 minute talk.

        And after realising that the talks are getting closer and closer to being a video, this year I'm going to try something unusual and include ACTUAL video. The big PITA talk, at 80 minutes long, is expected to have 15-20 minutes of TV-quality video footage in it.

        Will you be able to cope with that?

        Will I be the first person to crash it :)

        • 220 slides is fine. We can easily support a slide every 2 seconds with the current technology, and we've got further enhancements in the works.

          As for video, we're working toward that. One of our present solutions is to use a subclass of Net::VNC to capture local screen video. Those can then be converted to QuickTime movies or a series of image files for the resulting presentation. We're currently capturing at about 5 fps for typical desktop app motion, but there are certainly improvements to be made.

          The