|
|
|
|
|
by walterbell
4170 days ago
|
|
Just listened to the ZFS on Linux episode. I was sceptical about watching a command-line narrative, but this was incredibly well executed, with episode transcript and mini-reviews of related sites. As the episode started, the speech pattern was so slow I wondered if it was a TTS robot aimed at non-English listeners, but then the voice quickly picked up speed to reach excited-hacker cadence. How long does it take to write and produce each episode? Would you care to share the toolchain being used for screencasts? I miss the lost promise of SMIL which would have allowed in-context video links to URLs for related sites, or deep-linking to related video snippets in other episodes. If your project continues, you will quickly grow a library which will benefit from cross-indexing. You will also find that a subset of content will need to be refreshed, as tools and environments change. Metadata for modular snippets will improve discovery, reuse and update. Rails Tutorial has generated six-figure revenue from screencasts combined with an ebook, so there is precedent for monetizing self-service video training. |
|
> How long does it take to write and produce each episode?
Rough guide is about ~2-3 hours per minute of video. Research, playing around with ideas, demos, writing, recording video, recording audio, editing, etc. So, ZFS part one was 12 min, that's about 24 hours, and part two is 18 min, so about 36 hours. Those two episodes are about 60+ hours of solid work. ZFS did take a little longer than 60 though, since I ended up doing tons of research, but I rather error on a better quality video, than putting out sub optimal content. These figures are shocking to many people, but I have honestly not found a quicker way. As I learn to use the editing software a little more, I have been able to shave an hour here and there, so that is nice!
> Would you care to share the toolchain being used for screencasts?
Sure, here is a basic dump of the tools I use: