You likely don't want anything larger than 3840x2160
Posts by lrusak
-
-
Are you just looking for older versions to install?
-
It would be easier to port current LibreELEC to i386 than to try and revive openelec.
-
I disagree.
In contrast, I defrag my drives regularly.ref, An introduction to Linux's EXT4 filesystem | Opensource.com
How can I do it in LibreELEC?
You need to setup the LibreELEC build system then add the packages needed to compile the tools. You can try copying binaries from a similar system but YMMV.
-
You typically don't need to defrag ext4 filesystems (I've never done it in my 10ish years of usage).
If you absolutely need the tools you can compile them yourself and copy them to your system.
-
RPi4 doesn't support vp9 decoding IIRC. You will need to use HEVC files to be able to do 4k HDR
Code2021-07-22 14:37:51.996 T:2515526512 INFO: ffmpeg[95EFE370]: Input #0, matroska,webm, from '/storage/videos/BEST HDR DEMO FOR TVs _ 4KHDR TEST.webm': 2021-07-22 14:37:51.996 T:2515526512 INFO: ffmpeg[95EFE370]: Metadata: 2021-07-22 14:37:51.996 T:2515526512 INFO: ffmpeg[95EFE370]: ENCODER : Lavf58.20.100 2021-07-22 14:37:51.997 T:2515526512 INFO: ffmpeg[95EFE370]: Duration: 00:03:58.42, start: -0.007000, bitrate: 7010 kb/s 2021-07-22 14:37:51.997 T:2515526512 INFO: ffmpeg[95EFE370]: Stream #0:0(eng): Video: vp9 (Profile 0), yuv420p(tv, bt709), 3840x2160, SAR 1:1 DAR 16:9, 23.98 fps, 23.98 tbr, 1k tbn, 1k tbc (default) -
Please enable debug logging. Then try to play the file that doesn't play properly, then post the log.
-
I would recommend moving to the new youtube addon called "tubed". It's being actively developed by a team kodi member.
-
99% of all official add-ons will work with Kodi v19. If you are using unofficial add-ons or other add-ons not from the official repositories it is your job to check if they are compatible.
-
There have been no new builds sice June 4th (last nightly in test.libreelec.tv is 20210604-f6b7711), although the github page has 15-20 newer comments since then. Did something happen in the build system?
---edit
That build is actually from June 2nd, because this is when commit f6b7711 was made.
The releases.json isn't automatic, so it's whenever I decide to run it right now.
-
Bluetooth is broken on LE, so it maybe affects audio rooting in a bad way. Just deactivate it.
This isn't the problem. We just use pulseaudio for bluetooth audio. Alsa should be enumerated first however there is possibly a chance that the alsa device isn't ready and the fallback is the pulseaudio device (which is just a null sink when not using bluetooth).
-
turn on sync playback to display
-
OK, but I also have to delete the old version in the order
/usr/lib/kernel-overlays/base/lib/firmware/
How can I do that?
you can't
IIRC the firmware in /storage/.config/firmware will be preferred.
-
use /storage/.config/firmware/
You may have to create the folder if it doesn't exist
-
-
oops sorry i missed that. no radeon yet.
I'll go try another nuc with intel integrated graphics.
Thanks
HDR on AMD does work, I just don't think smp builds with amd graphics enabled.
-
perhaps the sdcard just isn't compatible with that device.
-
use the "blkid" command to check the disk label. You can do this with LibreELEC but because you don't have a booting system you may have to put the sdcard in another PC (linux). Or boot your RPi with a working sdcard and use a usb to sd converter to plug the faulty sdcard at the same time. You should see something like this.
Code# blkid /dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="SYSTEM" LABEL="SYSTEM" UUID="2303-0357" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="4cb80fca-01" /dev/mmcblk0p2: LABEL="STORAGE" UUID="66f7dd29-b2bc-41b1-aee4-74fd08640153" BLOCK_SIZE="1024" TYPE="ext4" PARTUUID="4cb80fca-02"The other thing to check is what your cmdline.txt file says in in the root of your sdcard. it should look similar to this.
Codeboot=UUID=2303-0357 disk=UUID=66f7dd29-b2bc-41b1-aee4-74fd08640153 ssh debuggingAs you can see I'm using UUID's (which is the default). So you have a mismatch somewhere.
