In theory the results should be superior because of the bigger latitude of the RAW files. I don't know if that would lead to a visible improvement compared to the Jpeg workflow, so keep it with a grain of salt. apply fine tuned deflicker data to the (already pre-deflickered). import developed Jpegs into LRTimelapse with the project file Open in LR or Bridge, export developed Jpegs (no need for full quality/resolution) save project file (not yet implemented) xmp/RAW files into LRTimelapse -> ramp values, deflicker xmp data of the RAW images in a second pass. To squeeze out the last bit of quality of the RAW files you could create a project file of the first pass of deflickering and use this to fine tune the. They have some neat ideas how to get flicker free footage like keyframing, perhaps you could adopt some of those into LRTimelapse? The general consensus seems to be that this is the best deflickering software for timelapse (of course after having access to RAW data like LRTimelapse has), though I can't comment on how their deflickering algorithm performs compared to LRTimelapse'. Instead of doing a second pass in LRTimelapse you could use GBDeflicker directly in After Effects. We are basically discussing the issue you mentioned in this thread. What you are requesting would require a two pass deflickering process that is hard to implement and would require lots of manual work or extensive of scripting if I am not mistaken. Interesting, I had the same idea yesterday, but saved the reply to Alan's questions as a draft to write a more in detail reply later: This post was last modified:, 10:01 by Joachim Buambeki. Here after the 1st pass (slight deflickering applied):Īnd here is the end result after the second pass, you can see the blue line is very smooth and flickerless: This is the original sequence without deflicker: My experiences gave me really great results with this workflow, please let me now if this works for you as well. Because all of the settings are already applied, we can focus on deflickering with no side effects.Ĭertainly you can use this Idea for a ACR/AE based workflow as well. In the second pass we don't need a huge dynamic range anymore, what we need is accurate input to LRTimelapse for deflickering. Now you are safe to switch into JPG processing. Applying all your settings in the first pass will provide of the whole dynamic range your RAW files offer, a slight deflickering will not harm as well. This way you circumvent the constraint mentioned above. In Lightroom: Load metadata for this new sequence.You may have to "refresh" above the folder panel to see the new folder. Open the LRT_*-folder with the intermediate sequence in LRTimelapse, ignore the warning.Export the images with LRTExport plugin like you would for rendering the video.In this case I recommend making a second pass. If you have done a lot of processing to you images (thus changing the end appearance severely in contrast to the original files/previews) you will run into the situation, that the original/preview images doesn't match with your development results. Go back to Lightroom, read the changed Metadata.Use the Smoothness slider to get a fairly smooth curve but please don't overdo it!.Turn on deflicker, set reference area (see deflicker tutorial!).Make your edits/keyframes but don't exaggerate.Prepare your original images as usual in LRTimelapse.That's not really a problem, if you do it right you will get fantastic results, but you have to know how to do it. This is because a lot of the Lightroom/ACR development settings doesn't act linear. The more you change your development settings, the more inaccurate deflickering could get. Thus deflickering will be done on the original JPGs or - in the case of RAW files - on the JPGs embedded as preview in the RAW. The biggest constrain is, that LRTimelapse does not "see" developed images. As a matter of fact it is a fairly complicated thing. Okay, a lot of discussion has taken place because of uncertainties regarding the best way to deflicker. This post was last modified:, 20:52 by Gunther.
0 Comments
Leave a Reply. |