Video Workflow for GoPro HD Hero2 Time Lapse photos

I’ve been one to do a lot of time lapse videos, I’ve actually been doing them since 2006, I think this was my first one, it is at least the oldest one I could find on YouTube. Over the years I have used a number of different cameras, different software and as you can see from my YouTube Channel different subjects (predominantly cars, though lots of them).

(To skip past all the back story and see my workflow, click here, though I would recommend reading what went into defining the workflow)

I think one of the best things for doing a timelapse, at least like I do in a very fixed environment (read garage) is the GoPro Camera HD HERO2 Motorsports Edition, the flexibility that the cameras provide make it very easy to get some great angles and shots. You can also for the most part turn it on and start shooting, and depending on how long you are working you can get by on one battery, or have multiple on hand (I think I have 5) that are charged and ready to go.

One problem you will likely run into though, especially with the new Hero2 versus the original Hero is the 11mp photo size of the new camera, you can easily start to run out of SD card space, even on a 32gb card. In my most recent video I had my GoPro recording a photo every 2 seconds, at the full 11mp resolution and over the 8-10 hours I was working on the car I generated 65gb of photos. That’s a lot of photos. But the GoPro can for the most part handle it, you do have to be careful once you go past 9999 photos that the Hero2 resets the counter, and I think you can start to lost original photos. Fortunately for me this happened over night, and my workflow is to organize photos by Date they were taken, so I didn’t have overlap issues.

When I went to create the time lapse video from these 65gb of photos however I ran into all sorts of trouble. I used to do my time lapse videos using Microsoft’s Windows Live Movie Maker, while you probably cringe at the word Microsoft, and even more so if you’ve ever tried to use Movie Maker to create “real” videos. The software, to be honest, is a POS for creating edited produced videos with lots of edits and clips, but it is free, and it used to frankly kick ass at making time lapses from a collection of photos, like the 65gb I have from the GoPro.

It kicked ass, until Monday, when I tried to start working with the photos and putting a video together.

Problem #1 CineForm Studio

I actually tried pulling these photos in using GoPro’s CineForm Studio, which is supposed to create time lapse videos, taking a look at the numbers of the photos and putting them together. I ran into two problems. The first photos taken on Sunday morning didn’t start at 0001, my fault, they started somewhere around 950 I think, the last photos taken on Sunday ended around 0300 (due to passing through 9999). When trying to create the time lapse sequence with CineForm Studio it got things all sorts of out of whack. The start of the sequence was 0001, which based on EXIF data should have been the end. It also ended up leaving photos out of the time lapse, I think due to me mistakenly recording video halfway through the series of photos. When I ended up doing more time lapse photos on Monday, I didn’t even bother trying to use CineForm studio again.

Problem #2 overlapping photo file names

This one wasn’t really WLMM (Windows Live Movie Maker)’s fault. As previously mentioned the GoPro starts renumbering photos after 9999, I had 12500+ photos from my time spent working on Project350z in the garage this weekend. Some of those photos had the same file name as other photos. To address this I needed to come up with a way to rename the photos, but I needed to do so in a way that allowed the photos to be properly named, in the order that the photos were taken, NOT the order that the photos were numbered initially. To do this I ended up downloading a tool called Bulk Rename Utility, it’s a free tool from a .UK domain name, google it, you’ll find it. It actually worked great, though it took me a bit to get things squared away. You have to enable a setting that allows the tool to extract the EXIF data, which slows things down considerably, but is the only way to do what I needed.

Using the utility I ended up renaming the photos in order 1,2,3,4, etc, all the way to 12559 (or whatever the last # was in my series).

Problem #3 Windows Live Movie Maker Can’t Handle the truth

When the truth is a large collection of photos, WLMM just can’t take it. I had the software crash so many damn times on me in the past 3 days. I just couldn’t get it to take my photos and create the timelapse I was looking for. I even tried resizing the photos down to 1920 width, instead of the original GoPro width, but that didn’t help. On my Quad Core 8gb Intel machine WLMM just couldn’t keep up.

Finding another software solution, Adobe Premiere CS5

I have Adobe Premiere CS6 installed, and I use it for a variety of video edits, though not typically time lapse video from photos, I did use it this weekend on speeding up a 1.75 hour video, also taken with the GoPro, you can watch that video over on my BicycleTips blog post about bicycle video being boring.

After a little googling I was able to see that Adobe Premiere could be used to take a series of images, Numbered Stills to be exact, and create a video from those.

Problem #4 Numbered Stills without padding

No matter what I did though, I couldn’t get the Numbered Stills option to work, much less sort my videos properly in the file browser. A little more googling and I figured out that in order for Premiere to do a time lapse with images you should have the files be of the following format

Something_00001.jpg
Something_00002.jpg

Something_12559.jpg

Not 1.jpg, 2.jpg, etc. After breaking out the bulk rename utility again I was able to get the files named properly, and importing them into Adobe Premiere as Numbered Stills was surprisingly easy. From there it was simply a matter of dropping the video (Premiere created it) into the Sequence, making any additional changes (I sped it up 150%) and then exporting it out.

So to rehash, here is my actual workflow I used (without all the extra steps that didn’t work).

My GoPro HD Hero2 Camera Time Lapse Workflow (as of 1/18/2012)

  1. Copy the files from the GoPro camera (I copied them into date specific folders)
  2. Copied from the date specific folders into a “temp” folder so I could work with copies instead of the originals.
  3. Resized the files down from the original 11mp to a smaller format (this step is likely unnecessary, but I did it trying to make things easier on WLMM).
  4. Rename the files, be sure to rename them using the EXIF data for Date Taken, and number them 00001, 00002,…,00010,…,12599 etc. I went with 350z-1-16-2012-00001.jpg as my format.
  5. Create your project in Adobe Premiere
  6. Import into the project, choose the 1st photo in your series and choose the Numbered Stills option below the file selection window.
  7. Edit video as normal in Adobe Premiere.

And of course, here is the video that generated all of this, originally posted over on Project350z.com

Recent Comments

You look into CineForm Studio again. Yes for longer that 10K sequence renaming is a good idea, but it works well. Here is a similar sequence (car work) using GoPro Hero2 and CineForm Studio.
Posted By: David Newman on Jan 2012
David, Unfortunately it appears that once you rename the files from the original GoPro names (I went with 0001 0002 etc, CineForm Studio will no longer import them as a sequence, just individual files.
Posted By: Chris Hammond on Jan 2012
This is great stuff. Thanks for this. I am really surprised how difficult this is. For time lapse, I have also used something called a "plotwatcher", and the HD viddy is phenomenal, while being UNBELIEVABLY easy to edit. IT's actually saved as a video, automatically. I barely have to do a thing. I just got my GoPro, and I am really anxious to figure this out. grr...
Posted By: uncle fishbits I said FishbitS! on Apr 2012
Thanks a bunch for posting this! I am planning a roadtrip from NYC to LA in a few weeks and was looking to buy a GoPro Hero2 to create a nice timelapse. I'll crop out a good portion of the night time driving but otherwise I still anticipate roughly 80 to 100k stills. How often did you find that you replace a 32gb card? Does it notify you once it is full or will I have to guesstimate?
Posted By: Tommy Boy on May 2012
I would recommend you get 2 32gb cards, and make sure you can power you GP off the car power adapter, otherwise you'll need two GPs one to charge an extra battery. In my experience, the battery will run out before a 32gb card will. I don't think you'll easily know when the card is full though, perhaps if you have the LCD back, but I would just recommend changing it every 3 hours or so, grab the photos off the one you remove, put it back in 3 hours later. Your night photos will be useless for a time lapse, at least in a moving car.
Posted By: Chris Hammond on May 2012
You may find it easier if you have access to a mac? Name mangler (free) will sort photos by taken date then rename sequentially. Quicktime 7 has the option to open image sequence. All you do is specify the framerate and point it to the first photo. You can then export at your chosen size/codec (including crop to 16:9 if wanted) and you are done. I've done this at 11mp around 7000 images on a mid level mac mini, so not a resource hog!
Posted By: Simon Woodgate on Jun 2012
This is extraordinary stuff. Much obliged concerning this. I am truly astounded how demanding this is. For time slip by, I have likewise utilized something many refer to as a "plotwatcher", and the HD viddy is amazing, while being UNBELIEVABLY straightforward to alter.
Posted By: roshni adelt on Apr 2013

Add Comment

Please add your comment by filling out the field(s) below. Your comment may need to be approved before it becomes visible.
Enter your first name for display with the comment
Enter your last name for display with the comment.
Enter your comment here.
If you can't type Human2 in, you can't post, plain and simple.
Submit Comment Cancel

Chris Hammond

Chris Hammond

is a father, husband, leader, developer, photographer and car guy. Chris has long specialized in ASP.NET and DotNetNuke (DNN) development, so you will find a variety of posts relating to those topics. For more information check out the about Chris Hammond page.

If you are looking for DotNetNuke consulting please visit Christoc.com Software Solutions

Find me on Twitter, GitHub and LinkedIn.