Having some issues with 2.6.2

[Bluethunder]

Here are the 2 5 5 (working) logs, and 2 5 9 (hangs) logs.

This is something that didn't show up in the 2 6 2 logs when it piled up (i think). It's reporting all the specs as 0 on the second run, but correctly in the first run.

2013-04-10 20:35:31.218 [DEBUG][6] Device reports resolution: 0x0 (fps:0) (aspect:0) (progressive:0) (videoIdCode:0)

**
Seems that 2 5 5 r1 never reported the resolution properly during any of it's sucessfull runs.

[johnsonx42]

yep, 2.5.5R1 works and 2.5.9 fails exactly the same way 2.6.2 does.

what do you think sub? any value in having him try 2.5.8? it's still on the server, just have to give him the url. (there were several colossus/hdpvr changes in 2.5.8, and a couple more in 2.5.9)

[Bluethunder]

yep, 2.5.5R1 works and 2.5.9 fails exactly the same way 2.6.2 does.

what do you think sub? any value in having him try 2.5.8? it's still on the server, just have to give him the url. (there were several colossus/hdpvr changes in 2.5.8, and a couple more in 2.5.9)

I will give it a go, that would nail down any code changes even further.

Seems odd that I seem to be the only one who's run into this problem. I wonder what's special about my combination that it doesn't like.

Cheers, Joe

[johnsonx42]

bump... sub is it ok if I pm him the download URL for 2.5.8, just to see if it breaks between 2.5.5 R1 and 2.5.8, or between 2.5.8 and 2.5.9?

[sub]

bump... sub is it ok if I pm him the download URL for 2.5.8, just to see if it breaks between 2.5.5 R1 and 2.5.8, or between 2.5.8 and 2.5.9?

Yes, that's fine.

[Bluethunder]

Unfortunately, 2.5.8 refuses to run on my computer.

If I go to live TV, the NPVR tray icon goes red, and then I get "failure to communicate with the recording service".

When I get home tonight, I'll post the logs from the run.

I tried a scheduled recording, but the recording never starts.

I also turned off my firewall, just incase it was getting in the way.

Unless there is any extra logging I can enable to track where it's getting hung up, I guess I'm stuck at 2.5.5.

[Bluethunder]

Here are the logs from 2.5.8..

[johnsonx42]

it looks like when you start the recording service, there's a recording already scheduled to start and it dies very early in the process of setting up the colossus to record. I'm really not sure what this means.

If you're still up for doing another test, try 2.5.5R1 with this patch: http://forums.nextpvr.com/showthread.php...post441916. That's an NShared.dll patch sub released for 2.5.5, yet we were already testing 2.5.9 which released a week later. If that fails, then it's easy enough to put the R1 version of NShared.dll back. I'm not even sure if the code that's going wrong here is in NShared.dll or Unmanaged.dll, but it's one of the two.

[Bluethunder]

I tried the patch, and Nrecord doesn't hang. I did a couple live TVs back to back, then a quick record.

Thanks for helping with this issue.

Cheers, Joe