DVB-T VHF frequency- wrong value requested

[regrepl]

I'm having problem tunning to correct frequency in band VHF.

To recreate problem im describing folowing steps.
Using "Signal Finder"

It seems fine

satipclient in debung mode

[9792.128][21804 rtsp.cpp            : 595][sendPlay                 ]   debug: PLAY DATA :
PLAY rtsp://SERVER-IP:554/stream=2?freq=191.5&bw=7&msys=dvbt RTSP/1.0
CSeq: 8
Session: 0221558440

Im getting scaning results

However when I'm trying to zap to scanned channel it dosen't work. Debug log is crazy and losing frequency

[8028.684][21804 rtsp.cpp            : 555][sendSetup                ]   debug: SETUP DATA :
SETUP rtsp://SERVER-IP:554/?freq=**3231.3**&bw=7&msys=dvbt&pids=none RTSP/1.0
CSeq: 1
Transport: RTP/AVP;unicast;client_port=46183-46184

Also this frequency is requested on SAT>IP server side.
0.5 Mhz dosen't change situation, it is not a notation problem.
Acording to sat ip documentation is also correct "fixed point type or integer value"

191.5 and requests for 191 are ok if I manualy try do get that from server, so that is not the issue here. Server reciving wrong frequency request and gives no signal.

In chanel info is even worse.

Signal Finder always requests proper frequency

PLAY rtsp://SERVER-IP:554/stream=1?freq=177.5&bw=7&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=1?freq=184.5&bw=7&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=1?freq=191.5&bw=7&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=1?freq=198.5&bw=7&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=1?freq=205.5&bw=7&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=1?freq=212.5&bw=7&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=1?freq=219.5&bw=7&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=1?freq=226.5&bw=7&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP554/stream=1?freq=219.5&bw=7&msys=dvbt RTSP/1.0
PLAY rtsp://SERVER-IP:554/stream=1?freq=226.5&bw=7&msys=dvbt RTSP/1.0

Chanel zapping always requests wrong frequency. I have only one DVB-T MUX in VHF to test.

Frequency from UHF band are requested correcly,both by signal finder and channel zaping. But there is also another problem with that descripbed in sepreret ticket.

#Test results form openatv 7.3, binary from feed and also custom compiled.