I'm not aware of any add-ons that source media content from the Internet Archive (Games, but not media).
There's the Internet Archive video addon.
I'm not aware of any add-ons that source media content from the Internet Archive (Games, but not media).
There's the Internet Archive video addon.
Post mediainfo of your recoded file.
Cutting a 1 minute sample that exhibits the problem, and uploading somewhere (e.g. google drive) is another option to identify what options are problematic.
Copy a test file to the Pi and see if it plays okay locally (e.g. from sdram or attached usb stick).
That will rule out if the network is a factor.
The working edid is the typical two 128-byte blocks.
The not-working edid is four 128-byte blocks which is unusual.
Not sure if something changed in the 6.6 to 6.12 kernel bump that means the extra edid blocks are reported, and whether their presence causes any issue for display-info library.
Looks like the first two blocks are the same. The additional blocks decode to:
```
Block 2, CTA-861 Extension Block:
Revision: 3
Underscans IT Video Formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
Native detailed modes: 0
Vendor-Specific Data Block (AMD), OUI 00-00-1A:
Version: 3.3
Minimum Refresh Rate: 48 Hz
Maximum Refresh Rate: 240 Hz
Flags 1.x: 0x00
Flags 2.x: 0x20
Maximum luminance: 129 (817.518 cd/m^2)
Minimum luminance: 11 (0.015 cd/m^2)
Unknown: 0x5f 0x10
Checksum: 0x0c
----------------
Block 3, CTA-861 Extension Block:
Revision: 3
Underscans IT Video Formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
Native detailed modes: 0
Checksum: 0x07
Display More
Not sure if this is related, but this is surprising:
Connector 0 (33) HDMI-A-1 (connected)
Encoder 0 (32) TMDS
Crtc 3 (100) [email protected] 594.000 3840/176/88/296/+ 2160/8/10/72/+ 60 (60.00) P|D
Plane 6 (125) fb-id: 726 (crtcs: 1 2 3 4 5) 0,0 1920x1080 -> 0,0 3840x2160 (XR24 AR24 AB24 XB24 RG16 BG16 AR15 XR15 RG24 BG24 YU16 YV16 YU24 YV24 YU12 YV12 NV12 NV21 NV16 NV61 P030 XR30 AR30 AB30 XB30 RGB8 BGR8 XR12 AR12 XB12 AB12 BX12 BA12 RX12 RA12)
FB 726 1920x1080 XR24
Connector 1 (42) HDMI-A-2 (connected)
Encoder 1 (41) TMDS
Crtc 4 (112) [email protected] 297.000 4096/1020/88/296/+ 2160/8/10/72/+ 24 (24.00) D 256:135
Do you have a second hdmi display connected?
If it fails with LE13 nightly, and you can reproduce with a sample file (e.g. create a one minute file around the part which crashes), then we can take a look at the file (e.g. upload the sample to google drive).
The GBM backend of kodi does not support screenshots.
There was an attempt to add support, but it didn't get completed.
The resolution list from kodi tends to be the list extracted from the edid, plus the mode kodi was launched in (internally denoted RES_DESKTOP). The latter of these shows as a duplicate.
In some places (like setting the default resolution for the GUI) they behave differently. Consider choosing 1920x1080@60 vs RES_DESKTOP (which we'll assume was 1920x1080@60).
e.g. if you connected to a different display that reported 1280x720@50 as it's preferred mode (but still supported 1920x1080@60) then choosing the former option would result in a 1920x1080@60 GUI resolution, whereas choosing the latter would result in 1280x720@50 GUI (this monitor's RES_DESKTOP).
As kodi doesn't make it clear which is which in the GUI, this distinction is less useful.
It would be better if in settings, RES_DESKTOP showed with a unique name (e.g. "DEFAULT").
And it should probably be filtered out from whitelist.
Your second duplicate resolution is probably the edid reporting two different modes with same refresh/timing, but some other differences (e.g. blanking period or aspect ratio).
may provide some clue.
In settings/player/videos, if you set "adjust display refresh rate"/"adjust display HDR mode" to "off", does the video play?
There doesn't seem to be much in the way of instructions at that GitHub page on what to do and what to expect... Is this the expected result? Do I simply power down, replace it with my (previously functional) libreELEC SD and reboot?
Yes - green screen means eeprom programmed correctly. Red screen means it failed.
Docs are here.
QuoteWhen the green activity LED blinks with a steady pattern and the HDMI display shows a green screen, you have successfully written the bootloader
Quote
- This suggests Kodi is dying when trying to render some text from an addon (or skin element) while Python is executing.
I don't see evidence for that from a single crash log. The font rendering thread is just what kodi was doing when other thread crashed with a SEGV. The crashed thread was python related. It's most likely just luck what other threads happen to be doing when the python thread crashes.
As chewitt says:
find the date of first nightly with the issue.
find if you can provoke the issue with a clean .kodi
To sum up; Popcornmix' solution with running kodi from rotated RPiOS (without LE then) is a verified working solution for this problem.
Glad that worked for you.
You might want to try installing kodi21 from RPiOS which supports wayland, and much like Xorg on the PC, allows the compositor (outside of Kodi's knowledge) to rotate the screen.
Note that this will use EGL for composition, rather than DRM which is a less efficient path. It should be fine for 1080p60, but will struggle with 4K video.
But you can give it a try quite easily, to see if it meets your requirements. Use the preferenced/screen configuration tool (from the desktop) to set the display rotation, then launch kodi (the desktop version, not the fullscreen version). You can switch the desktop kodi to use fullscreen when running.
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.