OnePlus 6 DxOMark Score Beats iPhone 8 Plus, Samsung Galaxy Note 8



[ad_1]

DxOMark, the popular camera testing portal, after a long wait, published its review of OnePlus 6. According to the test, the flagship product OnePlus received an overall score of 96, ranking it above the # 39, Apple's iPhone. 8 Plus and Samsung Galaxy Note 8 – which both have the same overall score of 94. That's behind the Xiaomi Mi MIX 2S, which has an overall score of 97. A score of 100 has been given to the OnePlus 6 while the phone is overall the score of the video is 87.

The photo score of any smartphone on DxOMark is calculated by combining different sub-scores between categories like Exposure and Contrast, Color, Autofocus, Texture, Noise, Artifacts, Flash, Zoom and Bokeh. In the case of OnePlus 6, the magazine notes that the smartphone surpbades in terms of autofocus considering that the performance is good in all lighting conditions. DxOMark says: "OnePlus 6 is one of the two most powerful models of the current range of high-end devices in our database [in the autofocus category]."

Another area where the dual camera back of the OnePlus 6 is very popular. Thanks to the double LED flash, the phone takes great photos with flash; photos that have a good exposure of the subject and a neutral white balance. However, some luminance noise has been noted and the texture is on the lower side. It has failed to function well in extremely light conditions. The performance of Zoom and Bokeh was below normal in the DxOMark review.

In terms of video performance, the OnePlus 6 would have obtained a "very good score" of 87 points. It has achieved very good results on such parameters as exposure, color, autofocus, noise and stabilization. The texture performance, in video, was below average.

"Negatives are rare for video capture, but retain little detail in most lighting conditions, especially in low light. to ring a combination of over-sharpening and other processing steps.There is also a slight loss of sharpness caused by exposure times that are too long, "noted DxOMark in the magazine that you can read here

<! –

->

[ad_2]
Source link