On LE 9.x add hdmi_pixel_encoding=2 to config.txt. On LE 10+, this setting belongs to cmdline.txt (I still have to figure out the syntax for this).
Posts by Da Flex
-
-
Yes, this is a known pheno-menon (censored word
) on all RPi's. There is no brightness setting, but you can increase the color space (mode "RGB full") by changing hdmi_pixel_encoding. This can affect brightness.Not sure which LE version you use, so this setting belongs to config.txt (older versions) or cmdline.txt (newer versions).
-
Part of the picture is cut off at the maximum resolution of my TV. The solution is to switch to a lower resolution.
This could be a TV issue. Many TV's have picture optimization modes, who blow up the picture size beyond the edges. This effect can be more intense, the higher the resolution is. Search for such a mode on your TV's picture settings, and switch it off.
-
Select the "InputStream Helper" add-on (at user add-ons -> program add-ons).
Select "Configure".
Downgrade to the former (working) Widevine version.
-
Finally!
-
svenfoo Read post #5 again. HiFiBerry is offering supported audio HAT's. If you want a more universal hardware, go for an HDMI audio extractor.
-
-
Is MVC no longer supported?
-
You can increase the log level (1 or 2 will be fine) by editing your existing advancedsettings.xml. It's worth to comment out all other tags inside <advancedsettings> for testing.
-
There are so many bug fixes since 8.2.5, which definitely makes it worth to install LE 10 Beta from scratch.
As the release note says: Do NOT upgrade, because it can break some installed software.
-
Please translate into English. We only accept this language.
-
PS: HDMI cables for higher resolutions (like 4K) have better electromagnetic shielding. Your current HDMI cable is pretty flexible, so even if you're not using 4K, the shielding can be an issue. If you get an HDMI 2.0 cable, you can be sure that the shielding is OK.
-
Hmm, I don't see HDMI 2.0 on the Amazon description. Maybe it's worth to try a cable, which guarantees HDMI 2.0 standard.
Please also try the first point of post #20.
-
With a bad cable you can try forever. New cable doesn't mean that it's conform to HDMI 2.0 or 2.1.
Read post #20, and check all points precisely.
-
Welcome to your new life as a non-pirate!
PS: Thread re-opened to allow thread starter to post his solution.
-
OK, I got some feedback from the dev. No obvious errors found at the log, but some hints:
- remove gpu_mem=320 from config.txt
- reduce the resolution to 720p for testing (cmdline.txt video=HDMI-A-1:1280x720@60D)
- if your monitor is using a lower resolution than your TV (or 2. hint is working), then check your HDMI cable (should be conform to HDMI 2.0 /2.1 standard to play higher resolutions)
-
Thanks! I gave a ping to a dev.
-
Kodi.log
You're still at log level 0:
Code2021-05-01 16:43:11.306 T:420 INFO <general>: Disabled debug logging due to GUI setting. Level 0.-> Follow my advice of post #8 to increase the log level.
