Tvheadend

No, because of how you associate tuners with networks with muxes and onwards, you don't duplicate muxes in 3.9.x... once you've defined the muxes for, say, Astra 28.2E as a network 'Satellite', then simply associating a new DVB-S tuner with that network immediately picks up all defined muxes/services/channels. Where it goes wrong is if you have e.g. DVB-T and DVB-T2 tuners, in that a DVB-T tuner obviously can't receive anything from a T2 mux, so it's worth defining Freeview SD and HD as separate networks in my experience.

You could try the 'linked tuner' option, see if that helps. It was intended for DVBSky units but might help... also, just check connections, as that low SNR looks suspicious.

Thanks, I've tested linking the tuners and it to make no difference. What I have noticed however is straight after a reboot, I can connect 2 clients to the two tuners (I have disabled the the other two as they have no feed at the moment) watching the stream tab both tuners SNR stay at 100% if I then change a channel on one client, both tuners drop right down to about ~5% - ~25% and the clients disconnect.

I've tested both connections using my skybox and both work ok, plus I think that I can now get the tuners working straight after reboot suggest to me that there is any issue with the dish, LNB nor cables.

Could the tuners getting not enough power be the problem? I have connected the power cable, but I've connected it to a spare socket that also powers a Solid state drive and a secondary 3TB drive, this cable connects directly into the Nano PS...does the power effect the SNR?

I suppose SNR (or S and N, anyway) would depend on power would if it's got an amp of some kind, which would make sense given the power you'd get otherwise... any way of taking things out of circuit, or trying a different configuration? Anything in any logs about power levels?

I havn't seen anything in the logs in regards to power levels - although I've only been viewing the logs via the web portal (by expanding the window at the bottom of the tabs) would that give me the same information than using the debug tab - I guess this just rights it to file?

I'm going to open up the case and check power connections etc just in case, I've also got it plugged into the PCiE x1 slot I think I read somewhere to try the x16 slot... I'll give it a try. This HTPC lark can be quite frustrating at times!

I suspect you're only seeing tvheadend messages in that panel, though, and not system messages. So it depends on whether tvh knows what's wrong and can report on it, versus the OS telling you what died in the first place.

Right then... I connected the card to the PCIe x16 slot instead of the PCI X1 slot (pcie x16 = 3.0 standard apparently where as x1 is not). There is an improvement, I'm can now seem to use 2 clients using the two separate tuners. Although occasionally it seems the tuners drops the snr for several seconds when I turn off a client and restart it. I'm not convinced I've found a solution yet... Will test and watch the logs over the next couple of days...

just to close this off, my testing was wasn't very successfully with TVhead. I decided to uninstall and give MythTV a go, after battling for 2 days setting it up, I got the same results!

I then decided that I should test with all four inputs connected and it works. I have have no knowledge on how a DVB card should work, I was under the impression that if you only use 2 inputs then only 2 adapters would be used and the other 2 adapers would not be used.... Any way it works with myth and I would presum it would work with TVhead (I really can't remember if I tried TVhead with all four adapters, I've tried so many differnt things!!).

I'm staying with myth for the time being, rewinding/fastforwardinh seems a lot more stable than TVhead at the moment although I'm not sure that's down to TVhead or the Kodi's addon?...

I'll keep an eye on TVhead's development and one day if version 4.0 is ever released I may return!