Booradley
Second Officer
Flight distance : 11349537 ft
United States
Offline
|
UPDATE VIDEO IS STILL COMPRESSING as of the time of this post
Yikes! So glad I researched this as I almost forked out $250 for an antiflickering program for TL and HL. (I do professional video and have to opt for the commercial version). Even the free trial couldn't correct it... This thread gives me both hope and frustration. Hope because DJI will need to fix this, it is completely unacceptable and technically not functioning as advertised.
Here's what my problem looks like (and initially I thought I was capturing lightning strikes or just missing the strike but seeing the residual light??? But clearly that is not the case (I will post more examples)
(I just uploaded this to Skypixel 40 minutes before this post, apparently at this time it is still compressing, if it is not corrected soon I will reupload direct)
Thunderstorm Hyperlapse Flicker
At first I thought it could be a white balance issue and maybe it is... Reason being, I was operating with automatic WB, saving a raw copy, and everything else full manual. I would edit in Lightroom and started to think that maybe I was overediting it somehow, or maybe the copy and paste was being interrupted with my PC not having enough memory, becoming overloaded and corrupting the paste of settings. So then I upgraded the memory for my Ryzen 6 core CPU, from 32gb to 64gb. Still flickers... So I started thinking about it and remembered something about DJI's RAW files. I shoot with a Nikon D780 and D7500 along with DJI Mavic 2 Pro and Mavic 3 Cine. I never had any flicker problems with M2P, nor with my Nikon files for HL. But I do remember one big difference about DJI RAW versus Nikon's truly RAW (.NEF files). If you have a Nikon RAW file and click on it in Windows (any version) there is no preview because it is a RAW file and you need a plugin to translate it into a viewable image. If you click on a DJI file, RAW or not, you can always view a preview of it, like it's an MP4. I have long suspected because of this that DJI files are not truly RAW, they are simply Jpeg files programmed to work like a RAW file. If this is the case, I could see how you could bring flicker to WB because if the white balance is changing in the middle of your Hyperlapse. But, based on other comments above where people have used full manual WB, I don't think this is the case.
I sincerely wish I could provide a solution for this one but it looks like the best work around until DJI addresses the issue, is to use 2 seconds instead of 1 second.... Which I'll be honest, really sucks. I want to literally squeeze every bit of dynamic range out of an aerial hyperlapse as I can. And it seems like I will need to go back to my M2P because I don't care how sharp or how much detail you pull out of the shadows, if there's flicker, it's distracting and not professional. Which is completely unacceptable for a professional photographer to use for professional applications and as a long time fan of DJI, this type of neglect has certainly nudged me in the direction of seeing what else is out there. DJI is releasing a lot of products, fast, and we are already a year in to the Mavic 3. This needs to be a priority or it never will be and if DJI isn't willing to fix it on this platform, they should offer to exchange our M3's for M4's when they come out or issue a very large partial refund right now.
So will DJI do what's right or should we start discussing good alternatives to DJI? As a longtime fan and owner of P3Pro, 2 x M2P, Ronin SC2 and 2 x M3Cine, I am sincerely just hoping DJI addresses this right away....
Has anyone here opened a ticket with technical support? |
|