Color space which setting to select?

[mihailuican]

@Pcristi:
as to afr, do you think their typical example for settings in the cfg file is the best for a HDR, UHD 8-bit TV like mine?
I mean BEST SETTINGS in terms of maximizing colorspace to 4:4:4 - and 12bit as much as posible?
Why not put averything inside 4:4:4:, 12 bit? Because it is not meeting HDMI 2.0 standards anymore and thus not possible?
I I were to put my best values in the cfg file, what would you recommend?
I attach my afr.cfg file.
These settings give me 4:4:4 12 bit color. (see attach)

[pcristi]

422/12Bit is safety option witch need cover all frequency 24/25/30/50/60 according HDMI standards also is preferred setting on blu-ray disc player, but not all TV/projector like it and can introduce severe color banding.
As probably you already see it AFR Assistant utility switch without failback check and can easy go on back screen/hdmi no signal.
Very few user will see difference between 422 and 444 on PQ.
Set as you prefer and use 12Bit where is possible if settings not introduce color banding.

LE: On your attached afr.cfg remove space before and after @, I'm not sure how AFR Assistant utility read parameters from line.

[Mount81]

pcristi: Which lines refer to in/out resolution and fps/Hz in and fps/Hz out and HDR / SDR status in your info tool?

I want to make a "simpler" version where only colorspcae, bitdepth, resolution,  fps/Hz and HDR/SDR info is displayed (but you can also make it if you want).

Edit: User (on a different Forum) reported, that if he sets the GUI to: 4K / 60Hz / 420 / 10bit the tool will report back 422 / 8bit while playing a video. And after the playback the GUI sets to "simple" 422 (no bits) in the Advanced Settings.

Edit2: Reported, that if he sets the GUI to 4K / 30Hz /444 / 10bit, itt will still that way during video playback and after he returns to the menu as well.

What could case this lame and unpredictable behavior of the bitdepth and colorspace switching during video playback?

In the case of 420 / 10bit GUI setting is should switch to either 444 or 422 10bit during video playback (eg. 23.976Hz), so why does it reduce and switch rather to 8bit? It's definitelly seems like a "bug" in how this auto switching works...

(OFW 2.1.1 and no additional patches installed).

Edit 3: I've corrected the first Edit as it it was 422 (no bits) and not 420 that the GUI has switched back after playback.

[mihailuican]

On your attached afr.cfg remove space before and after @, I'm not sure how AFR Assistant utility read parameters from line.

I removed all pauses, and also included ALL possible (complete) resolutions, with 4:4:4:-12bit.
I will test as many sample resolution films and see result, whether or not color banding, and with output info tool, and make downward adjustments where I will meet trouble.
When all results will be OK, I will attach here the file for everyone to use and test on their own, so we make sure maximized color and bit depth specs setup.
A good ide will be lake Mount81 said to have a shorter, more relevant in/out tool.
Cheers.

[pcristi]

@Mount81
Did you event read one time Q5Q10PRO-OUPUTINFO information? if Yes then you already know a answer.
FrcInRate/FrcOutRate/fps/SDR/HDR/etc.

Sorry I can't follow edits on your post.
HiMedia Setting/Display and Android settings/Advance options are relevant only if user don't use AFR scripts/AFR Assistant utility.
In first second when AFR scripts/AFR Assistant utility are install in box only reading output information will know real box output and a GUI information is become irrelevant.

[Mount81]

@Mount81
Did you event read one time Q5Q10PRO-OUPUTINFO information? if Yes then you already know a answer.
FrcInRate/FrcOutRate/fps/SDR/HDR/etc.

Sorry I can't follow edits on your post.
HiMedia Setting/Display and Android settings/Advance options are relevant only if user don't use AFR scripts/AFR Assistant utility.
In first second when AFR scripts/AFR Assistant utility are install in box only reading output information will know real box output and a GUI information is become irrelevant.

I guess you misunderstood my request. I just want to make a "simplified" version of the tool that ONLY shows the info's I've listed.

I don't know how AFR patch's concern my posts at all. I was as clear as possible to try to explain the issue reported by the user, sorry you couldn't decode. 

Nevermind...

[pcristi]

@Mount81
As "simplified" version of the tool can give a try of this one.

[Mount81]

Someone linked a solution on another Forum:

For setting 444 / 10bit (under 30Hz videos, while playing):

adb shell "echo outclrspace 2 > /proc/msp/hdmi0"
adb shell "echo deepclr 1 > /proc/msp/hdmi0"

For setting 420 / 10bit (for the GUI and videos with 60Hz or 50Hz):

adb shell "echo outclrspace 3 > /proc/msp/hdmi0"
adb shell "echo deepclr 1 > /proc/msp/hdmi0"

Will it work in a .bat file, like this?:

echo off
cls
taskkill /f /im adb.exe 2>NUL
set var=192.168.1.194
adb connect %var%:5555
adb shell "echo outclrspace 3 > /proc/msp/hdmi0"
adb shell "echo deepclr 1 > /proc/msp/hdmi0"
ping 192.0.2.2 -n 1 -w 7000 > nul
:Info
cls
adb shell "grep Color /proc/msp/hdmi0"
ping 192.0.2.2 -n 1 -w 7000 > nul
goto Info
exit

It looks like we need some "permission switches" also triggered first. But dunno' what exactly...

[pcristi]

Run script as root, will need to be OK, as I remember colorspace,  deepcolor is still there after box reboot.

Code: [Select]

adb connect %var%:5555
adb root
adb connect %var%:5555
adb shell "echo outclrspace 3 > /proc/msp/hdmi0"


[Mount81]

Run script as root, will need to be OK, as I remember colorspace,  deepcolor is still there after box reboot.

Code: [Select]

adb connect %var%:5555
root
adb connect %var%:5555
adb shell "echo outclrspace 3 > /proc/msp/hdmi0"


With this .bat file:

echo off
cls
taskkill /f /im adb.exe 2>NUL
set var=192.168.1.194
adb connect %var%:5555
root
adb shell "echo outclrspace 2 > /proc/msp/hdmi0"
adb shell "echo deepclr 1 > /proc/msp/hdmi0"
ping 192.0.2.2 -n 1 -w 7000 > nul
:Info
cls
adb shell "grep Color /proc/msp/hdmi0"
ping 192.0.2.2 -n 1 -w 7000 > nul
goto Info
exit

We get the following errors:

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 192.168.0.197:5555
'root' is not recognized as an internal or external command,
operable program or batch file.
/system/bin/sh: can't create /proc/msp/hdmi0: Permission denied
/system/bin/sh: can't create /proc/msp/hdmi0: Permission denied

What's wrong with the permissions? And why the command "root" not recognized?

Edit: Guess the adb was missing before "root":

echo off
cls
taskkill /f /im adb.exe 2>NUL
set var=192.168.1.194
adb connect %var%:5555
adb root
adb shell "echo outclrspace 2 > /proc/msp/hdmi0"
adb shell "echo deepclr 1 > /proc/msp/hdmi0"
ping 192.0.2.2 -n 1 -w 7000 > nul
:Info
cls
adb shell "grep Color /proc/msp/hdmi0"
ping 192.0.2.2 -n 1 -w 7000 > nul
goto Info
exit

Is this correct?

[pcristi]

Edit: Guess the adb was missing before "root":

Correct fix in OP
After adb root, need adb connect again if box run any CFW or start with v2.0.9 in OFW.

Code: [Select]

...
adb connect %var%:5555
adb root
adb connect %var%:5555
adb shell "echo outclrspace 2 > /proc/msp/hdmi0"
...


[mihailuican]

Hey guys,
after a couple of days of installing/uninsalling/modyfying afg.cfg files for several versions of FRT/AVR apps, the only one CERTAIN conclusions that I could draw up is that colorspace settings and bitdepth are NOT easy to understannd or FAR FROM CONTROL or setup.
Regardless what we write and modify in afr.cfg, the mediaplayer apparently has its own way on startup so modify your settings, playback specific files with OTHER settings than to ones that I throught I prescribed in the cfg file, so on ans so forth.
Many times I tried to force one 1080p series of films (hobbit and TLOTR) to playback 4:4:4:-12bit, and no AFR app could do so. Only Pcristi's FRT app could, with its default settings in its afr.cfg file.
Like my modifications were useless... The machine kept playing OTHER settings, not mine, as the OUTPUTINFO app indicated.
So I decided that I am lucky (if luck has anything to do with programming) anough to have my collection of 1080p played in 444-12bit and 4kHDR collection payed in 422-8bit so I will stop trying other setups or apps until something new appears.
Android and video playback applications ARE FAR BEYOND EXACT CONTROL. Is Erratic OR we still do not know weel enough how to control it, yet.
Cheers.

[Mount81]

Same observations as in the post above from 2 testing users on another Forum. HiMedia's auto colorspce and bitdepth switching on UHD resolution, works very unpredictable and unexplainable ways, thus' resulting in far-from optimal settings during playback.

Test results: Setting the GUI to 4K / 60Hz / 420 / 10bit, during the video playback (on 23.976Hz) it switched to 422 / 8bit every time. Returning to the GUI shows 422 (no bit's) in the Advanced menu.

Test2: Setting the GUI to 4K / 30Hz /444 / 10bit, during the video playback it kept these setting well, and after returning to the GUI it stayed this way also. (But very unsettling option is to keep the GUI on 30Hz all the time).

Tested with OFW 2.1.1. on two different model UHD / HDR / 10bit TV's and both with the info.bat tool and with the TV's own info displayed.

Just hope, that the following script started in a .bat file, will work for triggering 444 / 10bit mode even during playback.:

echo off
cls
taskkill /f /im adb.exe 2>NUL
set var=192.168.1.194
adb connect %var%:5555
adb root
adb connect %var%:5555
adb shell "echo outclrspace 2 > /proc/msp/hdmi0"
adb shell "echo deepclr 1 > /proc/msp/hdmi0"
ping 192.0.2.2 -n 1 -w 7000 > nul
:Info
cls
adb shell "grep Color /proc/msp/hdmi0"
ping 192.0.2.2 -n 1 -w 7000 > nul
goto Info
exit

Any risks or drawback that pcristi or any others know about concerning using a script like this -regularly- for colorspace and bitdepth switching on the player?

[mihailuican]

Hello Pcristi,
I am thinking of this: is your Q10PROOUTPUTINFO tool telling if the box is outputting HDMI1.4 or HDMI2.0a, given the cable used and tb hdmi pot settings? Just curious.

[mihailuican]

#Pcristi

attached outputinfo and DEBIG info, about 720p played as 1080p/23.976Hz with 4:4:4: 12 bit.
please feel free to comment.