deinterlace support was merged into LE11 nightlies a week or so ago, it is not in the LE10 codebase at this time.
I've compiled one of the nightlies but did not found any usable change at deinterlace level with RPI4.
Is there any additional compliation option I should have used ?
For LE9 i use the "Raspberry Pi VNC" addon ( which uses dispmanx)
But as referred by CvH, VNC stopped working in LE10.
A side note: In Raspberry Official OS, Real VNC works fine, don't know if it is possible to port it to LE10 ....
well ... I don't know in fact what to say...
I understand the difficulties and the need to wait.
I will probably continue with 9.2.8 in my main RPI4 andm and keep LE10 in the RPI4 testing.
For movie watching, netflix, tv series, LE10 is just great.
But for live TV, I've tried to disable DRM PRIME and force (software) deinterlacing, but
but unless I'm doing something wrong, it is not watcheable
there's an obvious lag, and probably the RPI4 is not able do do software deinterlacing with 1080i @ 50hz live tv.
Any sugestions / tweaks ?
yes. changes now go into linux-aarch64.conf.
I'veupdated the compiled drivers and upload them.
Available here:
I've been using this pack for a while. small, simple, without external dependencies or versions.
It does the job.
A great compliment for tvheadend on-the-fly transcoding.
With a transcoding web interface.
ffmpeg and nginx compiled with the more recent official sources.
Though it was a good idea to share it with the community.
You are free to use (or not).
Thanks
yes. but this addon was made to work also on LE10 - the compiled ffmpeg version has all the libs included for using omx and mmal for hw encoding acceleration, giving the on-fly transcoding for the proposed server 
This addon is more than ffmpeg:
It is a full transcode server with a ready to use configuration and user interface to help you serve your local content to an external device (example: stream from your pi --> ipad on the run).
It includes ffmpeg and nginx in order to have everything together in just one add-on without external dependencies.
isn't the included ffmpegx (ffpge-tools) already compiled with everything that it works with rpi transcode ?
For what I've seen in the past, omx and mmal weren't included.
Pi Foundation folks are currently focussed on finishing the 10/12-bit video and 4K60 work. This will firm up the kernel/DRM side of the puzzle and allow some ffmpeg cleanup, which needs to happen before more complication (with deinterlace) is added. It's vacation season so all of the above is running about 3/4 speed right now. IMHO the current software deinterlace capability is quite usable (not perfect, but usable).
Yes. it is of course acceptable to wait for deinterlacing,
But in my opinion and taste, the software deinterlace with RPi4 is not a good viewing experience.
At least for TV Reception of full-hd 1080i@50 fps soccer games - there's a movement lag that feels somehow "unnatural". And gives an uncomfortable viewing sensation (probably the RPi4 is not powerful enough to do software deinterlace).
But that's only my opinion, of course.
when deinterlace is not needed LE10 is great
Hi,
INTRO
I've mounted a transcoding server with a simple web control interface to help viewing your videos in a compatible web browser.
It includes ffmpeg own compilation ready to do real time transcode in rpi 3 and rpi 4 using omx and mmal.
It also works great spawned by tvheadend
Also includes nginx specific compile to help the transcoding process.
You can even add nginx additional configurations.
add-on will be identified as service.ffmpeg in kodi.
Download here:
https://mega.nz/file/YfZX0QCa#…_rFJARjn23rKJNsOLoWQMI_Hw
DETAILS
FFmpeg TRANSCODING Server for Raspberry Pi
This add-on includes:
1 ffmpeg with omx and mmal support for Pi, and also libx264 with presets (for fast transcoding).
can be used in a tvheadend profile (see bellow).
2 nginx with rtmp and hls for transcoding services.
nginx can also publish your custom sites.
3 A small transcoding web based service - you can transcode your local stored movies across the network.
even when on low bandwidth.
Compatible with vlc player and chrome (must install a m3u8 extension for playing streams).
= QUICK SETUP
After install go to add-on settings in kodi:
- Change user and pass (defaults to user / pass)
Access to the User interface with a web-browser:
http://ip:port/cgi-bin/movies.cgi?path_to_transcode
in which path_to_transcode is the directory path that contains video contents to be browsed and transcoded.
use linux format (example: /media/hdd/movies)
= TECH STUFF
1 FFmpeg
ffmpeg is used as the encoding for the server,
but it is also usable trought command-line.
just call as:
ffmpeg
TVHEADEND
If you use tvheadend, you may define a profile that pipes video streams trough ffmpeg before delivering.
The following example uses x264 to live transocde with a Rapsberry Pi4.
Assuming ffmpeg server kodi add-on installed in LibreELEC:
- tvheadend / configuration / stream / stream profiles / add
- create and enable new stream profiles with the followig:
. enabled = true
. Data timeout = 0
. Restart on error = true
. Continue if descrambling fails = true
. Descrambling timeout = 10000
. Command Line
/storage/.kodi/addons/service.ffmpeg/bin/ffmpeg -loglevel quiet -i pipe:0 -vcodec libx264 -preset faster -s 640x480 -vb 512k -bufsize 1024k -g 100 -af "aresample=async=1:first_pts=0" -acodec aac -ab 128k -f mpegts pipe:1
. Kill signal = SIGTERM
. Kill timeout = 15
- The ffmpeg provided command will do live transcode with the major setup:
. video codec : libx264
. preset : faster
. frame size : 640x480
. video bitrate : 512k
. audio codec : aac
. audio bitrate : 128k
. audio sync with video (to handle received lost frames)
2 NGINX - ADDITIONAL SITES:
As nginx is being used, you can define additional servers in:
/storage/.kodi/userdata/addon_data/service.ffmpeg/sites-custom
Or by samba as:
\\Userdata\addon_data\service.ffmpeg\sites-custom
3 TRANSCODING SERVER
- TRANSCODING CONTROL PORT : Defaults to 9996.
Simple CTRL GUI : http://ip:port/cgi-bin/movies.cgi
Start Transcode : http://ip:port/cgi-bin/transcode.cgi
Stop Transcode : http://ip:port/cgi-bin/stop-transcode.cgi
Play stream : http://ip:port/hls/movie.m3u8
Movies will default transcode to 640x480 @ 512kbps.
Publishing is made to rtmp://localhost/hls/movie (internal port 1935)
- USER AND PASSWORD:
User and password defaults to "user" and "pass".
Should be changed in kodi's add-on configuration screen.
- KODI ADD-ON CONFIGURATION:
In the add-on configuration screen, you can define:
- Server port (defaults to 9996);
- Transcoded streaming video frame size (defaults to 640 x 480);
- Transcoded streaming video bitrate (defaults to 512 Kbps);
- User and password to access the control site;
- Control GUI:
Should be called with the local server directory with movies to transcode.
Example:
http://ip:port/cgi-bin/movies.cgi?/media/hdd/recordings
This interface allows choosing the movie, start transcoding, start playback and stop transcoding.
m3u8 can be watched in chrome by installing an extension. VLC Plays them directly.
- TRANSCODE:
transcode.cgi can be called directly by giving the movie FULL PATH NAME WITHIN THE SERVER,
and several optional arguments.
The example bellow uses the default options:
http://ip:port/cgi-bin/transcode.cgi?input=/dev/stdin&frame=640x480&bitrate=512k&offset=00:00:00&caller=movies.cgi
All arguments are self explanatory, except "caller",
which is an optional address to transfer execution after the transcoding is started.
If "caller" is not passed as argument,
transcode.cgi will stay in browser with a small simple interface to playback and stop the stream.
- COMPILATION DETAILS:
ffmpeg and nginx were compiled using the following flags:
ffmpeg version N-103035 Copyright (c) 2000-2021 the FFmpeg developers
built with gcc 6.3.0 (Raspbian 6.3.0-18+rpi1+deb9u1) 20170516
configuration:
--prefix=/usr --enable-gpl --enable-libx264
--enable-omx --enable-omx-rpi --enable-mmal --disable-ffplay
--disable-ffprobe --disable-doc --disable-libxcb --disable-libxcb-shm
--disable-libxcb-xfixes --disable-libxcb-shape
--enable-libx265 --enable-openssl --enable-nonfree
nginx version: nginx/1.21.1
built by gcc 6.3.0 20170516 (Raspbian 6.3.0-18+rpi1+deb9u1)
built with OpenSSL 1.1.0l 10 Sep 2019
TLS SNI support enabled
configure arguments:
--add-module=../nginx-rtmp-module --with-http_ssl_module
--with-http_dav_module --with-http_flv_module --with-http_mp4_module
--with-http_gunzip_module --with-http_gzip_static_module
--with-http_auth_request_module
Did you by chance change gpu_mem in config.txt? If yes: don't do that, keep it at the default of 76 or you will experience crashes - LE10 needs lots of CMA memory, not GPU memory.
so long,
Hias
yes !
That was the issue.
Thank you very much.
Solved
I'm not using it either!
It simply comes with every release from the past weeks,, but my rpi4 simply crashes at boot if I have it selected.
I have to manualy disable it, placing the sc-card in my pc and manually editing distroconfig.txt.
Is cma-512 needed ?
could it be possible to NOT being enabled by default ?
thanks
I've lost some hours to understand why my RPi4 started to crash at boot after installing newer le10 nightly builds.
After some tests I've noticed that the line in distroconfig.txt:
dtoverlay=vc4-kms-v3d,cma-512
Is the one to blame.
If I remove cma-512 from distroconfig.txt, Le10 works just fine.
I have a RPi4 with 4 GB RAM.
What could be happening ? (the previous le10 builds did not had cma-512 and also worked ok).
No one else had the same problem ?
Thanks
SNR 28 db
strenght -78 dBm
Well ... assuming those are DVB-C signals, I will suggest you to try a different connection.
do you have a way to connect to 1 of the first cable wall plugs ?
Or even directly in the cable that enters your home ?
(just to make sure you are not getting a big signal drop in your home cabling, and assure that that is not the reason for your breaks)
Further testing and it looks like issue is with my streams and even recordings...ffmpeg is showing many errors while transcoding both live tv and recordings..strange thing is these corrupt segments are not teally visible when watching live tv and not even on recordings...my reception is a bit on the low side tough..about 43%..
Have you've been successful meanwhile ?
When you say 43%, can you report the SNR ? (in tvheadend's interface, status/stream).
For your reference, in average I have:
cable - SNR 36.3 dBm ; Signal strength 51.0 dBm.
sat - SNR 15. dBm ; -30.5 dBm.
Using a TBS 5520 SE combo receiver.
In my tests with le10, I’ve noticed I have always to disable and enable an addon after installing.
This was valid for tvheadend.
Sorry man ... my bad , forgot to include that lib in the zip file. 
this link is updated. Just tested in a fresh LibreELEC 9.26 running in RPi3:
About your error:
is strange, I use libreelec 9.2.6 and my ffmpeg works ok.
libdrm.so.2 is in /usr/lib/libdrm.so.2
Have you tried executing ffmpeg from a ssh shell ?
About clients:
I do my tests with vlc in PC to connect to tvheadend in my Rpi trough a m3u list got from http://tvheadend_ip_address:9981/playlist/channels
This transcoding, takes some seconds to start, after starting 5 to 10s after it stops for 2 seconds (buffering), but then it plays all the time without issues, providing I have a good network connection. of course.
There is also a nice free tvheadend client for iOS devices that works great, and it is easy to select a codec profile from it.
This is very strange.
I use the exact same approach with a RPi3 and a RPi4, but I have none of those issues.
As I've posted in another thread, this is my ffmpeg command line,
/storage/.kodi/addons/service.ffmpeg/bin/ffmpeg -loglevel quiet -i pipe:0 -vf scale=640:360 -vcodec h264_omx -vb 512k -bufsize 2048k -g 100 -af "aresample=async=1:first_pts=0" -acodec aac -ab 128k -f mpegts pipe:1The major diferences are that I'm not forcing the frame rate nor the pixel format and I use a different ffmpeg version.
I use a ffmpeg version compiled directly in my RPi3 from the official ffmpeg sources.
If you want to test with it, just download from this link:
https://mega.nz/file/NGIxxSIa#…IAtSfNVEoInPmL8
Install the add-on directly from libreelec's kodi interface.
ffmpeg path is:
/storage/.kodi/addons/service.ffmpeg/bin/ffmpegNote: Also take a look into gpu_mem in /flash/config.txt (i'm using 256 in my RPi3, and 512 imnRPi4)
Note: It is a personal add-on that I've not yet released, which includes ffmpeg to help nginx to serve as a transcode server
(if you are interested in knowing more, just read the txt file inside the add-on, or take a look at http://RPi_ip_address:9996/cgi-bin/movies.cgi?/storage after install - user/pass)
Another thing: What client are you using to test the stream ?