I'm now seeing the latest version doesn't even have analogue output as an audio option anymore. So that's a definite deal-breaker for me with my old stereo system. Apparently I'm expected to either replace my hardware/stereo, or buy an additional adapter (micro-HDMI to audio) just because Kodi thinks I should be limited to just HDMI and bluetooth outputs?
Add "dtparam=audio=on" to config.txt.
FWIW, I've not seen any issues with stalls and the iPlayer add-on; using an RPi5 not RPi4 but that shouldn't make any difference.
Have you tried "Watch Live"? Only that has the stall issue.
gpu_mem won't help with hevc playback. Setting it will just leave less memory for the system.
Remove the setting, and then post a debug/crash log.
I booted with no sdcard. The netboot screen came up and said ESC for diagnostics. I hit ESC and the screen went blank.
I said boot with just hdmi and power connected. No keyboard. Otherwise you won't get the diagnostic display.
Can you just connect hdmi and power (no sdcard inserted) and check output on display.
You should see a diagnostic screen. Report the output of the "display:" line.
Does adding "audio_pwm_mode=1" to config.txt help?
Still want to know why OMXPlayer dont support decode to 5.1 PCM 96khz, only MMAL does?
Im talkning about Rpi3
Simple answer is omxplayer is ancient and its replacements have had far more recent work on them including support for new features.
MMAL is still ancient (but a little less so). On Pi4 and Pi5 you can't use HBR audio passthrough (DTS-HD, TrueHD) with MMAL, but you can with the latest interfaces (arm side ALSA, and V4L2/DRM for video).
Is this operating at 60fps?
Yes (assuming you have chosen 60 for framerate above.
"Unlimited/1080 > 30FPS" means no limit resolution when current hdmi mode is 30fps or lower, and limit to 1080p above that.
But really keep it at 1080p - the skin only renders to 1080p, so any higher is usually just slowing it down with no visible change.
Also see info here: https://wiki.libreelec.tv/configuration/4k-hdr
TLDR: set default hdmi mode to 1080p60 and whitelist any 4k modes you want when actually playing videos.
Disabling DRMPRIME in the expert settings solved the problem for me.
I wasn't aware that the hardware decoders can have such an impact on system stability. If the decoder stops playing my (maybe broken/non-standard) ile -> ok. But, freezing the whole RPi4?
Can you be more specific. There are a few combinations of options here that will narrow it down. You have:
1) Allow using DRM PRIME decoder
2) Allow hardware acceleration with DRM PRIME
3) PRIME render method
The default is 1=enabled, 2=enabled and 3=direct which you've reported as hangs
Can you test:
1=enabled, 2=enabled, 3=EGL
1=enabled, 2=disabled, 3=direct
1=enabled, 2=disabled, 3=EGL
1=disabled, 2=N/A, 3=EGL
As chewitt says, provide us with an example file. Ideally cut one down to a couple of minutes, confirm issue still occurs and upload it somewhere (e.g. google drive).
If you believe it occurs with all files, then can you test a publicly available file (e.g. Big Buck Bunny and confirm you still see the issue?
If you disable "Allow using DRM PRIME decoder" in settings/player/video then the orientation flag is supported.
But performance will be lower.
I think on the nightly builds, you can leave that setting enabled but change "PRIME Render method" to EGL,
which will have better performance (but still not as good as using DRM for rendering).
It may be possible to setup dual audio using pulseaudio combine-sink. See here:
3. With old cable and 4KTV, I had flicker problems until resolution dropped all the way down to 720x576!!!! Any guesses as to why the old cable performed so much more poorly (poorly only with RPi4 & 4KTV, fine with RPi4 & 4K Monitor)? The microHDMI connector seems like a weak link, being so tiny. Or maybe 4KTV spews alot more EMI and old cable was poorly shielded?
The usual reason is thin wires, which means high resistance, which means significant voltage drop (and that is more significant with the higher resolution, higher clock frequency hdmi modes).
This video may be illuminating showing just how many random hdmi cables are sub-par.
My guess would be the HDMI cable. 4kp60 requires a very high clock rate and that needs a high quality cable.
Just because it works on another TV doesn't guarantee the cable is perfect (the other TV may just be better and handling a low level noisy signal).
But as chewitt says, follow the recommended instructions and you'll rarely be running at 4kp60 (most video content is 24fps) so are much less likely to hit the issue.
Where did you get this code from?
`transmission`means run transmission as a command and return the output.
I suspect you wanted normal quotes (" or ' would make more sense).
I think I was a bit hasty saying the new RPi4 was faulty. I have configured the mains so I can switch on the TV first and view the full boot sequence. Running 11.0.3 on one TV I am using to test bootup the first display frequency is 1080p 60Hz next 1366x786 62Hz for most of the boot sequence then 720p 50Hz which is the resolution in system settings! On this TV during the 62Hz time the display is torn and unreadable. In normal use with this RPi4 if this TV is not taken out of Standby within 5 seconds the screen locks up! Another TV displays nothing if this RPi4 is connected.
I'm not entirely understand the sequence of events here.
For TV's that don't provide an EDID when powered off (many but not all do),
you should power the TV on and select the correct AV input first.
Assuming you have done this, then I'm not sure how this occurs:
> In normal use with this RPi4 if this TV is not taken out of Standby within 5 seconds the screen locks up!
So, does the TV behave as desired when it is powered on and switched to correct AV input before powering on the Pi?
If yes, then then getedid create will make things much smoother in future (order of powering on won't matter).
If no, then post a debug log.
Looks like carsten888 has found the answer here.
(It's always better to check for the official addon thread on the kodi forum).
But for anyone else, the repo version of YouTube is broken and there is a fixed alpha version which you need to update from zip file.
(which for some reason has been working fine for a couple of months but hasn't been pushed to stable).
Be aware that the Pi0 2 has 512M of ram.
That is too low to be officially supported by LE.
It may be usable in some circumstances, but it's easy to exhaust RAM.
Can you revert to the last nightly that was working as you wanted?
If you can identify the first nightly with the issue we can look through the changes that went into it.
Also do all files play fast? (e.g. does this?)
A debug enabled log file may be useful.
