The photos below show the varying effects of the Color transform parameter. In both sets of photos, the value of CT Fix Standart most accurately reproduced what I saw.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Color transform value = CT System
Color transform value = CT Mod 1
Color transform value = CT Fix Standart
In this set, the values of CT System and CT Mod 1 imaged the leaves with a sheen that wasn't visible in person. In contrast, the value of CT Fix Standart imaged the leaves more accurately, without as much sheen.
Color transform value = CT System
Color transform value = CT Mod 1
Color transform value = CT Fix Standart
In this set, contrary to what occurred earlier, the value of CT Fix Standart imaged the leaves with a sheen and was more accurate for it. The other values imaged without as much sheen and were consequently less accurate.
_____________________________________________________________________________________________________________
The photos below show the varying effects of the a) Tone & Gamma Curve parameters, and the b) Global Options parameters. I used the default values for every parameter. The Tone & Gamma Curve parameters were enabled/disabled jointly and the Global Options parameters were enabled/disabled all together. In all sets of photos, the most accurately reproduced photos were generated with the Tone & Gamma Curve parameters disabled and the Global Options parameters enabled.
Tone & Gamma / Global Options = disabled
Tone & Gamma = enabled / Global options = disabled
For me, the yellow leaves are reproduced more deeply and with more saturation here than in the 1st photo.
Tone & Gamma = disabled / Global Options = enabled
Again, the leaves' color is a deeper, more saturated yellow here than in the 1st photo. There was only a tiny difference between the 2nd and 3rd photos.
Tone & Gamma / Global Options = disabled
Tone & Gamma = enabled / Global options = disabled
As with the yellow flowers, these also were reproduced with a deeper, more saturated purple.
Tone & Gamma = disabled / Global Options = enabled
Again, as with the yellow flowers, the purple is deeper and more saturated here than the first flower. And again, there was only a tiny difference between the 2nd and 3rd photos.
So both the Tone & Gamma Curve settings, as well as the Global Options settings, are able to reproduce colors more accurately when used independently. Surprisingly, if I enabled all three settings together, then the colors (yellow & purple) lost some of their saturation/vividness. That is, the best color reproduction came from enabling just one of those settings, rather than all three together. The one setting that seemed best enabled was Global Options.
Below are some photos of white flowers. I didn't notice any differences between the settings here.
Tone & Gamma / Global Options = disabled
Tone & Gamma = enabled / Global options = disabled
Tone & Gamma = disabled / Global Options = enabled
hey man, mind if i have your config please? thats looks sick
Rasyad said:
hey man, mind if i have your config please? thats looks sick
Click to expand...
Click to collapse
It's nothing special. Those photos were not taken with a complete config. I enabled one feature at a time. Now I have my config set thus:
Color Transform = CT Fix Standart (for better color)
Frame Duration > Back camera = 0.5x (to help prevent overexposure)
Max. Exposure > Back camera = 0.6 * Max. Exposure Time (to help prevent overexposure)
Lib Patcher > Global Options = all enabled at DEFAULT values (for better color)
I've tried using the other settings in Lib Patcher and didn't see any improvement.
Which version of the Nikita's Gcam are you using? And do you know which is the best Gcam for Max Pro M1?
xpbachx said:
Which version of the Nikita's Gcam are you using? And do you know which is the best Gcam for Max Pro M1?
Click to expand...
Click to collapse
Search for Nikita's GCam on Google and join the Telegram group
Front camera doen't work on my RN5 Whyred with the Nikita's 8.2 v1.5
Any idea about the origin of this problem ?
I have nothing to do with development. You should ask on their Telegram group.
Related
...nothing special.
Just sets the lowest autobrighntess value to the minimum.
For people that not now what this will do, a small explanation:
1. Set your brighntess to manual and put the slider to the far left, well just to ne minimum value.
2. enable autobrighntess then
3. cover your lightsensor with your hand
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. screen brighntess should go to the minimum autobrighntess value, if you turn it into teh light again the brighntess of screen should increase again.
5. ..still cover the lightsensor with your hand, then turn on manual brighntess again - which you setted to the minimum value on step 1.
6. you will notice, that the minimum manual briighntess is far lower then the minimum auto brighntess.
Well this small patch fixes this "issue"
Well I this patch will work for Leedroids latest honeycomb rom.
Pls dont try it on other roms - you will regret it when you didnt make a backup.
But I still suggest to make a backup before falshing this also on Leedroids HC rom.
Lower Autobrightness values Mirror: Lower Autobrightness values
j4n87 said:
...nothing special.
Just sets the lowest autobrighntess value to the minimum.
For people that not now what this will do, a small explanation:
1. Set your brighntess to manual and put the slider to the far left, well just to ne minimum value.
2. enable autobrighntess then
3. cover your lightsensor with your hand
4. screen brighntess should go to the minimum autobrighntess value, if you turn it into teh light again the brighntess of screen should increase again.
5. ..still cover the lightsensor with your hand, then turn on manual brighntess again - which you setted to the minimum value on step 1.
6. you will notice, that the minimum manual briighntess is far lower then the minimum auto brighntess.
Well this small patch fixes this "issue"
Well I this patch will work for Leedroids latest honeycomb rom.
Pls dont try it on other roms - you will regret it when you didnt make a backup.
But I still suggest to make a backup before falshing this also on Leedroids HC rom.
Lower Autobrightness values Mirror: Lower Autobrightness values
Click to expand...
Click to collapse
Doesn't work.
Remove your hand from the sensor(that is said to cover it while you toggle auto brightness) and you are at the same brightness levels.
I've had a problem for quite some time where Google Maps on my OnePlus One displays the normal Map view in near-zero contrast (no matter the screen brightness). You simply cannot tell, looking at the screen with the human eye, the difference between roads and not-roads. In Satellite view it's fine (but of course uses much more data, memory, CPU, etc, and Satellite view is much busier on the screen, so that's not a long-term acceptable solution).
I'm running CM13 on my OnePlus One; there is no Contrast setting. (In Accessibility there are a couple of related ones, but they don't actually control contrast, and they don't solve this problem, and they're both marked experimental - may impact performance).
I found an app, Netman "Screen Adjuster", which works perfectly .. but has to be always running to hold the contrast adjusted, leaves a post in notifications (despite its option to not do so), is ad supported, etc - simply should not be necessary.
Why isn't there/ how can we add/ who do we beg/pay to add a Contrast adjustment to the normal Settings in CyanogenMod 13 ?
thanks!
Content of my post from CyanogenMod forums:
On my OnePlus One running CM13 [nightlies] - I'm not sure if this specifically started with my upgrade some months ago to CM13, or if it was this way on CM12 before also - the contrast in Google Maps is much too low. Basically it's impossible to see the difference between road and not-road in the normal Map view. If I switch it to Satellite view then everything displays fine. On some other forums I've seen similar complaints both from OnePlus users and from users of some other platforms. So it's a maps+contrast thing, not exactly specific to this model.
I've attached two screenshots and a camera photograph of the same Google Maps display:
One screenshot is of normal Map view, which viewed here displays perfectly, so it's not the actual graphic content, but how the OPO screen displays it.
The other screenshot is of Satellite view, which viewed here and with human eyeballs on the OPO's screen is fine.
The photograph is of normal Map view (I tested both with the screen brightness quite high and the also quite low, both show near zero contrast making the map view unusable to the human eye, so I'm only posting one photo here).
My guess is that either contrast or something about the graphics drivers for the OPO in CM13 are causing the valid underlying graphic bits to be displayed in very low contrast.
I'm not sure why I don't notice this in other programs, just in Google Maps.
Hm. It's definitely the OPO's Contrast setting. I found an app (which I don't like as it has to be always running to keep the contrast set properly) "Screen Adjuster" by "Netman" which makes Google Maps perfectly readable by setting Contrast to "-100" (exactly halfway between the default 0 and the maximum).
So, without using some dodgy app, how to control Contrast on OPO or more generally in CM13?
thank you.
Photo of Map view - no contrast:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Photo of Satellite view - looks fine
Screenshot of Map view (exactly the same thing in the first photograph) - displays fine on YOUR screen which has proper contrast, just not on a (my?) OPO:
Try to change the color temperature. It might do the trick. Settings>Screen>Color temperature
Now, that's interesting.
On my OPO with CM13 within Settings -> Display & lights -> LIVEDISPLAY, I had Display mode set to Outdoor (which seems to boost display brightness and whiteness, though in no place does it speak of contrast).
It has Color Temperature (which did indeed help .. at the expense of some need-to-get-used-to-that color variations; I've re-set those to the defaults of 6500K day and 4800K night), color calibration (100% for each of R/G/B, and changing that is definitely not what I was looking for ), Power consumption (no effect) and Enhance colors (no effect).
So while color temperature makes a difference it doesn't seem to be the ideal... but I played with Display mode, switching it from Outdoor to Automatic, and instantly Google Maps became readable.
This is in my home office, which is presently lit by subdued outside lighting on a clear sunny day. I need to go outside and stand in full direct sunlight to see if Automatic goes to Outdoor and again washes out Google Maps displays to zero-contrast unreadability.
It still seems weird that Contrast is controllable (witness "Screen Adjuster" and several others) but there is no Contrast control in Settings.
Many thanks!
Im glad that helped
There is a new feature in the newest firmware (9.1.0.178 or .177) called "Flicker reduction". If this option is enabled the control method of the backlight changes from PWM dimming to DC (-like) dimming which helps to reduce screen flickering. Under the option there is following note: "Reduce flickering on the screen. This will affect color balance and auto-brightness control".
Today I have done some measurements to find out if there is a real difference in color reproduction, screen brightness, etc. between the two modes.
Device under test:
- P30 PRO 6/128 GB (VOG-L29), firmware 9.1.0.178 C431
- Notes: battery at around 35-38%, no screen protector (and cleaned screen)
Tools:
- X-Rite ColorMunki Display colorimeter
- Color HCFR 3.4.0 software (OLED profile) for measurement (PC side)
- Voodoo Screen Test Patterns V3.4 app installed on the phone (for the different color patterns)
Measurement method:
- HCFR patterns: primary + secondary colors (fast) and grayscale
- The different color patterns were selected/switched by hand on the phone (this can cause some error in the measurements)
- EMUI color profiles: vibrant/warm and vibrant/default
- (The measurements were performed in ambient light)
Results:
Luminance, white point, color accuracy:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Grayscale:
Color gamut:
There are only small differences in the screen's color gamut using different dimming methods and brightness levels.
To sum up, the color gamut of the screen is nearly equal to the DCI-P3 color space (covers the sRGB color space in 100%) using the "vibrant" color mode. (in case of the "normal" mode the screen's color gamut is equal to the sRGB color space, but these measurements are not part of this test...)
For details (CIE diagrams), please see attachments.
Flickering:
If I look at the screen I can't identify which mode is currently activated, there is mainly no difference.....but if I look at the screen through a camera the difference is visible and noticeable. In case of the PWM control the screen flickers in the whole brightness range, while using DC (-like) dimming the flickering is less significant and is only visible using lower brightness settings (typically ~<25%)
Summary:
It can be clearly seen, that the vibrant/warm preset produces much better results in terms of color/grayscale accuracy (using both settings).
The DC (-like) dimming reduces screen flickering while there is no significant difference in the visual experience compared to the PWM control.
Very nice work. I forwarded this to our Display Analyst to see if he has any comments.
MishaalRahman said:
Very nice work. I forwarded this to our Display Analyst to see if he has any comments.
Click to expand...
Click to collapse
Thank you very much!
Small update:
Added CIE diagrams and a short summary about my findings on the screen's color gamut to the OP.
Congrats for your analysis. I had the same doubt. Tks
What about battery consumption, which is better among the 2 methods?
This needs to be more visible! Thank you!
SymptomAfter a Laya game is packaged into a Huawei runtime quick game, the game screen cannot be displayed in full mode, as shown in the following figure.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cause Analysis
The possible cause is that the screen adaptation code is not modified before packaging or the adaptation mode is not flexibly modified based on the screen.
Solution
Check the screen design mode specified by scallMode of the current game. Generally, before packaging, you need to perform full-screen adaptation for different modes. Currently, there are three mainstream design modes: exactfit, fixedwidth, and fixedheight.
l Exactfit: Forcibly stretch the screen in full mode. In this mode, the width and height of the canvas and stage are equal to those of the game design. The screen is forcibly scaled to the full-screen mode without considering the design. In this way, you do not need to perform additional adaptation and can ensure full-screen display in any model. However, when the rate of the physical width and height of the mobile phone is different from the designed value, the screen will be stretched and deformed.
l Fixedwidth: height-adaptive mode, which is applicable to portrait screen games. Canvas width and stage width are equal to the designed values. However, the canvas height and stage height are scaled based on the rate of the physical width to the designed width. The width is fully proportional, and you only need to adjust the height. You can drag the background to the full screen by setting the relative layout attributes top and bottom.
l Fixedheight: width-adaptative mode, which is applicable to landscape screen games. In this mode, the canvas height and stage height are equal to the designed values. The canvas width and stage width are scaled based on the rate of the physical height to the designed height. The height is fully proportional, and you only need to adjust the width. You can drag the background to the full screen by setting the relative layout attributes left and right.
For the preceding values of scallMode, you can use different screen adaptation methods for different Laya versions when you pack Huawei quick games.
● laya.1.x
The adaptation method is provided in huawei-adapater.js. You only need to introduce huawei-adapater.js and add the screen adaptation code after Laya.init at the game entrance in the code.js file to redefine the stage width and height and designed width and height.
Code:
1. window.getAdapterInfo = function (config) {
2. let scaleX = 1;
3. let scaleY = 1;
4. let vw = window.innerWidth;
5. let vh = window.innerHeight;
6. let w = config.width;
7. let h = config.height
8. config.scaleMode = config.scaleMode.toLowerCase();
9. switch (config.scaleMode) {
10. case "exactfit":
11. scaleX = vw / w;
12. scaleY = vh / h;
13. break;
14. case "fixedwidth":
15. scaleX = scaleY = vw / w;
16. break;
17. }
18. return {
19. scaleX: scaleX,
20. scaleY: scaleY,
21. w: w,
22. h: h,
23. vw: vw,
24. vh: vh,
25. rw: w * scaleX,
26. rh: h * scaleY
27. };
28.};
29.Laya.init(600, 400, WebGL);// Here, 600 and 400 need to be changed to the designed width and height.
30.Laya.stage.scaleMode = "exactfit";//exactfit is used as an example only. You need to replace it with that in your game.
31.// Screen adaptation.
32.if(typeof getAdapterInfo !== "undefined"){
33. var stage = Laya.stage;
34. var info = getAdapterInfo({width:600, height:400, scaleMode:"exactfit"});// Change 600 and 400 to the values designed for the quick game.
35. stage.designWidth = info.w;
36. stage.designHeight = info.h;
37. stage.width = info.rw;
38. stage.height = info.rh;
39. stage.scale(info.scaleX, info.scaleY);
40. }
41.// Screen adaptation ends.
laya.2.0~~laya2.8.0
Add screen adaptation code following the program entry in the bundle.js file. Sample code:
Code:
1. // Entry.
2. // Initialize the loader based on the IDE.
3. if (window["Laya3D"]) Laya3D.init(GameConfig.width, GameConfig.height);
4. else Laya.init(GameConfig.width, GameConfig.height, Laya["WebGL"]);
5. Laya["Physics"] && Laya["Physics"].enable();
6. Laya["DebugPanel"] && Laya["DebugPanel"].enable();
7. Laya.stage.scaleMode = GameConfig.scaleMode;
8. Laya.stage.screenMode = GameConfig.screenMode;
9. Laya.stage.alignV = GameConfig.alignV;
10.Laya.stage.alignH = GameConfig.alignH;
11.// Screen adaptation.
12.if (typeof getAdapterInfo !== "undefined") {
13.var stage = Laya.stage;
14.var info = getAdapterInfo({ width: GameConfig.width, height: GameConfig.height, scaleMode: GameConfig.scaleMode });
15. // Note: GameConfig.width and GameConfig.height are the width and height of the quick game in the demo, respectively. Set them based on your needs.
16.stage.designWidth = info.w;
17.stage.designHeight = info.h;
18.stage.width = info.rw;
19.stage.height = info.rh;
20.stage.scale(info.scaleX, info.scaleY);
21.}
22.// Screen adaptation ends.
If the preceding methods cannot take effect, you can enable the retina canvas adaptation mode in versions later than Laya 2.0 to adjust the game screen adaptation. Sample code:
Code:
1. // Entry.
2. // Initialize the loader based on the IDE.
3. if (window["Laya3D"]) Laya3D.init(GameConfig.width, GameConfig.height);
4. else Laya.init(GameConfig.width, GameConfig.height, Laya["WebGL"]);
5. Laya["Physics"] && Laya["Physics"].enable();
6. Laya["DebugPanel"] && Laya["DebugPanel"].enable();
7. Laya.stage.scaleMode = GameConfig.scaleMode;
8. Laya.stage.screenMode = GameConfig.screenMode;
9. Laya.stage.alignV = GameConfig.alignV;
10.Laya.stage.alignH = GameConfig.alignH;
11.// Screen adaptation.
12.if(typeof hbs !== 'undefined'){
13. Laya.stage.useRetinalCanvas = true;
14.}
15.// Screen adaptation ends.
After the adaptation, the game is displayed in full-screen mode, as shown in the following figure.
Checkout in forum
Continuing from Part 2 (Best ColorOS Features). Also, here's a link to Part 1 (Built Quality & Design, Performance, Battery).
4. Camera
The main highlight of OPPO Reno8 5G is the camera. As a phone photographer, I am excited to find out its performance. Let’s check about the specs and what shooting mode it supports.
Rear camera consists of main camera (50MP Sony IMX766 sensor), wide-angle (8MP IMX355) and macro camera (2MP). Front camera has 32MP Sony IMX709 sensor. For video, the default for rear camera video is [email protected], maximum is at [email protected] While for front camera video is [email protected] (max).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Triple camera setup
Shooting mode available: Photo (default), Night, Video, Portrait, Pro, Extra HD, Pano, Macro, Slo-Mo, Time-Lapse, Dual-View Video, Sticker, Text Scanner, Soloop Templates (this won’t appear if camera is launched from lock screen)
Shooting mode available in Camera app
While it has so many modes, I have not used them all yet. I took some samples under different lighting condition, indoor and outdoor, daytime and nighttime.
Let’s explore and check the result! Camera app is easy to use and pretty straightforward.
This is my default setting for Photo mode, I enable HDR AUTO and AI function, it gives me the finest photo result with sharper detail and better color reproduction.
The lens will detect the type of object inside (mine says Green Plants). The 3-dots on the top left provides more options. The google lens icon is on the bottom right for easy access. The magic wand provides various filters.
As my photos are intended for social media, I seldom use 50MP because of the storage limitation.
[Shooting with Main Camera - Photo mode]
I am doing food photography for my business in social media. And I need a good phone camera to achieve the result I want.
Under sufficient/bright lighting condition, main camera can deliver ultra-clear shots. The image quality is impressive, with sharp details and vibrant colors. AI and HDR Auto are very helpful in achieving this high-quality result even without using 50MP mode.
I notice that there is a slight improvement if 50MP mode is used. However, the file size is something to think about.
AI on VS AI off
50MP on VS 50MP off[Shooting with Extra HD Mode]
This mode can cater up to 5x zoom. And there are filters available to use to further enhance the image result. I feel satisfied with the result without using any filter, but having the filter that matches with the final result I want will save time in editing.
[Shooting with backlight]
Normally, at this shooting condition, the object would be dark so the background could be seen OR the object could be seen, and the background would be in extremely bright condition. But now…
I am impressed on how the result turns out. The object and the background have the same exposure. Also, the portrait mode blurs out the background nicely.
Well done!
[Shooting in dim-light condition]
Don’t be fooled by the lightings, since the actual condition is pretty dim. And I notice the result is good for all zoom. Any slight movement during photo taking will affect the result in this kind of light condition. In my photos, some details on the edges are not too sharp for normal and wide-angle, I think I did move slightly.
Camera mode: Photo
Location: Changi Airport Terminal 3
[Shooting for night photography - indoor]
To be continued in Part 4.