- September 1, 2008
- 21,577
- 8,224
- Home Country
- New Zealand
Okay.No 3rd party firewalls. I'm on Windows 8.1 and just use the built in firewall which I find causes the fewest problems. Turned it off anyway but didn't make any difference.
Hmmm, I wouldn't necessarily assume that. You need to make sure that the tuner can open an RTCP (UDP) connection with your PC. It would be interesting to see what Wireshark shows is actually reaching the PC.The sat-ip box is connected to the router using a wi-fi bridge rather than cable but I don't think that should affect it...
I'm not familiar with this sample. Either way, there is no guarantee that it works in the same way as the code I've written, and therefore there's no guarantee that TVE will work just because the sample works. Different code => possibility for different results....and as I said, the SatIP-RTSP-Sample works well.
The problem has nothing to do with the RTSP command or parameters.What does your RTSP command look like? Could it be that this box doesn't understand some of the parameters? I could try the command directly to verify.
The issue is with the RTCP connection.
TVE has three connections to the tuner: RTSP, RTCP and RTP.
The RTSP connection is used by TVE to tell the tuner what to do. Tuning etc. There doesn't appear to be any problem with this.
The RTP connection is used for the streaming (video, audio etc.). There doesn't appear to be any problem with this.
The RTCP connection is used by the tuner to give signal lock, strength and quality updates. This connection is just as important as the other two connections, because if it doesn't work correctly then TVE will never lock on signal (ie. always say "no signal" when you try to tune).
[edit: Sorry, it is 2 AM here so I need to go to bed. I'll check on this thread again tomorrow.]