Bug #2700
closed
Picon name generation is not correct
100%
Description
Hi,
I assume that Tvheadend picon file names should be fully compatible with Enigma 2 systems. However there are differences in file name generation which results that picons migrated from Enigma box will not be shown or only a part of them will be shown due to file name mismatch.
I found this explanation of picon filename:
__What does an example file name pointing to the .png file look like? 1_0_1_957_327B_3277_6400000_0_0_0.png = the Plicon of 1600e_golden_west_network.png
The file name, what does it mean?
1 = reftype, fixed
0 = flags, fixed
1 = servicetype (1=tv)
957 = SID
327B = transponder id
3277 = network id
6400000 = namespace (orbital position 1600 --> 640 hex)
0 = parent SID
0 = parent transponder id
0 = unused_
_
The main problem is with satellites on the west side. e.g. Thor 0,8W picon generated filename in Tvheadend look like this: 1_0_1_7601_2BE_600_FFF70000_0_0_0.png. The Enigma version is: 1_0_1_7601_2BE_600_E0800000_0_0_0.png
The difference is that TVH assigns FFF7 -> (-9 decimal?) while the picon has E08 -> 3592 (359.2 degree East)
So the problem is with the calculation of orbital position. This is a bug.
On the other hand the namespace part of the picon name is not always the satellite position with traling 0s. It sometimes contains discrimination values which makes possible to distuingish between two DVB services having similar SID/TID/NID.
Unfortunately I could not find a reliable algorithm how to generate the rigth DVB namespace value.
Files
Updated by 
Updated by 
Updated by 
Updated by 
