Having issue with Automatic EPG updates on 3.1.1

[liteswap]

Cheers!

[sub]

Sub, my system reproduced the problem this morning (as I disabled restart of recording service). I used processexplorer to grab the threadlist and stacks for the 2 threads that were burning cpu cycles. Log included as well.

I took a look through this, unfortunately it doesn't seem to offer any useful clues.

Those threads are just standard directshow filters showing the graph is running and processing data. No real clues why though.

[sub]

I've had a good attempt at reproducing this again today, but I'm still unable to, even after moving my machine time forward etc, to force it to do multiple EPG updates.

I've attached an patch with more logging in the problem area. Can you guys please install it, then post the nrecord.log/ndigitalhost logs when the problem happens? Hopefully this new logging will lead me to the cause.

[liteswap]

New dll loaded - but it resulted in a 'failed to find capture device' error and a couple of failed recordings (grr!). Had to revert to standard version 3.1.1, and it now records OK - I'll report on the EPG issue if anything changes.

[jhr1948]

Hi sub,
I'm the OP and haven't had any info for a while. Not sure if this helps, all I did was change my 2 problem channels from grabbing atsc guide info to "none". Those 2 channels never had guide info and are very low powered anyways. Could it be somewhat related to that?

[sub]

Hi sub,
I'm the OP and haven't had any info for a while. Not sure if this helps, all I did was change my 2 problem channels from grabbing atsc guide info to "none". Those 2 channels never had guide info and are very low powered anyways. Could it be somewhat related to that?

Yeah, we know it's definitely related to the DVB EPG, but most people need that functionality so setting it to 'none' isn't going to help them.

[sub]

New dll loaded - but it resulted in a 'failed to find capture device' error and a couple of failed recordings (grr!). Had to revert to standard version 3.1.1, and it now records OK - I'll report on the EPG issue if anything changes.

It shouldn't have made any difference to this. All I added was a couple of lines of logging. Reproduce the problem, then zip and attach the logs and I'll check it out.

[mvallevand]

Yeah, we know it's definitely related to the DVB EPG, but most people need that functionality so setting it to 'none' isn't going to help them.

Actually for QAM it would be really nice.

Martin

[sub]

Actually for QAM it would be really nice.

They generally don't transmit EPG information on QAM systems, so it's not possible NextPVR to get.

On these digital cable systems it's carried in a special out-of-band frequency, which NextPVR can't see.

[mvallevand]

Yes that is why I figured None should be the default.

Martin