Not sure if that's a Straw Man, or just a circular argument.
No one (successfully?) reported it before, so it can't have been important. It can't have been important because no one reported it before.
And not content with telling me to stop posting, you are now deciding whether or not it's still a problem for
me. For the avoidance of doubt: Yes, yes it is. I still want to shoot 120fps 1080p rather than shooting in 2.7k or 4k at 30fps (because other speeds have artifacts too) and using other software and lots of time to downscale and reflow to get the result I want. It costs me time, which is a finite resource. How you could possibly imagine that that makes it not a problem
for me and somehow supports your argument about its insignificance, so that I should now apparently shut up and go fly is...well it's very revealing about your thought processes. You apparently think that everyone else should think and do as you do. Well...no thanks.
It's not a "huge" problem if you
know enough to work around it. It is a potentially "huge" problem if you shoot in 1080p while being
unaware of the issue and have no idea why your footage looks so awful and full of moire patterns even though you keep on adjusting the (non-functioning) sharpness settings. For commercial use, it is more likely to be rejected by people whose
job it is (such as TV companies) to be able to spot the quality issues that you might not be sufficiently qualified to judge. While some people are undoubtedly impressed by the aerial viewpoint itself; as you get closer to 'professional' use, the less that is important and the more quality is; as well as shooting in the correct mode and not leaving everything on Auto. So now I can already hear you winding up to say: "If you want
professional results, you should be using an
Inspire 2 or above anyway, blah blah etc." Wrong. Just wrong.
You apparently consider yourself somewhat of an expert in things 'gadgety'. The clue is in your chosen name. Did
you spot the problem? If so, did you report it? If not, why not? Is your
lack of complaining about it because you considered it unimportant
in general, or just to
you, so everyone else can just like it or lump it? Presumably your time is valuable to you, so maybe you made a choice...
You see, whether or not
you knew about it is a problem either way.
Either you, with your own enhanced skills, were unaware, or incurious about it just like "everyone else", in which case no one else reporting it before means nothing. They like you, just didn't spot it because they stick with one setting. I'd bet 95%+ of people just use 'Auto everything' and no ND filters and never use any of the faster speeds. It's kind of why the Spark is/was a success. One speed(29.97fps), one mode(Auto): go fly it. But you get what you paid for. I paid more for the P4Pro, so I want more.
Or, you
knew about it,
decided not to say anything and are now trying to retcon it as unimportant to feel better about your decision. How many hundreds of thousands of people could have had better video if you'd let DJI know about it early enough for them to consider fixing it? I only recently got the Obsidian and spotted it almost immediately. What's your excuse?
You've made it very clear that you only shoot in 4k because...reasons. So what are those reasons? Did you know about the problem or not?
BTW, the ISO being stuck at 500 for D-Log is also a huge problem and people complained about that too, but again: it's only going to affect the (significant) subset of people who color-correct their footage in post. A DJI representative who seemed to be involved in the decision actually come on a forum and told everyone they were wrong to even want other ISO settings (which were previously available before an update) because it
could produce poorer results. He was telling people who understand ISO settings and flat profiles and colour correction and who had previously got
better results than now: that they were idiots; rather than
advising people that DJI
think ISO 500 is best, but they were free to try other ISO settings and deal with the consequences. In bright sunlight you need a high value ND filter to make it work even half-acceptably, but do DJI supply those for free? Nope. So is there a workaround? Yes, don't shoot in D-Log because the results are awful. Due to DJI's arrogance, the mode is largely useless.
You've been similarly shafted with .SRT files. You have to strip them out, so DJI are stealing your time too, that same valuable time that you
either didn't spend in investigating all the modes in the first place,
or in reporting your findings to DJI if you
had found the problem before I did.
Complain, and keep on complaining until it gets fixed. If you don't continue to complain, DJI will - quite rightly - assume that if they ignore you long enough you'll go away and spend your own time on a workaround instead of them having to spend any of theirs fixing it.
Now the weather
is excellent and I
am going out to fly.
