Well HDHomerun is a complete no go

[jchiso]

Originally Posted by wnjj

... You can also check the running application in task manager: https://www.tenforums.com/tutorials/...dows-10-a.html

It looks like I have 32-bit installed, as it shows as "*32".

The TaskManager info under Win 7 is different than shown in the link, but Sage and a couple of programs were the only ones with this indicator ...

[jusjoken]

Originally Posted by jchiso

It looks like I have 32-bit installed, as it shows as "*32".

The TaskManager info under Win 7 is different than shown in the link, but Sage and a couple of programs were the only ones with this indicator ...

If I recall, System Info within SageTV Setup menu item should say 64 bit next to the version.

K

[jchiso]

Originally Posted by jusjoken

If I recall, System Info within SageTV Setup menu item should say 64 bit next to the version.K

Perhaps is does on some releases, but it does not for v9.1.x But, more importantly, 32-bit releases don't show "32" next to their versions ...

[KeithAbbott]

Originally Posted by jchiso

Perhaps is does on some releases, but it does not for v9.1.x But, more importantly, 32-bit releases don't show "32" next to their versions ...

Strange, my 32-bit client shows 32-bit in the System Information screen, and my HD300 shows 64-bit in the System Information screen (which would reflect the software running on the server). I'm running v9.2.5 on the server and v9.2.2 on the client, so maybe the 32/64-bit indicator was recently added.


SageTV 32-bit Client.jpg

[jchiso]

Originally Posted by KeithAbbott

Strange, my 32-bit client shows 32-bit in the System Information screen, and my HD300 shows 64-bit in the System Information screen (which would reflect the software running on the server). I'm running v9.2.5 on the server and v9.2.2 on the client, so maybe the 32/64-bit indicator was recently added...

A couple of other variables; this is Client versus Server, and you are running Win 10, versus Win 7.

But to get back to the dilemma raised in the original post, it may be that the newer release of the HDHomerun Setup app solves the issue for Win 7 64. I did have an issue when I initially tried to play content from the Homerun devices until I re-ran the setup with the latest release ...

[lanmat]

Same thing just started happening here. I think it must've been an accidental/auto HDHR software update. Now nothing I do makes Sage see any channels. Have both 32-bit and 64-bit clients installed (server running on Linux), even regressed to an older HDHR setup version I had thankfully saved somewhere, but to no avail. Still no channels detected. I tried using the J. River Media setting, but that's not working either.

Any suggestions or things to try next?

[sic0048]

I'm not sure what to say. I recently bought a HDHomeRun Flex 4k tuner and integrating it into SageTV wasn't a problem.

I run only 64bit SageTV. I do however use the OpenDTC server because I also use a Cable Card tuner that requires it. I know the Flex 4k tuners are picked up by OpenDTC the same way that the cable card tuners are.

I added this tuner about 2 months ago. I also just yesterday I moved my SageTV system to a new computer and the only thing I moved over was the wiz.bin file. Both times I did the channel scan in the video tuner setup and it found all the applicable channels on it's own without doing anything special. I certainly did not install the 32bit SageTV first. I'm guessing that the OpenDTC server acts as the special sauce.