If Mavic#1 isn't fixed, it would be like we paid to become their beta testers.
Actually, this can be said for any newly designed product on the market. Early adopters is what we are called and there will always be risk with these type of purchases. I would say that this is a highly successful "beta" program considering the overall success of the Mavic and it's ability to perform as it was designed. The product can always be improved, and it should with each future upgrade, like most products do. Easier for me to say because my Mavic doesn't have the level of issues this thread describes. Regardless, I accepted the risk of being an early adopter with this purchase, as should we all. And it's great how people are finding work arounds for their specific issues, I've learned a lot from this thread should a similar issue arise with me. I hope your issues get resolved so you don't feel like you paid to be a guinea pig, because I think we all paid for a terrific piece of technology!If Mavic#1 isn't fixed, it would be like we paid to become their beta testers.
I agree with you that it's an amazing piece of technology but not that we should accept it's flaws because we're early adopters. If they'd given me the thing to test for them that would be fine but I paid a shedload of cash for it & I would expect it to be tested & fit for purpose. I certainly wouldn't expect any tech, TVs, cars, to be released with the type of issues that this thing has.Actually, this can be said for any newly designed product on the market. Early adopters is what we are called and there will always be risk with these type of purchases. I would say that this is a highly successful "beta" program considering the overall success of the Mavic and it's ability to perform as it was designed. The product can always be improved, and it should with each future upgrade, like most products do. Easier for me to say because my Mavic doesn't have the level of issues this thread describes. Regardless, I accepted the risk of being an early adopter with this purchase, as should we all. And it's great how people are finding work arounds for their specific issues, I've learned a lot from this thread should a similar issue arise with me. I hope your issues get resolved so you don't feel like you paid to be a guinea pig, because I think we all paid for a terrific piece of technology!
I don't think we need to accept its flaws either. I said we accept the risk. With risk, comes the potential of problems and unmet expectations. As early adopters, we are, by definition, first time users. Maybe even testers to a degree. But I digress. If my Mavic had these major flaws I would not accept it and send it back for repair or replacement. We know DJI is doing this service, so I think I would go that route. A PITA to be sure!I agree with you that it's an amazing piece of technology but not that we should accept it's flaws because we're early adopters. If they'd given me the thing to test for them that would be fine but I paid a shedload of cash for it & I would expect it to be tested & fit for purpose. I certainly wouldn't expect any tech, TVs, cars, to be released with the type of issues that this thing has.
They don't all have it, but it seems that many do. If you post video for others to help you determine, be sure to note the settings you used.Got this issue also. Do they have it all or not?
I've had a bit more of a play around with this watercolour issue today. I was hoping the new firmware might have sorted it out. No luck there.
As I've mentioned before, it seems to be a function of level of detail in a scene and also light level.
Here's an example of the effect being a function of light level.
The sunlit grass under the tree looks ok but the grass in shadow has turned to mush.
I shot this on d-log -1,0,0.
I could have shot it at 000. That may have corrected the shadow detail but would have made the sunlit detail horribly digitally sharpened. I've been down that route before...
And in the shot of the sunlit trees, notice that there's a distinct level of detail above which there's definition and below which it's mush.
Once again, correcting to raise that level and get formerly mushy detail to be ok means everything that formerly was ok now becomes over sharpened.
With focus, the last few flights I've adopted what others here have suggested. It's a bit of hassle but when you get used to it it gets easier to remember. Start in auto focus. First thing after take off, get up to 40ft. Flick the camera straight down. Touch to focus, then toggle to manual focus & leave it there. Unless you're getting very close to objects during the flight everything, for my Mavic anyway, stays focussed.Got it up in the air and had everything on standard. Was using the auto focus on the white building back/center. It looks better than this morning, but still seems like its not focusing correctly? As the front parts seem to be rather in focus. Or am I expecting too much from the small sensor?
View attachment 8313
That looks a bit more than just the difference between DLog and Art. However my advice would be try Art -1,-1,0. D-log, even in it's latest100pct crops
Mavic from a friend:
My magic under same circumstances
Only difference here I was shooting in D-log, he was shooting in ART. Something wrong here. Replace?
With focus, the last few flights I've adopted what others here have suggested. It's a bit of hassle but when you get used to it it gets easier to remember. Start in auto focus. First thing after take off, get up to 40ft. Flick the camera straight down. Touch to focus, then toggle to manual focus & leave it there. Unless you're getting very close to objects during the flight everything, for my Mavic anyway, stays focussed.
I believe that every Mavic is different. I have done my own tests over the past several months and my results are as follows:That looks a bit more than just the difference between DLog and Art. However my advice would be try Art -1,-1,0. D-log, even in it's latest
form always looks just to muddy to me. Just too flat to get the image up in post. Personally unless you've never had one good image, I'd avoid sending the thing back to DJI.
Having followed this thread from page 1 and this issue from the moment it popped up AND having dealt with it myself in still images, I've come a few highly scientific conclusions (not)...
This isn't a real issue. It's a combination of user error and excessive expectations. This "issue" is only affecting a predictable group of folks:
1. People who insist on shooting negative sharpness values while complaining about a lack of sharpness.
and
2. People shooting a flat, log profile on already flat, nearly monochromatic scenes in which there's absolutely no reason to be using a log profile. Do you even know what the log profile does?
We use essential cookies to make this site work, and optional cookies to enhance your experience.