Channels given wrong frequencies..after channel scan (1 Viewer)

[Lotsofjazz]

Hi,

This happens to me all the time lately when I do a full rescan of the Cable TV/Radio channels, I think explaining works best with an example:

Last week Ziggo did move around some channels, so I decided to do a rescan of all channels.. note that the channel in the example did NOT MOVE!! and should not have been touched at all.

I tried to watch RTL 4 HD in Media Portal and got the error Channel not found (or something similar.. in dutch)

Because I had this before I checked the channel details in TV Server Setup and found what is shown in "RTL 4H channel details" (note the ID 2101 and frequency)

BUT the tuning details for 2101 are as shown in "Tuning parameter 2101 and 2102"

You can see that RTL4 HD was given the frequency of the NEXT tuning parameter 2102.

I wonder why this happens and If I can do something about this, because also with other channels this happened. If one channel in a particular transponder is affected, all other channels of that transponder are also given the frequency of the NEXT transponder in the list....

Rescanning the frequencies of 2101 and 2102 does solve the problem, but there should not be a problem at all...

Before I rescanned the above mentioned tuning frequencies, attached the TV Server logs of today as well, this should include the logs of the full rescan. Note that I did a rescan of 642750 and 634750 (transponder 2098 and 2099) already before attaching these logs.

Is this a bug, or is this something wrong at my side?

(I have reported this before, as part of another question, in case you got a deja vue ;-) )

 

[Lotsofjazz]

Just to add to this oddity... It is not with ALL transponders, most are OK, but just a few were given the frequencies of the next transponder in the list. I have found thus far 2097 was given the frequency of 2098;
2098 was given the frequency of 2099;
2099 was given the frequency of 2100. But the channels in 2100 were all OK.
2101 was given the frequency of 2102, But the channels in 2102 were all OK

2076, the transponder before 2097, was also OK
Also the following were OK, as I could watch the channels normally:

18, 2051, 2054, 2062, 2063, 2064, 2074 and 2112,

Other channels in other transponder frequencies I did not check, as I do not watch them anyway.

Attached the tuning details I used (Ziggo NID 5555, Alkmaar, Netherlands)

 

[mm1352000]

The log file shows that RTL 4 HD is found twice in the scan. First at 2101:
[2017-04-01 14:14:25,583] [Log ] [98 ] [INFO ] - dvbc: ScanVBC:tv: Freq:562750 ONID:-1 TSID:-1 SID:-1 PMT:0xFFFFFFFF FTA:False LCN:10000 SymbolRate:6900 Modulation:Mod256Qam
...
[2017-04-01 14:14:30,764] [Log ] [98 ] [INFO ] - 0) 0x600 0x835 0x4C05 0x7D0 RTL 4 HD type:19
[2017-04-01 14:14:30,764] [Log ] [98 ] [INFO ] - Found: DVBC:tv:Ziggo RTL 4 HD Freq:562750 ONID:1536 TSID:2101 SID:19461 PMT:0x7D0 FTA:False LCN:928 SymbolRate:6900 Modulation:Mod256Qam

...and then at 2102:
[2017-04-01 14:14:30,896] [Log ] [98 ] [INFO ] - dvbc: ScanVBC:tv: Freq:578750 ONID:-1 TSID:-1 SID:-1 PMT:0xFFFFFFFF FTA:False LCN:10000 SymbolRate:6900 Modulation:Mod256Qam
[2017-04-01 14:14:51,050] [Log ] [98 ] [INFO ] - 0) 0x600 0x835 0x4C05 0x7D0 RTL 4 HD type:19
[2017-04-01 14:14:51,050] [Log ] [98 ] [INFO ] - Found: DVBC:tv:Ziggo RTL 4 HD Freq:578750 ONID:1536 TSID:2101 SID:19461 PMT:0x7D0 FTA:False LCN:928 SymbolRate:6900 Modulation:Mod256Qam

From TV Server's perspective these two channels are identical. They have the same DVB identifiers (ONID, TSID and SID) so they are indistinguishable. The same.

After scanning 2101, RTL 4 HD would have the correct 2101 frequency. Afterwards that frequency is overwritten when 2102 is scanned. The latest details are always kept, so that's why the saved frequency is 578750 from 2102.

I can't see a problem with what TV Server has done here. Obviously the end result is wrong... but TV Server has no way to know that or make it correct.

 

[Lotsofjazz]

Ok, thanks... So the problem lies with Ziggo then, that they do not clean up their frequencies properly when something has changed... This is happening since they moved channels around at the beginning of this year. I understand MediaPortal cannot do much about this..

A work around is to change the transponder list order, like placing 2102 before 2101, and do this for all transponders that have this problem... I know about the few I listed, but there might be more of course.

 

[mm1352000]

So the problem lies with Ziggo then, that they do not clean up their frequencies properly when something has changed.

Yes, I agree.

A work around is to change the transponder list order, like placing 2102 before 2101, and do this for all transponders that have this problem.

I'm not so sure about this.
Maybe it would be better to completely remove the unused frequencies like 2102?