general performance questions (and rare artefacts on HD channels with Sat>IP)

    I've had no major problems with Gemini Lake Celerons for TV Headend server duties. I never run the Media Playback on the same platform as the server though (I try to keep media playing and TV Headend separate). My last TV Headend SAT>IP server was based around a <£200 Chuwi Herobox and a USB 3.0 external hard drive.

    No need for anything like an i3/5/7 for TV Headend duties unless you are also going to do transcoding or run other stuff on it (not recommended).

    As for why you see artefacts on some platforms or others - it's likely to be that some MPEG 2 Transport Stream processors and h.264 video decoders (assuming you're watching h.264 content) are better at concealing/correcting errors than others. You see very different artefacts when watching the same errors on different playback devices.

    noggin

    Yes that's exactly why I am hoping on an evolution for THV.

    This "canceling/correcting (of) errors" seems to be not a major issue, if that many (all) other Apps and Tools are capable of.

    Can I maybe switch the "MPEG 2 Transport Stream processors and h.264 video decoders" for TVH manually?

    DVBViewer seems to use "LAV Filter", which is an extra installation coming with DVBViewer.

    How can I configure those settings (transport stream, decoder, etc.) for TVH? (To tinker around with and trying e.g.).

    Unless you are transcoding prior to streaming, TV Headend isn't doing any video decoding (so won't be using an h.264 or MPEG2 video decoder), that's purely a function of your client platform that is playing the video (usually Kodi - though there are also TV Headend apps)

    TV Headend doesn't do any video or audio processing on the received streams unless you are transcoding (i.e. decoding and recoding the received video and audio bitstreams). By default TV Headend will just 'pass through' the h.264/h.265/MPEG2 and MP2/AAC/AC3/EAC3 audio it receives from the DVB-T/T2/S/S2/C or IP sources it has untouched.

    TVH will be simply demuxing the MPEG2 transport stream to split out the service you wish to stream/record (as transponders and multiplexes are usually a single transport stream containing multiple video+audio or audio services on that tp/mux) - so if there are errors at the transport stream level, this could cause errors in TV Headends demuxing.

    However the video and audio decoding (i.e. stream playback) isn't functionality that is part of regular use in TV Headend - so TV Headend doesn't need h.264 video decoders - that's all done on the client that connects to TV Headend that actually displays the video and audioo.

    If you are watching in Kodi - then it's the h.264 decoder that Kodi is using that is either able to cope with concealing errors or not. If you are using hardware decoding then this may well be a function of the hardware decoding on that platform. If you are using software decoding in Kodi, then it's likely to be the decoder code that Kodi is using (which is based on ffmpeg I think). I know there has been quite a lot of effort to improve ffmpeg's ability to cope with glitchy streams (as it's used in broadcast distribution chains these days) - so software decode may improve things if your Kodi platform has the CPU power to cope with it.

    AIUI some TVs will be using the same decode paths for TV Headend streams as for their own DVB-T/T2 tuners, which will be optimised to cope with error-filled streams (as they are TVs and expect errors), whereas media players are expecting clean, error-free streams, so don't have the same level of optimisation. Other TVs will use totally different paths for decode in Kodi compared to DVB streams (they may be decoded on totally different bits of silicon)

    However - the core cause of this is that you have continuity errors that you shouldn't have within TV Headend and a decent satellite signal. Fix those and all the platforms will be OK. (I can go days without a single continuity error in my Kathrein SAT>IP / Astra 28.2 set-up )

    Edited once, last by noggin (July 15, 2021 at 8:20 AM).

    noggin

    The "core cause" must have a root cause though.

    And although my workaround is doing it's job fine (in not using TVH at all, but instead usind DVBViewer Media Server on a Win10 Laptop),

    of course I would still love to get rid of that Laptop with its 1-2W in S3 and 10W while running the server.

    --> Even if it's just another/different workaround like running some extra conversion/filtering tool on the RasPi before or after the TVH-sofware to compensate for the cont. errors (like the other apps do).

    Sadly I am quite blank on how things all work together (especially in regards of the "cont. errors").

    (What's the output of the antenna/LNB, what is Kathein doing with it, how is the network/Fritzbox involved, what is TVH doing exactly, how is the TVH output "received", what does the "player" do with it?)

    Therefore I have no clue how to continue eliminating possible root causes.

    My stomach is still telling me, that the problem is either within or after the TVH server.

    Otherwise I still don't have any explaination why I dont' get artifacts on my old TV using my FireTV Stick, but I do get the artifacts using the SAME setup and FireTV stick on my new TV (--> just pluging the stick from one to the other TV).


    Update:

    Thios is the log file, that i got from DVBViewer Media Server:

    Device: KATHREIN SatIP EXIP418 DVB-S 2

    Timer Name: Der Soldat James Ryan

    Timer Start: 14.07.2021 23:39:00

    Timer Duration: 03:04:00 (184 min.)

    Timer Options: Teletext=0, DVB Subtitles=0, All Audio Tracks=1, Adjust PAT/PMT=1, EIT EPG Data=0, Transponder Dump=0

    Timer Source: API

    23:39:01 / 00:00:00 (~ 0,00 MB) Start Recording

    23:39:01 / 00:00:00 (~ 0,10 MB) PID 768: MPEG Audio Stereo, 48 khz, 192 kbps

    23:39:02 / 00:00:01 (~ 0,74 MB) PID 767: MPEG2 Video, 16:9, 720x576, 25 fps

    02:43:00 / 03:03:59 (~ 5878,24 MB) Stop

    Average Data Rate: 0,532 MB/s

    Total Size: 5878,2 MB (6163781724 Bytes)

    As you can see it reports ZERO errors for a 184min record. (It would reports all streaming errors from the EXIP etc. in that LOG.)

    The recordings from THVeadend on the other hand showed the same artefacts as live TV - so on THVeadend also for recording there is my issue.

    Is that maybe a helpful information for further root cause analysis on my siode?

    Please advise me things I could test to find out where the problem is with my setup and TVH.

    Can I write such a Logfile from THV aswell to check what error its reporting?

    Edited 2 times, last by LOLinger78 (July 15, 2021 at 11:46 PM).

    LOLinger78

    Quote

    Sadly I am quite blank on how things all work together (especially in regards of the "cont. errors").

    (What's the output of the antenna/LNB, what is Kathein doing with it, how is the network/Fritzbox involved, what is TVH doing exactly, how is the TVH output "received", what does the "player" do with it?)

    Assuming you have a Wideband/Quad/Quattro LNB connected to your Kathrein (Unicable and Unicable II is a little bit different)

    1. Your LNB receives a focused RF beam which the dish has focused, from the orbital position it is pointed towards.

    2. Your LNB contains Horizontal and Vertical polarisation functionality that lets it receive one or both horizontal and vertical polarised signals (polarisation allows the RF band to carry more signals without the H and V signals interfering with each other)

    3. Your LNB will have a Local Oscillator (for Universal LNBs this will have two different frequencies, for a Wideband just one) which is mixed with the RF signal received and creates a much lower frequency IF band that can be sent down the cable.

    3. Your Kathrein will select the right LNB input (and if a Quad LNB is used tell the LNB which of the 4 universal bands to feed down that LNB feed) and Local Oscillator setting (if required)

    4. Your Kathrein will then, under IP control from TV Headend, over SAT>IP, select which transponder frequency band in the IF band it receives down the cable to tune to.

    5. Your Kathrein will then, under IP control from TV Headend, demodulate that transponder using DVB-S or S2 demodulation, with the correct FEC etc.

    6. Your Kathrein will then, optionally, under IP control from TV Headend, select which PIDS (or audio, video, text, data etc. streams) to send to TV Headend over IP, and then will start streaming them. (In some cases it is possible to select every PID on a transponder - but for many SAT>IP tuners this causes them to fail as the network throughput and processing required is too high)

    7. Your TV Headend server will receive those IP streams and process them - either recording them to a local or network storage device, or streaming them back out over the network.

    (For Unicable / Unicable II LNBs the set-up is a bit different for points 2-4)

    It's points 1-7 that will influence continuity errors. These can be caused by poor signal, slightly incorrect IF oscillator setting, poor network handling (or in some cases the SAT>IP tuner being pushed too hard and sending more PIDs than is required). There are a number of SAT>IP settings in TV Headend for optimising different makes of SAT>IP tuner.

    Have you checked the accurate SAT>IP setting for your device in TV Headend - and checked whether there is any advice for your tuner on the TV Headend forums?

    The fact that you get good results with DVB Viewer and less-good result with TV Headend suggests this is a TV Headend config issue - or a problem with the platform you are running TV Headend on (continuity errors would be caused by dropped network packets - as SAT>IP uses UDP not TCP so no packets are checked and re-requested)

    noggin

    Hello Noogin I'm very happy that you try to help me. And I really would love to get things running.

    I am willing to do all kind of troubleshooting.

    First of all I am using a Quad LNB (KATHREIN KEL 444 Euroline Universal Quad LNB).

    My Antena is rather old, cheap and small.

    My Sat>IP is Kathrein 418 which, from my research, got pretty reasonable test results altogether, although not being a cheap device.

    But I am using this setup (antenna + LNB) since years and never had issues ever since (using both my HTPC with 2x Hauppauge Nova S2 cards and a Comag SL40HD receiver.)

    [The SAT>IP is brand new (2 weeks?).]

    For THV forums I have the issue to not receive an confirmation link e-mail. I tried like 5 times the last couple of days.

    Therefore I am unable to open threads there sadly.

    Poor signal quality would indeed be an issue to troubleshoot, since I can't really test it (withoput buying a new antena // LNB).

    I was kind of hoping for a logging possibility in THV to hopefullly get hints.

    Regarding settings:

    no I didn't do anything in the THV tuner settings yet. To me its 100% confusing. There are like 30 different entries//lines in THV - although i only have 8 tuners.

    I would have no clue at all, what to do - even for "trial and error" :(

    Regarding "continuity errors would be caused by dropped network packets": I would kind of cancel this out. Since not only does DVBViewer run fine, but also Simple IPTV (using a m3u) runs on both the LG TV itself (LG OS6 -SIPTV app) and also on Kodi (SIPTV Client Addon). Without any flaws.

    Wouldn't those two programs face the same issues with a root cause in my network?

    The "platform" I am running THV on is a RasPi 4b 8GB.

    And I tried both LibreElec 9.2.7 and Raspbian lite (using the latest 32bit version from "Raspberry Pi Imager"). Both with exactly the same poor results.

    Edited 8 times, last by LOLinger78 (July 17, 2021 at 2:41 AM).

    I'll see if I can post on your behalf at TV Headend forums - there are posts from other Kathrein users there I think - have you done a search on those and google to see how others have configured their Kathreins?

    I don't know what you mean about '30 different entries/lines'?

    You do understand how to set-up TV Headend and how to set-up your SAT>IP receiver within it don't you?

    As you only have one orbital position - you've done the basic stuff and disabled the other 3 positions for each tuner (configuring each of the 8 tuners for just a single position (rather than the 4 Diseqc options - A, B, C, D etc. )? (That shouldn't be an issue but will get you down from 32 tuner options to 8 )

    There are also SAT>IP specific settings that can differ between different SAT>IP tuners in TV Headend - as some tuners have more functionality than others (Some can send an entire transponder, others can just send a couple of services per transponder before running out of processing)

    As for network issues- no you can't assume that because other software works fine over the network with your Kathrein and TV Headend doesn't that it isn't the network. If TV Headend is requesting a lot more data (as it could be if it's not been configured not to) you could be running at much higher network loads with TV Headend vs other tuners.

    How much research have you done in to how TV Headend works with SAT>IP tuners?

    Hello noggin

    maybe you can open a thread in THV forums, which is saying, that I can't register (not getting a mail, although it is confired to be sent)?

    I have done all kind of research and along that of course I also googled things like "TVHeadend EXIP 418" to find setup guidance.

    (And all kinds of "TVHeadend SATIP artifacts".)

    I'm really at the point, where I have not even an idea what do to in locating where the problem is.

    Today I tried to activate all logging in TVH (both system add on and HTS client).

    When I was serching for the log file I noticed that MC showed 98% usage. And since I am kind of unable to browse/screen from SSH terminal I tried to link the SD-Card to my card reader. Sadly I can't see anything but the "boot" on the SD-card from windows.

    After putting it back to the raspi it now shows 96%:

    Does that actually mean free or occupied? Since 98%/96% occupied woul be a nightmare I guess?

    How can I browse/screen/search my drive in convenient ways, to find out in which folders large data was written (and when)?

    The log file itself is completely useless to me on SSH terminal. The file is tremendously large (e.g. it includes ALL EPG infotext !!) and I don't get a proper Scroll bar and especially have no search routine availlable. After using "page down" key for like 5 minutes I still was at 1% in MC displaying it.

    Is the only way to manually copy it over to my win PC for proper analysis?

    At least that's what I did, but the LOG file is 125MB for 40 seconds.

    It didn't even get to errors.

    It ends with:

    2021-07-17 12:34:24.380 [ TRACE]:epg: eo [0x30112f8, 22266, 3, tvh://channel-41d66df66d6a27d57b943f41442d0510/bcast-22265/episode] updated

    2021-07-17 12:34:24.380 [ TRACE]:epg: eo [0x30112f8, 22266, 3, tvh://channel-41d66df66d6a27d57b943f41442d0510/bcast-22265/episode] putref 0

    2021-07-17 12:34:24.380 [ TRACE]:epg: eo [0x30112f8, 22266, 3, tvh://channel-41d66df66d6a27d57b943f41442d0510/bcast-22265/episode] destroy

    2021-07-17 12:34:24.380 [ TRACE]:epg: eo [0x41be2d0, 22265, 4, (null)] destroy

    2021-07-17 12:34:24.380 [ ERROR]:epg: log buffer full

    2021-07-17 12:34:24.913 [ INFO]:epgdb: stored (size 2444344)

    2021-07-17 12:34:24.927 [ TRACE]:main: tasklet leave

    2021-07-17 12:34:24.927 [ TRACE]:main: mtimer tick thread join enter

    2021-07-17 12:34:24.927 [ TRACE]:main: mtimer tick thread join leave

    2021-07-17 12:34:24.927 [ TRACE]:main: dvb_done() enter

    2021-07-17 12:34:24.927 [ TRACE]:main: dvb_done() leave

    2021-07-17 12:34:24.927 [ TRACE]:main: lang_str_done() enter

    2021-07-17 12:34:24.927 [ TRACE]:main: lang_str_done() leave

    2021-07-17 12:34:24.927 [ TRACE]:main: esfilter_done() enter

    2021-07-17 12:34:24.927 [ TRACE]:main: esfilter_done() leave

    2021-07-17 12:34:24.927 [ TRACE]:main: profile_done() enter

    2021-07-17 12:34:24.927 [ TRACE]:idnode: unlink node 5d4138e6e314fa6ca9079fc834d42420

    2021-07-17 12:34:24.927 [ TRACE]:idnode: unlink node bf5c9ce6fabe2bf9615a42be014f556b

    2021-07-17 12:34:24.927 [ TRACE]:idnode: unlink node 5b401dfea48ef5c48ee4848bb750b1f6

    2021-07-17 12:34:24.927 [ TRACE]:idnode: unlink node 4280bfd591e49ada0bfb8f7cd0ddc0a2

    2021-07-17 12:34:24.927 [ TRACE]:idnode: unlink node b5efd3abde3499c0e01b1d8140de0e26

    2021-07-17 12:34:24.927 [ TRACE]:idnode: unlink node ab56854573ba9d464858296cac37a3d1

    2021-07-17 12:34:24.927 [ TRACE]:idnode: unlink node 40371a3057842aa467529cdeb36c882d

    2021-07-17 12:34:24.927 [ TRACE]:main: profile_done() leave

    2021-07-17 12:34:24.927 [ TRACE]:main: intlconv_done() enter

    2021-07-17 12:34:24.927 [ TRACE]:main: intlconv_done() leave

    2021-07-17 12:34:24.927 [ TRACE]:main: urlparse_done() enter

    2021-07-17 12:34:24.928 [ TRACE]:main: urlparse_done() leave

    2021-07-17 12:34:24.928 [ TRACE]:main: streaming_done() enter

    2021-07-17 12:34:24.928 [ TRACE]:idnode: unlink node 0038638bd88b09806e706bc9f6bc139c

    2021-07-17 12:34:24.928 [ TRACE]:main: streaming_done() leave

    2021-07-17 12:34:24.928 [ TRACE]:main: idnode_done() enter

    2021-07-17 12:34:24.928 [ TRACE]:main: idnode_done() leave

    2021-07-17 12:34:24.928 [ TRACE]:main: notify_done() enter

    2021-07-17 12:34:24.928 [ TRACE]:main: notify_done() leave

    2021-07-17 12:34:24.928 [ TRACE]:main: spawn_done() enter

    2021-07-17 12:34:25.113 [ TRACE]:main: spawn_done() leave

    2021-07-17 12:34:25.113 [ NOTICE]:STOP: Exiting HTS Tvheadend


    The second thing I did today was researching on a new sat antenna. To be honest this is the ONLY part in my HW setup that I can think of being "poor".

    The one I'm having is 80cm but no-name and old. My LNB is rather new. I replaced it in 2018.

    But a propoer antenna from Kathrein (CAS 120) is 600€ plus another 200€ for a mounting that is needed for it.

    So buying just to find out it was not the issue would really hurt. (But I would still do it, if I continue to fail on finding ways to futher troubleshoot my problems.)

    With the "30+" lines I meant the Muxes (and its even 107):

    Sadly I don't have deep knowledge "how to set-up TV Headend and how to set-up your SAT>IP receiver within it" - no. :(

    I used the auto setup wizard to do so.

    But that wizard removed the positions 2-4, as you mention:

    Only using 5 is intended from my side. To always have 3 spare ones to use for other needs (VLC, SIPTV app on the TV e.g.).

    I think first of all I need to provide a log where TVH is displaying the cont. errors.

    The best would be to have one directy related to a recording (like I provided from DVBViewer which has a dedicated check box for "write log with recordings" in the recordings-setup page).

    Because there I can directly check at the timesstamps on which I see the artifacts in the mpg to have a relation.


    But I can't find such a setting in THV:


    Is there a chance to do this with post processing commands?


    Today I also went back on reviewing my FireStick .

    As I said it runs fine on the old TV but has the same fragments on the new TV (which is still killing my brain as it makes not much sense to me).

    After 5-10 minutes watching carefully I was about to cancel and turn off (--> once again proofing there no issue).

    But exactly in that moment I got artefacts. I continued watching and withing the next 10 minutes I saw artifacts for another 2 times.

    They look a little different there (more greyish and more monolored vs. more colored), but I think its the same (a "micro stutter" and distrubuted squared artifacts).

    The huge difference still is the frequence. I have seen three in 15-20 minutes on the old TV and I see about three EVERY minute on my new TV.

    Edited 4 times, last by LOLinger78 (July 17, 2021 at 5:14 PM).

    Have you enabled Expert / Advanced mode in the menus on TV Headend? What SAT>IP settings in TV Headend do you have?

    Could you post grabs of your DVB config settings in TV Headend?

    Post Processing is not the route to fix this - those errors just shouldn't be there in the first place.

    I'm in the UK and have a small 50cm dish for Astra 28.2 - cost £50... I take it you are not in the target area for the satellite you want to receive?

    How long are you leaving TVH to capture EPG data before viewing - epggrab can sometimes swamp underpowered platforms.

    Edited 2 times, last by noggin (July 18, 2021 at 4:47 AM).

    One other thing - do you have any Transport Errors alongside your Continuity Errors?

    I fired up my TV Headend Debian server running on a Celeron PC. Currently just doing AutoRecs of the main UK networks (BBC One HD, BBC Two HD, ITV HD, C4 HD, C5 HD plus a cheeky Talking Pictures SD as that unearths some hidden gems!) TV Headend Server and Kathrein are on the same switch.

    Here are some screen shots in case they are useful.

    (Still no continuity errors after 3 hours)

    (After five hours there were a couple of continuity errors on three tuners - fewer than 10 errors though)

    Edited 3 times, last by noggin: Merged a post created by noggin into this post. (July 19, 2021 at 3:40 PM).

    Also - I've read that Continuity errors on SAT>IP set-ups can be the result of missed RDP UDP packets (I think RDP packets have an incrementing unique stamp number so a missed packet can be discovered ?).

    Discussion that some recent Linux kernel stuff has caused issues with some hardware in that regard - though no idea if the Pi is impacted. One TVHeadend user was seeing continuity errors every minute or more in that situation.

    Hello noggin

    sorry for responding late. I was busy the last two days and could not go on troubleshooting.

    First of all I found out, that MC obviously is showing some "random" numbers.

    The "easy" way I was looking for to browse my SD-card was the command "df -h".

    Luckily everything is fine :)


    I was using "Advanced" settings in TVH, therefore I switched to expert.

    My adapters look like this:

    Its the same like you, but with checks at "addpids/delpids supported" and "FE supported".

    But I didn't do them manually for sure.

    Also the later settings (e.g. "send rolloff settings") is not availlable in my Version of TVH (its 4.2).

    That one looks different than yours. I have "advanced settings" there aswell.

    Last one looks different than yours aswell.


    Anything I shall change? (E.g. the ones you have turned off "addpids/delpids supported" and "FE supported".)


    Today I sent an email to Kathrein Support. Maybe they have an idea what I shall look for.

    Because today I noticed that VLC player created the same artefacts on my Win10 Laptop. Probably even worse.

    I use it from UPnP auto detect with an m3u List from satip.info.

    Something I reported to be fine eralier in this thread btw.

    So not working: 1.) VLC over direct UPnP from EXIP 2.) TVHeadend server

    and working: 1.) DVBViewer media server 2.) SIPTV (both adddon for Kodi and App)

    Edited 2 times, last by LOLinger78 (July 20, 2021 at 4:24 PM).

    Ah - I'm on HTS Tvheadend 4.3-1909~gc66e3bc7d which I think I compiled from GitHub myself (I usually create a .deb pkg when I build TV Headend under a Debian OS)

    Afraid I'm not expert enough to give any more advice on the set-up of the SAT>IP tuner.

    I don't use MC much - I usually just SSH in for command line access and copy stuff manually, or use an SFTP client like FileZilla for remote file transfer.

    I would be surprised if Kathrein have much experience of their SAT>IP Tuners being used with TV Headend internally - but stranger things are known to happen!

    Out of interest - if you go STATUS->Stream do you also see any Transport Errors as well as Continuity Errors?

    No, I don't see transport errors. But I see uncorrected blocks:

    Today I reinvestigated on my network performance.

    I re-tested UDP packet loss, but to me everything seems to be ok.

    On low loads (100MBit) I see close to 0% loss (very occasional 0,01% loss).

    On a high load (800MBit+) I see around 0,3%-0,4% loss, depending on the room.

    But that should be pretty normal I guess, having 4 switches inbetween and using small buffer sizes for that high load with the auto setting (buffer size 41kb and packet size 1500b).

    I ordered another switch though, to test wheter something changes if I move the RasPi (TVH) in the cellar next to the EXIP.

    (And using the Firestick as my player.)

    Edited once, last by LOLinger78 (July 21, 2021 at 1:45 PM).

    • Best Answer

    noggin

    OMG I fixed it ! 2 weeks of nightmares are over.

    You won't believe what the root cause was: the Fritzbox 7590 !

    The answer from Kathrein brought the solution.

    They said it's either a defect EXIP or it's within the network.

    So today I setup a switch right next to the EXIP and tested TVH (and VLC) from there.

    And I didn't get the problems.

    So I setup another SD-card for RasPi with an IPerf3 server to test step by step (=wire for wire) where the packet loss came from. Because in the cellar itself I got 0% packet loss EVEN at 800MBit speeds (with 8 parallel streams each being 100 MBit).

    And voila I got 0% packet loss just until the Fritzbox (which I was using all 5 ports on, as a star point for my whole network).

    As soon as I switched over to a free port on the Fritzbox I measures loss, only the same wire connected to the cellar, that I measured 0 loss just "before" the fritzbox.

    So I tested from the other directions aswell (office e.g. with 2 switch after the Fritzbox). And what shall I say? 0% loss just until the Fritzbox.

    So what I did is to just buypass the whole Fritzbox with another 8-port switch, just ataching the box to that switch for Internet and the USB-disk @Fritzbox.

    And not only do I get 0 paket loss in all rooms, also my SAT>IP finally works without ANY issues.

    Edited 7 times, last by LOLinger78 (July 23, 2021 at 6:17 PM).

    I am glad that you saw that the SAT>IP server was not at fault. In my experience the SAT>IP servers work very well, I have a secondary CE server based on amlogic S912 that forwards the DVB-T channels, via SAT>IP, to a main server tvheadend LE based on intel x86_64 located 300 km away, and that in turn, It can forward all TV channels (tuners: USB, SAT>IP, and IPTV) to a CE client also based on amlogic S912 located 3000 km from the main server. Well, everything works great.

    Quote from elonesna

    I am glad that you saw that the SAT>IP server was not at fault. In my experience the SAT>IP servers work very well, I have a secondary CE server based on amlogic S912 that forwards the DVB-T channels, via SAT>IP, to a main server tvheadend LE based on intel x86_64 located 300 km away, and that in turn, It can forward all TV channels (tuners: USB, SAT>IP, and IPTV) to a CE client also based on amlogic S912 located 3000 km from the main server. Well, everything works great.

    Yep - I had a set-up that used a Raspberry Pi with a DVB-T2 tuner to forward channels between countries - though I didn't use SAT>IP, I eventually used an SRT protected tunnel (initially I just used plain https transport stream)

    Edited once, last by noggin (July 27, 2021 at 12:49 PM).