We'd need to know the format of the file you are trying to play, to know what the issue is.
1080p24 (and up to 30) with a hw decode supported codec - h264, mpeg4, mpeg2 (with licence), vc-1 (with licence) should be fine.
1080p60 may struggle (overclock can help).
Software decoded formats (including hevc) will struggle.
Post a debug log, or mediainfo of file and we can confirm.
Need to check with HiassofT. Possibly just add a way to get the 0x100 effect (probably with a better named option).
is mediainfo an addon for kodi?
You can install it on windows/linux/mac/etc
I need force_turbo because otherwise overclock is useless, because when i check the clock speed while playing videos it hovers above 900Mhz.
Assuming the videos are hw accelerated (e.g. hevc or h264) then the arm isn't used for video decoding, and there's no reason for the clock to be high. The hevc/h264 clocks will be high in this scenario.
You could always force full arm frequency without force_turbo with:
echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governorBut if the hard disk isn't detected with force_turbo, then I'd say it is power supply related.
Even if drive has an external power supply, that is often just 12V for the motor, and it will still take 5V through USB.
If you have a powered usb hub then try connecting through that.
Does ARD addon use widevine? It may be suffering from [this issue]([Netflix] audio is out of sync even on sd) and need a downgrade of widevine lib.
You could try:
systemctl stop kodi
mv /storage/.kodi /storage/.kodi_back
systemctl start kodiand check if the system with the problem can now play videos (I suspect it will be able to).
If it is that suggests the problem is either settings (config files in .kodi/userdata) or addons (while I suspect you have removed addons from gui, there may be some remnants left - check in .kodi/addons).
If it's not it's something outside. It could be custom stuff you've installed (perhaps in /storage/.config).
You can laboriously go through the file system renaming files or directories to narrow down what is causing the crash, but it may be quicker just to switch to the clean LE install that works, and set that up as you like (check playback works after each addon installed or setting changed just in cases a change breaks it).
One doesn't seem to be getting symbols for functions, so hard to say what's happening.
The other shows openssl is repsonsible. That will be user code (not kernel) so is isn't the issue I was referring to.
Is that the on with the watchdog addon?
In either case I'd be tempted to (temporarily) disable that addon (and potentially others) to try to narrow it down.
Are both SD and HD files interlaced? (or just the SD ones)?
Do they both report hw decode?
Run "perf top" when it's laggy. Leave for a minute to settle.
If you see "vc4_atomic_commit_tail"/"clk_request_start" appearing in list (and increasing in percentage), then you have the same issue.
I don't think LE has updated Pi kernel too recently, so you'll have to wait for that to happen, and then you can test a nightly.
camelreef what you describe sounds like a problem I encountered (not with kodi) where kernel gradually consumes more and more cpu.
This was due to a leak on a linked list (we only added, never removed items), meaning searching the linked list got slower with time.
https://github.com/raspberrypi/linux/pull/4940 fixed it (not directly, but it reverted and replaced the code with the bug).
Can you play the MPEG2-SD file locally (e.g. copy to sdcard or usb stick and play from there?)
We need to determine if it's a network issue, or decode issue.
How is Pi connected to NAS? Fully wired or wireless? SMB/NFS/other?
An iperf test may be useful between Pi3 and NAS.
Are you using built in SMB/NFS/other support or OS support (e.g. mounting network drive outside of kodi then playing from there).
Ok, bug is about 3 year old, so I guess there is not a lot interest in fixing it (too bad, given it is easily reproductible).
On the bug page, someone mentions disabling MMAL acceleration avoids the issue. How do you disable this acceleration (and is it even feasible on RPi 4)?
MMAL has gone. The bug appears to be a buffer overwrite (e.g. buffer allocated is smaller than amount written).
But they tend to have fairly random symptoms - often changing something unrelated (like disabling MMAL) may make the issue appear or disappear.
There are some known issues with seeking with TrueHD.
No solution (but it seems a bit random so some configurations get hit more than others).
Thanks madalone. I don't see any auto turn on in CEC settings.
Disable CEC completely and see if issue still occurs. That will narrow down whether it is CEC related or not.
Post mediainfo of a file with the issue
Are you connecting to the display through hdmi or composite (shared with headphones socket)?
Sorry for the long delay, life got in the way. I'm working on this issue, but the command getedid is not found. I'm using 9.2.8 on a RPI4. I tried adding the lines hdmi_group=1 hdmi_mode=16 to the config.txt but the device is still booting into 4k on the known good TV I'm working with. My plan is to get a good EDID from this TCL TV I have and then set it so it works on the picky Samsung unit, not sure if you think this is a good idea or not. I tried searching the edid commands for LE9 but I haven't found anything useful. Thanks for the help.
LE 9 is no longer updated. I'd suggest trying LE10 and seeing if that has the issue (and it will support getedid).
Would it be possible to add the option within the GUI to adjust this delay?
You said you fixed it with "vc4.inval_delay=0 vc4.cec_debug=0x100".
Have you fixed it with "vc4.inval_delay=<some number> vc4.cec_debug=0"
If not, there's no point adding a gui option to adjust the delay for you.
