Config crashes during digital mapping

[rapepperuk]

Hi same crash for me - Upgrade 1.2.13 over 1.2.9.

I scanned several times in 1.2.9 as I am trying to find out why a channel that WinTV (I have Nova-T500) finds (E4) is not found by GBPVR. (It's strange because E4+1 is found but not E4.)

Since the upgade to 1.2.13 the scan gets to 5 out of 6 channels them crashes.

RAP

[steeb]

Me too,

upgraded to v 1.2.13. and scan fails/crashes with both FireDTV and Nova S cards. Works fine if scanned first with v 1.2.9 then an install of 1.2.13 but given that Freesat is playing around a bit at the moment a frequent rescan seems good policy. Therefore have rolled back to 1.2.9 and am sticking with it for now. I have not managed to get More4 or E4 yet but works/scans and plays with the native viewers for both my cards.

Steeb

[sub]

My jet-lagged mind isnt able to look at this now, but bump me in a couple of days and I'll work out what is happening.

[steeb]

18 Hours not 2 days

Bump

Steeb

[sub]

It is most likely caused by something in the stream that GB-PVR's PSI Parser isnt expecting and doesnt like.

To look into it, someone will need to decide which frequency is causing them a problem, then try to get a 50MB or so full transport stream recording for that frequency, and make that file available for me to download. I can then run that test data through in the debugger to see what it doesnt like.

You may need to make that recording in another app, like the Twinhan capture tool, DVBDream, DVBStreamExplorer, TSReader pro etc...

[crlorentzen]

It is most likely caused by something in the stream that GB-PVR's PSI Parser isnt expecting and doesnt like.

To look into it, someone will need to decide which frequency is causing them a problem, then try to get a 50MB or so full transport stream recording for that frequency, and make that file available for me to download. I can then run that test data through in the debugger to see what it doesnt like.

You may need to make that recording in another app, like the Twinhan capture tool, DVBDream, DVBStreamExplorer, TSReader pro etc...

sub, as it takes a long time to complete/fail Digital Channel Mapping, I usually walk away while my computer works on it. Can you guide us on using the config.exe.log or the config.exe-native.log to figure out what channel it failed on?

Should we look for the last SubmitTuningRequest(T:x,y,z) in config.exe-native.log?

Then we need to use one of the tools above to capture on that channel for about 50MB?

Finally we need to upload this somewhere so that you can download and feed it through a debug on the PSI dec? I just hope that the time spent recording will produce data that would crash the Digital Mapping.

Please let me know if this is accurate. I just hope that I can get a tool to do QAM recording as most of those tools are for DVB (not U.S. Digital Broadcast).

[sub]

Should we look for the last SubmitTuningRequest(T:x,y,z) in config.exe-native.log?

Yes, that would do it.

Then we need to use one of the tools above to capture on that channel for about 50MB?

Yes

Finally we need to upload this somewhere so that you can download and feed it through a debug on the PSI dec?

Yes again.

I just hope that the time spent recording will produce data that would crash the Digital Mapping.

Yes. Based on past experience of these types of issues, there is no other way to determine what the problem is.

[crlorentzen]

Give me a few days and I will see about producing some data.

[steeb]

Can I just check here as aren't we talking 2 different things? Or are they a combination? Some stop with v 1.2.13 on scan, some just not getting certain channels?

[sub]

I was primarily wanting to look at the config app crashes that were occuring during the channel scan.

That said pretty much the same steps (user supplying a full transport file) would be required to work out why a channel is not found during a channel scan. As long as the users clearly identifies this in their posts then I can look at either.