It's little bit complicated. Your provider doesn't answer on SETUP RTSP request as filter excepts (filter specifies ports where is listening, but answer doesn't contain these ports). After this request, is approx. one minute of failures (it seems that requesting same stream fail for one minute, because previous request (request with bad answer) is not ended.
I try to made some changes, I hope that you can make some tests for me.
first rtsp by sat2ip Devices uses 554
the rtp can you Chose rtcp should be rtp +1 so is it describe in the spec
here a exsample of my Sat2Ip Library http://code.google.com/p/sat2ip/sou...rary/trunk/Sat2Ip.Library/Rtsp/RtspSession.cs
As I can see, you support only one type of transport of possible four (there are interleaved transport, multicast, UDP (this type you support) and TCP). And also I didn't that you support more than one track. Or I'm wrong?
Anyway, the core of problem is, that server have to respond to my request with my client ports specified. But server responds with client ports 0 and 0. So, in that case I'm not sure, if server understand my request correctly.
PLAY rtsp://192.168.178.55:554/stream=1?delpids=553,554,0,261,558 RTSP/1.0\\r\\n
I don't know if a filter is controlable from the c# side, but if the filter would support this it would decrease channelswitching timesPLAY rtsp://192.168.178.55:554/stream=1?addpids=533,534,0,259,538 RTSP/1.0\\r\\n
PLAY rtsp://192.168.178.55:554/stream=1?delpids=533,534,0,259,538 RTSP/1.0\\r\\n
PLAY rtsp://192.168.178.55:554/stream=1?delpids=18 RTSP/1.0\\r\\n
PLAY rtsp://192.168.178.55:554/stream=1?freq=394&msys=dvbc&sr=6900&mtype=256qam&pids=0 RTSP/1.0\\r\\n
PLAY rtsp://192.168.178.55:554/stream=1?addpids=18 RTSP/1.0\\r\\n
PLAY rtsp://192.168.178.55:554/stream=1?addpids=110,120,0,100,130 RTSP/1.0\\r\\n
yes. I modified your code to support DVB-C, but somehow it didn't worked out. Than I was to lazy to investigate it further But if you want to support DVB-C in your lib I will be happy to test it againfreakyJ do you use dvb c ?
that's what I meant, sorry if that wasn't so clear.channelchaning works only over Play if you would hold the current session
yes. I modified your code to support DVB-C, but somehow it didn't worked out. Than I was to lazy to investigate it further But if you want to support DVB-C in your lib I will be happy to test it againfreakyJ do you use dvb c ?
that's what I meant, sorry if that wasn't so clear.channelchaning works only over Play if you would hold the current session
My request was if the filter would support this somehow to get faster channel switching times It is clear that you must stay on the same mux if you only change pids. But anyway, thanks for taking care