Windows 64 bit Installer news

[brianrent]

I plan on switching to 64 bit when it is out of beta. I currently use a windows client as my main viewer and occasionally use an extender or two. 1024 heap has worked fine for me with no issues. Is there any benefit to the 64 bit version other than not running out of heap? Is there any noticeable improvement in performance?

[Zogg]

Originally Posted by wayner

Wow Snapstream - there's a blast from the past. I used that prior to SageTV and WMC.

I just switched about a year ago. Had used BTV for about 15 years.

[wayner]

Originally Posted by brianrent

I plan on switching to 64 bit when it is out of beta. I currently use a windows client as my main viewer and occasionally use an extender or two. 1024 heap has worked fine for me with no issues. Is there any benefit to the 64 bit version other than not running out of heap? Is there any noticeable improvement in performance?

Not sure the direct answer but if folks are looking for more info on this topic - I generally started running into issues when I had about 4 min-clients connected. Full Windows clients don't really use the server's resources, just miniclients like extenders, Android client or PlaceShifter.

[JustFred]

I installed the 64-bit Server, Client & Placeshifter, each using 'Install as Administrator'. Installation was to a Win7-x64 box which previously had the 1.103 beta installed and then uninstalled. 32-bit Sage v9.1.6.747 remains installed.

Installing the Server, the Installer Setup Welcome screen shows:
- "Install LAV filters..." is the default (good!)
- "Install USB-UIRT Driver Package" isn't checked by default.

Curious why isn't this the default? Any disadvantage to automatically installing it? I recall that Sage7 used to install these drivers by default, and it seems like that should be the default here, too. It would make it closer to the installation experience documented elsewhere in the forums.

Re: USB-UIRT..
Even though I checked the box to install USB_UIRT drivers, it was necessary to manually copy SageTv\redist\uuirtdrv.dll (278KB) to C:\Windows\system32 to replace the old x86 (236KB) version of the file. After that, the USB-UIRT blaster works.

No problems using the Hauppauge IR blaster.

Ran into strange problems with installing the Client. See attached notes for details. Even though the installer reported failure, the Client actually was installed and runs without obvious issues.

No problems installing or running Placeshifter.

Norton Security (antivirus) is installed on this system. NS didn't complain about anything during the installation process. But initially launching each of the 3 Sage components resulted in "Norton Firewall Alert - suspicious network activity has been detected." My response in each case: Allow Always. No further nags after that.

Even though this was a relatively clean **software installation**, I decided to migrate all my config settings from the old 32-bit Sage installation (which is still on this box) into the correct spots in the 64-bit SageTv folders.

For the benefit of others who might want to migrate their settings from 32 to 64-bit Sage, here's a rundown. First, edited a copy of the 32-bit sage.properties to remove " (x86)" from the paths. Then copied the edited sage.properties, sageclient.properties, wiz.bin, the clients folder (to retain all my client settings), 3 sd* files (to retain SchedulesDirect acct. info) and my customized .ir files from the RemoteCodes folder. I'm not using any plugins, so didn't copy any .jar files.

I also increased the Java heap to 0x800 (2GB) by editing the registry (JVMMaxHeapSize at HKLM\SOFTWARE\Frey Technologies\SageTv). Haven't noticed any spinning circles yet.

Overall, it appears that 64-bit is quite functional. Impressive.

[tmiranda]

Originally Posted by wayner

I can connect well over a dozen miniclients without having issues.

Holy TVaholic batman! Either you have an enormous house or you have 2 TVs in every room.

[jusjoken]

Originally Posted by JustFred

I installed the 64-bit Server, Client & Placeshifter, each using 'Install as Administrator'. Installation was to a Win7-x64 box which previously had the 1.103 beta installed and then uninstalled. 32-bit Sage v9.1.6.747 remains installed.

Installing the Server, the Installer Setup Welcome screen shows:
- "Install LAV filters..." is the default (good!)
- "Install USB-UIRT Driver Package" isn't checked by default.

Curious why isn't this the default? Any disadvantage to automatically installing it? I recall that Sage7 used to install these drivers by default, and it seems like that should be the default here, too. It would make it closer to the installation experience documented elsewhere in the forums.

Re: USB-UIRT..
Even though I checked the box to install USB_UIRT drivers, it was necessary to manually copy SageTv\redist\uuirtdrv.dll (278KB) to C:\Windows\system32 to replace the old x86 (236KB) version of the file. After that, the USB-UIRT blaster works.

No problems using the Hauppauge IR blaster.

Ran into strange problems with installing the Client. See attached notes for details. Even though the installer reported failure, the Client actually was installed and runs without obvious issues.

No problems installing or running Placeshifter.

Norton Security (antivirus) is installed on this system. NS didn't complain about anything during the installation process. But initially launching each of the 3 Sage components resulted in "Norton Firewall Alert - suspicious network activity has been detected." My response in each case: Allow Always. No further nags after that.

Even though this was a relatively clean **software installation**, I decided to migrate all my config settings from the old 32-bit Sage installation (which is still on this box) into the correct spots in the 64-bit SageTv folders.

For the benefit of others who might want to migrate their settings from 32 to 64-bit Sage, here's a rundown. First, edited a copy of the 32-bit sage.properties to remove " (x86)" from the paths. Then copied the edited sage.properties, sageclient.properties, wiz.bin, the clients folder (to retain all my client settings), 3 sd* files (to retain SchedulesDirect acct. info) and my customized .ir files from the RemoteCodes folder.

The registry has been edited to increase the Java heap up to 0x800 (2GB). Haven't noticed any spinning circles yet.

Overall, it appears that 64-bit is quite functional. Impressive.

Great info...much apprecuated.

usbuirt... under the new installer it now also launches the usb driver installer...did it do that? The base support files still get installed by default but i needed to include the driver installer so i could then copy over the new 64 bit driver. The v7 and prior v9 did not do that as far as i know, however i am not a usbuirt user. That's why it is not checked by default.

Following the success of the driver package install it then copies the 64 bit driver file to system32 . sound like that did not happen. A copy of the msi log would be handy from user/name/appdata/local/temp

As for the client...was this on the same pc as the server install? Although technically this should work i may need to test it out more as the server and client have the same product code (always have even in v7)...so it could get confused as to install vs upgrade. I will attempt to recreate this.

As for the default for those checkboxes...on a clean install they will follow yes for lav and no for usbuirt...after that i read a value from the registry to set it the same on an 'upgrade' so i dont change the users setting.

k

[Eternal]

I take it closed captions are doomed to 32 bit installations forever unless a new 64 bit decoder comes along?

[Tiki]

Originally Posted by Eternal

I take it closed captions are doomed to 32 bit installations forever unless a new 64 bit decoder comes along?

I don’t know the answer to that, but it is possible to install a 64-bit server and a 32-bit client and have them work together. The 32-bit client can definitely keep using whatever decoders you were using before.

[wnjj]

Originally Posted by Eternal

I take it closed captions are doomed to 32 bit installations forever unless a new 64 bit decoder comes along?

I'm not sure. What particular software/driver/plugin/DLL is used for that on 32-bit? Is it the original MPEG2 filters that came with V7 that you're needing? Does LAV offer CC?

[Eternal]

Originally Posted by wnjj

I'm not sure. What particular software/driver/plugin/DLL is used for that on 32-bit? Is it the original MPEG2 filters that came with V7 that you're needing? Does LAV offer CC?

only the original, ati and powerdvd decoder ever provided cc

[tmiranda]

Originally Posted by brianrent

I plan on switching to 64 bit when it is out of beta. I currently use a windows client as my main viewer and occasionally use an extender or two. 1024 heap has worked fine for me with no issues. Is there any benefit to the 64 bit version other than not running out of heap? Is there any noticeable improvement in performance?

There is no functionality difference and I doubt there is much of a performance difference.

[JustFred]

Ken: Email sent

[Tiki]

What do these new options in the installer do? Can these choices be changed later (after install)?

New: The installer has options for setting "EnableSageTVStreamDemux" and AlwaysSwapForAC3Filter

[rnadeau]

Originally Posted by SHS

Good news I able to reuse all my SageTV
First you want to do uninstall the all old Java and SageTV
After do that move from C:\Program Files (x86)\ the folder SageTV to new place
Now install the lates Java and this ver of SageTV
Next you copy the all the files from the old 32bit SageTV folder over to new 64bit SageTV folder in C:\Program Files\SageTV\
Next time some editing
Find Sage.properties or the SageClient.properties
Open with Notepad click on Edit menu then Replace
Find what: Program Files (x86)
Replace with: Program Files
Then Save it
Note you may get a google plugin error don't worry about just remove the message and restart SageTV
Good Luck

I just did this and have sage 64 running with all my original content and settings. Thanks!

[wnjj]

Originally Posted by Tiki

What do these new options in the installer do? Can these choices be changed later (after install)?

New: The installer has options for setting "EnableSageTVStreamDemux" and AlwaysSwapForAC3Filter

Those both affect the filters used for playback. Stream Demux normally handles all formats that are NOT MPEG2-TS/PS or AVI. It's the internal filter that leverages FFMPEG. With it disabled, the DirectShow filter graph selects filters that match the media based upon merit settings.

Looking at the code, I think the AlwaysSwapForAC3Filter only applies to MPEG2 and the "SageTV" MPEG audio decoder (i.e. the one only available on 32-bit V7 upgrades to V9). I'm guessing it picks the externally available AC3 filter instead of the stock V7 one.

Both of these settings are registry settings that can be edited later.

[Tiki]

Well I built a new PC this week with plans to use it as a replacement Sage server and playback device (AMD Ryzen 2400G with Windows 10 Pro). I took the plunge with the new 64-bit installer and it seemed to go smoothly. But, I ran into my first problem. I can't get the USBUIRT to work.

When I ran the Sage installer, I did not have the USBUIRT attached (it was still in use in my old PC). But I told it to install the drivers and it did.

Now I have it attached, but I can't get Sage to recognize it. I tried attaching it to both a USB2 and USB3 port. I rebooted several times. I checked the Windows Device Manager and it sees it and reports it as functioning.

The light on the USBUIRT blinks when I press a button on my remote. I download the lrnhelper.exe utility from the USBUIRT website and it seems to register remote codes when I press buttons, so I think the USBUIRT is working - Sage just doesn't see it.

When I try to setup the remote in Sage it says "Failed setting the Infrared Receive Port! Please ensure that the device is connected."

Any ideas what could be causing this?

[SHS]

Originally Posted by Tiki

Well I built a new PC this week with plans to use it as a replacement Sage server and playback device (AMD Ryzen 2400G with Windows 10 Pro). I took the plunge with the new 64-bit installer and it seemed to go smoothly. But, I ran into my first problem. I can't get the USBUIRT to work.

When I ran the Sage installer, I did not have the USBUIRT attached (it was still in use in my old PC). But I told it to install the drivers and it did.

Now I have it attached, but I can't get Sage to recognize it. I tried attaching it to both a USB2 and USB3 port. I rebooted several times. I checked the Windows Device Manager and it sees it and reports it as functioning.

The light on the USBUIRT blinks when I press a button on my remote. I download the lrnhelper.exe utility from the USBUIRT website and it seems to register remote codes when I press buttons, so I think the USBUIRT is working - Sage just doesn't see it.

When I try to setup the remote in Sage it says "Failed setting the Infrared Receive Port! Please ensure that the device is connected."

Any ideas what could be causing this?

Sorry I don't used a IR remote on the server only IR blaster

[Tiki]

Originally Posted by SHS

Sorry I don't used a IR remote on the server only IR blaster

I use it for both (Receives commands from my remote, and also blasts the channels on my cable box for the Colossus).

I decided to try to move forward with my testing and installed my Colossus card. Sage can see that OK and preview a channel, but when I tell it to use the USB-UIRT for tuning, it fails with a similar error:

"Failed setting the Infrared Transmitter Port! Please ensure that the USB-UIRT is connected, its drivers are properly installed, and that no other applications are using it."

[SHS]

Originally Posted by Tiki

I use it for both (Receives commands from my remote, and also blasts the channels on my cable box for the Colossus).

I decided to try to move forward with my testing and installed my Colossus card. Sage can see that OK and preview a channel, but when I tell it to use the USB-UIRT for tuning, it fails with a similar error:

"Failed setting the Infrared Transmitter Port! Please ensure that the USB-UIRT is connected, its drivers are properly installed, and that no other applications are using it."

Hmm ver odd

[Tiki]

Originally Posted by SHS

Hmm ver odd

Since my last post I also tried a repair install of Sage (didn't help), and a complete uninstall (and deleted the leftover Sage folder), followed by a fresh re-install with the USBUIRT attached. Also didn't help.

I also downloaded the driver from the USBUIRT website. It appears to be the same version that Sage installed, but I went to Device Manager and told it to update driver to this one anyway. This also made no difference.

How does Sage detect the USBUIRT?

I attached the debug logs in case it helps (running in service mode, so included Sage Client log too). I don't see anything odd in them.