Open jyrts opened 1 year ago
I think the problem is more complex, but I also notice that this problem exists. To recreate this problem I used „Signal Finder”. Yes you can use it in with SAT>IP solution and scan transponders/multiplexes.
satipclient running in console with -l4 debug.
Settings are “User defined transponder”, so that omits any errors in terrestrial.xml System settings is an issue here I set system to dvb-t and changed Bandwidth setting so see effects. Every time I’m getting a new request with parameters
PLAY rtsp://SERVER-IP:554/stream=3?freq=474&bw=10&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=3?freq=474&bw=8&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=3?freq=474&bw=7&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=3?freq=474&bw=6&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=3?freq=474&bw=5&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=3?freq=474&bw=1.712&msys=dvbt RTSP/1.0
All fine in log.
When system is set to DVB-T2 and I change any parameters I’m getting in log
DTV_DELIVERY_SYSTEM : 16
Every single time, and no rtsp requests.
And that also when I’m trying to zap to channel on list
[7422.524][21804 vtuner.cpp : 601][vtunerEvent ] debug: MSG_SET_PROPERTY
[7422.524][21804 vtuner.cpp : 311][setProperty ] debug: DTV_DELIVERY_SYSTEM : 16
[7422.524][21804 rtsp.cpp : 736][handleRTSPStatus ] debug: RTSP STATUS : RTSP_STATUS_SESSION_TRANSMITTING
I have access only to one DVB-T mux, but that creates another problem.
satip-client requests dvb-t2 channels as old dvb-t
Some DVB-T2 SAT>IP servers with old hardware wont lock to transponder when using msys=DVBT for requesting DVB-T2 The problem is on the satip client side, because msys=DVBT2 should be used for DVB-T2.
When DVB-T config file terrestrial.xml has system="1" enabled for transponder, then msys=DVBT2 should be used instead of msys=DVBT...
From the bright side the same thing for DVB-S2 requests works as it should...