Maybe the AVR adds some sort of an "AVR tag" to the HDMI mode, and then the connection isn't in PC mode anymore.
Posts by Da Flex
-
-
Please test those songs directly from a USB thumb drive. If the issue remains, we can rule out SMB buffer issues.
-
Another issue could be the HDMI cables. If one of them isn't HDMI 2.0 / 2.1, then it might be the bottle neck, and 4K modes aren't offered anymore. So check the HDMI cable standards.
-
Maybe...but when I go to the Whitelist settings, 3480x2160 60hz is no longer available there -- even though the 4k 60hz setting stayed selected in the main display settings menu.
I think the whitelist is loading HDMI modes from the current display, but the older EDID is still in use. Probably your AVR is old, and has a problem with 4K modes.
-
Then, I reconnected the Pi through the receiver, as per normal. The refresh rate stayed at 60hz, even across a boot. It disappeared as an option in the Whitelist settings, but that doesn't seem to have mattered. (Unless Kodi is showing 60hz, but really using 30hz....?)
Theory: Your EDID was updated during your direct RPi - TV connection. Now your current RPi - AVR - TV setup keeps that setting.
-
I wanted to run chrome
Chrome is only available on Generic-legacy, because it needs X11 as display server.
-
Yes, the Intel J4105 HTPC seems to work with LE:
PostRE: GPU recommendations for 4K HDR
From memory LE should run well with a discrete Intel card like Arc A380 if you want to retain your existing hardware. But I suspect a RPi5 would provide a comparable experience for far less power consumption.
I've got a RPi5 as a secondary setup and I can't notice any difference with my J4105 based HTPC in the lounge. I've got the RPi5 booting off a NVMe drive and it's a slick experience.PANiCnzFebruary 10, 2024 at 7:56 PM Read the rest of that thread for pros & cons, as well as other hardware recommendations.
-
@gizmomelb If the user just wants more codecs, and less trouble, then my answer is right. Kodi runs as an app on Nvidia Shield.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
NUC --HDMI--> LG TV --OPTICAL--> LG compact home theater system
The optical TOSLINK and/or the TV is the bottle neck here. TOSLINK is too slow for EAC3, but HDMI can handle it.
-
I have to ask how I can find the log..
We prefer to get a copy on our log server, which saves storage space here. If you have SSH access, you can activate log level 1 by creating an advancedsettings.xml. Then reboot, run pastekodi from SSH, and post the resulting URL.
-
Will I have any chance installing an older version?
Let us see the log from latest LE 12 Generic-legacy first.
-
Is it safe to use built-in kodi commands (Powerdown) to shutdown the device?
Yes. The most important part is unmounting devices, which shutdown / poweroff commands do.
-
This is precisely what I am currently using, RPI 4B, i thought I could take advantage of these boxes which cost half price !
In that case, Nvidia Shield would be the right upgrade, but it's more expansive.
-
-
Pretty new hardware, so try the latest LE 13 nightly build.
-
Just put the release build (img.gz file) into /storage/.update, and reboot.
You can use wget to download the file from SSH.
If you're a nerd, make a backup first.
-
Piracy logic - not our turf.
