Bug #2163
Wrong frequency on discovered muxes using sat-ip and dvb-t
0%
Description
I'm using an octopus net with an additional DVB-T module. My muxes list was obviously empty so I've manually inserted the frequency (like 730000) of a known local mux. The other parameters have been automatically guessed. Great!
The mux discovery mechanism continues to propose additional muxes but they all have a wrong frequency! Such muxes have frequencies like 674000000 with all the additional parameters specified. In few seconds they are marked as FAIL. If I manually insert the correct frequency (674000) on a new mux record, it is correctly verified.
A side note, I've tried to correct the frequency on the discovered muxes using the 'edit' link, but they don't change on save...
History
Updated by Jaroslav Kysela over 9 years ago
Updated by - Status changed from New to Fixed
There is some work in the area in the recent code. TVH accepts only info received from mux... If provider offers additional frequencies available in other areas, TVH does not have any possibility to detect it.
Updated by Mario D over 9 years ago
Updated by What I'm saying is that the frequencies transmitted by the mux are correct but in the wrong format: 674000000 instead of 674000. I don't know if they are transmitted wrong or it is tvheadend that misunderstand them.
Look at this screenshot: http://postimg.org/image/ll937j38z/full/
The former muxes are manually added, the latters are automatically detected with the wrong frequencies.
Updated by Jaroslav Kysela over 9 years ago
Fixed in v3.9-1322-gc31a0c8 . The bug in the SAT>IP client code accepted wrong values (in kHz) but the frequency values for DVB-T and DVB-C should be in Hz. I also changed in v3.9-1323-ge5fda6d the mux name fields in the mux grid to show all values in Mhz (with kHz part after the decimal point).
Updated by Mario D over 9 years ago
The frequencies of the discovered DVB-T muxes on SAT>IP are now correct.