HDPVR issues after v9 upgrade

[imeric]

sage v7 log, v9 logs and error logs attached
1. Uninstalled completely
2. Installed v7 and setup the colossus (deleted entire sagetv folder)
3. Configured the colossus only , started logs and watched a bit the colossus
4. Installed V9 on top (3 times and as admin just in case..)
5. V9 crashes no matter what decoder I use.

[Narflex]

You said before you were getting video rendering errors...in the logs you posted, it doesn't even get that far, Java crashes completely when trying to to use the Colossus...but that just means it's a capture problem.

With V7, it's getting the device capabilities from the registry here:

Thu 11/3 12:11:12.147 [main@199bd52] Get CaptureMask from registry SOFTWARE\Frey Technologies\Common\AdditionalCaptureSetups\Hauppauge Colossus Capture 0, 0x800 (hybrid:'')

which yields in the end:

Thu 11/3 12:11:12.153 [main@199bd52] DeviceCap: 0x100800

With V9, it does not find this in the registry, and it ends up with this:

Thu 11/3 12:20:39.692 [main@af905d] DeviceCap: 0x15010

So it thinks its a totally different kind of capture device under V9, if you simply replicate that registry setting for V9 it should fix the problem. You should also bring this up to the maintainer of the Windows Installer, since this might be something missing in the installer.

[imeric]

Can you tell me where I would need to manually insert this reg entry in the registry for v9 to see it?

Please find attached a log for v9 where I:
1.Remove the colossus in v9
2. re-add it as a source (you will see the rendering error messages here)
3. try to play something and crash

The frey Technologies folder I could find on my machine is under HKLM\SOFTWARE\Wow6432Node\Frey Technologies\Common\AdditionalCaptureSetups

Doesn't seem to get deleted or added when I install v9 on top of v7

[jusjoken]

SOFTWARE\Frey Technologies\Common\AdditionalCaptureSetups

and

SOFTWARE\Wow6432Node\Frey Technologies\Common\AdditionalCaptureSetups

Are equal in Windows. Windows will handle matching these.

So is the registry setting "Hauppauge Colossus Capture 0, 0x800 (hybrid:'')" in your registry ?

If it exists, then it is likely a permission issue and you need to try to run SageTV as Admin to see if that resolves it.

BTW: what OS and version are you installing SageTV onto ?

k

[imeric]

Windows 10. Running sage.exe as admin seems to change the behaviour (not popping up a separate audio configuration page during source setup but I still get the rendering error.
CaptureMask Dword value is 800 (hexadecimal).

[imeric]

I checked "run as admin" under compatibility and it resolved the issue...
Windows 10... dunno how manyt times I needed to do this for other (usually older) softwares...

[Fuzzy]

Originally Posted by imeric

I checked "run as admin" under compatibility and it resolved the issue...
Windows 10... dunno how manyt times I needed to do this for other (usually older) softwares...

Strange. I just checked my 'test system', which is Win10 - and v9's registry entries are all there, and permissions seem to allow reading for Everyone, so I wonder what sage is doing wrong in trying to read these.

[jusjoken]

Originally Posted by Fuzzy

Strange. I just checked my 'test system', which is Win10 - and v9's registry entries are all there, and permissions seem to allow reading for Everyone, so I wonder what sage is doing wrong in trying to read these.

Is your version of Windows 10 the same version as his?

I think MS makes so many changes in releases/updates to Win 10 that perhaps the registry is being blocked in some cases?

This is also a v9 over v7 install....so am also wondering if the installer skips changing the registry (as it exists) BUT v9 needs some permission set that is different from v7 and then cannot read it. I think we saw something similar earlier on upgrades but cannot recall specifically.

Glad it's working.

k

[imeric]

A clean install of v9 lead to the same issue.

[jusjoken]

Originally Posted by imeric

A clean install of v9 lead to the same issue.

By clean do you mean on a fresh pc with a clean registry?

k

[imeric]

Originally Posted by jusjoken

By clean do you mean on a fresh pc with a clean registry?

k

Oups..No...Just uninstalled, deleted remnants in the program files x86 folder but no deletions in the registry.

[jusjoken]

Originally Posted by imeric

Oups..No...Just uninstalled, deleted remnants in the program files x86 folder but no deletions in the registry.

Make sense then as the issue was registry access and that was the same on a clean v9 install vs an upgrade from v7.

The v9 installer tries to change the registry access at the Frey level and below to allow "everyone" full access but i think that is failing on Win 10 in certain cases. I don't have a win 10 test setup to determine the specific issue or resolution so run as admin would not be needed.

k

[Vaskill]

Originally Posted by 4T2

Long time sage user just updated from v7 to v9 using the windows installer.

Everything went smooth except now my HDPVR shows up as 480i (4:3) when recording and is all squashed.

I've verified that they are still getting 1080i input via the hauppauge app.
Can't find anywhere in sage that would be messing with this nor could I find anything via a quick forum search.

Is this a known issue with a fix or am I going to have to revert back to my v7 backup?

oh, and don't ask me why i decided to try this at 11pm on a weeknight

Have you inspected the video file itself to determine if it is indeed the recording vs. the playback. Even just a quick review of format from within sage can reveal a lot when troubleshooting. E.g. Does SageTV think it's playing back a 4:3 or 16:9, 480i or 720p/1080i. Also, check you aspect ratio settings in sage, and your overscan settings. I have seen some odd behaviour when these don't get configured properly, especially after upgrades.