config tvh for SATIP from DMS

[Nayef]

Hello 

i have "HTS Tvheadend 4.3-2375~g653bd0400" and want what setting must i set for DMS

 

here my setting

https://ibb.co/kgnHjbqd
https://ibb.co/vvVWLTh9
https://ibb.co/5x8mx21M

 

but i have error

2025-03-01 04:12:34.324 mpegts: 11117V in 13e - tuning on SAT>IP DVB-S Tuner #4 (10.147.17.178@UDP)
2025-03-01 04:12:34.324 subscription: 01FB: "scan" subscribing to mux "11117V", weight: 6, adapter: "SAT>IP DVB-S Tuner #4 (10.147.17.178@UDP)", network: "13e", service: "Raw PID Subscription"
2025-03-01 04:12:44.324 mpegts: 11117V in 13e - scan no data, failed

 

 

[Griga]

The screenshots look ok. Same as my working configuration for Astra 19.2° East. But what about this Configuration -> DVB Inputs -> Position Parameters page?

 

 

Please also provide a support.zip from the DVBViewer Media Server PC.

 

[Nayef]

https://ibb.co/v42DwsGr

https://top4top.io/downloadf-3347njkox1-zip.html

 

 

[Griga]

Please attach the support.zip here in the forum. I can't use the download page, because I can't read it.

 

[Nayef]

forum here limit size upload Max total size: 3.08 kB !

Edit: ok i remove all my old attach

and upload new one

 

support.zip

 

also i see connect tvh with DMS but no data!

 

 

Edited March 1 by Nayef

[Griga]

This is bad for running a server:

 

Zitat

Public Firewall Profile is active

 

You should use the private profile for a home network. The DVBViewer and Media Server installers add firewall rules for enabling inbound network traffic, but the rules are only valid for the private profile. Please search the internet for the key words firewall private public profile to get instructions how it can be changed.

 

[Nayef]

6 hours ago, Griga said:

This is bad for running a server:

 

 

You should use the private profile for a home network. The DVBViewer and Media Server installers add firewall rules for enabling inbound network traffic, but the rules are only valid for the private profile. Please search the internet for the key words firewall private public profile to get instructions how it can be changed.

 

 

 now i set private profile

but same issue

[Griga]

I had a look at your svcdebug.log. The last attempt of the 10.147.17.128 client to get data from the Media Server happened on Saturday, 01.03.25 11:50:13. The relevant log entries are
 

Spoiler

01.03.25 11:50:13.609 TRTSPWebserver       ClientConnect    07D3C920
01.03.25 11:50:18.738 TServiceMain         AddReference     RTSP-Client 10.147.17.128: 1
//...
01.03.25 11:50:19.271 TRTSPUDPClient       AllocateHardware Digital Devices DVB-S/S2 Tuner 1 (5)
01.03.25 11:50:19.271 TRTSPUDPClient       SetTuner         Got new hardware
01.03.25 11:50:19.271 TBDADigitalDevices   SetTuner         TType: 1, Freq: 11861, Symrate: 27500, LOF: 10600, Tone: 1, Pol: 0, DiseqC: 3, FEC: 3, APID: 0, VPID: 0, PMT: 0, SID: 0, TID: 0, NID: 0, SatMod: 1, DiseqCVal: 0, Flags: 0, Group: 0
//...
01.03.25 11:50:19.371 SETUP                200              src=1&fe=2&freq=11861&sr=27500&msys=dvbs&mtype=qpsk&pol=h&fec=34&ro=0.35&pids=0
//...
01.03.25 11:50:19.465 PLAY                 200              pids=0,1,16,17,8187
01.03.25 11:50:19.564 PLAY                 200              pids=0,1,16,17,8187
01.03.25 11:50:20.358 PLAY                 200              pids=0,1,16,17,8187
//...
01.03.25 11:50:38.980 TEARDOWN             200              
01.03.25 11:50:39.075 TRTSPWebserver       ClientDisconnect 07D3C920
01.03.25 11:50:44.993 ReleaseStandbyblock  RTSP-Client 10.147.17.128

 

This indicates, that the client has successfully connected to the Media Server and sent a SETUP command. The Media Server in return has allocated a Digital Devices tuner, tuned the requested transponder (11861 H SkyItalia on Hotbird) and replied with a 200 OK status code.

 

Then the client tried three times to get some data by using the PLAY command, requesting PID 0, 1, 16, 17, 8187 (which means, it has received the 200 OK reply and proceeds with the next step). The PIDs are the service information tables PAT, CAT, NIT, SDT (read more about it here), that a scanner usually requests for finding channels on a frequency. PID 8187 does not exist on this transponder, so I don't know why it is requested.

 

The Media Server again replied with 200 OK, which means, it can fulfill the request, and it will send the data as UDP stream to the client address and port. However, the repeated PLAY requests suggest that this UDP stream doesn't arrive in the client, for whatever reason. It's hard to tell why. Maybe Linux firewall settings or other network conditions are preventing it. I don't know enough about Linux to provide help in this respect. All I can say is that the TCP connection for sending commands from the client to the server works, but obviously not the UDP stream from the server to the client. It is blocked somewhere.

 

BTW: Tvheadend should be configured for not using the FE (frontend) parameter) when using the DVBViewer Media Server as source. However, currently it is using it, as I can see in the log (fe=2). So I would rather uncheck the "FE supported" checkbox in the advanced settings (see your third screenshot). However, this is only a general hint. It will not fix your problem.

 

So what can we do now? I'm currently working at a new method for Sat>IP data transport in the Media Server. It doesn't use an additional UDP return channel, but sends all data through the TCP connection (called RTP/AVP/TCP). This method is also supported by Tvheadend (already tested) and would probably work in your case. I could provide a beta test version. Do you want to try it?

 

[Nayef]

Thank you for your interest

if i uncheck FE i have error:

2025-03-06 03:06:17.878 satip: SAT>IP DVB-S Tuner #5 (xx.xx.xx.xx@UDP) - RTSP cmd error 7 (DONE) [8-404]
2025-03-06 03:06:18.544 subscription: 01BA: service instance is bad, reason: Tuning failed

 
In the past few days I tried everything by checking if the ports are open between the server and the client and by modifying some options in tvheadend and some channels appeared when checking the satellite,

setting: 

Signal scale (240 or 100): 82 

Maximum PIDs: 100

Maximum length of PIDs: 512

 

but I faced many interruptions and errors in the broadcast that I did not know how to solve,

13e/10872V/Laayoune TV HD: H264 @ #35 Continuity counter error (total 1)
13e/10872V/Laayoune TV HD: MPEG2AUDIO @ #36 Continuity counter error (total 1)
13e/11117V/Eleven Sports 1 4K: TELETEXT @ #707 Continuity counter error (total 1)

 

I read in Google but did not reach a radical solution
If you have an advanced version I would like to try it 

also can set new option for support full TCP in tool: "Media Server Tweaker" So that the user has a choice in choosing what suits him

Edited March 6 by Nayef

[Nayef]

Am 3.3.2025 um 09:19 schrieb Griga:

I could provide a beta test version. Do you want to try it?

 

any news for new method?

wait...

 

Edited March 12 by Griga
unnecessary quoting removed

[Griga]

Please don't quote whole posts unnecessarily. I've corrected your post above. Select the part(s) that you want to quote with the mouse and use the "quote selected" popup provided by the forum software.

 

I was waiting for your reply to my question, because I didn't notice your post three days later. You can use the test version that I have provided as attachment in a private forum message for someone else. You have just been invited to the conversation.

 

Stop the Media Server and replace DVBVservice.exe by the test version in a 3.1.1 installation. It enables using the "RTP/AVC/TCP transport supported" option in Tvheadend (see screenshot above). The advantages of this "TCP interleaved mode" are dropout prevention (at the cost of more protocol overhead) and less firewall issues, since it only sees a single outbound connection established by the client, which is usually accepted without blocking.

 

Please post feedback here, not in the PM.

 

[Griga]

On 3/12/2025 at 7:12 AM, Griga said:

Please post feedback here, not in the PM.

 

[Nayef]

On 3/12/2025 at 9:12 AM, Griga said:

Please post feedback here, not in the PM.

 

 

 

Sorry for the delay in responding.
I haven't been feeling well these days. I'll double-check my settings.
Quick test results:

Some channels work quickly.
Some channels experience errors, such as:

 

RTSP error -90 (Message too long) [8-0]
...
H264 @ #161 Continuity counter error (total 1)

 

but i have less error when set: 

Pass specinv: Off

[Nayef]

15 minutes ago, Griga said:

 

Sorry, I went directly to the messages section and tried the beta version directly, and I didn't read your response in the thread here

[Griga]

9 hours ago, Nayef said:

but i have less error when set: 

Pass specinv: Off

 

Spectrum inversion is only specified for DVB-C cable reception in the Sat>IP specifications and not used for DVB-S.

 

9 hours ago, Nayef said:

H264 @ #161 Continuity counter error (total 1)

 

Quite unlikely that packets get lost with a TCP connection, except if the network conditions are very bad. So I guess it's the result of a reception or driver problem on the server side. Or with other words: It would also appear in a recording log if you would record the channel with the DVBViewer Media Server, without Tvheadend being involved.

 

9 hours ago, Nayef said:

RTSP error -90 (Message too long) [8-0]

 

Don't know what that means.

[Nayef]

is DMS support :addpids/delpids supported ?

[Griga]

Yes, of course.

 

Please attach your zipped svcdebug.log, so I can check some things.

 

[Nayef]

4 hours ago, Griga said:

Yes, of course.

 

Please attach your zipped svcdebug.log, so I can check some things.

 

 

svcdebug.zip

[Griga]

Looks ok. Tvheadend is using RTP/AVP/TCP transport (also called RTSP interleaved mode) as intended. It is indicated by the log entries containing the word TRTSPInterleavedClient. Support for this mode is new in the test version. 

 

There are no errors in the log, so on the server side it seems to work as it should. Thanks for beta-testing!