Mailing List Archive

Missing EPG on a number of channels
Dear MythTV users,

I'm missing EPG for a number of channels.
The problem started mid December when several channels announced that they were changing their place and that viewers should rescan.
I rescanned several times, but this did not fix the issue.
Strangely, MythWeb showed a channel that I had deleted in mythtv-setup.
So I gave up, deleted all channels, video sources and capture cards and created them anew.

First, only 39 channels appeared in the scan. Only after turning off "Logical Channel Numbers required" I got 86 more of the usual channels.
But then again, a number of channel don't get EPG. I checked the channel settings, and strangly these were added with "Use 'Over-the-Air' programme listings" off. I turned the setting on for the channels but this did not help.
What the channels lacking EPG have in common is the same two mplexid values.
I turned debugging on for eit, but all I can see is that it seems to scan the two mplexids.
So, I wonder whether it's the data that is missing or the software that has problems with the data on the two mplexes.
How to find out?

I have a quadHD card connected to some kind of DVB-C that comes via FTTH (fiber), in Germany.
I'm running MythTV 1:31.0+fixes20211113.git25f1bb1d12-dmo0+deb11u1 on Debian 11 (upgraded from 10 a few days ago but that did not fix the EPG problem).
(/etc/apt/sources.list: deb http://ftp.uni-kl.de/debian-multimedia/ bullseye main)

Thanks,
Robert

Jan 02 12:22:25 hostname mythbackend[1310]: 2022-01-02 12:22:25.320880 E MPEGStream[3](0x7f8e50079368): Error: AFCOffset(4)+StartOfFieldPointer(182)>184, pes length & current cannot be queried
Jan 02 12:22:25 hostname mythbackend[1310]: 2022-01-02 12:22:25.471459 E MPEGStream[3](0x7f8e50079368): Error: AFCOffset(4)+StartOfFieldPointer(181)>184, pes length & current cannot be queried
Jan 02 12:22:25 hostname mythbackend[1310]: 2022-01-02 12:22:25.922921 E MPEGStream[3](0x7f8e50079368): Error: AFCOffset(4)+StartOfFieldPointer(181)>184, pes length & current cannot be queried
Jan 02 12:22:26 hostname mythbackend[1310]: 2022-01-02 12:22:26.173914 E MPEGStream[3](0x7f8e50079368): Error: AFCOffset(4)+StartOfFieldPointer(181)>184, pes length & current cannot be queried
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.409973 I EITScanner[2]: Added 91 EIT Events
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.410492 I Reschedule requested for MATCH 0 1 12 2022-01-05T23:00:00Z EITScanner
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.411678 I EITCache: Writing 2 modified entries of 953 for channel 10001 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.416399 I EITCache: Writing 2 modified entries of 863 for channel 10009 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.419562 I EITCache: Writing 1 modified entries of 1034 for channel 10033 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.421863 I EITCache: Writing 1 modified entries of 1073 for channel 10035 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.432885 I EITCache: Writing 2 modified entries of 843 for channel 10201 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.433674 I EITCache: Writing 2 modified entries of 1006 for channel 10234 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.434395 I EITCache: Writing 2 modified entries of 910 for channel 10237 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.436618 I EITCache: Writing 1 modified entries of 1096 for channel 10302 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.439046 I EITCache: Writing 1 modified entries of 1034 for channel 10305 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.442639 I EITCache: Writing 2 modified entries of 899 for channel 10407 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.443338 I EITCache: Writing 2 modified entries of 888 for channel 10408 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.444217 I EITCache: Writing 2 modified entries of 960 for channel 10409 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.445798 I EITCache: Writing 1 modified entries of 1096 for channel 10411 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.447735 I EITCache: Writing 1 modified entries of 1096 for channel 10412 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.448601 I EITCache: Writing 1 modified entries of 1096 for channel 10413 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.451877 I EITCache: Writing 2 modified entries of 863 for channel 10417 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.452625 I EITCache: Writing 2 modified entries of 937 for channel 10418 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.453376 I EITCache: Writing 2 modified entries of 931 for channel 10419 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.455225 I EITCache: Writing 2 modified entries of 979 for channel 10421 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.456031 I EITCache: Writing 2 modified entries of 979 for channel 10422 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.456762 I EITCache: Writing 2 modified entries of 979 for channel 10423 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.457488 I EITCache: Writing 2 modified entries of 979 for channel 10424 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.458292 I EITCache: Writing 2 modified entries of 928 for channel 10425 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.459094 I EITCache: Writing 2 modified entries of 928 for channel 10426 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.459939 I EITCache: Writing 2 modified entries of 928 for channel 10427 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.460738 I EITCache: Writing 2 modified entries of 961 for channel 10428 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.461330 I EITCache: Writing 2 modified entries of 615 for channel 10429 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.461910 I EITCache: Writing 2 modified entries of 633 for channel 10430 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.462789 I EITCache: Writing 2 modified entries of 1190 for channel 10431 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.463421 I EITCache: Writing 2 modified entries of 400 for channel 10432 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.478009 I EITCache: Writing 1 modified entries of 1034 for channel 10452 to database.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.485441 I EITScanner[2]: Now looking for EIT data on multiplex of channel 5
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.485470 I EITCache: Pruning all entries that ended before UTC 2022-01-01T11:27:29Z
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.553194 I EITCache: Deleting old cache entries from the database
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.645143 I Scheduled 198 items in 0.1 = 0.01 match + 0.00 check + 0.05 place
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.650510 I EITScanner[2]: Stopped passive scan.
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.736828 I TVRec[2]: TuningFrequency
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.774904 I CardUtil[2]: Set delivery system: DVB-C/A
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.777599 D DTVChan[2](/dev/dvb/adapter1/frontend0): SetChannelByString(5): Initialize multiplex options m_tunerType:1 mplexid:13
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830877 D SignalMonitorValue(Signal Lock, slock, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830884 D SignalMonitorValue(Signal Power, signal, 0, 0, 0, 100, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830889 D SignalMonitorValue(Script Status, script, 0, 3, 0, 3, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830895 D SignalMonitorValue(Seen PAT, seen_pat, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830899 D SignalMonitorValue(Seen PMT, seen_pmt, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830902 D SignalMonitorValue(Seen MGT, seen_mgt, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830906 D SignalMonitorValue(Seen VCT, seen_vct, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830909 D SignalMonitorValue(Seen NIT, seen_nit, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830911 D SignalMonitorValue(Seen SDT, seen_sdt, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830915 D SignalMonitorValue(Seen Crypt, seen_crypt, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830919 D SignalMonitorValue(Matching PAT, matching_pat, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830923 D SignalMonitorValue(Matching PMT, matching_pmt, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830926 D SignalMonitorValue(Matching MGT, matching_mgt, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830929 D SignalMonitorValue(Matching VCT, matching_vct, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830933 D SignalMonitorValue(Matching NIT, matching_nit, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830935 D SignalMonitorValue(Matching SDT, matching_sdt, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830939 D SignalMonitorValue(Matching Crypt, matching_crypt, 0, 1, 0, 1, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830944 D SignalMonitorValue(Signal To Noise, snr, 0, 0, 0, 65535, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830948 D SignalMonitorValue(Bit Error Rate, ber, 0, 65535, 0, 65535, 0, 0, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830952 D SignalMonitorValue(Uncorrected Blocks, ucb, 0, 65535, 0, 65535, 0, 0, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.830955 D SignalMonitorValue(Rotor Progress, pos, 0, 100, 0, 100, 0, 1, false)
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.831236 D Setting 'Lossless transcoding' changed to 0
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.831243 D Setting 'Resize video while transcoding' changed to 0
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.831247 D Setting 'Enable auto-transcode after recording' changed to 0
Jan 02 12:22:27 hostname mythbackend[1310]: 2022-01-02 12:22:27.831958 D Setting 'Enable auto-transcode after recording' changed to 0
Jan 02 12:22:28 hostname mythbackend[1310]: 2022-01-02 12:22:28.290493 I EITScanner[2]: Started passive scan.
Jan 02 12:22:28 hostname mythbackend[1310]: 2022-01-02 12:22:28.682839 E MPEGStream[3](0x7f8e50079368): Error: AFCOffset(4)+StartOfFieldPointer(182)>184, pes length & current cannot be queried
Jan 02 12:22:28 hostname mythbackend[1310]: 2022-01-02 12:22:28.733074 E MPEGStream[3](0x7f8e50079368): Error: AFCOffset(4)+StartOfFieldPointer(181)>184, pes length & current cannot be queried
Jan 02 12:22:28 hostname mythbackend[1310]: 2022-01-02 12:22:28.883669 E MPEGStream[3](0x7f8e50079368): Error: AFCOffset(4)+StartOfFieldPointer(182)>184, pes length & current cannot be queried
Jan 02 12:22:29 hostname mythbackend[1310]: 2022-01-02 12:22:29.034206 E MPEGStream[3](0x7f8e50079368): Error: AFCOffset(4)+StartOfFieldPointer(181)>184, pes length & current cannot be queried
Jan 02 12:22:29 hostname mythbackend[1310]: 2022-01-02 12:22:29.939884 D Running HouseKeeper.
Jan 02 12:22:29 hostname mythbackend[1310]: 2022-01-02 12:22:29.939892 D Checking to run DBCleanup
Jan 02 12:22:29 hostname mythbackend[1310]: 2022-01-02 12:22:29.939897 D Checking to run HardwareProfiler
Jan 02 12:22:29 hostname mythbackend[1310]: 2022-01-02 12:22:29.939909 D Checking to run JobQueueRecover
Jan 02 12:22:29 hostname mythbackend[1310]: 2022-01-02 12:22:29.939911 D Checking to run LogClean
Jan 02 12:22:29 hostname mythbackend[1310]: 2022-01-02 12:22:29.939913 D Checking to run MythFillDB
Jan 02 12:22:29 hostname mythbackend[1310]: 2022-01-02 12:22:29.939919 D MythFillDatabase is disabled. Cannot run.
Jan 02 12:22:29 hostname mythbackend[1310]: 2022-01-02 12:22:29.939922 D Checking to run RecordedArtworkUpdate
Jan 02 12:22:29 hostname mythbackend[1310]: 2022-01-02 12:22:29.939926 D Checking to run ThemeUpdateNotifications
Jan 02 12:22:30 hostname mythbackend[1310]: 2022-01-02 12:22:30.188307 E MPEGStream[3](0x7f8e50079368): Error: AFCOffset(4)+StartOfFieldPointer(181)>184, pes length & current cannot be queried
Jan 02 12:22:30 hostname mythbackend[1310]: 2022-01-02 12:22:30.389145 E MPEGStream[3](0x7f8e50079368): Error: AFCOffset(4)+StartOfFieldPointer(181)>184, pes length & current cannot be queried
Jan 02 12:22:31 hostname mythbackend[1310]: 2022-01-02 12:22:31.192008 E MPEGStream[3](0x7f8e50079368): Error: AFCOffset(4)+StartOfFieldPointer(182)>184, pes length & current cannot be queried
Jan 02 12:22:31 hostname mythbackend[1310]: 2022-01-02 12:22:31.342548 E MPEGStream[3](0x7f8e50079368): Error: AFCOffset(4)+StartOfFieldPointer(181)>184, pes length & current cannot be queried
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Missing EPG on a number of channels [ In reply to ]
See comments below.

On Sun, 2 Jan 2022 at 13:50, Robert <2201mythtvml@rainbow.in-berlin.de>
wrote:

> Dear MythTV users,
>
> I'm missing EPG for a number of channels.
> The problem started mid December when several channels announced that they
> were changing their place and that viewers should rescan.
> I rescanned several times, but this did not fix the issue.
> Strangely, MythWeb showed a channel that I had deleted in mythtv-setup.
>

This can happen if you have an old version of MythWeb. Nowadays when a
channel is deleted it is not immediately removed from the database but it
is marked for deletion later. This is fixed in the latest version of
MythWeb.
I recommend using mythtv-setup for all configuration activities.

So I gave up, deleted all channels, video sources and capture cards and
> created them anew.
>

This is a good action.


>
> First, only 39 channels appeared in the scan. Only after turning off
> "Logical Channel Numbers required" I got 86 more of the usual channels.
>
This option is described in the Wiki on page
https://www.mythtv.org/wiki/Channel_Scanning#Logical_Channel_Numbers_required
.


> But then again, a number of channel don't get EPG. I checked the channel
> settings, and strangly these were added with "Use 'Over-the-Air' programme
> listings" off.


This should not have happened. Check, just to be sure, the settings of your
capture cards and of the video source to make sure that EIT is enabled.
See the Wiki in pages
https://www.mythtv.org/wiki/Channel_Scanning#Use_DVB_card_for_active_EIT_scan
and https://www.mythtv.org/wiki/Channel_Scanning#Listings_grabber.
Maybe do "Delete all channels" in the Channel Editor of mythtv-setup and
scan again.


> I turned the setting on for the channels but this did not help.
> What the channels lacking EPG have in common is the same two mplexid
> values.
> I turned debugging on for eit, but all I can see is that it seems to scan
> the two mplexids.
> So, I wonder whether it's the data that is missing or the software that
> has problems with the data on the two mplexes.
> How to find out?
>
Check that an ordinary TV shows the EPG guide data. If a TV can do it then
MythTV should also be able to get the EPG guide data.
What sometimes happens is that guide data is sent encrypted over a data
channel and not according to DVB standards.
In that case the guide data is only available when using a
provider-supplied set-top-box. It could just be that your provider is
moving in this direction.


> I have a quadHD card connected to some kind of DVB-C that comes via FTTH
> (fiber), in Germany.
> I'm running MythTV 1:31.0+fixes20211113.git25f1bb1d12-dmo0+deb11u1 on
> Debian 11 (upgraded from 10 a few days ago but that did not fix the EPG
> problem).
> (/etc/apt/sources.list: deb http://ftp.uni-kl.de/debian-multimedia/
> bullseye main)
>
> Thanks,
> Robert
>
> Jan 02 12:22:25 hostname mythbackend[1310]: 2022-01-02 12:22:25.320880 E
> MPEGStream[3](0x7f8e50079368): Error:
> AFCOffset(4)+StartOfFieldPointer(182)>184, pes length & current cannot be
> queried
>
These messages should not be there on a regular basis. Does this really
happen with the latest mythtv v31-fixes?
It is possible that there is room for improvement in the way MythTV does
parse the streams.

Klaas.
Re: Missing EPG on a number of channels [ In reply to ]
>
>
>
>> But then again, a number of channel don't get EPG. I checked the channel
>> settings, and strangly these were added with "Use 'Over-the-Air' programme
>> listings" off.
>
>
>> The most simple explanation is that these channels are flagged with a bit
that says that there is no EPG guide data present for these channels.
This does not mean that the EPG guide data is not present; the bit could be
wrong.
You can check this by enabling the "Use 'Over-the-Air' programme listings"
for *all channels* on those two multiplexes.

Klaas.
Re: Missing EPG on a number of channels [ In reply to ]
On 22-01-02 18:42:04 CET, Klaas de Waal wrote:
> So I gave up, deleted all channels, video sources and capture cards and
> > created them anew.
> >
>
> This is a good action.
>
>
> >
> > First, only 39 channels appeared in the scan. Only after turning off
> > "Logical Channel Numbers required" I got 86 more of the usual channels.
> >
> This option is described in the Wiki on page
> https://www.mythtv.org/wiki/Channel_Scanning#Logical_Channel_Numbers_required
> .

This longer explanation makes it clear what it's about. The shorter
explation in mythtv-setup mislead me to believe that only service
channels for firmware downloads and such would be omitted.

> > But then again, a number of channel don't get EPG. I checked the channel
> > settings, and strangly these were added with "Use 'Over-the-Air' programme
> > listings" off.
>
>
> This should not have happened. Check, just to be sure, the settings of your
> capture cards and of the video source to make sure that EIT is enabled.
> See the Wiki in pages
> https://www.mythtv.org/wiki/Channel_Scanning#Use_DVB_card_for_active_EIT_scan
> and https://www.mythtv.org/wiki/Channel_Scanning#Listings_grabber.

I had EIT enabled on all four. After reading there that it should be
enabled on one card only, I disabled it on three. I don't notice any
difference in behaviour, though, regarding getting EPG into the database.

> Maybe do "Delete all channels" in the Channel Editor of mythtv-setup and
> scan again.

I don't want to do this again. After deleting all channels, all
recordings lose their channel information. :-(
It was quite a bit of work to add additional channels in mythtv-setup
and patch their chanids in the database to the old recordings' chanids.

[missing EPG on some channels]
> Check that an ordinary TV shows the EPG guide data. If a TV can do it then
> MythTV should also be able to get the EPG guide data.

Good hint. I checked with a neighbour who's got a TV set: it doesn't
show EPG for the same channels where mythtv doesn't show EPG.
I mailed the provider, let's see what they say about it.

> > I have a quadHD card connected to some kind of DVB-C that comes via FTTH
> > (fiber), in Germany.
> > I'm running MythTV 1:31.0+fixes20211113.git25f1bb1d12-dmo0+deb11u1 on
> > Debian 11 (upgraded from 10 a few days ago but that did not fix the EPG
> > problem).
> > (/etc/apt/sources.list: deb http://ftp.uni-kl.de/debian-multimedia/
> > bullseye main)
> >
> > Thanks,
> > Robert
> >
> > Jan 02 12:22:25 hostname mythbackend[1310]: 2022-01-02 12:22:25.320880 E
> > MPEGStream[3](0x7f8e50079368): Error:
> > AFCOffset(4)+StartOfFieldPointer(182)>184, pes length & current cannot be
> > queried
> >
> These messages should not be there on a regular basis. Does this really
> happen with the latest mythtv v31-fixes?
> It is possible that there is room for improvement in the way MythTV does
> parse the streams.

It's the latest from the debian-multimedia repository. The version
number seems to indicate it's from 2021-11-13. (I never built the
package myself.)
I downloaded the source (`apt-get source mythtv-backend`). The ChangeLog
in there has these top lines:

commit 25f1bb1d12fdee5b9ea3841fd39332db9431e4a2
Author: Klaas de Waal <kdewaal@mythtv.org>
Date: Wed Nov 3 21:18:47 2021 +0100

Thanks,
Robert
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Missing EPG on a number of channels [ In reply to ]
On 22-01-02 20:22:39 CET, Klaas de Waal wrote:
> >
> >
> >
> >> But then again, a number of channel don't get EPG. I checked the channel
> >> settings, and strangly these were added with "Use 'Over-the-Air' programme
> >> listings" off.
> >
> >
> >> The most simple explanation is that these channels are flagged with a bit
> that says that there is no EPG guide data present for these channels.
> This does not mean that the EPG guide data is not present; the bit could be
> wrong.
> You can check this by enabling the "Use 'Over-the-Air' programme listings"
> for *all channels* on those two multiplexes.

It is enabled for almost all channels, even those I've set to not
visible.
But how is this supposed to help?

Robert
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Missing EPG on a number of channels [ In reply to ]
>
>
> > Maybe do "Delete all channels" in the Channel Editor of mythtv-setup and
> > scan again.
>
> I don't want to do this again. After deleting all channels, all
> recordings lose their channel information. :-(
> It was quite a bit of work to add additional channels in mythtv-setup
> and patch their chanids in the database to the old recordings' chanids.
>
> Yes, that is definitely a lot of work.... The good news is that with the
latest v31 that you are using and with the new v32 there should be no need
to modify chanid values manually. I have updated the description in the
Wiki https://www.mythtv.org/wiki/Channel_Scanning#Delete to clarify what
happens when channels are deleted.


> [missing EPG on some channels]
> > Check that an ordinary TV shows the EPG guide data. If a TV can do it
> then
> > MythTV should also be able to get the EPG guide data.
>
> Good hint. I checked with a neighbour who's got a TV set: it doesn't
> show EPG for the same channels where mythtv doesn't show EPG.
> I mailed the provider, let's see what they say about it.
>
> This makes it almost 100% sure that it is a problem in the signal and not
a problem in MythTV.
A possible alternative is Schedules Direct that according to the website
https://www.schedulesdirect.org/regions does have schedule information for
Germany. I have never used it myself but it is supported in MythTV and many
people in the USA use it.


> > >
> > > Jan 02 12:22:25 hostname mythbackend[1310]: 2022-01-02 12:22:25.320880
> E
> > > MPEGStream[3](0x7f8e50079368): Error:
> > > AFCOffset(4)+StartOfFieldPointer(182)>184, pes length & current cannot
> be
> > > queried
> > >
> > These messages should not be there on a regular basis. Does this really
> > happen with the latest mythtv v31-fixes?
> > It is possible that there is room for improvement in the way MythTV does
> > parse the streams.
>

I think I fixed this only in master and not in v31. It is a minor bug that
has been there for years and it does not really give problems.
If you observe this in the new version 32, to be released soon, then please
report again or create a ticket on Github.

Thanks,
Klaas.
Re: Missing EPG on a number of channels [ In reply to ]
On 23-01-27 23:35:48 CET, Klaas de Waal wrote:
> On Fri, 27 Jan 2023 at 20:23, Robert <2201mythtvml@rainbow.in-berlin.de>
> wrote:
>
> > Dear MythTV users,
> >
> > I'm missing EPG for a number of channels. Unlike one year ago, this time
> > it is not on the provider's side: two neighbours have the EPG on the
> > channels (on their normal TV sets) where I haven't got it in MythTV.
> > I did a full rescan, but this did not fix the problem.
> > The affected channels share a small number of mplexid values in the
> > database, one these multiplexes no channel seems to have EPG.
> > useonairguide is 1 for all of them.
> >
> > What can be the reason for the missing EPG on just a few multiplexes?
> > Why doesn't a rescan fix this?
> > How can I get the EPG back? Delete the affected channels and do a rescan?
> >
> > I have a quadHD card connected to some kind of DVB-C that comes via FTTH
> > (fiber), in Germany.
> > I'm running version 1:31.0+fixes20220227.git7e4ce1ba98-dmo0+deb11u1 from
> > http://ftp.uni-kl.de/debian-multimedia/.
> >
> > Setting the verbose to eit and loglevel to debug did not give me any
> > clue. mplexid is one of the ones lacking EPG data.
[...]
>
> Sometimes there is guide information sent as private data which can only be
> used by set-top-boxes from the provider.
> MythTV can only use guide data that is coded according to the DVB standards.
> However, if a standard TV without a set-top-box can show the guide then I
> expect that MythTV should also be able to do that also.
>
> I suggest first upgrading to the latest fixes/32.

Last weekend, without upgrading, I deleted all channels and rescanned.
This brought back EPG in some of the channels. Weirdly, both Mythweb and
the backend's own Web interface seemed confused. For certain channels,
Mythweb did not show its program, but it showed upcoming recordings!
I wondered whether all this was due to the old version, so this weekend,
I switched to deb-multimedia.org's bullseye-backports. It provides a
version 1:32.0+fixes20230124.gitf2ce7e33aa-dmo0~bpo11+1.

> Then with mythtv-setup do the following
> - delete all channels
> - do a full scan with the following log options "-v
> channel,chanscan,eit,siparser --loglevel=debug"
> - capture all output of the full scan, e.g. with "mythtv-setup -v
> channel,chanscan,eit,siparser --loglevel=debug 2>&1 | tee
> this_is_my_logfile.log"

I did this, but this time I deselected "Remove duplicates". My source is
supposed to be DVB-S received by the Internet provider who feeds it to
us via fiber to the home.
I chose to insert the channels manually. This meant having to enter all
the channels' numbers again, quite a bit of work. Interestingly, many
channels appeared twice or more, even though it's supposed to be
not DVB-T2.

Again, EPG is missing on some channels, at least at their first
appearance which I gave the old number.
But - EPG is present on another channel with the same name which I gave
a higher number.
One example, I hope the query makes sense:

MariaDB [mythconverg]> select chanid, visible, useonairguide, deleted, count(*) as eit_count, from_unixtime(max(endtime)) as maxend from channel left join eit_cache using (chanid) where name='ONE HD' group by chanid order by maxend;
+--------+---------+---------------+---------------------+-----------+---------------------+
| chanid | visible | useonairguide | deleted | eit_count | maxend |
+--------+---------+---------------+---------------------+-----------+---------------------+
| 10005 | 1 | 1 | 2023-01-29 17:14:37 | 1 | NULL |
| 16376 | -1 | 0 | NULL | 1 | NULL |
| 60005 | -1 | 0 | NULL | 1 | NULL |
| 501429 | 1 | 1 | NULL | 1 | NULL |
| 20354 | 1 | 1 | 2023-02-05 10:21:04 | 681 | 2023-03-01 02:05:00 |
| 10405 | 1 | 1 | NULL | 796 | 2023-03-05 01:10:00 |
+--------+---------+---------------+---------------------+-----------+---------------------+

If I understand this correctly, I've got two visible non-deleted
channels, one with EIT data (10405), the other without (501429).

Another example:

MariaDB [mythconverg]> select chanid, visible, useonairguide, deleted, count(*) as eit_count, from_unixtime(max(endtime)) as maxend from channel left join eit_cache using (chanid) where name='TLC' group by chanid order by maxend;
+--------+---------+---------------+---------------------+-----------+---------------------+
| chanid | visible | useonairguide | deleted | eit_count | maxend |
+--------+---------+---------------+---------------------+-----------+---------------------+
| 10148 | 1 | 1 | 2023-01-29 17:14:37 | 1 | NULL |
| 20397 | 1 | 1 | 2023-02-05 10:21:04 | 1 | NULL |
| 501425 | 1 | 1 | NULL | 1 | NULL |
| 10548 | 1 | 1 | NULL | 128 | 2023-02-09 01:05:00 |
+--------+---------+---------------+---------------------+-----------+---------------------+

Is this normal to have multiple channel records for the same channel?

> Please create a ticket for this issue on
> https://github.com/MythTV/mythtv/issues and then attach the log file to
> that ticket.

I'm not sure what issue to report.
Should I get rid of the extra non-deleted channels first? How?

> Then when you run mythbackend use the following log options: "-v
> channel,eit,siparser --loglevel=debug", capture the output for a few days
> and post that also.
> This will also be a fairly big file.

It is currently running that way, in case it's needed.

Thanks,
Robert
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org