Project

General

Profile

Problem configuring TVheadend as SAT>IP client

Added by Aydan Ulysses about 10 years ago

Hello everybody,

I have a principal problem of configuring a SAT>IP source in tvheadend
i'm just trying to get my head wrapped around tvheadend.
For now I'm trying to get my DVBviewer recording service to work as a SAT>IP server.
I can see a response from it (see attached logfile) but I can't see the server in TV adapters.
I'm using version 3.9.1476~g388c665 from github.
Can somebody give me a hint on how to proceed

Regards
Aydan

tvh.log (8.54 KB) tvh.log satip trace

Replies (4)

RE: Problem configuring TVheadend as SAT>IP client - Added by Aydan Ulysses about 10 years ago

Now I have a Inverto IDLI-8CHE20 and it gets detected in TV adapters.
I enabled 4 of the 8 Tuners and enabled all four Positions for all enabled tuners and associated them all with the same network.
I added a mux manually and it tries to scan but I get this message:
2014-10-08 21:39:15.000 [ INFO] mpegts: 12.187H in Astra - tuning on SAT>IP DVB-S Tuner #5 (192.168.177.23)
2014-10-08 21:39:15.003 [ INFO] subscription: 'scan' subscribing to mux, weight: 4, adapter: 'SAT>IP DVB-S Tuner #5 (192.168.177.23)', network: 'Astra', mux: '12.187H', hostname: '<N/A>', username: '<N/A>', client: '<N/A>'
2014-10-08 21:39:25.000 [ INFO] mpegts: 12.187H in Astra - scan no data, failed
2014-10-08 21:39:25.001 [ INFO] subscription: "scan" unsubscribing

The <N/A> in username, hostname and client seems suspicious to me.
Did I forget to set up something important?

Regards
Aydan

PS: I updated to 3.9.1743~ga510248

RE: Problem configuring TVheadend as SAT>IP client - Added by Aydan Ulysses about 10 years ago

After setting predefined muxes for the network to Astra 19.2 E at least the scan is returning results. Seems the channel data I took from the DVBviewer didn't match up properly.

RE: Problem configuring TVheadend as SAT>IP client - Added by Kev S about 10 years ago

The N/A's are normal (at least for me with my Triax TSS 400)

Oct 10 19:33:09 williams tvheadend4386: subscription: 'scan' subscribing to mux, weight: 5, adapter: '28.2ºE β', network: 'Astra - 28.2°E', mux: '11876H', hostname: '<N/A>', username: '<N/A>', client: '<N/A>'

I found I needed to restart TVHeadend AFTER the TSS had first booted, but it works fine since then. I couldn't get the multiplexes from within TVHeadend's automatic add to work properly and ended up adding one manually myself and after a successful scan (with network discovery turned on) it was able to add the rest (although there was an issue with DVB-S2 Pilots but the option seems to have vanished since then!)

    (1-4/4)