With that in the file, and the HDMI plugged in closest to the power cable, it does work, as long as the HDMI is plugged in at boot, and not afterwards.
You should be using:
video=HDMI-A-1:1920x1080M@60D
The D means assume it's connected (otherwise you will need to have a display connected at boot).
You should always use the primary hdmi connector (closest to power connector).
Note: the linked patch is for a 180' rotation.
It's not clear if Soundie wanted a 90'/270' rotation which is far more complicated.
Pi2/Pi3 have no HEVC (H.265) hardware decode support, so are likely to struggle with files encoded this way.
Stick with H.264 encoded files if you want to play them smoothly on this device.
Pi4/Pi5 do have HEVC hardware decode and should play them fine.
I wonder if this patch (done properly) could make it into the official repo? While it is a workaround for an LG TV bug, I am not sure the possibility of engaging PC mode would ever be preferable for a Kodi distro.
Reporting a PC style device as a PC style device sounds like the correct behaviour.
The TV not allowing the user to choose picture enhanced based based on this seems like the bug.
I'd be nervous about changing the reported source type for everyone. I believe using PC mode will often default to a non-overscanned display which is desirable and the change you are suggesting may make things worse for others.
The correct solution is to complain to LG and hopefully a firmware update will allow your use case to work.
The workaround should be that the kernel defaults to PC mode. but allows a runtime override (perhaps through sysfs) to change the SPD_SDI type. A display settings option in kodi could allow setting this. But that is more work, and really needs to be done in the upstream linux and kodi repos, not by LibreELEC.
You can see the infoframe used:
LibreELEC:~ # edid-decode -I /sys/kernel/debug/dri/axi:gpu/HDMI-A-1/infoframes/spd
edid-decode InfoFrame (hex):
83 01 19 93 42 72 6f 61 64 63 6f 6d 56 69 64 65
6f 63 6f 72 65 00 00 00 00 00 00 00 09
----------------
HDMI InfoFrame Checksum: 0x93
Source Product Description InfoFrame
Version: 1
Length: 25
Vendor Name: 'Broadcom'
Product Description: 'Videocore'
Source Information: PC generalI'm guessing it's the "PC general" that causes the bad behaviour in your TV which is set here.
This is generic linux kernel code, so all linux platforms will behave the same (assuming they support the spd infoframe).
I'd say the code is correct. Based on the options available that is the best match for a Pi or PC.
HDMI_SPD_SDI_UNKNOWN,
HDMI_SPD_SDI_DSTB,
HDMI_SPD_SDI_DVDP,
HDMI_SPD_SDI_DVHS,
HDMI_SPD_SDI_HDDVR,
HDMI_SPD_SDI_DVC,
HDMI_SPD_SDI_DSC,
HDMI_SPD_SDI_VCD,
HDMI_SPD_SDI_GAME,
HDMI_SPD_SDI_PC,
HDMI_SPD_SDI_BD,
HDMI_SPD_SDI_SACD,
HDMI_SPD_SDI_HDDVD,
HDMI_SPD_SDI_PMP,Changing from HDMI_SPD_SDI_PC to HDMI_SPD_SDI_UNKNOWN might avoid the issue with your TV, but it's not runtime configurable (you will need to patch that line in kernel and rebuild LibreELEC).
There is (effectively) no AAC passthrough anywhere.
It is mentioned in specs, but n o consumer devices output it and kodi doesn't support it.
Kodi can decode the 6-channel AAC and output 6-channel PCM.
This is lossless and will have perfect quality, but relies on connection to AVR to support multichannel PCM.
It's not clear from your post how the TV and AVR are connected.
Ideally you connect pi-<hdmi>-AVR-<hdmi>-TV but it sounds like you are not (due to AVR not supporting 4K, but TV does).
I assume you care connecting pi-<hdmi>-TV-<something>-AVR?
What is the <something>? Is that ARC or toslink/spdif?
They are limited to two-channel PCM. But two-channel PCM can carry passthrough of AC3 or DTS.
(Note: AAC and AC3 are distinct formats).
The good news is kodi can be configured to decode AAC, encode it to AC3 and output that as passthrough.
That will likely get you multi-channel audio. The operation is lossy, but would be imperceptible to most people.
In system/audio settings set:
Number of channels: 2
Allow passthrough: On
Dolby Digital (AC3) capable receiver: On
- Enable Dolby Digital (AC3) transcoding: On
DTS capable receiver: Off (you could try on, but that is less commonly supported by TVs)
I'd be interested if CoreElec is good forever, or if the buttons will stop working after a while.
I can make my Panasonic work with the magic keys (*Power*-button, keep it pressed, and press *7* *3* *Stop* - which was actually documented in the user manual) but it always stops working after a while.
The problem is at the TV end, not the Pi end. If the TV doesn't send the button presses there's nothing that can be done.
See here for a possible fix - but I found that also tended to be temporary. I've ended up remapping unused buttons that are forwarded (e.g. the coloured ones) for functions I use.
I'm not aware of any regression.
If you could identify the exact nightly build where the performance regression started, then the changes there can be investigated.
Edit: We are suspecting https://github.com/LibreELEC/LibreELEC.tv/pull/10258
In my settings, I've switched Refresh to "Off" - keeping it on with my TV makes the movies look too smooth and unnatural, and not like "movies".
You want that setting on. If what you see is unnaturally smooth ("soap opera effect") then that is a setting on your TV.
See here.
To avoid ambiguity, are you saying a build you make from commit 4e4a6f9 is good and the very next commit (a794735ee) is bad?
Or are you testing official nightly builds (which may jump a few more commits).
Unfortunately, switching from 3D to 2D still doesn't work in LE13. In which file is this controlled? I'm not a programmer, but maybe there's a way to fix it.
StereoscopicsManager.cpp is the main control of what 3d mode is configured.
Some of the gui rendering code is in GraphicContext.cpp and some of the video playback rendering code is in VideoPlayerVideo.cpp
Have fun.
One other note, I've notice a message in the journalctl -a -b -0 section of the log when running pastekodi that had a warning about undervolting. I was originally using a 10W power supply, and I've changed that to a 20W power supply now. Wanted to mention that in case that solves the issue.
Running with an inadequate power supply (that the undervolting lines prove) can certainly cause random crashes.
Terrestrial (via aerial)? What country?
Just run "sudo apt install kodi21" on RPiOS Bookworm. (installing kodi will get the older kodi 20).
If you really need to build your own version, then see here.
Might be worth reading through https://github.com/xbmc/xbmc/pull/25813
It sounds like the default behaviour of some types of subtitle has changed.
It's not clear to me whether this is a regression, or a correction to behaviour.
Might be worth finding a nightly from just before and just after that PR went in, to confirm if that was the cause of the change you see.
I started 3 movies. The first 2 were mpeg-2 and h264 had no problems, the third was h265 and worked until the moment I opened the menu. The picture wasn't affected in any way but the sound suddenly stopped (the AVR's indicators for Dolby-HD/Dolby Atmos went out), that's when I ran "dmesg | pastebinit":
Nothing unusual in there.
No real ideas. After a failure run "dmesg | pastebinit" and post the url just to see if anything complained in the kernel.
If it were me, I might try adding "force_turbo=1" to /flash/config.txt.
If that didn't work, I might try a core_freq overclock (note: too high and this could crash - backup before experimenting).
Start with core_freq=600 (but you could try 700 or 800).
