Time-lapse post-processing workflow
Here’s an announcement I’ve been looking forward to sharing with you all for a while now! After meeting in person with a customer to walk them through post-processing a few months ago, I realized that for many people if they’re not already familiar with the process it’s pretty hard to follow, and it’s easy to mess up and get disappointing results. I’ve also seen this is a pretty common pain point.
So it got me thinking about what I could be do to make it simpler for the most common use case. I finally came up with a plugin for Lightroom. With the plugin, the common tasks in dealing the post-processing time-lapse from the VIEW are all automated, and you don’t have to use XMPs. Just import the photos, and let the plugin guide you through the rest.
If you already have a workflow you like, you may not gain anything from the plugin — it’s mainly for those starting out that just want great results with a minimal learning curve.
Check it out and let me know what you think. Since it’s generally useful for time-lapse, I’ve made it available to all for a fee (to support development), but it’s free for VIEW users.
I just ordered the Dynamic Perception Sapphire Pro + Stage One PLUS kit that includes the VIEW+. A serious upgrade from my previous rig which is a DIY made replica of the Stage Zero rig and an Emotimo TB3 and the original Timelapse+ 🙂 I’m really stoked to have a more portable more capable easier to program rig. So thank you!!! 😉 As for processing, I’ve been using LRtimelapse Pro for quite a few years now in my workflow and I love it. I’m curious how having the XMP sidecar files written to the internal VIEW+ SD card and imported into Lightroom will affect my workflow? I’m concerned that the first initialization into LRT will over-write any XMP data that the VIEW+ had created..? Perhaps I need an understanding of exactly what the VIEW+ is doing during ramping that involves the XMP file. My guess is that in addition to the VIEW+ physically changing the shutter speed and ISO of the camera, it’s also writting XMP data that facilitates smoothing out those exposure changes for a more smooth ramp/transition between exposure changes? This is something that LRT dos as well during the workflow process, so is it redundant to have them both doing XMP exposure smoothing? Thank you so much for what you do, and that goes for Jay too at DP, amazing hardware and software 😉
The VIEW creates an XMP file during a time-lapse to correct for slight differences in what the calculated exposure should be and what the camera sees with the current shutter, ISO, and aperture settings. My guess is that the VIEW captures images with the current shutter, ISO, and aperture, and stores them in the RAW file format. The XMP file then provides the data needed to to make slight adjustments and fine tune the photo sequence. This is supposed to eliminate a lot of guesswork and editing in the workflow process, and provides a more accurate picture of how the exposure actually changed during the time-lapse. And by using the XMP file, you’ll know that the final result will make full use of the built-in ramping algorithms in the VIEW, which is either PID Luminance or LRTimelapse.
Hi! A new Timelapse+ View user here 🙂 Tried to register the Timelapse Workflow plugin on my second PC. Even if the registration seem fine with a “Thank you” message, I have to fill in email and password every time. Is this free licence limited to one PC?