joe12south
Veteran
I appreciate what those who take exception to the findings indicate, but I must say that I think you are being willfully ignorant. A lot of people are apologizing for what Panasonic released, instead of calling it what it is...brittle, fragile, thin.
It's been well proven that this isn't a post-camera pipeline issue, nor operator error. It's really, really, simple to demonstrate on any number of common, naturalistic scenes. Or if you prefer, MATH: Nobody is making-up the fact that the profile only uses about 60% of the usable, raw bit range, and worse biases the image towards areas that the codec compresses most.
It's very difficult to avoid...but even if you can...WHY would you want to? Why not just use a linear profile if recording internally? It's so tempting to WANT V-LOG L to work internally. Who wouldn't want an extra stop of latitude? But the truth is, unless recording 10-bit to cover its sins, trying to do so is a big bag of hurt.
I made this post because I happened to be testing V-LOG L for Paul Leeming's new LUT, and was reminded just how fragile it is.

It's been well proven that this isn't a post-camera pipeline issue, nor operator error. It's really, really, simple to demonstrate on any number of common, naturalistic scenes. Or if you prefer, MATH: Nobody is making-up the fact that the profile only uses about 60% of the usable, raw bit range, and worse biases the image towards areas that the codec compresses most.
It's very difficult to avoid...but even if you can...WHY would you want to? Why not just use a linear profile if recording internally? It's so tempting to WANT V-LOG L to work internally. Who wouldn't want an extra stop of latitude? But the truth is, unless recording 10-bit to cover its sins, trying to do so is a big bag of hurt.
I made this post because I happened to be testing V-LOG L for Paul Leeming's new LUT, and was reminded just how fragile it is.
