Comcast switch to MPEG-4 - How to change config with least impact/hassle?

[sub]

Can you see if this patch helps? Remove both of those extra registry settings.

[HarryH3]

OK, the registry is back to normal. I renamed the old NPVRNetPushSource.ax file in the Prgoram Files (x86)/NPVR directory, put the new one there and then rebooted the system. Then I started a recording on channel 730, BBCAM, at 14:00. I'm able to select the recording, while it is in progress, and play or resume it. I can jump forward and backward with no problems. Comskip is processing the file now, but looks like it's going to take a while, so I'm updating with what I have this far.

However, if I try to have NPVR record more than one MPEG-4 channel, the recording service crashes and I get an error about the tuner being needed for another recording. This crash also leaves the HDHR Prime thinking that it is streaming to somehwere, as the tuner is still in use. But we're definitely making progress!

I noticed one oddity while checking to see if Comskip was running. NextPVR.exe has 9 instances of itself running. :eek:

Task manager process screenshot attached.
Logs attached.

[sub]

NextPVR.exe has 9 instances of itself running. :eek:

Task manager process screenshot attached.

Are you using webclient in XNEWA?

[sub]

OK, the registry is back to normal. I renamed the old NPVRNetPushSource.ax file in the Prgoram Files (x86)/NPVR directory, put the new one there and then rebooted the system. Then I started a recording on channel 730, BBCAM, at 14:00. I'm able to select the recording, while it is in progress, and play or resume it.

So, are you now getting audio and video with the new patch?

[HarryH3]

Are you using webclient in XNEWA?

No. Everything is running on the server, with an ATI HD5570 video card feeding the TV.

So, are you now getting audio and video with the new patch?

Yes! But so far it only appears to work for a single MPEG-4 stream. If I start a recording on another channel at the same time, the recording service crashes. You might be able to see that in the logs above, around the 13:46 mark. (I then rebooted, to clear everything up, before starting the recording at 14:00 (Or 13:58 with pre-padding).

[mvallevand]

Are you sure you removed those registry entries?

Martin

[sub]

You might be able to see that in the logs above, around the 13:46 mark.

Your logs don't go back as far as 13:46, since your restart the recording service a few times.

Can you reproduce the problem at will, or was it a one-off problem?

I can't see the patch being related to what you're describing.

[HarryH3]

Are you sure you removed those registry entries?

Martin

Yep. Double and triple checked.

[HarryH3]

Your logs don't go back as far as 13:46, since your restart the recording service a few times.

Can you reproduce the problem at will, or was it a one-off problem?

I can't see the patch being related to what you're describing.

The recording service was going berserk. It restarted 3 times in 3 minutes.

Check the logs here, if all the restarting didn't overwrite them. I started 1 MPEG-4 quick record, then an MPEG-2 quick record, then another MPEG-4 quick record. All in the 16:36-16:37 timeframe. Carnage ensues when the second MPEG-4 recording starts. All of the recordings are restarting every minute.

I'm also attaching the latest crash.mdmp

[mvallevand]

It looks like you have to

taskkill /im NRecord.exe /f

to see if that helps clear the older version running on port 8968. If not you will need to reboot.

Martin