There is test firmware in this thread which may help this issue.
Posts by popcornmix
-
-
It is possible the test firmware from this post may help
-
Issue is over voltage
Cannot be set higher then
over_voltage=3I've found an issue with over_voltage=4 (or higher) on Pi2.
Can you test this firmware
Unzip and replace start.elf/fixup.dat on boot partition with start_x.elf/fixup_x.dat from zip file.
Let me know if over_voltage=4 starts to work again. -
Your sample does generate a "hevc @ 0x168ca90] Out of pu + coeff intermediate memory: pus=768" warning which doesn't seem to be handled well.
I've forwarded the report to our hevc codec guy.
The bitrate limits are complicated. Generally higher bitrates means more motion vectors which tends increase cache misses and so increase sdram bandwidth. sdram bandwidth is usually the constraint on playing harder samples.
You can get a slight increase in sdram bandwidth with hdmi_enable4kp60=1 (even if you don't use a 4kp60 mode) as it runs the AXI bus at 550MHz rather than 500MHz.
The GUI overlay takes some bandwidth, so subs, OSD, debug info etc will cost some additional bandwidth.
It may also be worth monitoring the hevc clock (vcgencmd measure_clock hevc) when the video is playing. I believe it will be 500MHz when busy and 250MHz when less busy. If it's dropping to 250MHz when your stream is playing that would limit the streams you can play.
hevc can be overclocked, or you can disable the lower frequency (force_turbo=1 in config.txt) which could help.
-
Can you provide a sample file that freezes the Pi4
While we're unlikely to be able to play very high bitrate clips smoothly, they shouldn't cause a freeze.
-
As it's showing same symptoms with raspbian, then it might be worth creating an issue here:
Issues · raspberrypi/firmware · GitHub
where the right people should see it.
-
OffLoad could you try installing raspbian on an sdcard, and use the display configuration tool to switch to 4kp30.
Does that have the same problem? If so can you also try with hdmi connected to other hdmi port
(this doesn't work with kodi, but should with raspbian).
Does 4kp24 work?
I'm suspecting that the cable is borderline (I know it has worked on another device, but it could be just on the edge of being usable at 4kp30).
But to begin with see if we can rule out a kodi/LE issue.
-
The fix was done long ago, but is stuck in a PR and hasn't made it into an official build:
-
That sounds like 1366x768 doesn't work on raspbian (the scrambled display should be showing a dialog saying "do you want to keep this resolution" which is timing out and putting you back to the old resolution)
Can you confirm that it still fails with latest firmware (using rpi-update on raspbian).
Assuming it does then this is a firmware issue rather than a kodi issue and reporting it here would be best:
-
Can you choose 1366x768 from raspbian? Does it work?
-
state 0xa [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60Hz, progressive
Okay so that is using a more standard resolution so not surprising that worked.
Was that the default resolution when you booted raspbian or did you change it yourself?
-
I've poked the hdmi experts for advice. Can you report output of "tvservice -s" when using raspbian (and display is working)?
-
I wonder how the Pi 4 will behave with enclosures such as these that are basically one large heat sink for all chips.Would make it easy to carry around also. I refuse to rely on active cooling. A Pi has to be completely silent to begin with, and I travel quite a lot so the less parts and wires that can break the better.
I'd expect that to work well assuming it is a large piece of aluminium with good thermal connection to SoC.
Flirc cases have historically worked very well using the same principles.
I'm also expecting the new Pi4 version of Flirc case to work well when I get to try one.
-
Looks like we are sending the same signal in the working and non working case.
You can make absolutely sure of this by booting directly connected to TV (which works),and then uplugging hdmi cable to go through amp (while kodi is running). Do you get a display?
Connect back to TV to confirm signal is still being sent).
If you see picture on TV before and after and no picture when using amp, I'd say you have some faulty
hardware outside of Pi. Check all cables. Try different cables. Try different sockets on amp and TV.
Try a different amp if available to try to narrow it down.
-
Can you ssh into the pi when display is working (direct connection to TV) and when not working (going through amp)
and report output of "tvservice -s"
I wonder if the amp is advertising support for 4kp30 which the TV can't handle.
-
Yes Pi3 builds support 3D
-
If you provide a link to the problematic file I can take a look.
-
3D is not supported yet on the Pi4.
It will come but it's not the highest priority.
