Response to Cinema5D GH5 Criticism
Photo Moment - March 02, 2017
A rather unpleasant article was released about the GH5 by Cinema5D yesterday, and we're gonna talk about that. Plus, I'll clarify a mistake from yesterday's electronic vs mechanical shutter discussion.
PRODUCTS MENTIONED IN TODAY'S PHOTO MOMENT (MANY ARE AFFILIATE LINKS):
Panasonic LUMIX GH5: [B&H - https://bhpho.to/2kQ9LT3 ] [Amazon - http://amzn.to/2lE4X1U ] [Adorama - http://jal.bz/2lNYpQv ]
VIDEOS MENTIONED IN TODAY'S PHOTO MOMENT:
GH5 Bit Depth Difference Electronic vs Mechanical Shutter?: https://youtu.be/IfH07v5Tpwc
OTHER LINKS MENTIONED IN TODAY'S PHOTO MOMENT:
Cinema5D GH5 Article: https://www.cinema5d.com/panasonic-gh5-lab-review-10-bit-flaws-vlog-free…
EOSHD response to Cinema5D: http://www.eoshd.com/2017/03/cinema5d-slate-panasonic-gh5-call-v-log-10b…
And to be clear… I am genuinely that excited about the camera. Not because I'm a Luminary but because it's awesome. I am not going to discuss any shortcomings on a camera that isn't finished yet. I think my "cake in the oven" analogy is fair. Criticism can come once a finished product is in people's hands. Until then… reserve negative judgement on things that may change.
Since you are dealing with misinformation:-)
There seems to be some confusion around DFD. It has been suggested by users of one brand of m4/3 cameras, that DFD works by utilising the poor axial CA inherent in DFD capable lenses (and possibly other defects) which is why DFD does not work with other brand lenses, because those other brand lenses are optically, so superior and lack the defects that make DFD feasible.
Can Panasonic (ie, Sean Robinson, perhaps) address this suggestion, but also go into some detail as to how DFD does work; or point to any articles that don't just reproduce marketing materials with pseudo explanations? Would be appreciated, thanks.
DFD uses all optical information available from our lenses. Simply put, we use things like OOF blur at any given focus point, optical sharpness, etc to determine where the lens is at any given focus point. That information combined with the new vector tracking in the GH5 produce a focusing & tracking system that rival most PDAF systems (In my opinion after shooting with the camera for a few months now). Cameras prior to the GH5 don't have the vector tracking system, so tracking will not be as good as it is on the GH5.
The reason we state that non Panasonic or Panasonic Leica lenses may not perform as well as our lenses is because we do not profile the other optics with the DFD system. Its as simple as that. Not because of optical faults, not because x-brand makes better lenses or not. Those notions couldn't be further from the truth.
I hope this helps clear up some of the misinformation being spread by some people.
I have followed C5D for a while and every now and then they commit slips and mistakes like this, even more issues that require more technical knowledge, which is the case - there are often comments pointing out their mistakes. In my mind this is quite terrible, I'm not condemning mistakes but if you don't know something or you are not knowledgeable enough, just say so or ask for help, don't keep going and creating more misinformation.
Saying this is a color depth issue before even doing an external recording test to rule that out is just irresponsible. More importantly, this has all the signs of compression macro blocking, how could they not know it? This really put in check their technical knowledge, but again, the worst part is that there are already few places talking more in-depth about matters like color depth, chroma subsampling, codecs, type of compressions, etc. and then to spread misinformation, this will only makes matter more complicated.
Those that don't know much will take their word for it and keep spreading more misinformation. There are already plenty of bad tests of 10-bit 422, we don't need more articles perpetuating these mistakes. A guy by the name of James Miller that have been doing GH5 tests lately was quite more careful and did a lot of internal and external tests and he was able to eliminate these same compression issues and and even in 8-bit, proving it's not a color depth issue.
C5D should really do a proper test and correct themselves. But this also shows that people that need this level os result and pixel peeping will really take advantage of 400Mbps codec that should be based on the H.264 All-I Varicam's division AVC Ultra codec, a much more robust codec and then, as long as Lumix engineers can match it, there shouldn't be compression artifacts like the one found in the IPB 150Mbps codec.
About V-Log L and Cinema5D, I think EOSHD are right. The problems with V-log L could be partially down to the bit rate and h.264 codec which can have macroblocking which can be fixed with noise reduction like neat video in editing or if you render to a codec with has a deblocking option. Also knowing how to work with its limitations can really help as pushing it hard can cause issues if the bit rate isn't high enough or the best codec is used. If Cinema5D had used an external recorder in 10-bit to test the V-Log L footage, then that could have tested V-Log L properly in a robust codec like DNxHR or ProRes at higher bitrates
I know many had issues with V-Log L on the GH4, but with my Atomos Ninja 2 and GH4, I found aside from the noise which made it hard to use in areas with dark shadows and some banding in skies (not always), it was quite a bit usable if exposed to +2 stops and from seeing V-Log L footage on the GH5 from Neumannfilms in an older pre production camera, it looked quite good to my eye and better than other profiles in both color and dynamic range.
Comments from YouTube