The bitrate doesn't look big. Also CPU doesn't look like to be used at max. HEVC samples from Jellyfish Bitrate Test Files for 10 mbps bitrate can max out RPi CPU to 100% for all cores momentarily and still without drops. So I am wondering where is the actual bottleneck.
Jellyfish samples are 29.97 fps. Your DVB recording is 50 fps. The bottleneck is probably the GPU or RAM speed (or both).
So it is unstable at default 1400? Did you try to add more voltage to see if this fix the crashes? Disabling the clock throttling with force_turbo=1 may be useful too.
Use SMB1 to browse
- HEVC (x265) movie 1920x1072 pixel 10-bit doesn't start (I see the play icon on the right top of the screen but nothing appens: only the system slows down).
You need Kodi 18 / LE 9 to play 10-bit HEVC.
Not sure why VC-1 movie is stuttering. VC-1 should work fine as long as you applied the decoder code.
VDR 2.3.9 for RPi2 (LE9) Seem to be working fine.
Ubuntu Server as a host OS for LE build system, not for DVD playback.
Maybe I wasn't clear in my original post... The resulting RPi2 images don't play any DVDs (including VIDEO_TS folders and ISOs) unless I disable LTO in Kodi's package.mk. I reported about the issue here a while ago but milhouse have no idea what's causing this.
This issue occur even if I don't make any changes (a clean build from current LE master).
Any ideas? I thought that Linux Mint could be the cause of this weird bug, so I installed Ubuntu Server 16.04 (64-bit). Same issue.
Is it compatible with FLIRC and similar cases? It looks to me that the CPU heat spreader could be an issue (CPU height difference compared to pi2/3).
I don't understand why they chose to place the LAN/USB chip differently. This will probably cause an issue with my aluminum case.
What is the default sdram_freq and gpu_freq?
A small sample of the unplayable file would be useful.
I have dvb tevii 650 usb , only with this tar file is scanned correctly 16 east channels.
Kernel 4.8.13 and Kodi 17.3
I restored the file - the dropbox link should work now.
I need this libreelec tar:
LibreELEC-RPi2.arm-8.0.2-k48
I already deleted it. Why do you need it?
is there a way to get the SMB chunk size fixed in the latest stable 8.2.3 LibreELEC
I built a 8.2.3 image with modified SMBFile.h (chunk size set to 64K). I did not test it and have no idea if this change has a positive (or any) effect on Kodi 17.
Try the current Milhouse build. And check out the last few pages of that thread regarding the changes of the SMB chunk size.
But I dont see continuity errors in the tvheadend webinterface.
Then It's an unrelated issue.
I have a PCIe DVBSky T9580 V3
I don't think that PCIe cards are even affected by the kernel softirq problem.
Which would indicate that my system is not overclocked
Your log file suggests otherwise:
arm_freq=1000
sdram_freq=500
core_freq=500Are you using pi2 or pi3?
Default arm_freq for pi2 is 900, core_freq is 250.
For pi3 default value for arm_freq is 1200, core_freq is 400.
Also from your log file:
18:53:01.854 T:1961745360 NOTICE: ARM mem: 864MB GPU mem: 160MB MPG2:0 WVC1:0160 mb for GPU mem is too low. This will cause issues with HEVC decoding. You definitely need to add or edit the gpu_mem_1024 value in config.txt.
Update: I just tested with gpu_mem_1024=160 on my pi3. With that setting Kodi crashes immediately after I start the playback of a HEVC file.
Sadly nothing has changed in regard to my problem with playback. Some files still crash the system
Try to temporarily remove all overclocking.
Also, set the the gpu_mem_1024 value in config.txt to 256.
What could I have overlooked?
added screenshot showing update file in folder
I'm not really sure, It looks fine to me. Maybe berryboot has something to do with this.