Colossus issue with 3.3.8

[IanSpringfield]

FYI, my intent is to run npvr from a client rather on the server although all of the tests and results I have posted are with my eyes on the server screen and my fingertips on the server keyboard.

Obviously, when I do run the client, the same issue exists. However, I've tried xbmc as the client and to the best of my testing, the channel change issue does not exists. At least if it does, I haven't seen it in my multiple tests.

[IanSpringfield]

Were these logs from a single machine, or are you trying to do client/server?

All of the logs and tests and settings are on the server. I have learned if the server doesn't work, the client has no chance.

[sub]

I'd rather keep client out of the mix for now, so we can focus on any Colossus issue, without having to worry about more variables that comes with a client/server or xbmc client type of setup.

[sub]

This patch adds a bit of extra logging. Reproduce the problem, and repost those same log files.

[IanSpringfield]

I'd rather keep client out of the mix for now, so we can focus on any Colossus issue, without having to worry about more variables that comes with a client/server or xbmc client type of setup.

Trust me, I'm keeping the client out of it for this thread. I just thought it was interesting that channel changing from the client via xbmc doesn't seem to suffer from the problem (although channel changing from the client does suffer from the problem.)

[IanSpringfield]

Also, FYI, all my machines are currently running 3.3.8 (and have been for a few days now) but, as I've mentioned before, this issue goes back many releases and occurs with the original 3.3.8 and the revised 3.3.8 (with that patch included)

[IanSpringfield]

Sorry sub, I originally missed the post with the patch. Now I've found it and here are the files.

This time I changed the channel 5 or 6 times before it froze. The freeze channel was 356. I took these files when npvr was still frozen on the screen.

[ScaryBox]

That's odd. I'd been watching live tv for an hour or so..... Would you like me to try the detailed logging that IanSpringfield did??

[sub]

Yes, I might as well take a look at your logs too.

[ScaryBox]

You'll need to reproduce the problem, with that file writer logging enabled, that was mentioned early in the thread. Also set LogSlipFile=1 and LogReaderAutomap=1, which will cause a couple more files to be created in c:\temp. After you reproduce this problem, post the logs from c:\temp, and the npvr.log/nrecord.log and I'll take a look.

sub,

I can't find these setting in the registry. Should I be adding them or should they already be there?