-
Welcome to the new forums! Please read this first. For known issues we are working to resolve, click here.
LX3 timelapse video
- Thread starter neekoh_dp
- Start date
Thanks all for your comments.
When you import project media and browse for an image, you can check a box to open still image sequence... Just like it should be (Vegas 9 Platinum at least). I can't believe I missed it.
You can right click the sequence in the project media and set parameters later, such as frame rate. That's all I would have needed basically.
KinniKinnik's option changes the default duration a single image (ie. not sequence) is displayed.
I've also now found how to stabilize hand-held videos with excellent results (VirtualDub and DeShaker plugin). It of course also applies to timelapse, but requires and analysis pass and a rendering pass, and currently this doesn't go to the Vegas workflow at all. Well, better use a tripod anyway.
I thought I'd come back here to mention this now that I checked.
When you import project media and browse for an image, you can check a box to open still image sequence... Just like it should be (Vegas 9 Platinum at least). I can't believe I missed it.
You can right click the sequence in the project media and set parameters later, such as frame rate. That's all I would have needed basically.KinniKinnik's option changes the default duration a single image (ie. not sequence) is displayed.
I've also now found how to stabilize hand-held videos with excellent results (VirtualDub and DeShaker plugin). It of course also applies to timelapse, but requires and analysis pass and a rendering pass, and currently this doesn't go to the Vegas workflow at all. Well, better use a tripod anyway.
John Brubaker
Leading Member
I'm tagging because this is such a nice video!
coopr
New member
I'm not even sure you need Quicktime Pro - I think regular Quicktime may do this.
This should help: http://digitalcommons.psu.edu/node/4469
When used correctly, H.264 quality should be as good as, or better than, every other compressed video format available to you! Of course, uncompressed will be even better, but file sizes are potentially huge. Be sure to review and adjust the various quality settings when you export your movie.
Looks like I'm late noticing this thread, but I just wanted to say that this is exceptional!!!
Really lovely, and to note that you shot on-the-fly, no-tripod and compromised by the need to be social with friends? Wow!
I do have one question on the post, if you have time to answer. I am an experienced Final Cut Pro editor, but of docs and narrative stuff, not rather massive assemblages of stills. So ... hmmm -- how do you do that? You mentioned avisynth -- I'm not familiar with it, but I'm wondering you are using a script to string together each shot ... that is to time the duration of each shot? Surely you're not doing that by hand in an editing application!
And then there's the wonderful pans and zooms. Here again, are you scripting this in some way? They are so utterly smooth -- that math has to be perfectly accurate!
Sorry if those questions are too basic and perhaps to difficult to explain to someone who hasn't worked in this way, but I'm quite taken by your sensibility and your ability to execute in post.
Thanks for sharing,
Bradley
Really lovely, and to note that you shot on-the-fly, no-tripod and compromised by the need to be social with friends? Wow!
I do have one question on the post, if you have time to answer. I am an experienced Final Cut Pro editor, but of docs and narrative stuff, not rather massive assemblages of stills. So ... hmmm -- how do you do that? You mentioned avisynth -- I'm not familiar with it, but I'm wondering you are using a script to string together each shot ... that is to time the duration of each shot? Surely you're not doing that by hand in an editing application!
And then there's the wonderful pans and zooms. Here again, are you scripting this in some way? They are so utterly smooth -- that math has to be perfectly accurate!
Sorry if those questions are too basic and perhaps to difficult to explain to someone who hasn't worked in this way, but I'm quite taken by your sensibility and your ability to execute in post.
Thanks for sharing,
Bradley
Thanks, Bradley!
ImageSource("c:\photos\lintsi\carousel\P101%04d.JPG", 1234, 2345, 12)
Basically what that does is opens a continuous sequence of images (P1011234.jpg to P1012345.jpg) and produces a 12fps video clip out of it. The source images were shot at a quite constant rate, so I only needed to find a good output rate.
In Vegas there's a way to import image sequences as media, and I would have just had to import that to the project and drop in on the timeline. That would have yielded a huge resolution video, though. But that part really wasn't tedious at all.
If I was to do it now, I'd try to do it all in Vegas. But scripting had the benefit that I could easily change speeds and durations and sizes for the individual clips. I did my trial and error -phase mostly in 640x360 resolution, then just selected the final resolution when relatively ok with things. There scripting can definitely make things easier, but sometimes it can be a bit painful... :|
Heh, yeah it becomes quite easy with Avisynth. I don't have the script at hand, but one shot (I mean location in this case) would become something like:
ImageSource("c:\photos\lintsi\carousel\P101%04d.JPG", 1234, 2345, 12)
Basically what that does is opens a continuous sequence of images (P1011234.jpg to P1012345.jpg) and produces a 12fps video clip out of it. The source images were shot at a quite constant rate, so I only needed to find a good output rate.
In Vegas there's a way to import image sequences as media, and I would have just had to import that to the project and drop in on the timeline. That would have yielded a huge resolution video, though. But that part really wasn't tedious at all.
Yeah, scripting - it's essentially a crop rectangle moved across the image over time. It's quite common for still images, but also great for stationary movie or timelapse. Again for each shot (location) I tried to pick and interesting source and target crop rectangle (in Photoshop) in the same aspect ratio as the target resolution (16:9). The cropped image was always resized to the final resolution. In Avisynth you can use Lanczos and Spline resizing algorithms, and more importantly, provide the crop rectangle in floating point coordinates to the resizing functions. The smoothness becomes from animating floating point coordinates and doing the animation in the final framerate which was higher than shot-to-shot speed. In Vegas I presume I would get pretty much the same smoothness, with using a proper UI and not having to type the coordinate values.
If I was to do it now, I'd try to do it all in Vegas. But scripting had the benefit that I could easily change speeds and durations and sizes for the individual clips. I did my trial and error -phase mostly in 640x360 resolution, then just selected the final resolution when relatively ok with things. There scripting can definitely make things easier, but sometimes it can be a bit painful... :|Similar threads
Keyboard shortcuts
- f
- Forum