Are you saying you get video out of both hdmi ports?
Or are you saying you can get video from one port and audio from the second hdmi port?
The original post read to me like they wanted video from both ports, which I don't believe can be done.
Video from one, and audio from the other can be done.
Never cut down a log. The most useful information in the log is at the start.
Sorry, that's not supported by kodi. You may be able to use a hdmi splitter to get the same result.
config.txt:
gpu_mem=384M
framebuffer_depth=32
otg_mode=1
hdmi_enable_4kp60
dtoverlay=hifiberry-amp100
MALLOC_ARENA_MAX=2
initramfs edid.cpiogpu_mem=384M - Remove it. That memory is likely just being wasted.
framebuffer_depth=32 - Remove it - will have no effect when kodi is running
hdmi_enable_4kp60 - you need an =1 on end to do anything
MALLOC_ARENA_MAX=2 - Remove it. This will have no effect in config.txt
Have you added hdmi_enable_4kp60=1 to config.txt?
"dtparam=audio=on" added to config.txt will enable the headphone socket in audio settings.
Almost certainly the hard drive doesn't get enough power.
Externally powering the drive, or using a powered USB hub may fix this
If cpu usage is unexpectedly high, you can run "perf top", leave it to settle for a few seconds,
and the functions it identifies may give a clue to what it taking the cpu.
If you disable cec does the issue stop? (just to confirm it is cec related)
If you want cec enabled then you could try just disabling "switch source to this device on startup",
and make sure "devices to power on during startup" is set to none.
For 4kp50/60 yes, but 4kp30 and below will use 12bit RGB 4:4:4 if supported by the TV.
So lots of 10-bit videos (eg 4kp24 or 1080p) now can have 50% higher clocks than before.
True
Keep in mind that LE 10.0.2 will now output 10bit video files as 10 or 12 bit instead of only 8bit before - which obviously requires higher HDMI output clocks.
The hdmi pixel clock is actually the same.
12-bit YCC422 is 24-bits per pixel. Which is the same as 8-bit RGB444.
But the core clock does drive many parts of the SoC.
And it may be that a part of the chip that was dormant when we were outputting 8-bit RGB444 is now required with 12-bit YCC422 and has an overclock limit below 700MHz.
Can i simply copy over the firmware files from 10.0.1 to 10.0.2, or is the newer firmware requered by Kodi on 10.0.2?
In general yes. Obviously if the firmware goes back before a feature was introduced that feature won't work.
So give it a try. (Back up first if you are not sure you can undo any changes made).
Not much info in backtrace:
Thread 1 (Thread 0xe8f63280 (LWP 1115)):
#0 0x005f1c20 in ?? ()
#1 0x005f8570 in CGUIListItem::GetProperty(std::string const&) const ()
#2 0xf2c01e60 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)other than it's gui related rather than video playback related.
You mention using kore controller - can you confirm the issue still occurs when playing video through other means (e.g. from keyboard control)
Can you rename /storage/.kodi and check if you can play 4K hevc files? Something like:
systemctl stop kodi
mv /storage/.kodi /storage/.kodi_back
systemctl start kodiThat may indicate if the crash is from some local settings or installed addons.
Debug log may help.
But make sure desktop resolution is set to 1080p. Enable "adjust display refresh rate".
If you care about 4k, add hdmi_enable_4kp60=1 in config.txt and add modes you care about to display whitelist.
The fact work was done on this, and a test build was provided and no one commented for over a month makes us believe this isn't a high priority issue. Effort can be better spent on issues where we get some response.
Also check output of dmesg for any kernel errors (e.g. allocation failed).
The strange thing here is that using the exact same hw configuration with le 9.2.8, plays flawlessly.
What have changed in le 10 that makes impossible to use tv server + client in the same machine ?
I suspect the issue is at the tvheadend end, rather than the decoder end.
I don't know if you've tried using LE 10 on the Pi4 as the client, with the tvheadend server on a different device (either another Pi, or a different device).
If LE10 works when used as both client and server on separate Pi's, that would suggest there is a problem with the load when used on a single Pi, causing lost data.
If it still fails, then it would suggest something is worse on the server end - either tvheadend or the kernel driver for the tv device.
