anon(7901790)
Well-known member
Hmmm. Good question. I have my display set to max resolution. That may be a factor. Also, if you're streaming to a TV that is not 4K, the video may not look as great as if you're watching it on your phone.
I don't think that's it. The extreme macro-blocking is visible at the phone's maximum screen resolution, as well as on UHD monitors, as reported earlier in the thread. But most of our S8-recorded UHD videos look fine whatever resolution they're replayed at (just some specific kinds of shots show the problem). (And aren't macro-blocking artifacts more likely to arise when converting from low-res recording to hi-res playback than vice versa?)I don't know if this has been asked before but OP, what resolution is your screen set on?
Except for you, everyone here who reports having tried the rapid trees-to-bright-sky pan says they encountered the macro-block problem. Again, it would be helpful if you could post your video for comparison.
Exactly. Like you, I initially posted here that my phone didn't have the macro-blocking problem, until I tried that specific shot and found that it did.Ok. I think I see the "problem." I'm just not sure I can explain it easily. It has something to do with rapidly changing from a darker (trees) to a lighter (sky), and the camera is trying to keep the proper exposure.
Possibly, though to my knowledge that hasn't been reported in other UHD-video phones. (If anyone knows of such reports, I'd appreciate a pointer.)It's part of the nature of digital photography/videography. When transitioning from a relatively dark area to a much brighter area the sensor is going to have a hard time compensating for the abrupt change. Especially with the small, relatively cheap sensors that smart phones use. If you did the same thing with an iPhone or LG G6 I'd be willing to bet that you'd have the same problem, maybe less pronounced, but the same problem.
Possibly, though to my knowledge that hasn't been reported in other UHD-video phones. (If anyone knows of such reports, I'd appreciate a pointer.)
I'm not sure I understand the explanation you're proposing. What sort of "hard time" would the sensor have making the transition? The only thing that occurs to me is that the transition could be delayed; but it doesn't look like that's happening. First, even though the problem arises during the overall tress-to-sky transition, the macro-blocking itself is within the sky region, including areas of the image sensor that stayed within the sky the whole time. And second, I don't see how brightness-transition-delay would result specifically in macro-blocking (and without any evident change in the playback image's overall brightness).
My tentative guess would be that we're seeing a flaw in the compression algorithm.
Um, yes, that's why I requested any pertinent information, if it exists.Exactly, to your knowledge.
Thanks, I appreciate the further details. But what still puzzles me is that during playback, there's no apparent change in the brightness of either the trees or the sky during the rapid panning. And both regions of the image continue to seem properly exposed. How can that be explained if there is a lag in ISO adjustment?When transitioning from a dark area to a light area, the camera has to lower the ISO. The processor has to register the change in brightness, then lower the ISO to compensate. That time it takes to register the change and make the change is not instantaneous.
But why the particular artifact of sky-region macro-blocking? If anything, the fast transition would result in overexposure of the bright region, not underexposure, correct? (Though in fact, neither is apparent.) I can see why underexposure might result in macro-blocking, but why would overexposure do so?Because of the fast transition from dark to light, you're going to get artifacts, which the processor can't process out.
Don't S8s have separate GPUs? Also, the intricate trees and leaves remain crisp during the panning, while the relatively uniform, easily compressed sky information is what's macro-blocked. That doesn't sound like processor overload.Smartphones, unlike dedicated cameras[,] don't have dedicated image processors. It has to do all of that as well as monitor for incoming phone calls, location, wifi, bluetooth, etc.
If you "update" software in a way that degrades its performance compared to older software running on older hardware, that's what's called a "bug".The newer phones also run updated software that requires more processing speed and ram to keep it running smoothly.
Why offer 4k shooting ability if you can't do it right? Why does it also affect QHD quality on those handsets suffering from the issue? And most importantly: Why are some on this thread not suffering from this issue? The argument doesn't make sense, and Samsung is clearly saying it "isn't right" in that they're offering to fix/replace the phone.
Why offer 4k shooting ability if you can't do it right? Why does it also affect QHD quality on those handsets suffering from the issue? And most importantly: Why are some on this thread not suffering from this issue? The argument doesn't make sense, and Samsung is clearly saying it "isn't right" in that they're offering to fix/replace the phone.