AI is also there on 6z. But for some reason the stock camera images have gone good to really bad.
This might help you. CH_ASUS agreed to it
Were the picture taken night mode? Pls don't say yes??
I own 5Z and juz to let u guyszz know 5Z sensor has gr8 low light sensing technology compared to 6Z sensor,even 5Z sensor is gr8 at dynamic range thats all about sensor folks..✌️? @nishaanth5000
I see your point
Photos in artificial light are not atthe expected level
@Anders_ASUS @LP_ASUS are you guys going to give a camera update since we have provided enough instances here and comparisons between 5z and 6z. I want to know what is asus going to do about it. Please don't post a generic comment. We have paid hell lot for this device.
Read the whole thing, would you?
I know that other manufacturers are stepping over the legal line to help GCam ports, those manufacturers are based in China where copyright rule is like air and I get that ASUS can't afford to get into legal trouble. This is something I understand, but...
I would like to remind to you that breaking GCam with Android update with no good reason is like updating Python from 3.7 to 3.7.1 with no major feature changes and suddenly all the libraries won't work and Python rep comes out saying that the libraries are not made by Python so no support. A good example of software upgrade done well is Python 2 to 3. Sure, as in this GCam situation, thing are not backwards compatible, like print 1 in Python 2 and print(1) in Python 3. Python never ported one library from 2 to 3, but the are not crossing their arms doing nothing and defending with their mouth.
Let's compare Python 2 to 3 with ASUS Android 9 to 10 (in terms of GCam situation), don't mind if I point out the facts.
Feature upgrades: Python Yes ASUS No
Software that is broken: Python third-party ASUS third-party
Software that was fixed by first party: Python none ASUS none
Saying it is not their fault: Python No ASUS Yes
Breaking backwards compatibility without warning: Python No ASUS Yes
Summary | Feeling of end user: Python Good ASUS Not-so-good
(Feel free to argue that this is not the case besides GCam. This shows the split personalities towards first-party stuff and third-party stuff)
Telling us that GCam excels than stock camera so it is not a fair comparison, so compare with other phones with stock camera is like if Python breaks matplotlib in updates then says of course matplotlib plots better graph with inbuilt print() function so should compare Python's print() with C's println()
May we now compare Python with ASUS once again to drive my point home
Third-party software superior to first-party: Python Yes ASUS Yes
Allow the use of third-party software: Python Yes ASUS Tacitly-no
Blaming the comparison for not fair: Python No ASUS Yes
(I am a hobbyist programmer in Python and C, and if you don't know the terms wiki them. I believe only making such analogies can we make the mods realize how they must change to have a better image in everyone's eyes, after all, a mod commenting with the content basically a GTFO will certainly not be a good sign. I am always open for further discussion / debates.)
Buddy thank you for coming out and supporting us. It seems us raising a question has hurt their ego. They were in a dreamland thinking the devices priced with 6z don't have a good camera. Reality check @Anders_ASUS even a $110 dollar phone from realme has a better dynamic range and mind you i am comparing 6z with a device which is priced quarter of the price of 6z. If you can keep your ego aside and help in resolving this situation it would be helpful. #dontkillagreatdevice
It seems I owe you an apology. I've seen the other thread that compares results with 5Z and man, that's a big difference. Sorry for criticizing you in that regard.
As I have said and as the photo points out, no significant changes in stock camera app, but GCam broken. Have I spotted split personalities in different threads? You’ll be the judge.
Could you kindly check my new post? Referring to your 2nd paragraph , ive compared with an asus phone itself that sells at half the price of zf6 in my country , now Let's talk ?
ok, let me give you a preview of what I've been doing.
TL;DR (too long didn't read) = There are differences between Pie and Q but they are small, much smaller than you think. We will investigate further on how to improve. I will also ask them to double check our camera API's for improved compatibility with 3rd party camera apps
The much longer version
I've walked around the office with ZenFone 6 on Pie 1908.191 update, ZenFone 6 on latest Q 1910.68 update. ZenFone 5z on Q 20191115, OnePlus 7Pro on Q 02_BETA_6 and Mi 9 on Q 190825002. I've taken both indoor photos and several photos out of an open window. Each time with less daylight.
For every scene there's a new winner. The same scene during different hours with changing lighting conditions could sometimes present a new winner but it's also subjective which one you prefer. I think overall I would say that OnePlus 7Pro has the best camera but as I said, this is not always the case and in many cases, the difference between all phones is smaller than you think.
ZenFone 5z is not by any means a bad camera. During some conditions it performed exceptionally well. The problem is that no one expects it to. So in a scene were you only take one photo which ZenFone 5z and 6 and ZenFone 6 gets it wrong, it could very well be that ZenFone 5z is the winner. But if you move the camera way and back or focus on something, then you normally correct this. In some scenes where you photograph something with a lot of texture, ZenFone 5 could very well be the winner because it has a lot less noise reduction which results in more details.
I need to spend more time analyzing the photos but I can conclude already now, and this is the most important part for this thread, that the difference between ZenFone 6 with Pie and Q is not the major difference that you think. In most cases there's no difference at all. Sometimes Q win and sometimes Pie win. There are software differences but they are minor compared to how you take the image.
It happened sometimes that pie took the better photo and my reaction was always "what!?!" Every time I took one new set to confirm if it really was better and every time the differences were erased in the next set of photos. The conclusion is that it takes so little handshake that even a surgeon can have different results. I was leaning both body and hands against doors and window frames while using a shutter timer to make sure I was as steady as possible to minimize unfair differences.
I do notice that the AI may have a little different approach in Pie and Q but moving the camera away and then back again can make both recognize the scene in the same way. I'm not talking about which AI logo you see but the actual outcome of the image. I also believe there's a tad more noise reduction in the Q version compared to Pie and this can in some scenarios make a difference on textured surfaces. This is something I will feedback to our camera devs.
Another thing which both Pie and Q has is that the scene needs to be really dark for night mode to activate, or it will just take a normal HDR photo. You notice this when there's no circle loading. So in some scenarios, 5z could actually show a brighter photo. This is something my team asked the camera team to consider changing before and we will remind them again.
It feels like Pie spends more time in night mode than on Q but it's actually only two different types of approach on the animation. They spend the same amount of time taking and processing the image.
I will post images later but all in all, I can already conclude that the differences that you're experiencing are not there. I've seen all your comparison images but to these i reply that it's not hard to find instances when one camera is better than the other if you take enough of them. There are so many factors involved. If you experience that your camera performance has gone down, then it's only natural that you choose the samples that strengthens the point you want to make. If I wanted to prove that Pie is better than Q, then I might not have bothered to go back and take a new set of photos to double check if it was me shaking or a difference in the camera performance.
I do believe that we can make improvements to the AI because sometimes, it analyzes the scene incorrectly. It could be that while changing how the AI is supposed to detect a specific scene, we unintentionally changed something somewhere else (minor differences). I also believe we sometimes go a little too far with our noise reduction algorithms and that it may recognize texture as noise. I would rather lower this setting to show some noise and keep more details but it's easy for me to say and much harder for our camera team to solve. I have some observations and suggestions from my comparison that I hope can help them improve but it's too early to say.
Regarding GCam, this is a special subject. We haven't actively made any changes to prevent GCam from running and we can't actively focus on making it work because of the circumstances. What I can do is to ask our camera team if there's anything in our camera API's that may prevent 3rd party camera apps in general from working.
I hope this update makes you a little happier as I'm doing my best to make your voices heard.
@Anders_ASUS thanks for replying and taking your time
Really appreciate your efforts , we respect it . Hoping for more improvements in camera
Here are a few suggestions
hdr ++ isn't properly working in Q at the moment , its more contrasty than regular hdr+ (supposed to be opposite) shadows are more darker in hdr++ and there is slight pink tint too (shadows should be brighter and obviously without tints)
About night mode , noise reduction is waay to much man , actually in indoor lighting auto mode has more details and sharpness than night mode , i do see that you guys are trying to push out a more cleaner image through night mode , but we d rather have more details instead and that's the purpose of us wasting more time at snapping a night mode pic than a regular pic . Actually this could also be due to using a slower shutter speed in night mode or something off with image stacking , not sure , finding the cause is not my job anyway
AND MAINLY : SELFIES!!! HDR ON is changing my whole skin tone man , hdr literally works like a beauty mode effect now , its making making my skin whiter , I'm forced to use hdr off due to that , I've attatched documents , dont mind me , just for sample purposes
Also there are pink tints and green tints in night mode , in "not even that dark" conditions , look into that too.
An overall reduction in noise reduction will also give a big boost to camera , there is noise reduction happening even in broad outdoors , and it's killing the minor details and giving a watercolor look.
Hope you take these suggestions positively , and use it to improve our experience thanks .
Attaching samples of selfie hdr issue , give it a look.
Guess we should change the title of the thread (≧▽≦)
Expecting quick reply , thanks :) we need yo help
Thanks for your kind words. I need to take more "non HDR", vs "HDR+ AUTO" vs "HDR++" to really be able to say if we have made any major change lately but I would be surprised if it's any worse compared to an older Pie firmware.
The HDR++ has never been perfect but sometimes it gives really great results. We recommend to use this mode when there's time to experiment, otherwise HDR+ AUTO should always be your preferred mode.
Looking at your pics it actually does what it's supposed to do if we disregard this this was a selfie that it totally messed. I say this because it did brighten upp the dark parts in the second scene. The first scene didn't really have any shadows. The AI obviously failed to recognize these scenes correctly and brightened up your skin too much.
The way night mode works with these small sensors is that it blurs everything a little bit. All cameras that I've tried have this effect to a certain degree.
But anyways, I'll investigate our HDR more thoroughly and with the help from our users, I will try to act as a compass for our camera team.
I wish I could just just tell them to do a better job but that's is like telling an athlete to train harder to get faster/stronger. Duh! A lot of users on ZenTalk have actually made this request. Sure, it helps us understand that the camera is important to our users but we already know this.
But we can help them, because a phone camera isn't like sports. Sure, there's performance and enough performance will win every time but a phone camera have hardware limits. Limits that can be pushed with software. There are two parts of the software. One part is the clever one, where we see technologies like Night Mode. We can't help them with this part, but the other part is tuning. Everything with tuning are trade-offs and if I can tell them that our users prefer detail over noise reduction, then this is something that they might actually listen to.
I thought about the camera a bit and have these following tips / suggestions / problem analysis. Try to have a read, and if you see feasible items, insert into the to-do list.
For testing raw HDR capturing performance, try taking a photo of a flashlight shining at your camera. That is a repeatable test of dynamic range performance, and AI will be disabled since it seems nothing interesting. If your camera can handle that and the AI is good, you'll be dominating the competition
For HDR++ in stock, I have learned to that to take a good photo on current Q version, and possible in older versions as well, you need to tap a position that you want to focus strategically. Pick a spot where the brightness of it is between the darkest of the picture and the brightness of the picture. That way, when the camera takes the HDR, it works up a couple and down a couple from the current exposure, and you can prevent overexposed bright spot or underexposed dark spots (the pink hue will come). For a permanent fix, in HDR++ mode, change exposure measurement mode from just sampling the focus point to sampling the entire picture.
For AI detection in various versions, you can consider informing the option of adding an AI refresh button to the devs such that no need to face the camera away and face the desired object again due to AI miss
You said that the night mode may not be active when the scene is not dark enough, so I can already think of night mode AUTO and night mode ENHANCED already, so that in auto mode night mode turns itself on when necessary and in enhanced more it is forced on.
Now here comes a crazy idea, if overhaul of camera is not your thing. How about adding the option to change how the camera app works on the fly to act like different versions? Maybe install two camera apps on the phone, one is P .189 version, and one is Q .73 version. If pro mode is preferred then P version is launched and if more recent AI is preferred then Q version is launched. I don't know whether this can work, but since previously you said that it is possible that Q use same version of camera app as P, maybe there is a slight chance of this being a reality.
I hope it can help make ZenFone 6 camera great again
Thanks @Anders_ASUS , give it a test and forward our requests...
And about that selfie hdr skin tone problem.. it happens 90% of the time , my guess is.. for people with darker skintones , the camera thinks its a shadowed region and brightens it up , funny tho..
So if u have some one there with a darker skin tone try taking comparison pictures between hdr on and off...
Seems like the world's best selfie camera needs some attention too...
Thanks.. looking forward to the next update or the one after that.. :)
@Anders_ASUS thanks for the response its appreciated.... i have 1 issue though with it.... i did not ''pick an choose photo's to prove/justify my point'' pics are actually that bad.. an as i wrote before... an will show again in case you missed it....ive only taaken 15 pics with cam since A10 update... some are here some are on other site.... its bad man... like bad... hdr off hdr on an (what i refer to it as) hdr --
hdr off the white dude is flat.. no details no definition the wall an tree on left behind him black the other trees no details an all at all.... black roof.. black.... car...barely any red coloring in it streetlights same as man flat no detail or definition even the sidwalk is crazy looking...bad pic
hdr on... flat man continues to look....flat its a bit brighter yes.... trees still black with a hint of color wall is still darker than it should be sidewalk an streetlights still a mess hardly any detail recovery or anything else
hdr-- darker than no hdr!!! everything is a disaster the wall on left is darkest thing ever trees go blacker than ever even the sunlight is darker an still no real color streetlight is flat signs flat wall tree is flatter sidewalk is .... yeah.... no definition or detail from all 3 pics taken one after the other not handpicked an chosen but timestamped an proven ...just a hazy mess on all
what my viewfinder sees with hdr-- on
what it actually looks like
an the video jitter... oh man.. with stabilization on its pretty annoying to say the least even tip toeing its still there gsm arena picked it up 1st an pointed it out, an no one wants to walk around all day with a gimbal
what it looks like in 1080p 60.... you dont want to see 4k .... jitter all day long
would be to much to ask to possibly brighten up video as well... very window tint esqe on all resolutions... dont wanna sound like an ass but... (dont get mad) 5z bright would be nice in video... if it can be done
thanks again man... you are appreciated P.S gcam for zenfone 6 is the devil!!!...(not for 5z tho... cuz no nightmode)