Q5/Q10 Pro Official Firmware

[mihailuican]

Thank you Pcristi,
was this the implicit setting, because I did not change it. If it is default, then it should have not interfered.
I think I found, the guilty:
In settings-More - Video Output - Maintain Aspect Ratio - It was setup to EXTRUDE, not ADD BLACK BARS...
Do you personally think that in terms of Picture Quality and Image IQ, 2.1.0 is and ENHANCEMENT compared to 2.0.6 and I SHOULD upgrade.
(I don't mind renaming srt to txt, it is easy, I can do it while I rename the movie and the subtitle the same).
Cheers.

[Mount81]

mihailuican: Have you checked if in the case of the renamed .txt subs, are all the character customizations still working in HiMedai Player?

And have you (or any others) checked also on OFW 2.1.0, that embedded PGS (found mostly in Remuxes) and external PGS subs (.sup extension must be renamed to .ass) is also working flawlessly and without any line skipping issue?

I can provide a test video and subs for testing, if needed.

Thanks!

[pcristi]

Thank you Pcristi,
was this the implicit setting, because I did not change it. If it is default, then it should have not interfered.

FW v2.0.9/v2.1.0 is implicit setting is Full Screen and is not change from HiMediaVideoPlayer, so need to be change it to Keep ratio from  Settings/PlayBack.

[mihailuican]

mihailuican: Have you checked if in the case of the renamed .txt subs, are all the character customizations still working in HiMedai Player?

And have you (or any others) checked also on OFW 2.1.0, that embedded PGS (found mostly in Remuxes) and external PGS subs (.sup extension must be renamed to .ass) is also working flawlessly and without any line skipping issue?

I can provide a test video and subs for testing, if needed.

Thanks!

Actually no, I did not check thoroughly, I just took for granted and true what someone else wrote in the forum, I renamed a srt subtitle simply as txt, with no other modifications, and the subtitle played OK without problems, WITH DIACRITICS, for a few minutes thatI watched.
I did not perform any statistical, methodicatl, complete, thorough tests. Just superficially, at first sight.
The reply that I mentioned is in a forum here, and the post actually was a response to YOU. Check here: http://www.futeko.com/newforum/index.php?topic=2109.0

I would LOVE to be sure if the txt subtitle works completely. Cheers everybody.

[mihailuican]

Thank you Pcristi,
was this the implicit setting, because I did not change it. If it is default, then it should have not interfered.

FW v2.0.9/v2.1.0 is implicit setting is Full Screen and is not change from HiMediaVideoPlayer, so need to be change it to Keep ratio from  Settings/PlayBack.

THANK YOU.
Please, also question 2 above, very important for me: Image QUALITY and PQ of 2.1.0 vs 2.0.6.  Is there any NOTICEABLE increase in quality so that I should UPDATE?  Thanks.

[stl]

Thank you Pcristi,
was this the implicit setting, because I did not change it. If it is default, then it should have not interfered.

FW v2.0.9/v2.1.0 is implicit setting is Full Screen and is not change from HiMediaVideoPlayer, so need to be change it to Keep ratio from  Settings/PlayBack.

THANK YOU.
Please, also question 2 above, very important for me: Image QUALITY and PQ of 2.1.0 vs 2.0.6.  Is there any NOTICEABLE increase in quality so that I should UPDATE?  Thanks.

There's no noticeable image quality difference, you shouldn't upgrade because of that.

[Mount81]

Does OFW 2.1.0 and/or 2.1.1 have the option 422 / 12 bit in the Advanced settings? Or do we necessary need the CFW or install the AFR patch for the 12 bit option?

Please clarify this, thank you!

[pcristi]

OFW v2.1.0/v2.1.1 don't have written option "422 12 bit" is only 422.
12bit mode need to be check on TV info or via adb shell a result will vary by TV models.

Note: Support for 12Bit in 422 without scripts is community users observation and are not official HiMedia announcement about 12Bit support with OFW.

[Mount81]

OFW v2.1.0/v2.1.1 don't have written option "422 12 bit" is only 422.
12bit mode need to be check on TV info or via adb shell a result will vary by TV models.

Note: Support for 12Bit in 422 without scripts is community users observation and are not official HiMedia announcement about 12Bit support with OFW.

So if we set to the "simple" 422 in Advanced setting it is possible (if the TV supports it) that it would switch to 422 12bit during video playback even on OFW?

And the way to use ADB shell for checking:

adb connect boxipadresshere
adb shell "grep Color /proc/msp/hdmi0"

Than it will display the current colorspace and bitdepth values.
That's all, am I correct?

And if we install the AFR patch, will there be a visible option in the Advanced settings for 422 12bit?   

Thanks!


Info to add: There has been user complains, that from 4K / 60Hz / 420 / 10bit setting the Box will switch back to "simple" 420 (with no bits) every time after any video playback. And as far as I know the "simple" 420 setting is just 8bit. What could be the "trick/problem" here?

[pcristi]

Yes, correct msg24226 is show example of grep output.
No, AFR patch script is not change Advanced settings. AFR patch is only try to switch to 12bit when video is playing.

 "simple" 420 (with no bits) is a typing mistake? 
Word "422 12 bit" are only translation in CFW v.2.1.0[1.4/1.5]  or CFW v2.1.0[v4] assembly for @Rico97 both use mod Settings.apk by @tomeeli.
Please understand 422 8Bit and 422 12Bit is only one option, output on 8Bit or 12Bit is depend if connected display is support or not.
Apparently 422 12Bit is support on FW v2.1.0/v2.1.1 and is maybe not support by HiMedia AFR switch in any version.
I rely don't have idea who user witch complain about HiMedia AFR did checking of 12Bit when they test it.
My UHD NO HDR display is support on 8Bit in all frequency.

If is still not clear for you do testing by itself on your's environment and see if is working or not.

[Mount81]

pcristi:

"simple" 420 (with no bits) is a typing mistake?

Why would be? Isn't there three 420 options in the Advanced menu on 4K / 60Hz?: 1. 420 8bit / 2. 420 10bit and 3. 420 (no bits).

What the user is complained about is that when he sets to 420 / 10bit the GUI first and every time after video playback, when he checks back on the Advanced menu it's somehow switched to 420 (no bit's).  All these without any patches and on OFW 2.1.1.

I've tried to suggest him to do the adb shell info check, but he seems more confy with complaining about, rather than really testing stuff out.

I've tested, but I've only got a FHD TV, so my result are here irrelevant. These "issues" seems to affect mostly the UHD zone.

[ultrasilent]

Can I flash FW in any way in the range of this OFW`s: 2.0.4 and later?
 for example: downgrade from any OFW (later than 2.0.4) to 2.04?

[ultrasilent]

Please understand 422 8Bit and 422 12Bit is only one option, output on 8Bit or 12Bit is depend if connected display is support or not.
Apparently 422 12Bit is support on FW v2.1.0/v2.1.1 and is maybe not support by HiMedia AFR switch in any version.
I rely don't have idea who user witch complain about HiMedia AFR did checking of 12Bit when they test it.
My UHD NO HDR display is support on 8Bit in all frequency.

there is no such option as 422 8 bit in HDMI standart.
himedia output 422 in 12 bit ONLY. This option works well from 2.0.4 for sure. I have Vertex and many times have proven this.
BUT same quality HDR signal you can get outputting in 4K 8 bits.

[pcristi]

@ultrasilent
HiMedia box show like that 4K 422 24
DeepColorMode have to be ignore "current output colorspace YUV422 not support deepcolor set"



Is was better to recheck before to comment about 422 and additionally translation from Settings.apk by @tomeeli.
Every day I have learn something. Sorry guys.

[ultrasilent]

Can I flash FW in any way in the range of this OFW`s: 2.0.4 and later?
 for example: Can I downgrade from any OFW (later than 2.0.4) to 2.04?