Dedicated eth interface for tvheadend
I use tvheadend on an i3 6100 running Ubuntu 18.10 with an onboard Intel I219-V gigabit NIC. As well as serving TV it is my general fileserver/NAS and a bunch of other things. My tuner is an HDHomeRun Connect.
For a while I've noticed that when I transfer files at a high speed (generally 60MB/s or more) off the server, the picture breaks up. I initially blamed my router, but then realised it happens even with a different router. Further testing (i.e. doing transfers between client PCs and bypassing the server) revealed it's the server's ethernet interface that is getting overloaded, not the router.
I've now upgraded to gigabit internet so even running a speed test or downloading very fast on my server causes the picture to break up. I need to solve this!
It seems like the easiest way to achieve an uninterrupted picture would be to give tvheadend (which, in conjunction with a HDHomeRun, appears to be quite sensitive to heavy network traffic) its own dedicated ethernet interface. However I can't see an obvious way to bind tvheadend to a specific eth network. Does anyone know how to do this? Is it a tvheadend thing or a general linux thing?
Alternatively - does anyone have an ethernet card which can handle 1GBps transfers at the same time as receiving a HDHomeRun signal without breaking up? If my problems are simply due to a crappy onboard NIC, maybe I just need to replace it and be done with it...
RE: Dedicated eth interface for tvheadend - Added by Em Smith 5 days ago
I'm surprised that the picture breaks up. However, if your HDHomeRun is near your PC, you could buy a USB Ethernet (or PCI if you have spare ports) and connect a cable direct from the PC to the HDHomeRun bypassing everything. The HDHomeRun (and most modern Ethernet) is auto-selecting so you don't need a special crossover cable. The HDHomeRun should then self-assign an address 169.254.x.y, subnet 255.255.0.0.
(I don't have an HDHomeRun but the manuals state they support this).
To answer your other question about autoscheduling on +1 channels, this should be fixed on 4.3 if you tick the box "attempt to find better time slots" in config->recording->dvr profiles.