V2 unofficial patch

[sonicblue]

Here is an unofficial patch I wrote for the V2.

My goal was to resolve as many of the technical issues reported in V2 various issues thread, and add some other minor improvements.

It was developed and tested on firmwares 19.3.20200328 and 19.3.20200901. I would expect compatibility with earlier versions of 19.3 as well, but testing has not been done on those.

Fixes:

• Video enhancements: auto flesh not disabled when set to 0
• Aspect ratio: wrong aspect for non-16:9 content
• Autores/multi: frame rate incorrectly detected as 30fps
• Autores: redundant display mode initialisations
• AV Settings: incorrect colour after playing HDR content
• AV Settings: colour space reverting to RGB after applying 2160p modes
• DVB tuner: persistent frame rate stutter after signal interference on HD channels
• Autores/multi: unhandled progressive/interlaced value of -1
• Autores/multi: falling back to invalid display mode strings
• AV Settings: wrong port/mode/rate shown after disconfirming display mode

Improvements:

• AutoTimer: append event title to custom record path when importing from EPG
• Movie player: remove redundant service restart on exit
• Autores: detect up to 2160p + vertical videos with improved accuracy
• Autores: increase detection of video content change
• Autores: support 1080i and 1080p independently
• Autores: remove redundant modes: 25hz, 30hz
• Autores: add i60/p60 suffix to 60hz modes
• Autores: new mode ordering and defaults
• Autores: remove duplicate delay setting
• Aspect ratio: always show in AV settings, remove redundant setting, new nomenclature
• Colour space: default to YCbCr444, remove redundant settings, new nomenclature
• Video enhancements: remove redundant settings, new nomenclature
• AV Settings: consistently apply video mode and aspect on OK

Unresolved issues:

• 23.976fps content cannot be output at 23.976hz
• System may become unresponsive when video output mode is 60hz
• Incorrect colourimetry when video output mode is 576i
• Sharpness setting becomes nonfunctional after playing HDR content
• Sharpness setting behaves inconsistently if adjusted after reboot (fix: tiny.cc/AutoSharpness)
• Events occasionally missing from EPG cache
• Inconsistent detection of interlace/progressive on certain media files

Installation instructions can be found on my Bitbucket page: tiny.cc/BeyonwizPatch

The installer allows you to uninstall the patch at any time without having to reflash the original firmware or lose any configuration settings or autotimers etc. MD5 hashes are used to verify which files have been patched, and file copy operations are rigorously implemented.

Screenshot:

[sonicblue]

A bug in the patch installer has been corrected where if one of the payload files fails MD5 verification, instead of presenting an error message to the user, the plugin would simply crash.

The cause was a syntax error on line 482 of plugin.py: https://bitbucket.org/CalibrationTools/ ... ec69172102

At time of publication there has only been 1 download of the patch, so currently there is 1 copy in the wild with this bug. If you downloaded it prior to the date of this forum post, then that person is you and you may want to re-download it. However since the bug is harmless in relation to data integrity of the patch, it is not necessary to do so.

[MrQuade]

Have you considered presenting some of the info and your discoveries on the OpenATV forums as well?
They are a bit closer to the bleeding (and I do mean bleeding) edge of development and are running on newer drivers.
I am not sure how much additional access they have to driver code or communication with chip vendors for resolving these sorts of issues at a core level.

I think at the very least that your list of patches would assist in identifying problems and potentially getting them resolved in a more overarching manner. That's not to say that your patch is at all compatible with the OpenATV firmware, just that it presents a nice concise summary of things that need fixing.

If you were to post in the BeyonwizV2 subforum on opena.tv, Captain is usually pretty quick to read and respond. IIRC he has responded to one of your threads here at an early point in your investigations too.

[sonicblue]

Thanks, I'll look into that.