A couple of months ago I created some documentation on Joomla for some web admins using Joomla to build country sites. After delivering the documentation, the users needed something more visual, so I set about creating screencasts. I created 30 screencasts to match the tasks in the documentation (which I transferred from InDesign to Mediawiki). I then integrated the screencasts with the various pages of the wiki. You can see a list of the screencasts here.
Embedding Flash in Wiki
I used the Flash SWF extension to embed the SWF videos directly into Mediawiki. I would have used an MP4 format, but I couldn’t find a functioning extension that embeds MP4 into Mediawiki.
I planned to use Camtasia Studio’s Express Show format to upload the videos directly into Mediawiki through the wiki’s built-in file uploader, because this format combines the player buttons with the media in one integrated package. But Express Show injects some XML into the file, and my server interpreted the SWF as a mixed file type and rejected it.
I could have reverted to the Legacy SWF format (it also includes buttons in the SWF), but the Legacy format is not nearly as sexy as the Express Show format, so I uploaded the videos to an external media server instead and pulled them in from there. It’s probably better that way anyway, as the media server is more robust.
I used the recording method that I described in this post. Basically I have a Shure SM58 XLR microphone connected to a Behringer mixer routed through my Zoom H4 audio interface and then connected to my laptop. I record in Audacity for ease of editing and then add it to a Camtasia Studio project as an MP3 file. Then I listen to the audio while recording the screen using Camtasia Studio. It’s a two-part process. Sometimes it takes a little editing to sync it up, but I’ve found this method to be the easiest. I was able to create 30 screencasts in a couple of weeks.
I recorded the screen at 1280 x 720 pixels, because this is the minimum dimensions for creating HD quality screencasts when uploading to youtube. However, in hindsight, I would have chosen a smaller dimension and foregone the pursuit of HD. I forgot that you need an HD encoding engine to transform your videos into HD. If you record a 1280 x 720 video and upload it to youtube, youtube’s HD encoding engine will make it clear even when played at smaller dimensions. But if you’re working with the files locally and not going the HD route, you should record at the same dimensions that you plan to publish, because otherwise playing the videos at smaller dimensions leaves them a bit fuzzy.
The resolution on my work laptop is notably high, so even a 1024 pixel width looks small to me. But when I open the same file on my home laptop, which has a much smaller resolution, it extends off the screen.
I ended up creating two sizes: the full 1280 x 720 pixel size, which I link to at the bottom, and a 1024 x 576 pixel size, which is more viewable with smaller computer resolutions. As I said, the smaller dimension isn’t as clear as it could have been had I chosen to record the screen at a smaller dimension.
The next time I create screencasts, I’ll shoot for a smaller frame, such as 850 or 900 pixels. However, the smaller frame will force me to use more panning and zooming, which will increase the editing time and file size.
I also compiled the videos into a theater-style frame. I did this using the Camtasia Theater function within Camtasia Studio. One problem with this theater is that the table of contents adds another 250 pixels of width to the videos, giving you less room to work with. But the theater makes it a lot easier for users to navigate the videos.
I would have included just the theater style frame were it not for the advantages of individually embedding the videos on separate wiki pages. By embedding videos on their own wiki pages, users can comment on the discussion tab of each video. And I can link to a specific video (which is not possible in the theater).
When you’re creating 30 videos, you can wait forever for the videos to render. To speed this up, I recommend using the batch production feature within Camtasia. There’s a nice video tutorial on creating batch productions here. However, I found that running batch productions to create an Express Show format with the MP4 format crashed after the third video conversion. I followed up with support and learned that
Each time this library encodes a video, it consumes memory but does not release the memory until you close CamtasiaStudio.exe. This will cause batch productions to consume a lot of memory and its possible that it will crash the software.
I ran into another bug as well. When packaging SWF videos into a theater frame and configuring a hierarchical table of contents, a one-inch gap appeared at the bottom of the video frame. Support is still troubleshooting that one, but I ended up using the FLV format instead. (One thing I like about Camtasia is that it gives you so many format options—MP4, SWF, FLV, AVI, WMV, Quicktime, M4V, and others.)
Music and Headshots
If you watch that batch production video from Techsmith that I linked to above, you’ll hear music in the background. Music enhances the entertainment experience significantly, and I tried to incorporate music into my screencasts, but it ended up sounding distracting, so I removed it. Finding the right music for a church-based IT organization is quite hard. Ensuring that the same music repeated 30 times doesn’t tire the reader is even harder.
I also didn’t include headshots in these screencasts. It’s something I might do in the future, but I’m not so sure the headshots wouldn’t follow the same possible fate as the music and end up more annoying than appealing.
If you have any feedback or suggestions on the screencasts, please let me know.