![]() As you can see the 4 keyframes I set don't correspond to any exposure jumps so not really sure what I'm doing wrong.Ģ. I have tried rotating and stretching the curve but cannot find a working set up. Even though the exposure of all the images was OK in Lightroom, when the holy grail curve is added, the luminance/exposure of the entire sequence goes much too bright. I edit my 4 keyframed images in Lightroom to my liking and then reload them to LR Timelapse. I then set the holy grail keyframes as seen in the attached image. In the timelapse I'm currently working on I have set 4 manual keyframes. Set my initial keyframes, select the holy grail wizard, save, make my edits in Lightroom, return and reload my XMP data and then auto transition and visual preview. I think I'm following the correct method. I've recently been toying with the Holy Grail method but have encountered some issues on every one I've tried so far. I absolutely love LRTimelapse and how easy it makes timelapses now. Guess what I'm not doing? UPGRADING! The R5 is looking pretty good right now.This post was last modified:, 01:28 by gavinsheehan. Interesting to know that the A7R4 is just as screwed up. Honestly, I'm back to using my A7R2 in some cases to deal with this crap. I know the sensor is ISO invariant, but jacking up the post exposure by 3 or 4 EV seems to induce some extra noise. That's why there is a MAX ISO setting! Why dump your operating philosophy when the internal intervalometer is used?Īs it is now, I have to crank up the exposure in post (even at ISO 800) to make this work. I can see that they don't want to over expose and blow things out, but they should ramp the ISO to the MAX ISO setting when the camera cannot meter. I have no idea what Sony is thinking with their internal intervalometer software. This is way too low! However, if you bias up +3 EV you only get ISO 800. For a holy grail timelapse, if you don't bias up EV, it settles on ISO 400 for dark times when the camera can no longer meter. The thought of carrying an external intervalometer is nauseating. I'm a landscape photographer carrying gear in a backpack deep in the Grand Canyon over may days. Be sure to manually crank down the EV shortly before dawn or you'll blow it out. You only have two options: 1) use an external intervalometer and it works fine, or 2) manually crank in +3EV as it gets really dark (+1EV steps over time) and use LRTimelapse to smooth out the transitions. Obviously, this is far too low for really dark nights when you're shooting the Milkyway. Ironically, this works quite well on the A7R2 where the ISO will float up to the MAX ISO setting in really dark conditions, but the A7R3 arbitrarily halts increasing the ISO at 400 when using the internal intervalometer. I set the camera(A7R3) to aperture priority and minimum shutter to 15s allowing the camera to adjust the shutter first (to 15s exposure) then start increasing the ISO (ISO max set to 12,800). I shoot a lot of holy grail (sunset to Milkyway to dawn) lapses. I wonder if the R5 would have been a better choice? Buy a new camera and watch your productivity plummet. ![]() My website has one of my timelapse films on the home page that I made from many a7r2 holy grail lapses in the Grand Canyon (here): I can't believe I have to eff with an a7r3 to do this kind of thing. I feel stranded with an expensive paperweight. I'd switch back to firmware version 3.0 if Sony would allow you to. I've shot 100's of holy grail lapses with my a7r2's and a6000's using the Sony timelapse app. Unfortunately, after shooting some milkyway lapses with the a7r3, I've discovered that I can only get about 500 to 550 hi iSO 15s exposure shots on a battery so a USB bank is still going to be required. One of the most attractive things about the a7r3 was the bigger battery. ![]() I always run out of power for milkyway lapses so I usually need to have an external USB battery attached. I did a test today with an external intervalometer in the USB 2 port and a USB battery in the USB C port and it worked fine. Clearly a bug was introduced in the new firmware. I wish they would just ask engineering why version 3.0 firmware works and 3.1 firmware doesn't. The AEL tracking sensitivity doesn't affect this bug in the least. Unfortunately, Sony's response is worthless.
0 Comments
Leave a Reply. |