My Football Video Processing Workflow

Video capture, processing, and publishing are a huge part of my football coaching routine. We film all of our games (Julie being my go-to videographer) and I spend a lot of time on the road capturing scout film of future opponents. I commonly have 2-3 hours of video processing to work through on a given weekend, often with a 12-18 hour required turnaround before we have our coaching meeting on Sunday evening.

"Back in the day" things were a bit simpler. We would capture the film on a digital camcorder then burn a few DVDs for coaches. Problem solved. Some things have changed that no longer make this viable:

  • Parents and family of players really like to see game film. We have parents who live away from their player, parents who travel, grandparents, etc. Making DVDs for all of these folks could turn into a part-time job.
  • We started using Hudl for film analysis and scouting. This requires that we have a digital version that we can upload and turn into a play-by-play breakdown.

This year I publish game film in multiple forms:

  • I publish whole-game film to Vimeo, usually password-protected so as to make things a bit more difficult for opponents to easily gain access to our film. The later we get in the season the less I worry about this. Our players love this because they can share the film with families and even download their own copies of the games for their records.
  • I upload individual play clips to Hudl for breakdown and analysis. This allows the coaches to do deep analysis on tendencies, our opponent's best plays and players, and review our own film for the same. We also mark up individual plays (think John Madden with a telestrator) to share with our players.
  • As a last resort I can burn a DVD using the awful iDVD application from Apple. I think I've had to burn a total of 2 DVDs this year.

I thought I'd share my detailed video processing workflow -- you may find something useful in here whether or not you process film for football.

Video Capture

Most of my video is captured on a Canon 7D DSLR with Canon EF 70-200mm f/2.8L lens. This is an expensive setup for filming but I'm a photographer and this works pretty well for us. Ask Julie sometime how hard it is to get acquainted with a setup that requires manual exposure control and lacks follow focus. My backup camera is a Panasonic Lumix DMC-TS2 -- the camera we bought for our underwater shooting in Galapagos earlier this year. This is the camera I give to friends who will go scout games for me.

My rules for football film capture are simple:

  • One play per video clip. Start the camera before the start of the play and stop it after. This is critical for making it easy to load film into Hudl.
  • Try to start zoomed out so that you can easily see the field position and down/distance.
  • Show the scoreboard after each scoring play and end of each quarter.

A typical full youth game (12 minute quarters) has about 30-45 minutes of video. On my Canon 7D this equates to about 15GB of video data recorded in 1080p full HD, 1920x1080, 30 frames per second, H.264 encoded. This is higher quality than I need for film analysis, but with 32GB flash cards I'd rather just capture at the highest quality and downgrade later for processing.

Example -- Here is a video of our end-of-game Bowmen cheer taken last weekend. It is about a minute long, and out of the camera it was a 400MB file.

Initial Processing

I used to pull the raw video straight into iMovie for processing on my now 3-year-old iMac with attached Drobo 3TB storage device. Importing 15GB of HD video could sometimes take all night (10+ hours). Some of this is my slowish iMac, some of this is iMovie and how it handles video like this.

This year I changed my workflow to compress and downgrade my video for easier processing. Initially I did this manually using HandBrake with great success. I just used the "Apple TV 2" preset which converts the video to 1280x720 H.264 and saw file sizes reduced by an order of magnitude. The video above went from 400MB to 48.3MB.

Still, manually converting individual clips was not going to be a winning solution - I needed a way to automate it for large collections of clips -- typically about 100-120 clips per game. The solution for me was to use the HandBrake Command Line Interface combined with my favorite file automation tool on the Mac, Hazel. I created a special folder on my Mac called "ToConvert" and created a processing rule to act on all files not ending in mp4 (input files will typically have a .MOV extension)

The script that gets invoked for each file is very simple and calls the HandBrakeCLI with the "AppleTV 2" preset:


if [[ $1 =~ ([0-9a-zA-Z_.-]*)\..* ]]; then
    /usr/local/bin/HandBrakeCLI -i "$1" -o "${BASH_REMATCH[1]}.mp4" --preset="AppleTV 2"

I throw all 15GB or so of my movie clips at this directory and my MacBookPro starts spinning (with CPU temperature hitting 190f or so!) and completes the processing in less than an hour. Now I have a set of 1280x720 mp4 files that I can easily work with in my other tools.

Note that this approach works for any kind of movie file that HandBrake can handle, so those AVCHD files that come out most consumer camcorders also work just fine.

Post Processing

After converting these files I immediately copy them to an external drive and walk over to my Windows desktop to upload to Hudl. Yes, you can only upload to Hudl using a Windows desktop. Hopefully they address this at some point and offer a Mac option. Because my upload is comprised of play-by-play clip files, I generally don't have to do any manual intervention on the upload to support the breakdown in Hudl -- it just works.

Simultaneously with the Hudl upload I will begin importing these downgraded files into iMovie. This usually takes about another hour or so to process for a full game. Once they are imported I quickly add a title screen and add the rest of the clips in order. Rarely will I do any other editing. You can see a sample of one of my game films on Vimeo.

The Hudl upload also takes about an hour for me. Once that is complete I dive into film breakdown. This involves looking at each play and marking it as offense/defense/kicking, recording down/distance and field position, and for our offense recording details about our formation, motion, and play called. I'll do another post in the future showing what I record for opponent scout film.


The great thing about Hudl is that once I've uploaded film it is instantly shareable to the other coaches and players. I'll often mark big plays as highlights, even tagging some specific player highlights, and Hudl automatically creates highlight reels for the team on a game-by-game basis. The Hudl Youth package that I subscribe to does not support film sharing between coaching so I have no first-hand experience using that. It uses a robust escrow model though and I know our high school coaches trust it.

My other publishing avenue is through Vimeo, which involves uploading the full movie file produced from iMovie. I will usually password protect our game film and send a direct link to the coaches and players so that they can view and share with family. Password protected videos will not automatically show up in my profile. It is a weak form of security given how broadly I send the links and passwords, but good enough for my use. When I need to share film with an opponent coach I can just send the URL and password - so much easier than arranging a face-to-face meetup to exchange DVDs. That said, most of the other coaches don't have an online option so I often end up receiving DVDs that I then need to rip and process myself.


The incorporation of HandBrakeCLI and the Hazel automation was the real game changer for me this year. I come home from the game, insert my CF card into the reader, drag the movie files into my conversion folder, then walk away and consume a chilled adult beverage. I usually have the film ready to view by the coaches in Hudl within 2 hours of the game finishing. If Hudl offered a Mac upload option I could streamline things even more.

Do let me know here in the comments if you have questions on the workflow or suggestions for improvement.

Headed to St. Louis

Tonight after Jacob's football game Julie, Jacob, and I will dash off to the airport to catch a red-eye to St. Louis. We are visiting our alma mater, Washington University in St Louis, as a first visit for Jacob who has the school on his short list of want-to-attend schools. Some cool points about this visit:

  • Jacob will get to participate in an athletics recruiting presentation, attend the home football game vs College of Wooster, and meet some members of the football team. Jacob is interested in playing football at the Division III level.
  • Julie and I get a full day on Sunday to show Jacob around campus and the city of St. Louis. We still aren't sure what we'll do but I'm sure a stop at Ted Drewes is in our future.
  • Julie and I will ditch Jacob on Saturday night to see Matthew Sweet's 20th anniversary Girlfriend tour at Blueberry Hill. We first saw Matthew Sweet together in Cincinnati 1993.
  • Jacob will start the day on Monday with a visit to my old AFROTC Detachment. Interestingly, the detachment commander there is someone I was in AFROTC with during my stay at Washington U.
  • The rest of Monday will involve campus tours and sitting in on a computer science class. We return late Monday night.

Needless to say Julie and I are at least as excited as Jacob.

Review: Wits and Wagers Family

I've been a big fan of Wits & Wagers since it was first released back in 2005. I even participated in a Wits & Wagers game show back in 2006. North Star Games positioned this game from the start as the trivia game for people who don't know stuff ("Not a trivia buff? It doesn’t matter!") and it mostly held true to that claim. Each question has an answer that is a positive number. Players secretly guess what the numerical answer is, then everyone reveals and the answers are arranged lowest to highest. Each player then wagers on what they think is the right answer, with a very cool twist: the further an answer is away from the median, the higher the payoff if you guess correctly. Example: "How many feet are in a furlong?" Guesses might be 200, 500, and 1000. The answer of 500 would only pay 1:1, but the other two might pay off 2:1.

While I loved this betting mechanism it lead to confusion for many players and created some bad end-of-game "I'll just bet it all" brokenness that led to anti-climatic endings. I concluded that the game was more of an enjoyable activity than a real game because of this.

North Star Games recently sent me a review copy of their newer Wits and Wagers Family version which shipped in 2010. There's good and bad inside the box but mostly good.

What I like:

  • They fixed the game mechanics and took away the betting odds element. Instead, each player has a large meeple and a small meeple to bet with and players score points by having the right answer and placing the right bets. The game is a race to 15 points.
  • The price point is very attractive -- you can probably find a copy for around $15 online.
  • Even though the game only supports up to 5 players, this is one of those party games that works very well as a team game. Just find some multiple that works for your group (8 people? 4 teams of 2! 9 people? 3 teams of 3!). The group version may even be more fun than solo as you kibitz about what the correct answer might be.

What I don't like:

  • I think the questions are inferior (too family-ish?) compared to the original version. Not a problem for me as I just mixed in my questions from the original into the new box. You can also buy more questions in the Expansion Pack, which I haven't tried.

Conclusion: This is a party game staple in my house and is highly recommended. Great for gamers and non-gamers alike.

I remember Steve Jobs

Apple logo

I can't fully explain the impact Steve Jobs had on my life, but I can at least share a chronology of memories directly linked to his creations.

I remember first learning that my friend Mike was getting an Apple II computer when we were in the 6th or 7th grade and being extremely jealous. I made it clear to him that he'd need someone who knew how to program in BASIC to help him operate it (that being me of course). I remember scrambling to learn BASIC so I could prove my worth.

I remember spending late nights at Mike's house playing Wizardry and Olympic Decathlon, then staying up even later after Mike went to sleep learning how to "enter the monitor" with Call -151 and start programming 6502 assembler language.

I remember encountering my first Macintosh as a sophomore in high school in 1984 and using it alongside a PDP-11. It was clear that the world was changing.

I remember programming my own version of Tetris on a Mac during my sophomore year in college using 68000 assembly language. I remember using a Mac IIcx to produce many term papers during my senior year in college. I remember designing a medical imaging system as a senior project based on the NeXT computing platform.

I left the Mac world for at least 15 years, but I remember coming back in a flurry in 2007 with a MacBook Pro, an iPhone, and an iMac. Since then the Apple virus has consumed our household and we are better off for it. Steve Jobs -- you will be dearly missed.