Windows 64 bit Installer news

[Malfunction]

Originally Posted by SHS

That wrong nyplayer
Enhanced Video Renderer (EVR) Uses Direct3D 9. Requires Windows Vista or later.
Video Mixing Renderer 9 (VMR-9) Uses Direct3D 9. Requires Windows XP or later.
Video Mixing Filter 7 (VMR-7) Uses DirectDraw. Requires Windows XP or later.
Overlay Mixer Supports hardware overlays through DirectDraw.

I'm still mystified about why EVR doesn't run or appear in the menu. I'm not sure it would be any better than VMR-9, which is what I use now.

[jusjoken]

Originally Posted by Malfunction

I'm still mystified about why EVR doesn't run or appear in the menu. I'm not sure it would be any better than VMR-9, which is what I use now.

Try searching the sagetv_0.txt log file for...

EVR support detected=

That should tell you if the sage code sees it as supported.

k

[SHS]

Originally Posted by Malfunction

I'm still mystified about why EVR doesn't run or appear in the menu. I'm not sure it would be any better than VMR-9, which is what I use now.

That kind odd as I see VMR in the menu even in beta ver of Windows 10 64x
What decoder codec are set?.

[Malfunction]

Originally Posted by SHS

That kind odd as I see VMR in the menu even in beta ver of Windows 10 64x
What decoder codec are set?.

Using LAV for everything.

[Malfunction]

Originally Posted by jusjoken

Try searching the sagetv_0.txt log file for...

EVR support detected=

That should tell you if the sage code sees it as supported.

k

sagetv_1.txt has EVR support detected=false

[SHS]

Originally Posted by Malfunction

Using LAV for everything.

Yes

[Malfunction]

I got EVR working today. It's so simple I didn't think it could work. Install K-Lite Codec Pack Basic. Use the codec tweaking tool to fix DirectShow filters. That's it. This will enable EVR.

K-Lite Codec Pack will make you uninstall the LAV filters from the SageTV installation. Let it do that. Reboot. SageTV now has EVR. You can now uninstall K-Lite and Sage 64. Reinstall Sage 64 with LAV filters. Reboot.

I reinstalled the EVGA GT 1030SC card. EVR works a little better than VMR-9, The crawl at the bottom of the screen on Mad Money is greasy smooth with EVR and Full Screen Exclusive. The whole system works better than it ever has before with Sage 32. All video issues are resolved. The overlay video works now as well, but I'm using EVR. SageTV needs a few minutes to cache the user interface on startup and the video may also be choppy for a few minutes. Toggling full-screen to window and back seems to eliminate the choppiness.

[KryptoNyte]

I'm running through my old 32 bit program guide and enabling those channels in the 64 bit tuner setup. Why are some channels that used to populate my guide just fine no longer appearing in the list of available channels? I'm using the exact same Schedules Direct Lineup.

Is there a way to add channels that didn't get into the list during "Channel Setup" or do I need to contact Schedules Direct?

[RonBoyd]

Originally Posted by KryptoNyte

I'm running through my old 32 bit program guide and enabling those channels in the 64 bit tuner setup. Why are some channels that used to populate my guide just fine no longer appearing in the list of available channels? I'm using the exact same Schedules Direct Lineup.

Is there a way to add channels that didn't get into the list during "Channel Setup" or do I need to contact Schedules Direct?

This is after >Setup Video Sources>]any tuner]>Channel Setup>Scan for Available Channels and >Edit Channel Line up?

The only time I have found a channel missing is if the channel was not sending a signal at the time I "scanned" or was simply no longer "in range." This "no longer in range" has become quite common since the FCC frequency auction. Some broadcasters have had to move their transmitter to a different location that even if "in range" may carry a different call sign. I might add that this is all too common and very irritating.

Am I missing something?

[KryptoNyte]

Because I'm using OpenDCT with a Ceton tuner (cablecard) I don't ever do a channel scan in Sage. We're kind of in the same location, though, in Channel Setup, where you can enable and disable various channels. The image attached is a good example. In my 32 bit installation, I have a channel 1218 that is WGN America. In the 64 bit installation, using the exact same lineup (through Schedules Direct), it's just not there.

Sometimes Spectrum supplies channels at both 218 and 1218 as an example, but neither of them exist in the 64 bit install.

[RonBoyd]

Originally Posted by KryptoNyte

Because I'm using OpenDCT with a Ceton tuner (cablecard) I don't ever do a channel scan in Sage.

Yeah, I am a "never corder" and am unfamiliar with that setup. Therefore not much use to this conversation. <shy grin>

[KryptoNyte]

I cranked the Java heap up to 4096 and with (3) HD300's all running at the same time, and with Gemstone on each, I see the usage up to about 1700MB, and not a single hiccup so far. Very snappy.

This is fantastic. Thanks to wnjj for all the hard work that went into bringing SageTV up to 64 bit, and jusjoken for the installer, and anyone else that contributed.

[easperhe]

All,

I've been using SageTV 32 bit forever now. But, I want to expand and use placeshifter, etc. So, I was going to reinstall SageTV latest rev 9.2

Is there any advantage/disadvantage to using 64 bit installs?

[wnjj]

Originally Posted by easperhe

All,

I've been using SageTV 32 bit forever now. But, I want to expand and use placeshifter, etc. So, I was going to reinstall SageTV latest rev 9.2

Is there any advantage/disadvantage to using 64 bit installs?

The single biggest advantage (and it’s a big one) is the ability to crank the heap memory size way, way up, supporting more miniclients, provided your system has enough memory. 32-bit is limited to ~1G which means only 2 or maybe 3 extenders without issues.

The disadvantages include things like using USB-UIRT along with Eventghost, as the latter isn’t compatible with 64-bit. FireWire drivers aren’t available for 64-bit. You also cannot use the “SageTV MPEG decoder” which originally shipped with V7 but LAV seems to work in its place.

You can still install 32-bit clients on other machines if you want and they’ll talk to the 64-bit server just fine.

[JustFred]

Originally Posted by wnjj

The single biggest advantage (and it’s a big one) is the ability to crank the heap memory size way, way up...

And this advantage becomes even more significant when any of the (memory-hungry) Sage plugins are installed.

[wayner]

Originally Posted by wnjj

The single biggest advantage (and it’s a big one) is the ability to crank the heap memory size way, way up, supporting more miniclients, provided your system has enough memory. 32-bit is limited to ~1G which means only 2 or maybe 3 extenders without issues.

And was the impetus that caused me to switch to the unRAID version of SageTV which was the best move that I ever made.

[tvmaster2]

Originally Posted by wayner

And was the impetus that caused me to switch to the unRAID version of SageTV which was the best move that I ever made.

And the USBUIRT works with both standard Windows 10 64 bit and unRAID versions?

[easperhe]

Originally Posted by tvmaster2

And the USBUIRT works with both standard Windows 10 64 bit and unRAID versions?

Yes - wondering if USB-UIRT and Girder work on windows 64-bit. I'd like to have my new SageTV clients (Intel NUCs) stay with 64-bit.

[easperhe]

The single biggest advantage (and it’s a big one) is the ability to crank the heap memory size way, way up, ...

I saw an older post that indicates that you edit registry to increase SageTV heap size. Is that still the case? My intended media server is 64-bit and has 32 GB of RAM. So more than enough. And 2 clients with (I think 16 GB). What is recommended for both server and clients?

[wnjj]

Originally Posted by easperhe

I saw an older post that indicates that you edit registry to increase SageTV heap size. Is that still the case? My intended media server is 64-bit and has 32 GB of RAM. So more than enough. And 2 clients with (I think 16 GB). What is recommended for both server and clients?

Yes, you still edit the registry. Just be sure it's the 64-bit location which does not include "wow6432node" in the path.

I think regular clients don't load the server memory like miniclients do. I would just get it all up and running and then check the memory usage in system info inside SageTV. If you find either of the first 2 numbers nearing the max, increase the heap setting.