Connected two Tvh via SATIP. Descrambling on client takes about 10 seconds
Added by Markus Wölfer over 6 years ago
Hi,
I'm running two Tvh server. One acts only as SATIP Server. The second acts as SATIP client (imported the first one with --satip_xml).
On the second Tvh I also configured CAPMT (DVBAPI) to descramble channels.
The problem is now, that it takes about 10 seconds before the client is starting descramble the channel. There must be some kind of delay. But I don't know if it's on the server or on the client.
To verify that it's not a issue in oscam, I configured CAPMT on the first TVH (and disabled it on the second one). Descramble is now nearly instant.
But my goal ist, that the descramble is done on the second server.
Log from Tvh SATIP Server:
2018-07-31 19:47:48.081 subscription: 0002: "SAT>IP Slave/Unitymedia/154MHz/RTL2 HD" unsubscribing, client="SAT>IP Slave/Unitymedia/154MHz/RTL2 HD"
2018-07-31 19:47:48.099 subscription: 0003: "SAT>IP Slave/Unitymedia/154MHz/VOX HD" subscribing to service "Unitymedia/154MHz/VOX HD", weight: 100, adapter: "HDHomeRun DVB-C Tuner #0 (10.0.1.11)", network: "Unitymedia", mux: "154MHz", provider: "Unitymedia", client="SAT>IP Slave/Unitymedia/154MHz/VOX HD"
2018-07-31 19:47:50.098 subscription: 0003: service instance is bad, reason: No descrambler
2018-07-31 19:47:50.099 subscription: 0003: "SAT>IP Slave/Unitymedia/154MHz/VOX HD" subscribing to service "Unitymedia/154MHz/VOX HD", weight: 100, adapter: "HDHomeRun DVB-C Tuner #0 (10.0.1.11)", network: "Unitymedia", mux: "154MHz", provider: "Unitymedia", client="SAT>IP Slave/Unitymedia/154MHz/VOX HD"
2018-07-31 19:47:52.099 subscription: 0003: service instance is bad, reason: No descrambler
2018-07-31 19:47:52.099 subscription: 0003: "SAT>IP Slave/Unitymedia/154MHz/VOX HD" subscribing to service "Unitymedia/154MHz/VOX HD", weight: 100, adapter: "HDHomeRun DVB-C Tuner #0 (10.0.1.11)", network: "Unitymedia", mux: "154MHz", provider: "Unitymedia", client="SAT>IP Slave/Unitymedia/154MHz/VOX HD"
2018-07-31 19:47:54.099 subscription: 0003: service instance is bad, reason: No descrambler
2018-07-31 19:47:54.099 subscription: 0003: "SAT>IP Slave/Unitymedia/154MHz/VOX HD" subscribing to service "Unitymedia/154MHz/VOX HD", weight: 100, adapter: "HDHomeRun DVB-C Tuner #0 (10.0.1.11)", network: "Unitymedia", mux: "154MHz", provider: "Unitymedia", client="SAT>IP Slave/Unitymedia/154MHz/VOX HD"
2018-07-31 19:47:56.099 subscription: 0003: service instance is bad, reason: No descrambler
2018-07-31 19:47:58.099 subscription: 0003: No input source available for subscription "SAT>IP Slave/Unitymedia/154MHz/VOX HD" to service "Unitymedia/154MHz/VOX HD" in mux "154MHz in Unitymedia"
2018-07-31 19:48:00.099 subscription: 0003: No input source available for subscription "SAT>IP Slave/Unitymedia/154MHz/VOX HD" to service "Unitymedia/154MHz/VOX HD" in mux "154MHz in Unitymedia"
2018-07-31 19:48:02.099 subscription: 0003: No input source available for subscription "SAT>IP Slave/Unitymedia/154MHz/VOX HD" to service "Unitymedia/154MHz/VOX HD" in mux "154MHz in Unitymedia"
2018-07-31 19:48:04.099 subscription: 0003: No input source available for subscription "SAT>IP Slave/Unitymedia/154MHz/VOX HD" to service "Unitymedia/154MHz/VOX HD" in mux "154MHz in Unitymedia"
This is the part, where the description is starting on the client:
2018-07-31 19:47:56.099 subscription: 0003: service instance is bad, reason: No descrambler*
Is there anything I can do?
Replies (1)
RE: Connected two Tvh via SATIP. Descrambling on client takes about 10 seconds - Added by Markus Wölfer over 6 years ago
Ok I think I figured it out by myself.
I had so set the value of "Descramble services (limit per mux)" to "0". It was "1" before.