Hi I didn't enabled this option in config.txt and I was able to play 4k HEVC movie anyway. Is that possible? Now i tried enable this option and only difference is, that I can put Kodi interface to 4k 60fps mode, previously I could use just 4k 30fps.
enable_4k=1 adds support for 4kp60 HDMI output (which requires higher clocks and voltage). 4kp30 (and lower) doesn't require this setting.
You can play 4k HEVC videos with or without this option (most video content is 4kp24).
Quick one, when on the menus moving about, there seems to be alot of screen tearing, is this just down to it being early days? Im displaying on a Samsung NU7020 at 3840 x 2160 and just wondered what it was.
Yes tearing is a known issue. It is significantly reduced with the testing firmware (that fixes the stutter with some video files).
It's a software issue - it will be fixed in a later update.
I had the same issue. For me it helps to use the other HDMI port. I do not know if its a hardware or software related problem.
Yes - use HDMI0 - it is more capable (larger fifos means it can be run with lower clocks).
HDMI1 is largely untested with kodi.
Issues: I can select resolutions of 4096x2160p @ 30, 29.97, 25, 23.98 and 3840x2160p @ 30, 29.97, 25, 23.98 --- but not at 60fps
Also the same content that used to be 4K HDR under the Rock64 build won't activate HDR on the RPI4.
Add hdmi_enable_4k=1 to config.txt and you should see the 4kp60 modes.
(4kp60 requires higher clock frequencies and scrambling so isn't enabled by default).
HDR isn't currently supported but should come soon.
The Kodi Plex Add-On have a setting to allow HEVC, and hardware acceleration of it works in Kodi on my Windows laptop, so I wonder if the RPi4 will be able to do that as well?
Does anyone of you who owns an RPi4 and use the 9.2 Alpha also use Plex
I don't use Plex, but HEVC decode should be fine on a Pi4.
LE for Pi4 is listed as alpha.The device has only been out a week.
Atmos/DTS-HD are supported in hardware but support isn't in kodi yet.
Hi! I've bought a Pi4 2GB to use it in my restaurant to display menus and offers. I'm trying to boot with two LG 4K Tvs connected but I get a rainbow screen. If I boot with only 1 TV connected it works. I'm wondering if it's posible to make Kodi work with more than one display connected and play different videos on each screen. Maybe it would be easier to run two instances of Kodi and sign each one to a screen. I've tried VLC and OMXplayer but I think they don't support HW HEVC decode at this moment.
I don't think kodi supports dual video output on any platform, so no.
HW HEVC support is coming to VLC and that should support running fullscreen on either display so that should be an option.
You could use omxplayer and H.264 videos is you want a solution that works now.
This fixes the issues I have seen with h.264 1080i interlaced content (i.e. Freeview HD stuff) - but my 2160p59.94 Rec 709 SDR HEVC test stuff is still frame dropping like crazy. (Some other 2160p59.94 stuff isn't though)
High bitrate HEVC is next on the list to investigate. Currently it's just been "got working" rather than optimised.
Hi guys i am at the lates aplpha on my Raspberry Pi 4 4GB but i notice some screen Tearing when i am in the settings or so. is a known probleme and maybe a fix for it?
The test firmware mentioned does improve tearing (but there are still occasional glimpses). It is still being investigated.
For the stuttering reports there is a fix. Either wait for the next LE update or grab firmware from here:
rename and replace http://start.elf/fixup.dat on the FAT partition of sdcard.
Anyway - the new Raspi has potential to solve one of my problems. My TV has one 4K HDMI input, but my reciever is 1080P only. Unfortunatly the TV will only send stereo back down the ARC if the source is external. So I need a way of getting passthrough audio to the reciever.
Will it be possible to use the second HDMI to output the audio (with or without 1080P or lower video) while sending the full 4K video to the TV on the other HDMI?
I think this is possible from a hardware perspective.
We'll need a way for kodi to choose a different hdmi port for the audio
(possibly a different Sink, or maybe just a config option).
Don't hold your breath - there are more important things to support first,
but it's something I'll bear in mind.
Okay. You are on a Pi2, right? The commit I reverted should affect Pi3 behaviour rather than Pi2.
But, assuming you are still happy with the last test firmware can you try:
https://drive.google.com/uc?id=1ag88d56gimdzu7sxnc191hirepmgcnf8&export=download
This only partially reverts the commit to try to narrow it down. Let us know if you are happy or not with this version.
vamp. Okay, that's a little surprising. I've built a top of tree firmware with the commit we suspect reverted. Can you test it?
https://drive.google.com/uc?id=1flqknowjd6tpr1yrpc2dh8cghktjbzaq&export=download
Extract start.elf and fixup.dat and replace the ones on the boot partition of your sdcard.
(Using a build that is currently showing the problem). Let us know if the problem still occurs.
vamp could you test the latest Milhouse nightly build?
The firmware you identified had an increase to the i2c clock frequency used for setting chip voltages
which we found caused problems on some boards, and more recent firmware has reverted this change.
Sure, alsamixer does not work. But what about amixer? Shouldnt that work?
amixer: "allows command-line control of the mixer for the ALSA soundcard driver"
It won't affect kodi which doesn't use ALSA for hdmi or analogue audio.
Ignore alsa mixer. Kodi doesn't use alsa for audio (it uses openmax).
Volume on analogue does work, so it's possible you have custom settings that are affecting it. A debug log may be useful.
But to start with I'd suggest using the "reset settings to default" option in the system/audio settings page, and just change the output device to analogue.
If that doesn't work then renaming /storage/.kodi to /storage/.kodi_back and restarting kodi will start from completely clean settings.
You can then set audio output to analogue and see if it's any different. If not you can rename back to .kodi to get back to your original settings.
There is an dtparam that can control led behaviour - see https://github.com/raspberrypi/firmware/blob/master/boot/overlays/readme#l96
It was added March 21, so required a kernel newer than that date.
Yes, as smp says, try removing "arm_freq=1200" and try adding "over_voltage=2"
Is that stable?
