For the past several weeks I have been running a live video podcast called Authored Content over Google+ Hangouts with my fellow lynda.com staff authors James Williamson and Ray Villalobos. This new platform and it’s direct connection to YouTube makes it easier than ever to record and publish conversations over webcam.
The success and simplicity of Authored Content made me think: Could we use the same technology to broadcast and tape a WordPress Meetup talk? Yesterday I put that to the test, with mixed results. I’m sharing my experiences, experiments, and ideas about improvements with you so you can try this out for yourself. Feel free to pipe in with questions, comments, and suggestions so we can all share in the knowledge and make this work for everyone.
Google+ Hangouts On Air
One of the relatively new features of Google+ Hangouts is Hangouts On Air. This feature allows your Hangout to be a) broadcast live on your Google+ stream and on your YouTube channel page, and b) be recorded and published on YouTube for posterity. Getting Hangouts On Air to work requires a Google+ account, a YouTube account, and the interlinking of both. I’m not going to go through the process here. Suffice it to say it’s simple and takes about 10 minutes the first time you do it.
Google+ Hangouts allows up to 10 participants, each of which can share their webcam, screen, or a specific window along with voice. So in a nutshell it’s Skype plus auto-publishing to YouTube.
Having worked in TV for many years I have many pet peeves about videos published online: They are poorly shot, the audio is horrible, and when slides are displayed, they are usually taped with a camera producing dismal results. This is one of the reasons I have hesitated taping the Vancouver WordPress Meetup Group talks: I don’t want to put something online that isn’t done properly. Of course when you look at the videos we made yesterday you’ll see that I have changed my mind, at least to a degree.Anyone who has
The reason I wanted to try Google+ Hangouts for this is because it would allow me to not only show a video of the speaker, but also potentially have the speaker share her screen on Hangouts so it could be displayed properly. This would circumvent the problem of screen capture which is horribly complicated under normal circumstances.
Thus evolved the plan:
- Use one computer with a webcam and a microphone to record the speaker. This will be the main computer from which the Hangout is started.
- Have the speaker join the hangout with her computer and set it up to share the screen or window.
- Mute the microphone on the speaker computer so only one microphone is active.
- Use the Cameraman tool in Hangouts to control what screen is being displayed at any one time
This setup would allow switching between a screen grab and the speaker and could also potentially be rigged up with more cameras (computers) to have multiple camera angles.
Looks good in theory, right?
We have accumulated a lot of professional audio and video gear over the years at Pink & Yellow Media and I spent quite a bit of time figuring out what would be the best setup. One of the major hurdles of Google+ Hangouts is that it only allows the use of webcams to display video (unless you rig something up to stream in a window and then share that window) so I couldn’t use any of my video cameras. I resorted to and old and surprisingly crappy LifeCam that has been kicking around but never used for years to experiment.
Audio is also a challenge. Computer microphones are omnidirectional and crappy, so that was a non-starter. The microphone on the webcam is only minutely better. Instead I chose to test out the onboard microphones on my trusted Zoom H4n hooked up as an audio interface. The audio from this microphone is incredible and you can also control directionality quite well. Since this was an experiment I chose to forego the option of dragging my shotgun mic or wireless LAV with me, something I will do next time around.
The results of the experiment were mixed. The first session recorded was Jill Binder’s CSS101 talk. We managed to get the screen sharing to work, but the H4n wouldn’t tether properly so as a result the audio was recorded through the aforementioned crappy LifeCam. You can see the result below.
Verdict for this talk: Screen capture worked well, the webcam will live the remainder of its life on a landfill, and a better microphone is definitely necessary.
I had a chance to reset for the 2nd session and got the H4n to tether properly. However, I encountered a new problem: Robert Dall, who was talking about Backgrounds, was using the Presenter Mode in PowerPoint to display his slides, and in the short time we had between sessions I was unable to get Hangouts to share this window (more on that in the Lessons Learned below). As a result only the video was shared, and as you can see from the video below, that is exactly the type of crappy illegible slides-on-a-wall video I do not want to share on the internet.
After this initial experiment there were many lessons learned, most of which will hopefully help you as you try to do this at your Meetup:
- Broadcasting and taping a WordPress Meetup with Google+ Hangouts works!
- You need a high quality webcam to make it look even remotely acceptable. Preferably one with excellent low-light performance and zoom capabilities. And ideally one that can be mounted on a tripod. (Even more ideally you should use a proper video camera and tether it through a video capturing device. This is expensive and over the top but would produce the best results.)
- A professional audio device is a must. A semi-directional mic like the one on the H4n works in a pinch, but ideally you want to couple it with a shotgun mic or a LAV or both. For the next meetup I am brining my Sennheiser G2 wireless kit for the presenter and my Audiotechnika shotgun to record audience questions. Because the H4n has two XLR inputs I can have both wired in and even switch between them.
- More experimentation needs to be done to figure out how to share presentations where the presenter is using Presenter View in PowerPoint and switching between screens. This is probably the most complicated part about the process and I have no immediate smart solutions.