Having some issues with 2.6.2

[Bluethunder]

Is there any further logging we can turn on to catch where NRecord getting hung up?

It's set to debug level in the config file right now.

[johnsonx42]

the recording session you did was all back-to-back recordings, so there was only a single graph start; it just kept switching the same graph to a new recording file. Try doing several recordings with some time between them; that should make it crash.

[Bluethunder]

the recording session you did was all back-to-back recordings, so there was only a single graph start; it just kept switching the same graph to a new recording file. Try doing several recordings with some time between them; that should make it crash.

Ahh, I didn't realize that.

I just set up a recording (last minutes of a program), waited a couple minutes, then started another.

It piled up, like you predicted.

I haven't rolled back to 2.5.5 yet, just because I would like to see this get fixed.

Thanks for the response. Cheers, Joe

[johnsonx42]

Yep, hung the second time it tried to start a recording graph as it did with your live tv logs. As per your original post you have installed the latest Colossus driver (the 30151 driver here: http://www.hauppauge.com/site/support/su...ossus.html, yes?), I'm not sure what else I can suggest.

If you're willing to remove and re-install some more, you could go back to 2.5.5 and verify this problem doesn't happen with that version, then install the 2.5.5 R1 update (attached) and check again, then go to 2.5.9, then through the 2.5.9 R1, R2 (both attached), and Post-R2 Rollup 2 (http://forums.gbpvr.com/attachment.php?a...1362447762). If you can determine exactly when it breaks it may help.

Or sub could jump in and say "don't bother, I see where the problem is".

[sub]

Or sub could jump in and say "don't bother, I see where the problem is".

I'm afraid not. About an hour go I dug out a Colossus and installed it in my machine, and scheduled a few recordings, with gaps between each, and they've been successfully stopping and starting.

[johnsonx42]

any possibility it's due to some change you made between 2.5.5 and now that works fine on Win 7 & 8, but breaks it on XP?

will the suggestion I made to go back to 2.5.5 where it works, then iterate forward through the versions and patches until it breaks, be at all helpful to you?

[sub]

any possibility it's due to some change you made between 2.5.5 and now that works fine on Win 7 & 8, but breaks it on XP?

Maybe, but there wasn't any changes in the Colossus stuff that I could see that would possibly cause this.

will the suggestion I made to go back to 2.5.5 where it works, then iterate forward through the versions and patches until it breaks, be at all helpful to you?

Hopefully.

[Bluethunder]

I'm willing to give it a go.

I know that 2.5.5 R1 works, so I will start there. I'm going to image this machine, in the current state since other than the nrecord lock up, it seems to be working well.

I know 2.5.9 (base) is where it broke before, but I don't have any logs of it doing it.

[johnsonx42]

Logs of it working with 2.5.5 R1 and failing with 2.5.9 would be interesting to see. Very little changed between the two.

[mvallevand]

There definitely were some core hdpvr changes in Sept. http://forums.nextpvr.com/showthread.php...h&p=441916 you might want to play with those settings among other things.

Martin