Incorrect LCNs associated with service names in service list

[Peter Urbanec]

Incorrect LCNs associated with service names in service list (UP or DOWN from LiveTV) for Sydney. See attached screenshot for details.

See Wikipedia List of digital television channels in Australia for correct LCNs for service names.

Reproduction steps

After scanning Sydney location, use UP or DOWN to display the service list, then check the LCNs and service names against teh Wikipedia list. The incorrect LCN/Service name combinations appear to happen to LCNs > 40, and are 2 or 3 less than the value they should be.

Reproducability is set to Always, as the problem is always found if it happens at all.

[prl]

Confirmed for scans of Canberra, see http://www.beyonwiz.com.au/forum/viewtopic.php?p=102020#p102020 for details.

[prl]

The issue was updated with the following change(s):

• The issue's poster has been changed, from prl to peteru.

[Peter Urbanec]

The issue was updated with the following change(s):

• The status has been updated, from New to Confirmed.

[Peter Urbanec]

The issue was updated with the following change(s):

• The priority has been updated, from Normal to High.

[Peter Urbanec]

The issue was updated with the following change(s):

• The severity has been updated, from Normal to Major.

[Peter Urbanec]

A file was uploaded. reference to attachment LCNs_20140117_1319.jpg (Screenshot showing incorrect LCNs in Sydney)

[Peter Urbanec]

The issue was updated with the following change(s):

• This issue's description has been changed

[Peter Urbanec]

The issue was updated with the following change(s):

• The status has been updated, from Confirmed to Delegated.

[Peter Urbanec]

The issue was updated with the following change(s):

• The priority has been updated, from High to Critical.

[IanSav]

A file was uploaded. reference to attachment 20140317_IanSav_Melbourne_Etc.zip (/etc/enigma2 directory contents from IanSav in Melbourne) This comment was attached:

I have attached the contents of my /etc/enigma2 directory immediately after upgrading the firmware and performing a "Restart GUI" as directed. I am based in Melbourne and only see the transmitters at Mount Dandenong.

C-31 on LCN-44 has been assigned LCN-45 by the scan. All channels after this channel now have an assigned LCN one greater than the value they are mean't to have. GO! for example is not LCN-99 but LCN-100.

[prl]

A file was uploaded. reference to attachment 20140318_prl_Canberra_settings.zip (/etc/enigma2 directory contents from prl in Canberra) This comment was attached:

I have attached the contents of my /etc/enigma2 directory immediately after upgrading the firmware and performing a "Restart GUI" as directed. I am based in Canberra and only see the transmitters at Black Mountain.

LCNs from 2-34 are correct, LCNs from 50-66 are one greater than the correct value, and LCNs 80-90 are two greater than they should be.

Scanned    Correct
 LCN         LCN   Network/Service name
  2           2    ABC/ABC1
  3           3    SBS/SBS ONE
  5           5    SCA/SC10 Canberra
  6           6    PRIME/PRIME7 Canberra
  8           8    WIN Television/WIN Canberra
 21          21    ABC/ABC1
 22          22    ABC/ABC2 / ABC4
 23          23    ABC/ABC3
 24          24    ABC/ABC News 24
 30          30    SBS/SBS HD
 32          32    SBS/SBS TWO
 33          33    SBS/SBS 3
 34          34    SBS/NITV
 51          50    SCA/ONE Canberra
 55          54    SCA/TVSN
 56          55    SCA/ELEVEN
 57          56    SCA/Aspire
 61          60    PRIME/PRIME7 Canberra
 62          61    PRIME/PRIME7 Canberra
 63          62    PRIME/7TWO Canberra
 64          63    PRIME/7mate Canberra
 65          64    PRIME/4ME
 66          65    PRIME/ishoptv
 82          80    WIN Television/GEM Canberra
 84          82    WIN Television/GOLD 2
 86          84    WIN Television/GOLD
 90          88    WIN Television/GO! Canberra

[Ian Brabham]

A file was uploaded. reference to attachment 20140317_IanB_Melbourne_settings.zip (/etc/enigma2 directory contents from IanB in Melbourne) This comment was attached:

LCN's 44 to 99 are one higher than they should be, i.e. 44 is 45, 70 is 71, ...., 99 is 100

[prl]

A file was uploaded. reference to attachment 20140318_prl_Canberra_settings-1.tgz (Compressed tar archive of /etc/enigma2) This comment was attached:

prl @ Canberra Black Mountain

Re-created in case there were problems with the first file I attached, which didn't show any LCN problems on the developer's test machine.

[Ian Brabham]

A file was uploaded. reference to attachment 20140318_IanB_MelbourneAsPerth_settings.zip (/etc/enigma2 directory contents from IanB in Melbourne using Perth table) This comment was attached:

No LCN44 in userbouquet.terrestrial_lcn.tv file.

[Peter Urbanec]

The issue was updated with the following change(s):

• The status has been updated, from Delegated to Testing.

[Peter Urbanec]

The issue was updated with the following change(s):

• The status has been updated, from Testing to Closed.
• This issue has been closed
• This issue's progression has been updated to 100 percent completed.
• The resolution has been updated, from Not determined to Fixed.

[Ian Brabham]

PeterU, why did you close this when it is still not fixed completely!

From my post on the 18th, easy-gui-aus-4.0-beyonwizt3-20140317 thread

Sorry guys no cigar. The order is now right except C31 on LCN 44 is missing. Attached 20140318_IanB_MelbourneAsPerth_settings.zip to bug 61.

Just to make sure I used the Perth table with has the same main channel set as Melbourne, i.e 6,7,8,11,12,32,... and C31 came up short, with this scan order it is the last successful frequency scan.

The issue was updated with the following change(s):

• The status has been updated, from Closed to Reopened.
• This issue has been reopened
• The resolution has been updated, from Fixed to Not determined.
• This issue's progression has been updated to 0 percent completed.

[Ian Brabham]

The missing LCN seems to have been fixed.

The issue was updated with the following change(s):

• The status has been updated, from Reopened to Closed.
• This issue has been closed
• This issue's progression has been updated to 100 percent completed.
• The resolution has been updated, from Not determined to Fixed.