Thank you fegol for yours great work.
Can you add this file frontend.h frontend.zip to tvheadend for supporting dvb s2x ?
This need to be replaces in all locations in /vednor/dvb-api/ ?
Why not PR in official repo?
Thank you fegol for yours great work.
Can you add this file frontend.h frontend.zip to tvheadend for supporting dvb s2x ?
This need to be replaces in all locations in /vednor/dvb-api/ ?
Why not PR in official repo?
Just a simple question for those with are familiar with libdvbcsa code patching.
Is it possible this patch to be applied over TVHCSA?
https://github.com/tvheadend/t…ee/master/src/descrambler
this will make more easy to be added as commit to main branch I guess.
You need to GIT PULL/CLONE and then GIT REVERT
Hey
can anybody help i get this message wenn i build the docker image with patched files =/
I used chris guide in this post Guide
CodeDisplay MoreCC src/htsmsg_binary.o src/htsmsg_binary.c: In function 'htsmsg_binary_des0': src/htsmsg_binary.c:80:39: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=] 80 | ((char *)f->_hmf_name)[namelen] = 0; | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~ In file included from src/htsmsg_binary.h:22, from src/htsmsg_binary.c:26: src/htsmsg.h:84:14: note: at offset 0 to object '_hmf_name' with size 0 declared here 84 | const char _hmf_name[0]; | ^~~~~~~~~ src/htsmsg_binary.c:98:7: error: writing 16 bytes into a region of size 0 [-Werror=stringop-overflow=] 98 | memcpy((char *)f->hmf_uuid, buf, UUID_BIN_SIZE); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from src/htsmsg_binary.h:22, from src/htsmsg_binary.c:26: src/htsmsg.h:84:14: note: at offset 0 to object '_hmf_name' with size 0 declared here 84 | const char _hmf_name[0]; | ^~~~~~~~~ cc1: all warnings being treated as errors make: *** [Makefile:715: /tmp/tvheadend/build.linux/src/htsmsg_binary.o] Error 1 make: *** Waiting for unfinished jobs.... The command '/bin/sh -c echo "**** build tvheadend ****" && if [ -z ${TVHEADEND_COMMIT+x} ]; then TVHEADEND_COMMIT=$(curl -sX GET https://api.github.com/repos/tvheadend/tvheadend/commits/master | jq -r '. | .sha'); fi && mkdir -p /tmp/tvheadend && git clone https://github.com/tvheadend/tvheadend.git /tmp/tvheadend && cd /tmp/tvheadend && git checkout ${TVHEADEND_COMMIT} && echo "**** patch tvheadend ****" && git apply /tmp/patches/tvheadend/tvheadend43.patch && echo "**** configure tvheadend ****" && ./configure `#Encoding` --disable-ffmpeg_static --disable-libfdkaac_static --disable-libtheora_static --disable-libopus_static --disable-libvorbis_static --disable-libvpx_static --disable-libx264_static --disable-libx265_static --disable-libfdkaac --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 `#Options` --disable-avahi --disable-dbus_1 --disable-bintray_cache --disable-execinfo --disable-hdhomerun_static --enable-hdhomerun_client --enable-libav --enable-pngquant --enable-trace --enable-vaapi --infodir=/usr/share/info --localstatedir=/var --mandir=/usr/share/man --prefix=/usr --python=python3 --sysconfdir=/config && echo "**** compile tvheadend ****" && make -j 2 && make DESTDIR=/tmp/tvheadend-build install' returned a non-zero code: 2
Remove this commit
Some one posted this
https://tvheadend.org/issues/6227
And the fun start ;)
Display MoreHello:
I'm using fegol (thanks again) tvheadend modified for CoreELEC ( https://www.linuxsat-support.c…tachment/208297-19-5-zip/ ) + normal "oscam" (entware, CoreELEC).
In my experience with 098D:
a) When ECM times are in the range of ~ 500 ms, the video is perfectly stable
b) When ECM times are more or less from 1000 to 2000 ms, the video has small image cuts
c) When ECM times are > 2000 ms, the video has considerable image problems (image stops, restarts, etc.)
Is there any configuration for modified tvheadend or for oscam (any other oscam version?) to obtain more "stable" video with ECMs "not so fast"?
Thanks in advance and kind regards
This is a normal for not only this CAID
Will this patch ever make it into the official tvheadend?
If is send as PR to Github repo of TVHeadend
there is no reason not to be applied.
The reason I mention it is because I think its fair to assume people will be building on the same machine they intend to run it on.
If this is the case then its also fair to assume it could be more than just a TVH server... It could be file sharing, Plex, router/DNS, surveillance, downloads, etc.
Didn't want people upset when there servers lock up/crash
Let's imagine that they have dual core cpu without hyper-treading
what is difference?
Using all cores might not be such a good idea?
2 is low but then it doesn't take a long time anyways.
If have more treads doesn't matter, load on all tread is less concentrated.
Peak load is shorter and cannot interrupt near anything, even Turbo-boost is not activated (depend on system)
so to be safer let's make compromise
the following error occurs
CodeCT101:/tmp/tvheadend# make -j 2 make -f Makefile.webui LANGUAGES="ach ady ar bg cs da de en_US en_GB es et fa fi fr he hr hu it ko lv lt nl no pl pt ro ru sl sk sq sv tr uk zh zh-Hans" all make[1]: Entering directory '/tmp/tvheadend' make -f Makefile.webui WEBUI=std compile-std make[2]: Entering directory '/tmp/tvheadend' CC src/uuid.o CC src/main.o stat: unrecognized option: printf=%-35n %7s\n
Do you have an idea how to solve this?
This is because not installed package "coreutils"
p.s.
If dont want to wait compilation to take hours
edit
wherever you found it
to
This will use all available CPU treads of host for compilation, not just 2 of them.