I compiled a Kodi 17.1 (final) builds for RPi2/3. Linux kernel 4.8.13, without and with media_build.
LibreELEC-RPi2.arm-8.0.1.kernel.4.8.13.no.mb.tar
LibreELEC-RPi2.arm-8.0.1.kernel.4.8.13.with.mb.tar
Kodi now defaults to Bob deinterlacing on HD channels (when deinterlace method is set to Auto). If you want to use a higher quality Advanced deinterlacing you'll have to manually select "MMAL-Advanced".
Today i tried the 8.0.0 kernel 4.8.13 with mb.. still conituity counter errors. The build without media_build works fine for me.
This is odd. Probably some media_build driver issue, unrelated to the issue I described in my original post.
On my RPi3 + DVBSky s960 I tested the following:
Official build - 8.0.0 with media_build, kernel 4.9.8 - problematic (as described in original post). Advanced deinterlacing causing video corruption.
8.0.0 without media_build, kernel 4.9.8 - problematic (as described in original post). Advanced deinterlacing causing video corruption.
8.0.0 with media_build, kernel 4.8.13 - no issues. Can use Advanced deinterlacing, no video corruption.
8.0.0 without media_build, kernel 4.8.13 - no issues. Can use Advanced deinterlacing, no video corruption.
Tried updates from post #14 and #22 but it doesn't help.
Did you update VDR/VNSI to the latest versions?
Dropbox - Link not found
service.multimedia.vdr-addon-8.1.104.zip?dl=1
Probably there is same problem with kernel on my box.... Any chance you could compile 905x build for me smp?
Amlogic devices have nothing to do with linux kernel 4.x. They provide their own kernel which is currently based on linux 3.14.
Tried to build with 4.9-rc1 but failed.
linux-01-RPi_support.patch from 8.0.0 seem to be incompatible and it does not build so I have no idea how to proceed.
For what it's worth I tried a 4.9.0 build a while ago and the issue is definitely there.
IMO without media_build should be your first choice. If it does not work try the media_build version.
Just to make things clear: media_build has nothing to do with the issue from my original post. I made 2 versions (media_build and non-media_build) because some DVB devices only work with media_build drivers and some devices for whatever reason only work with default kernel drivers.
The issue occur with and without media_build as long as the build is based on 4.9 kernel.
Kernel 4.10 has the same issue as 4.9 - it does not fix anything. Only kernel 4.8 and earlier work as expected.
Would it be possible for you to prepare a media_build build as well?
Dropbox - Link not found - Generic x86_64, ver. 8.0.0, kernel 4.8.13, without media_build
Dropbox - Link not found - Generic x86_64, ver. 8.0.0, kernel 4.8.13, with media_build
I assume you're running oscam on same machine as vdr backend?
Yes.
Can you help me set it up as this what you talking about TVH drives me crazy for a week now ;/
Make sure that the options for DVB-Api are correct (Config-->DVB-Api from Oscam's web interface):
Boxtype=pc
PMT Mode=4
Listen port=2000
Now I can see it is on the edge when wathcing a single HD channel. I assume paralel recording or timeshifting can be completely forgotten.
Not sure about RPi2 but RPi3 is usable as a DVB receiver. However, some tweaking is obviously required to get an acceptable performance. Also, in my experience VDR is far more robust than Tvheadend, so you definitely should give it a try.
RAM/GPU overclocking should help as well. Push it as far as possible.
Can you point sakos at your build to see if it helps his issue too?
Which kernel does your custom build use?
4.8.13
I can't think of a reason why an older kernel would work better, but if it does I'd like to know why.
I'd like to know this myself. I noticed the inferior performance of kernel 4.9 back in December with Milhouse build #1215. The issue is easy to reproduce as long as you have a DVB tuner connected to the Pi and PVR server/client are on the same Pi. The difference in performance is huge, with kernel 4.8 I can run this setup without a single issue (with Advanced deinterlacing enabled). With kernel 4.9 I absolutely have to disable Advanced deinterlacing (even increasing arm_uc doesn't help).
I also tested Milhouse's kernel 4.10-RC builds and they are just as bad as 4.9.x.
- "vcgencmd arbiter set arm_uc 12 0" command improves the behavior but it is still present. Shall I try with other parameters?
No, other parameters will not improve anything.
With the latest LE builds that use Linux kernel 4.9.x - "arm_uc 12 0" will not fix those errors.
Use an older, pre-kernel 4.9 build (or my custom 7.95.2 build) + "arm_uc 12 0" and the errors should be gone.
- "Switch from Advanced deinterlacing to Bob". There are only MMAL BOB and MMAL BOB halved options. By selecting them there is no picture. The configured HW acceleration is OMX and not MMAL. Does it matter?
Always use mmal. Never enable omx except for troubleshooting purposes.
I run VDR on my RPi3 24/7 for months without a reboot. It is rock stable, not a single crash.
Tvh crashes every chance it gets. It would *always* cause Kodi to crash when the signal is poor (e.g. during rain) but sometimes it crash for no apparent reason. I actually thought it was a Kodi issue until I switched to VDR.
The only nice thing about Tvh is it's web interface.
I still see some sporadic artefacts while watching TV but the recorded streams are perfect.
Try to switch from Advanced to Bob deinterlacing. Advanced is using a lot of RAM bandwidth and it may cause issues (especially on HD channels) when both PVR client and server are on the same Pi.
Also, increasing "arm_uc" value should help a lot with sporadic artefacts. The default value is "10 0". To check the current value run "vcgencmd arbiter status".
"arm_uc 12 0" works great for me, anything higher will cause HDMI dropouts.
To change it to "12 0" run "vcgencmd arbiter set arm_uc 12 0", you can add it to autostart.sh to make the setting permanent.
Will you provide one for the final release, too?
Sure.
