No stream on client, newa or vlc - Unexpected error in RTSPKeepAlive

[andydld]

Here are the logs include the "netpush.log".

> I might need to you to capture a 30 second or so full transport stream

A capture from another pvr or wireshark or another tool ?

[sub]

> I might need to you to capture a 30 second or so full transport stream

A capture from another pvr or wireshark or another tool ?

Usually I can just tell people to use the TSCapture evaluation version. Unfortunately that wont work for SAT>IP devices.

I'm not sure what to suggest for capturing this. I'd hoped you might have already had a tool that can capture the full transport stream.

[sub]

The netpush.log is showing the software is receiving the transport stream, so we're probably going to need to try capturing a full transport stream, so I can run it through the code.

[sub]

You could try capturing it by setting HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\NPVR\ DumpNetPush=1 (DWORD), and should end up with a .ts file created in c:\temp.

[andydld]

Here's the suggested "DumpNetPush"-file and the current logs.

By the way: This *.ts can't be played with vlc media player.

[mvallevand]

It is a valid ts file but doesn't contain a/v data. It seems to only be passing the pids 0 and 18 that NextPVR requested in the url you showed us here https://forums.nextpvr.com/showthread.ph...post515444 I actually was surprised the DVB Viewer url worked.

Martin

[andydld]

The url's was seen thru wireshark, maybe i missed something.
To make the chaos complete, i have done a tcpdump on the tvheadend-linux-machine, too.

tvheadend:

SETUP rtsp://192.168.0.6/?src=1&fe=1&freq=11493.75&sr=22000&msys=dvbs2&mtype=8psk&pol=h&fec=23&ro=0.35 RTSP/1.0
PLAY rtsp://192.168.0.6/stream=1?addpids=0,1,16,17,18,5110,5111,5112,5113,5114,5115,5116,5117,5118,5119,8187 RTSP/1.0

nvpvr:

SETUP rtsp://192.168.0.6/?src=1&freq=10744&sr=22000&pol=h&msys=dvbs&fec=56&pids=0,18 RTSP/1.0
PLAY PLAY rtsp://192.168.0.6/stream=1 RTSP/1.0

dvbviewer:

OPTIONS rtsp://192.168.0.6:554/ RTSP/1.0
SETUP rtsp://192.168.0.6:554/?src=1&freq=10744&msys=dvbs&plts=off&fec=56&pol=h&ro=0.35&sr=22000&mtype=qpsk&pids=0 RTSP/1.0
PLAY rtsp://192.168.0.6:554/stream=1?addpids=18&delpids=0 RTSP/1.0

The "OPTIONS"-part i have only seen with dvbviewer.

Please note, that i tested with different channels.

[sub]

It's normal for NextPVR to start out with only pid 0 and 18 with SAT>IP, then dynamically discover and add the rest. It looks like it'll be something to do with the PAT or PMT in the stream. I'm investigating.

[sub]

I think I generally understand what is happening now. You're basically trying to tune a channel that is not on that frequency. ie, you're trying to watch a channel with a service_id of 28721, but that frequency only has channels with service_ids 7031, 7032, 7034, 7035 and 7036. It never finds the channel information for 28721, so doesn't map the rest of the PIDs.

Basically, something went wrong back and scan time. I'm pretty sure when it's scanning, you've ended up with channels from the previous frequency, rather than the current frequency. I'd first try deleting all the channels, then rescanning - hopefully that will fix it. If not, we'll need to work out why this scanning issue is happening for you.

[mvallevand]

He is playing multiple channels so it is hard to say. The ts file has that tsid in the pat.

Martin