Corrupt EPG after addition of Freeview HD (1 Viewer)

[Branksome]

If you could try it with EPG grabbing from both Freesat and Freeview (i.e. your original configuration) that would be really useful Tony

I will turn on the epg grabbing from the T2 card this evening and report back

Tom

 

[Branksome]

Oh dear. I have just turned the computer on and found the names of the 2 BBC hd chnnels in the epg corrupted. The rest of the epg seems OK. I had forgotten that yesterday I had turned grabbing on for the T2 card but by the end of the evening (the HTPC went to bed later than me) no data has appeared for any Freeview only channels. I believe that this is because I would need to select at least 1 freeview channel alongside freesat and radio caroline. I was going to do that this evening but have not yet done that

I attach a screen grab and will upload some logs.

To aid interpretation of the logs, I made the following notes for 2 Apr -

TV Service stopped at 12:35 (to install fix)
TV Service restarted at 12:42
Refreshed epg (satellite only) start at 12:43 and finished at 12:50. Machine was then left on all day until the early hours.

I did make available the T2 card for epg grabbing possibly early evening but it appeared that no data collected

 

[elliottmc]

Perhaps someone else can confirm, but I would not expect the channel names to be changed during an EPG grab.

For me, this is working fine (DVB-T/DVB-T2 only).

Perhaps it is trying to decode the channel name when it isn't actually encoded.

For the DVB-T2 card, have you selected channels to grab EPG for? This seems to be necessary.

Mark

 

[Branksome]

A couple of additional log files which could be significant

 

[elliottmc]

A couple of additional log files which could be significant

The persistent error is

2012-04-02 23:00:48.146712 [scheduler thread(18)]: Exception  :System.ArgumentException: Illegal characters in path.
  at System.IO.Path.CheckInvalidPathChars(String path)
  at System.IO.Path.ChangeExtension(String path, String extension)
  at TvService.Recorder.Start(IUser& user, String& fileName, Boolean contentRecording, Int64 startTime)

What is your recording path? It seems as though there is a naming issue here. There are so many instances of this error that it would be hard to spot anything else.

If you use the MediaPortal debug mode to collect the logs, it will include the files that will give us that information. Please could you try this. Otherwise we are just guessing.

Edit: if the channel name is included in the path, and the channel name is corrupted, then maybe this would explain the error.

 

[elliottmc]

The TV log has

2012-04-02 23:01:20.555566 [scheduler thread(18)]: Scheduler : record to C:\Users\Public\Recorded TV\Modern Spies - ¹ÿ - 2012-04-02.ts

and

2012-04-02 23:01:20.325553 [scheduler thread(18)]: Scheduler : record to \\LS-CHL-V2084\share\Stream\Modern Spies - ¹ÿ - 2012-04-02.ts

Where the corrupt bit is indeed the channel name.

I assume that you have different recording folders for the different cards.

Did the channel name only get corrupted after you turned on grabbing from the DVB-T2 card?

Ideally we need the log where this got corrupted. As far as I know, channel names are never encoded, so it should not need decoding. Perhaps they are encoded on freest but not on free view HD.

Mark

 

[elliottmc]

IF we look at the error,

2012-04-02 23:00:11.600622 [scheduler thread(18)]: Exception   :System.ArgumentException: Illegal characters in path.
   at System.IO.Path.CheckInvalidPathChars(String path)
   at System.IO.Path.ChangeExtension(String path, String extension)
   at TvService.Recorder.Start(IUser& user, String& fileName, Boolean contentRecording, Int64 startTime)

but at 22.00

02-04-2012 22:04:06.467 Recorder: RECORD    Stop '\\LS-CHL-V2084\share\Stream\Metal_ How It Works - BBC HD - 2012-04-02.ts'
02-04-2012 22:04:06.610 Recorder: RECORD    Reset
02-04-2012 22:04:06.613 CDiskRecorder::Reset() - Reset write buffer throttle

so whatever went wrong happened between 22.00 and 23.00.

Mark

 

[Owlsroost]

There is no evidence from the epg.log/epg.bak that the DVB-T2 card is being used for EPG grabbing - it's always grabbing from the two Freesat channels.

Branksome - do you have the 'EPG grabbing while timeshifting/recording' option enabled in TVServer config -> DVB EPG section ?

Tony

 

[elliottmc]

According to the logs, the BBC1 HD name is corrupted on DVBS but fine on DVBT.

Tony - should channel names ever be updated during EPG grabbing? If so, perhaps we can add specific logging when this happens.

 

[elliottmc]

This looks interesting, from tv.log

2012-04-02 21:52:57.015857 [(30)]: OnLinkageReceived()
2012-04-02 21:52:57.039858 [Channel linkage update thread(29)]: ChannelLinkage received. 8 portal channels read
2012-04-02 21:52:57.041858 [Channel linkage update thread(29)]: [Linkage Scanner] New portal channel 9018 4163 4163
2012-04-02 21:52:57.043858 [Channel linkage update thread(29)]: [Linkage Scanner] - èÿ nid=9018,tid=16514 sid=17540
2012-04-02 21:52:57.045858 [Channel linkage update thread(29)]: [Linkage Scanner] - èÿ nid=9018,tid=16515 sid=17540
2012-04-02 21:52:57.046859 [Channel linkage update thread(29)]: [Linkage Scanner] - èÿ nid=9018,tid=16516 sid=17540
2012-04-02 21:52:57.048859 [Channel linkage update thread(29)]: [Linkage Scanner] - èÿ nid=9018,tid=16517 sid=17540
2012-04-02 21:52:57.049859 [Channel linkage update thread(29)]: [Linkage Scanner] - èÿ nid=9018,tid=16520 sid=17540
2012-04-02 21:52:57.050859 [Channel linkage update thread(29)]: [Linkage Scanner] - èÿ nid=9018,tid=16521 sid=17540
2012-04-02 21:52:57.052859 [Channel linkage update thread(29)]: [Linkage Scanner] - èÿ nid=9018,tid=16526 sid=17540
2012-04-02 21:52:57.053859 [Channel linkage update thread(29)]: [Linkage Scanner] - èÿ nid=9018,tid=16572 sid=17596
2012-04-02 21:52:57.055859 [Channel linkage update thread(29)]: [Linkage Scanner] - èÿ nid=9018,tid=16573 sid=17597
2012-04-02 21:52:57.056859 [Channel linkage update thread(29)]: [Linkage Scanner] - èÿ nid=9018,tid=16574 sid=17598
2012-04-02 21:52:57.080860 [Channel linkage update thread(29)]: Linked channel with name=èÿ, networkId=9018, transportId=16514, serviceId=17540 not found
2012-04-02 21:52:57.133864 [Channel linkage update thread(29)]: Linked channel with name=èÿ, networkId=9018, transportId=16516, serviceId=17540 not found
2012-04-02 21:52:57.135864 [Channel linkage update thread(29)]: Linked channel with name=èÿ, networkId=9018, transportId=16517, serviceId=17540 not found
2012-04-02 21:52:57.138864 [Channel linkage update thread(29)]: Linked channel with name=èÿ, networkId=9018, transportId=16520, serviceId=17540 not found
2012-04-02 21:52:57.140864 [Channel linkage update thread(29)]: Linked channel with name=èÿ, networkId=9018, transportId=16521, serviceId=17540 not found
2012-04-02 21:52:57.143864 [Channel linkage update thread(29)]: Linked channel with name=èÿ, networkId=9018, transportId=16526, serviceId=17540 not found
2012-04-02 21:52:57.146864 [Channel linkage update thread(29)]: Linked channel with name=èÿ, networkId=9018, transportId=16572, serviceId=17596 not found
2012-04-02 21:52:57.149864 [Channel linkage update thread(29)]: Linked channel with name=èÿ, networkId=9018, transportId=16573, serviceId=17597 not found
2012-04-02 21:52:57.151865 [Channel linkage update thread(29)]: Linked channel with name=èÿ, networkId=9018, transportId=16574, serviceId=17598 not found

It seems that this is specifically because the channels are linked, or would it have changed the channel name for DVBS anyway?

Where is the channel linkage code? Presumably in TsWriter.ax, since TsWriter.log has

02-04-2012 21:52:57.12 ChannelLinkageScanner: do callback
02-04-2012 21:52:57.33 ChannelLinkageScanner: reset

and also in tv.log there is

2012-04-03 16:37:53.017046 [(27)]: OnLinkageReceived()
2012-04-03 16:37:53.028047 [Channel linkage update thread(15)]: ChannelLinkage received. 2 portal channels read
2012-04-03 16:37:53.031047 [Channel linkage update thread(15)]: [Linkage Scanner] New portal channel 2 4752 2026
2012-04-03 16:37:53.033047 [Channel linkage update thread(15)]: [Linkage Scanner] -  šOTV1 nid=2,tid=2004 sid=8021
2012-04-03 16:37:53.037047 [Channel linkage update thread(15)]: Portal channel with networkId=2, transportId=2026, serviceId=4752 not found
2012-04-03 16:37:53.040047 [Channel linkage update thread(15)]: [Linkage Scanner] New portal channel 2 5505 2026
2012-04-03 16:37:53.046048 [Channel linkage update thread(15)]: [Linkage Scanner] -  šOTV1 nid=2,tid=2004 sid=8021
2012-04-03 16:37:53.052048 [Channel linkage update thread(15)]: Portal channel with networkId=2, transportId=2026, serviceId=5505 not found

with networkID = 2, which doesn't correspond to freesat or freeviewHD.