Take Tvlib v3. Screenshots what's wrong, and time of start timeshifting for each channel
Take Tvlib v3. Screenshots what's wrong, and time of start timeshifting for each channel
HelloHD09-11-2013 18:11:17.157 EPG Info for channel with networkid=[0x9F], transportid=[0x19C8], serviceid=[0x28]:
09-11-2013 18:11:17.157 Event: id=[0x4237], date=[10.11.2013 (MJD=0xDD1E)], timeUTC=[21:00:00], duration=[00:30:00], running_status=[0], free_CA_mode=[0]
09-11-2013 18:11:17.157 Short Descr+:lang=[hun], event=[Eszement jбtйkok] / enc=[10.2.2], text=[Illъziуk, konfъziуk] / enc=[10.2.2]
PolarisMedia definitely uses ISO-8859-2 (same as HelloHD above) but doesn't set encoding flags for it. Detecting of non-conformed ISO-6937 won't work in this case because all chars, that are used in this particular text, are allowed in 6937. So MP tries to convert 8859-2 as 6937, that results in wrong symbols.09-11-2013 18:14:51.780 EPG Info for channel with networkid=[0x1], transportid=[0xB], serviceid=[0x1CE]:...
09-11-2013 18:14:51.781 Event: id=[0xFC82], date=[10.11.2013 (MJD=0xDD1E)], timeUTC=[15:55:00], duration=[01:50:00], running_status=[0], free_CA_mode=[0]
09-11-2013 18:14:51.781 Short Descr+:lang=[srp], event=[Ko№arka-ABA liga: Crvena zvezda-Cedevita, prenos] / enc=[-], text=[] / enc=[-]
exactly same as with 2 (Polaris media).09-11-2013 18:16:34.727 EPG Info for channel with networkid=[0x1], transportid=[0xB], serviceid=[0x1D0]:
09-11-2013 18:16:34.727 Event: id=[0xFCB5], date=[09.11.2013 (MJD=0xDD1D)], timeUTC=[16:00:00], duration=[02:00:00], running_status=[0], free_CA_mode=[0]
09-11-2013 18:16:34.727 Short Descr+:lang=[srp], event=[Ko№arka ABA LIGA: Zadar - Igokea] / enc=[-], text=[] / enc=[-]
Technically NID is allocated by DVB... but some providers use random values. In answer to your question: no I would not recommend/like to detect/apply encoding by depending on NID+TSID.Is provider identification on NetworkID and TransportID reliable only for one satellite? If i have NID and TID (coming from EPG), can i detect specific provider only on this information, without knowing satellite? Or this pair can appear several times on different satellites?
that i have seen already, after comparing DVB NID table with NIDs of some providers and found some incostintences...some providers use random values
I wouldn't make any recommendation because I don't like the idea of provider-specific code in the EPG encoding detection. If I've understood correctly some of these providers are not DVB-compliant. IMO we should not be adding hacks to support non-compliant providers. The best way to fix such problems is for us to provide the technical information to the provider so they can correct their broadcast stream. If they don't respond or refuse to make changes... well, might have to look for a different EPG source where encoding is known and specified correctly.What would you recommend to use as provider identificator (applied to encoding)?