Search the Community

Hi, I like to list here (I apologize for opening a new thread) the current bugs related to SAT>IP protocol in the last version of DVBViewer Pro (& Recording Service): 1) In the scanning process, regardless of the SAT>IP server used (sat, terrestrial, software, hardware...) the FIRST frequency in a range never works. The code is wrong with the first tunning (next frequencies are working as expected). 2) When you uncheck "DVB-T2" with a SAT>IP DVB-T tuner, the option isn't saved. When you return to the config window, the "DVB-T2" is another time checked. 3) When you select "prefered" over "normal" for a SAT>IP device, then the device used for scanning is the one marked as "normal" not the one marked as "preferred". This applies to devices using the same "Channel Groups" so it's a bug. 4) The signal strength of devices that don't use the RTCP Announcement method (values of signal in RTP UDP+1) but uses the DESCRIBE method (parameter "a=" in the response) is not indicated in the status bar of the DVBViewer (signal always 0% but you receive the correct channel). This is a semibug because the standard references two methods for receive the signal values. 5) The Recording Service ins't including the MANDATORY parameter <satip:X_SATIPCAP> in description.xml. Without this is imposible that several clients (like Elgato Android App) can use the RS as SAT>IP server. I feel is time for another release... you agree?

Hi, I'm a registered user of DVBViewerPro. I found a bug in the DVBViewerPro - This is the behaviour with the free "SatIP DVBViewer" Lite Edition version 1.0.15: * Select Options * Go to Scanner * Select Expert * Select the correct Transporder List corresponding to your Source * Select ANY Frequency (same transponder in End Frequency) * Select Scan Frequency Then the spected behaviour is: the transponder is scanned (PAT, PMT and SDT go green) and N programs found. - Now repeat with last version of DVBViewerPro v5.3.2.0: * Select TV/Radio + Channel Scan * Select your Trnaspoder List * Select ANY Frequency (same transponder in End Frequency) * Select Scan Frequency Then the behavious is: regardless of the selected frequency the tunning always fail (PAT only yellow, then red). No programs found. The Current Device is the correct RTSP Network Device. However, if you select "Scan Range" the first transponder fails, but then the scanning process continues and you found the channels. So the bug is related to scan one frequency. I hope developers fixes this in next version. Regards.