I told a neighbor about this who used to work in Broadcast many years
ago locally. And back then when they were just setting up the digital
gear for the switch over, she said the engineers they where bringing in
were not engineers and had little clue what they were doing. It's only
gotten worse.
She did hear something about CW and KGUN local stations now being owned
by the same company.
Another problem is, I built this using an Asus motherboard. I will never
buy anything from them again. I have had a number of Asus boards and and
all have had problems. All where unstable and VERY picky about what
cards you used. Swap the motherboard and nothing else and all the
strange problems would go away. One of the problems I have is that when
I try to run the ATSC plugin's channel scan, 80-90% of the time it
crashes VDR and no one could figure out why. Sometimes it works just
fine. other times no. And it looks like I won't be getting any more
scans for awhile because it is back to crashing. Maybe some day I'll get
the time and money and time to build another system.. someday...
On 3/10/2018 1:30 AM, Klaus Schmidinger wrote:
On 10.03.2018 01:21, Torgeir Veimo wrote:
Isn't there a plugin that can change such data before it gets processed?
The problem is that these are *duplicate* channels - they can't be in the
channel list to begin with. They need to have different Transport Stream
Ids.
And as wen can see from Timothy's old channel list, they used to have
these.
So somebody just screwed up!
Klaus
On 10 March 2018 at 08:47, Timothy D. Lenz <tlenz@xxxxxxxxxx
<mailto:tlenz@xxxxxxxxxx>> wrote:
Welllll, it gets better. Tonight I see VDR is grabbing guide data
for 9x and using it for 58.x. So 58.x data is now being lost. grrrr
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@xxxxxxxxxxx
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
