I sent an email to KGUN and if they don't fix the conflict right away, I guess I'll have to make a complaint to the FCC, not that it will do much good.
On 3/9/2018 2:29 AM, Klaus Schmidinger wrote:
On 08.03.2018 22:38, Klaus Schmidinger wrote:
On 08.03.2018 22:13, Timothy D. Lenz wrote:
I was hoping it was something simple I could fix in the conf. I haven't worked on it or in linux in a long time and don't have the free time to figure it all out again. I'll have to look at this some other time. I am in the U.S. and these are ATA channels. They each have their own freq. and my guess is that they can use what ever numbers they want since they are on there own freq which they bought.
Well, it's funny though that they use exactly the same IDs ;-).
Sure they can do whatever they want, but there are a few basic rules that should be followed in order to guarantee a reasonable coexistance. One of them is that channels that are broadcast in the same area (like from the same terrestrial transmitter, on the same cable or the same satellite) should use unique IDs, even if they are on different transponders. One of these IDs is the "transport stream id", which in your case is 207 for both channels. This should be different.
For testing I added your new channel list to my channels.conf. Here's what my VDR reported upon startup:
Mar 9 10:21:46 raspi4 vdr: [3134] loading ../cfg/channels.conf Mar 9 10:21:46 raspi4 vdr: [3134] deleting duplicate channel KWBA-HD,KWBA-HD:653028615:M10:A:0:49=2:0;52=eng@106,53=esl@106:0:0:3:0:207:0
Mar 9 10:21:46 raspi4 vdr: [3134] deleting duplicate channel LATV,LATV:653028615:M10:A:0:65=2:0;68=eng@106:0:0:4:0:207:0 Mar 9 10:21:46 raspi4 vdr: [3134] deleting duplicate channel ThisTV,ThisTV:653028615:M10:A:0:81=2:0;84=eng@106:0:0:5:0:207:0
With your old list I get no such log entries. So I guess somebody messed up with the TIDs, and the problem should be fixed there.
Klaus
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr