Thank you for the video, Nate. It's very informational and definitely helps everyone improve their timelapses and ease the necessary manual work in post.
Awesome timelapse. I have a goal to get the Milky Way like you did. Heading to Yellowstone in October. Crossing my fingers. Thanks for the posting your process.
Oh my dude, I saw that happen on the last video and wondered if your arm was in the shot! Painful! I've been using LRTimelapse for years and still learned a few tricks from this. Thank you!
=Wow! This is exactly what I was looking for, I wanted to learn how to make timelapses of the milky way, but I couldn't find a good step-by-step guide for a beginner anywhere. I think it's time to learn lightroom, I used photoshop before. Btw. your sky looks beautiful! At my place unfortunately I can get max b3 for timelapses. I'm very curious if I can get 20% of your effect!
I just finished the two videos. IT WAS AWESOME. You just made me buy a dummy battery and more things and I will make my GF angry as I miss a dinner to go for this. Just, WOW, thanks man! I will try and publish a video of my journey to failing (can't be too confident!) this, hope to connect with you to show how inspiring you were!
Beautiful MW timeplapse! I've been using LR Timelapse for about 7 years but I'm always wondering if my process is as it should be. Your video covered all the steps and most of the reasoning behind them which is very reassuring. I'm using a Macbook Pro M1 Max and processing the files from a Sandisk Extreme Pro 4TB. You computer (a Macbook, I assume) seems to be blazing fast. Can you tell me what it is and how it is spec'd out. I'm wondering it's time for another upgrade. I'm processing about 50,000 storm chasing timelapse images. Again, thanks for the amazing timelapse.
I actually bought a Mac Studio specifically because my current workflow involves huge timelapses and lots of video footage. I also have an M1 Max MacBook pro and it works for timelapses but is definitely much, much slower than the one I used for this video. If you watch some of my other editing videos (for Lightroom, not timelapses) I do those on my laptop, but there's a very specific reason I'm sitting at a different desk than usual for this video 😂
@@Nateinthewild Do you think a maxed out Stuido with the M2 Ultra is the way to go or is it possible to get away with a less powerful Studio model. I'm not heavy into video processing (yet) but would like LR exports to go much faster.
@@RichardRostant1 I personally went with a maxed out Studio with the M2 Ultra, but I think even a MacBook Pro with the M3 will be quite a bit faster than the M1!
Can LRTTimelapse do the same functions like in LR such as the AI masking, clarity, dehaze, texture, shadows, highlights, etc. etc.? Also, in that one part where you said you have to 'read' in - it almost gives me the impression you can't have two or more 'runs' over the sequences. For example, say apply just a LR Detail > denoise and export as DNG sequence after, running LRTimelapse over that denoised sequence? Or just do some basic masking for different areas and adjust in LR those masked areas to establish some relative differences/accentuations, etc. Then export as a sequence and go over like in the way you did for a general grading of the sequences in LRTimelapse? Or would one have to export as a jpg/png or tiff in order to do a 'layover' in LRTTimelapse? I recently tried doing some grading in Davinci on a sequence that was already denoised in LR but exported as DNG. But Davinci can't see the DNG of a file and only sees the RAW. If however, if I export from LR as a jpg, png or tiff then I can grade over those denoised sequences in Davinci.
I'm thinking of trying this process but am having to resolve an annoying issue with LightRoom that I haven't been able to find an answer for even on the forums. And want to resolve first before trying this process here. I have about 1k+ images of RAW (All at nighttime in a remote location so there's no short term increase of having additional light sources come along; meaning from frame to frame in RAW all the images are basically the same exposure, except the changing position of the stars). I've tried this several times with different presets and my last test was just to go with a basic 'reset' Preset settings in Development. When I apply that preset(or any other one) to all the images, I find that at about every 10 - 30 images, I get an image that is like it has had an entirely different preset applied. I get these images that stick out that are very different. Can't figure out why Lightroom is not applying the preset/s consistently to each image. I haven't tried doing this in smaller batches to confirm but the only thing I can think of is that Lightroom can only batch process a certain number of images at one time before getting 'wonky'. Have you ever had this kind of issue?
Hmm that's fascinating. LR tends to have a mind of it's own, it is a very frustrating program. I'd definitely suggest giving it a try in LRTimelapse, I can almost guarantee it'll solve the issue for you.
Is a Peak Design travel tripod strong enough for this long exposure. That is what I plan to carry on a trip into the mountains. Is it worth the weight and size in the backpack to go with a bigger tripod?
Personally I don't think the Peak Design tripod is good for almost any scenario. The Gitzo Traveler weighs the same and is literally twice as stable, but I'd recommend a series 2 tripod at a minimum for timelapses like this.
Yes, another thing, that damn "Save Metadata" and "Read Metadata" commands should NOT be right next to each other. I can't tell you how many times I've accidentally moved the mouse at the last second.
Hahaha YEP, I figured I should take a second to be VERY explicit about those commands because it's way too easy to accidentally reset your entire project
Thank you for the video, Nate. It's very informational and definitely helps everyone improve their timelapses and ease the necessary manual work in post.
Awesome timelapse. I have a goal to get the Milky Way like you did. Heading to Yellowstone in October. Crossing my fingers. Thanks for the posting your process.
You've got this!!
Oh my dude, I saw that happen on the last video and wondered if your arm was in the shot! Painful! I've been using LRTimelapse for years and still learned a few tricks from this. Thank you!
Great tutorial! Thank you🙌🏼
=Wow! This is exactly what I was looking for, I wanted to learn how to make timelapses of the milky way, but I couldn't find a good step-by-step guide for a beginner anywhere. I think it's time to learn lightroom, I used photoshop before.
Btw. your sky looks beautiful! At my place unfortunately I can get max b3 for timelapses. I'm very curious if I can get 20% of your effect!
thanks a lot!
Awesome video man, thank you. LOL the arm just has a mind of its own.
Can't believe I'm still getting in my own timelapses after 10 years of doing them hahaha
I just finished the two videos. IT WAS AWESOME. You just made me buy a dummy battery and more things and I will make my GF angry as I miss a dinner to go for this. Just, WOW, thanks man! I will try and publish a video of my journey to failing (can't be too confident!) this, hope to connect with you to show how inspiring you were!
Haha YES I love to hear that!! Please tag me when you share your attempt, I'd love to see it.
@@Nateinthewild doing some testing now, hope to be able this week!
Beautiful MW timeplapse! I've been using LR Timelapse for about 7 years but I'm always wondering if my process is as it should be. Your video covered all the steps and most of the reasoning behind them which is very reassuring. I'm using a Macbook Pro M1 Max and processing the files from a Sandisk Extreme Pro 4TB. You computer (a Macbook, I assume) seems to be blazing fast. Can you tell me what it is and how it is spec'd out. I'm wondering it's time for another upgrade. I'm processing about 50,000 storm chasing timelapse images. Again, thanks for the amazing timelapse.
I actually bought a Mac Studio specifically because my current workflow involves huge timelapses and lots of video footage. I also have an M1 Max MacBook pro and it works for timelapses but is definitely much, much slower than the one I used for this video. If you watch some of my other editing videos (for Lightroom, not timelapses) I do those on my laptop, but there's a very specific reason I'm sitting at a different desk than usual for this video 😂
@@Nateinthewild Do you think a maxed out Stuido with the M2 Ultra is the way to go or is it possible to get away with a less powerful Studio model. I'm not heavy into video processing (yet) but would like LR exports to go much faster.
@@RichardRostant1 I personally went with a maxed out Studio with the M2 Ultra, but I think even a MacBook Pro with the M3 will be quite a bit faster than the M1!
“How much we’ve given our lord and savior Steve Jobs” 😂
Literally though. Having a powerful enough computer cannot be overstated enough.
Awesome! You earned a sub from me.
Can LRTTimelapse do the same functions like in LR such as the AI masking, clarity, dehaze, texture, shadows, highlights, etc. etc.?
Also, in that one part where you said you have to 'read' in - it almost gives me the impression you can't have two or more 'runs' over the sequences.
For example, say apply just a LR Detail > denoise and export as DNG sequence after, running LRTimelapse over that denoised sequence?
Or just do some basic masking for different areas and adjust in LR those masked areas to establish some relative differences/accentuations, etc. Then export as a sequence and go over like in the way you did for a general grading of the sequences in LRTimelapse?
Or would one have to export as a jpg/png or tiff in order to do a 'layover' in LRTTimelapse?
I recently tried doing some grading in Davinci on a sequence that was already denoised in LR but exported as DNG.
But Davinci can't see the DNG of a file and only sees the RAW.
If however, if I export from LR as a jpg, png or tiff then I can grade over those denoised sequences in Davinci.
I'm thinking of trying this process but am having to resolve an annoying issue with LightRoom that I haven't been able to find an answer for even on the forums. And want to resolve first before trying this process here.
I have about 1k+ images of RAW (All at nighttime in a remote location so there's no short term increase of having additional light sources come along; meaning from frame to frame in RAW all the images are basically the same exposure, except the changing position of the stars).
I've tried this several times with different presets and my last test was just to go with a basic 'reset' Preset settings in Development.
When I apply that preset(or any other one) to all the images, I find that at about every 10 - 30 images, I get an image that is like it has had an entirely different preset applied. I get these images that stick out that are very different.
Can't figure out why Lightroom is not applying the preset/s consistently to each image.
I haven't tried doing this in smaller batches to confirm but the only thing I can think of is that Lightroom can only batch process a certain number of images at one time before getting 'wonky'.
Have you ever had this kind of issue?
Hmm that's fascinating. LR tends to have a mind of it's own, it is a very frustrating program. I'd definitely suggest giving it a try in LRTimelapse, I can almost guarantee it'll solve the issue for you.
@@Nateinthewild Thanks.
Is a Peak Design travel tripod strong enough for this long exposure. That is what I plan to carry on a trip into the mountains. Is it worth the weight and size in the backpack to go with a bigger tripod?
Personally I don't think the Peak Design tripod is good for almost any scenario. The Gitzo Traveler weighs the same and is literally twice as stable, but I'd recommend a series 2 tripod at a minimum for timelapses like this.
Yes, another thing, that damn "Save Metadata" and "Read Metadata" commands should NOT be right next to each other. I can't tell you how many times I've accidentally moved the mouse at the last second.
Hahaha YEP, I figured I should take a second to be VERY explicit about those commands because it's way too easy to accidentally reset your entire project
What computer monitor and laptop do you use?