Channels are not opened #437
Comments
|
Hi,
Can you upload minisatip logs?
Thanks
…On Mon, Mar 26, 2018, 4:41 AM Shporterator ***@***.***> wrote:
Despite a steady signal, some transponders are not scanned, if you scan
the channels do not open
log tvheadend
2018-03-26 09:54:55.767 subscription: 0002: "HTTP" subscribing to service
"NC+ & Orange Polska & Cyfrowy Polsat /12188V/TV Okazje", weight: 100,
adapter: "SAT>IP DVB-S Tuner #1
<#1> (192.168.0.104)",
network: "NC+ & Orange Polska & Cyfrowy Polsat ", mux: "12188V", provider:
"Cyfrowy Polsat S.A", profile="pass", hostname="192.168.0.105",
client="VLC/2.2.8 LibVLC/2.2.8"
*2018-03-26 09:54:56.392 satip: SAT>IP DVB-S Tuner #1
<#1> (192.168.0.104) - RTSP
cmd error 7 (Unknown error -7) [8-404]*
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#437>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH0gEZyp4S1LiXgBaij44bFZJaI5pHEiks5tiNPrgaJpZM4S6-Ga>
.
|
|
can you describe your hardware |
|
tbs5580 |
|
the problem starts with [26/03 12:39:41.692]: |
|
it seem to reach MAX_PIDS and may fail there |
|
and how to solve this problem? |
|
not sure how this could happen and if this is supported by the tbs drivers |
|
the only way I see is to switch to FULLMUX_PID (8192) when the PID filter overflows |
|
how to do it? I use tvheadend |
|
I'm using the latest version, but apparently the problem persists. |
|
The problem is that minisatip subscribes all PMT PIDs (for descrambling?), so tvh cannot manage PID list itself. [27/03 15:33:34.898]: Got the new transponder 1CE8 7400, position 0, 129 ms after tune [27/03 15:33:34.899]: Start streaming for stream 0, len 188 to handle 11 => 192.168.0.104:47534 [27/03 15:33:34.950]: PAT Adapter 1, Transponder ID 7400, len 279, version 50 [27/03 15:33:12.567]: Adapter 1, PMT sid 7304 (1C88), pid 38 [27/03 15:33:12.567]: Adapter 1, PMT sid 7305 (1C89), pid 49 [27/03 15:33:12.568]: Adapter 1, PMT sid 7355 (1CBB), pid 75 [27/03 15:33:12.569]: Adapter 1, PMT sid 7356 (1CBC), pid 66 [27/03 15:33:12.569]: Adapter 1, PMT sid 7380 (1CD4), pid 94 [27/03 15:33:12.570]: Adapter 1, PMT sid 7393 (1CE1), pid 52 [27/03 15:33:12.571]: Adapter 1, PMT sid 7394 (1CE2), pid 53 [27/03 15:33:12.572]: Adapter 1, PMT sid 7395 (1CE3), pid 54 [27/03 15:33:12.572]: Adapter 1, PMT sid 7396 (1CE4), pid 55 [27/03 15:33:12.573]: Adapter 1, PMT sid 7397 (1CE5), pid 56 [27/03 15:33:12.574]: Adapter 1, PMT sid 7398 (1CE6), pid 57 [27/03 15:33:12.575]: Adapter 1, PMT sid 7399 (1CE7), pid 58 [27/03 15:33:12.575]: Adapter 1, PMT sid 7392 (1CE0), pid 59 [27/03 15:33:12.576]: Adapter 1, PMT sid 7384 (1CD8), pid 88 [27/03 15:33:12.577]: Adapter 1, PMT sid 7382 (1CD6), pid 90 [27/03 15:33:12.577]: Adapter 1, PMT sid 7381 (1CD5), pid 91 [27/03 15:33:12.578]: Adapter 1, PMT sid 7385 (1CD9), pid 92 [27/03 15:33:12.579]: Adapter 1, PMT sid 7386 (1CDA), pid 95 [27/03 15:33:12.579]: Adapter 1, PMT sid 7389 (1CDD), pid 98 [27/03 15:33:12.580]: Adapter 1, PMT sid 7390 (1CDE), pid 99 [27/03 15:33:12.581]: Adapter 1, PMT sid 7391 (1CDF), pid 89 [27/03 15:33:12.582]: Adapter 1, PMT sid 7318 (1C96), pid 42 [27/03 15:33:12.582]: Adapter 1, PMT sid 7302 (1C86), pid 35 [27/03 15:33:12.583]: Adapter 1, PMT sid 7303 (1C87), pid 36 [27/03 15:33:12.584]: Adapter 1, PMT sid 7375 (1CCF), pid 48 [27/03 15:33:12.585]: Adapter 1, PMT sid 7301 (1C85), pid 34 [27/03 15:33:12.585]: Adapter 1, PMT sid 7373 (1CCD), pid 47 [27/03 15:33:12.586]: Adapter 1, PMT sid 7307 (1C8B), pid 40 [27/03 15:33:12.587]: Adapter 1, PMT sid 7315 (1C93), pid 41 [27/03 15:33:12.588]: Adapter 1, PMT sid 7316 (1C94), pid 50 [27/03 15:33:12.588]: Adapter 1, PMT sid 7306 (1C8A), pid 39 [27/03 15:33:12.589]: Adapter 1, PMT sid 7308 (1C8C), pid 256 [27/03 15:33:12.590]: Adapter 1, PMT sid 7310 (1C8E), pid 44 [27/03 15:33:12.591]: Adapter 1, PMT sid 7349 (1CB5), pid 43 [27/03 15:33:12.591]: Adapter 1, PMT sid 7351 (1CB7), pid 61 [27/03 15:33:12.592]: Adapter 1, PMT sid 7352 (1CB8), pid 62 [27/03 15:33:12.593]: Adapter 1, PMT sid 7353 (1CB9), pid 63 [27/03 15:33:12.594]: Adapter 1, PMT sid 7358 (1CBE), pid 68 [27/03 15:33:12.594]: Adapter 1, PMT sid 7359 (1CBF), pid 69 [27/03 15:33:12.595]: Adapter 1, PMT sid 7361 (1CC1), pid 71 [27/03 15:33:12.596]: Adapter 1, PMT sid 7362 (1CC2), pid 72 [27/03 15:33:12.597]: Adapter 1, PMT sid 7363 (1CC3), pid 73 [27/03 15:33:12.597]: Adapter 1, PMT sid 7321 (1C99), pid 81 [27/03 15:33:12.598]: Adapter 1, PMT sid 7322 (1C9A), pid 82 [27/03 15:33:12.599]: Adapter 1, PMT sid 7325 (1C9D), pid 85 [27/03 15:33:12.600]: Adapter 1, PMT sid 7326 (1C9E), pid 86 [27/03 15:33:12.600]: Adapter 1, PMT sid 7327 (1C9F), pid 87 [27/03 15:33:12.601]: Adapter 1, PMT sid 7328 (1CA0), pid 188 [27/03 15:33:12.602]: Adapter 1, PMT sid 7320 (1C98), pid 80 [27/03 15:33:12.603]: Adapter 1, PMT sid 7323 (1C9B), pid 83 [27/03 15:33:12.604]: Adapter 1, PMT sid 7324 (1C9C), pid 84 [27/03 15:33:12.605]: Adapter 1, PMT sid 7376 (1CD0), pid 65 [27/03 15:33:12.606]: Adapter 1, PMT sid 7350 (1CB6), pid 70 [27/03 15:33:12.607]: Adapter 1, PMT sid 7365 (1CC5), pid 51 [27/03 15:33:12.608]: Adapter 1, PMT sid 7354 (1CBA), pid 64 [27/03 15:33:12.609]: Adapter 1, PMT sid 7331 (1CA3), pid 7001 [27/03 15:33:12.610]: Adapter 1, PMT sid 7330 (1CA2), pid 7000 [27/03 15:33:12.611]: Adapter 1, PMT sid 7332 (1CA4), pid 7002 ..... [27/03 15:33:34.963]: MAX_PIDS (64) reached for adapter 1 in adding PID: 7000 |
|
You can disable this behavior by changing opts.pmt_scan = 0 in minisatip.c. |
|
@catalinii : I don't think that this option should be turned on by default. It really confuses the PMT allocation logic in clients. @Shporterator : You may also try to increase the PID limit in dvb.h - MAX_PIDS . |
|
I will push the MAX_PIDS to 128 in any case in dvb.h in the next commit. @perexg, the client should not know about what minisatip does (adding more PMT), can you tell me more about what happens on the tvh side when this option is enabled ? Thanks |
|
Yes, TVH does also PMT scan, but there's max PID limit set in the adapter settings and TVH does not cross this limit (the scan is split - only allowed count of PIDs is subscribed at the time). Of course, if there's a request for streaming (higher priority) which is beyond the PID filter limit, the full-mux stream is requested. TVH assumes the configured maximal count of PIDs is available. If you do something hidden in the server (open more PIDs than the client expects) you'll screw the PID management in TVH. Basically, you should not return the error to the client when the internal PID limit is reached (but open the full-mux stream in minisatip instead and do the software filtering). |
|
Hello, I have compiled the latest version from git in which MAX_PID is set to 128 already. Still, I get the error Shouldn't this problem be fixed now? Is there anything else, I need to do in order to use minisatip as source of tvheadend? Regards, |
|
Hi, can you upload minisatip log ? Thanks |
|
Hello, thanks for your quick reply. Would help? Regards, |
|
yes, try |
|
Hello, I got a bit further, but this seems a bit more complex... First, I did run Then I ran TVHeadend reported
Now I wanted to reproduce the original problem by starting VDR again. But the problem did not re-appear. Instead I got: Then I startet to write this post. So, I have the impression that this could be related to tvheadend and vdr fighting for the satip-devices. Is that right? Greetings, |
2 similar comments
|
Hello, I got a bit further, but this seems a bit more complex... First, I did run Then I ran TVHeadend reported
Now I wanted to reproduce the original problem by starting VDR again. But the problem did not re-appear. Instead I got: Then I startet to write this post. So, I have the impression that this could be related to tvheadend and vdr fighting for the satip-devices. Is that right? Greetings, |
|
Hello, I got a bit further, but this seems a bit more complex... First, I did run Then I ran TVHeadend reported
Now I wanted to reproduce the original problem by starting VDR again. But the problem did not re-appear. Instead I got: Then I startet to write this post. So, I have the impression that this could be related to tvheadend and vdr fighting for the satip-devices. Is that right? Greetings, |
|
Hello, I got a bit further, but this seems a bit more complex... First, I did run Then I ran TVHeadend reported
Now I wanted to reproduce the original problem by starting VDR again. But the problem did not re-appear. Instead I got: Then I startet to write this post. So, I have the impression that this could be related to tvheadend and vdr fighting for the satip-devices. Is that right? Here my configuration in tvheadend. This was auto-detected: Greetings, |
|
Hi Hendrik, Yes both tvheadend and vdr are fighting for resources but both behave a bit differently. I am not sure if there is a way to specify in VDR plugin satip whcih adapter to use (I did not check recently). The option to use would be "fe=X" where X is adapter number Thanks |
|
Another way is to disable first two tuners in tvheadend (enable tuners 3 and 4). With this setup, the first two tuners will be available for clients which does not use fe= parameter (auto tuner assignment). |
|
Closing due to inactivity. If |
Despite a steady signal, some transponders are not scanned, if you scan the channels do not open
log tvheadend
2018-03-26 09:54:55.767 subscription: 0002: "HTTP" subscribing to service "NC+ & Orange Polska & Cyfrowy Polsat /12188V/TV Okazje", weight: 100, adapter: "SAT>IP DVB-S Tuner #1 (192.168.0.104)", network: "NC+ & Orange Polska & Cyfrowy Polsat ", mux: "12188V", provider: "Cyfrowy Polsat S.A", profile="pass", hostname="192.168.0.105", client="VLC/2.2.8 LibVLC/2.2.8"
2018-03-26 09:54:56.392 satip: SAT>IP DVB-S Tuner #1 (192.168.0.104) - RTSP cmd error 7 (Unknown error -7) [8-404]
The text was updated successfully, but these errors were encountered: