Windows 64 bit Installer news

[jusjoken]

NOTE The BETA has ended and you should now use the release version of SageTV 64 bit edition for Windows****

Release version available here....

Thanks to WNJJ for all the work on getting the 64 bit changes completed to make this option available to SageTV users.

The 64bit version has been reported as fairly stable and should be ready for production use soon (I am sure a few are already there). There are only minor fixes in this release.
This version of the installer has some larger changes so please report any issues during testing so we can call this a production release.

There are a few functionality changes included in this release - see list below

Please use this forum to discuss issues with both the installer as well as the 64 bit and 32 bit versions of the SageTV software.

SageTV Version is 9.2.0
Installer Version is 1.104

x64 Downloads

• SageTV Server 64bit edition installer
• SageTV Client 64bit edition installer
• SageTV Placeshifter 64bit edition installer

x86 Downloads
Note: the x86 version contains code that is now being compiled with each release that was previously included from the original Open Source release. Testing of the x86 version would be appreciated.

• SageTV Server 32bit edition installer
• SageTV Client 32bit edition installer
• SageTV Placeshifter 32bit edition installer

Notes:

• If you have previously installed a prior BETA version you may need to perform an uninstall of the prior version before installing a newer BETA
• Please BACKUP your existing SageTV folder PRIOR to installing and testing this software
• 64 bit install is a NEW product and will NOT perform an upgrade of x86 versions
• Default install folder will be "Program Files" rather than "Program Files(x86)
• Installation into the same folder as an x86 (32bit) version needs testing. It should work but please do NOT do so into your production Sage folder.
  
• New: Installer will now default the install folder to the previous install location for upgrades - the 64 and 32 bit installs are handled separately for this
• You should be able to have BOTH the 32 bit and 64 bit version installed on the same computer under different folders. They cannot/should not be run at the same time for numerous reasons
• There will be a new SageTV64 Service entry that should operated independently of the 32 bit one
• If you copy your Wiz.bin and properties to your new installation, keep in mind that the .properties will need to be edited manually for the different paths
• Java is NOT embedded in the installer any longer. If Java (x64) 1.7 or higher is not found on the system then the installer will download Java 1.8 from BinTray and install it. If you want a different x64 Java version then please install it prior to running the installer.
• AC3Filter is NO LONGER part of the installer - removed 12/01/2018 installer version 1.102
  
• New: LAV Filters is now offered as part of the 32 bit and 64 bit installers.
  
• New: The installer has options for setting "EnableSageTVStreamDemux" and AlwaysSwapForAC3Filter
• Registry entries for the 64 bit install follow the windows standard so will be in a new location than the 32 bit ones (no longer under WOW6432node)
  
• New: The installer has an option to install USB_UIRT support in the 64 bit version
• HDHR fresh installs will not find the 64 bit install. As a work around you need to install the 32 bit version somewhere else, configure HDHR first time, and then you could uninstall the 32 bit version....hopefully we find a better solution.

9.2.0 Change Log:

• Reworked for Windows 64-bit version
• Added ExeMultiTunerPlugin project
• Added USB-UIRT transmit project
• Added HCWIRBlaster project
• Changed defaults: video/audio decoder to 'Default', video/dvd_video renderer to 'EVR'
• Updates to whitelist LAV Filters
• Updated STV to remove prompt on new install for the weather underground plugin
• Fix: Sage-x64 hang due to CableCARD tuners (Windows)
• Fix: Add support for HVR-4400 and other 885 variants (Windows)
  

Note: all 6 of the installers were submitted to Microsoft and have had the false positive virus message removed for them. You may need to update your virus definitions if you receive a false positive. Here is Microsofts response...

We have removed the detection. Please follow the steps below to clear cached detection and obtain the latest malware definitions.

1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender 
2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”

Alternatively, the latest definition is available for download here: https://www.microsoft.com/en-us/wdsi/definitions

k

[jusjoken]

I am considering removing at least some of the redistibutables that previously were embedded inside the installer executable...namely java. I plan to ensure at least java 7 is installed but if 7 or newer is not found then java 8 will download from bintray and install. The redist of java 8 is 200MB (7 was 30) so excluding it and downloading on demand shrinks the installer.

Thoughts?

Should i do this for Directx9, VC10 or VC14, AC3 filters ?

k

[wnjj]

Originally Posted by jusjoken

I am considering removing at least some of the redistibutables that previously were embedded inside the installer executable...namely java. I plan to ensure at least java 7 is installed but if 7 or newer is not found the java 8 will download from bintray and install. The redist of java 8 is 200MB (7 was 30) so excluding it and downloading on demand shrinks the installer.

Thoughts?

Should i do this for Directx9, VC10 or VC14, AC3 filters ?

k

I'd say non-embedded is fine since it makes the installer lightweight. To complement that, I'd suggest a README file that contains the exact download paths to either the 3rd party download sites or bintray for anything not embedded. That way someone could grab everything needed up front for an install which could be done even while offline.

[Tiki]

Originally Posted by wnjj

I'd say non-embedded is fine since it makes the installer lightweight. To complement that, I'd suggest a README file that contains the exact download paths to either the 3rd party download sites or bintray for anything not embedded. That way someone could grab everything needed up front for an install which could be done even while offline.

I would say it’s OK as long as it automatically downloads the dependencies on-demand as needed. Most Windows users are not accustomed to needing to check a readme file and manually download and install other dependencies.

Having a light weight installer is nice (faster to download and takes less storage space), but most people aren’t downloading it very often. Also for people who are most likely going to be recording TB’s of stuff, a few hundred MB is almost nothing (though it could add up if you save copies of every version).

[jusjoken]

Originally Posted by Tiki

I would say it’s OK as long as it automatically downloads the dependencies on-demand as needed. Most Windows users are not accustomed to needing to check a readme file and manually download and install other dependencies.

Having a light weight installer is nice (faster to download and takes less storage space), but most people aren’t downloading it very often. Also for people who are most likely going to be recording TB’s of stuff, a few hundred MB is almost nothing (though it could add up if you save copies of every version).

Absolutely the download is automatic as long as there is an internet connection. Manual download of dependencies would only be needed for an offline install which is an unlikely case IMHO. And of course in an upgrade where the dependencies are already installed then no download is needed.

k

[Carlton Bale]

Originally Posted by Tiki

I would say it’s OK as long as it automatically downloads the dependencies on-demand as needed... For people who are most likely going to be recording TB’s of stuff, a few hundred MB is almost nothing.

Unless you're paying for server bandwidth, I don't the size of the installer is a significant concern. I'd rather have an installer that I know is going to work every time. There's nothing more frustrating than not being able to install because a different server is down or the path has changed. Also, having as few clicks as possible to install is desirable.

[wnjj]

Originally Posted by Carlton Bale

Unless you're paying for server bandwidth, I don't the size of the installer is a significant concern. I'd rather have an installer that I know is going to work every time. There's nothing more frustrating than not being able to install because a different server is down or the path has changed. Also, having as few clicks as possible to install is desirable.

The dependencies are on the same server as the installer however I suppose the server could go down after you have already grabbed the installer but before you ran it.

In any case it’s the same number of clicks. It’s just a matter of whether the installer continues to download components when it’s run or if they’re bundled up front.

[SHS]

Originally Posted by jusjoken

I am considering removing at least some of the redistibutables that previously were embedded inside the installer executable...namely java. I plan to ensure at least java 7 is installed but if 7 or newer is not found then java 8 will download from bintray and install. The redist of java 8 is 200MB (7 was 30) so excluding it and downloading on demand shrinks the installer.

Thoughts?

Should i do this for Directx9, VC10 or VC14, AC3 filters ?

k

I see no point in having the AC3 filter
Yes the LAV Filters
Yes the Visual C++ Redistributable Packages install run-time components should also be included for Windows 7 on up.

[KryptoNyte]

I will be running this new installation in either January or February, right when the cable company decides to omit my already ridiculous "introductory" rate ... again. I'm sick of that yearly battle, and with 64 bit Sage, an antenna, and the HDHomerun Premium TV service (with a Quatro device), I finally have a real exit. I almost look forward to that phone call early this next year.

Thanks again for bringing SageTV into the 64 bit era, it's been a long time coming.

[jusjoken]

Originally Posted by SHS

I see no point in having the AC3 filter
Yes the LAV Filters
Yes the Visual C++ Redistributable Packages install run-time components should also be included for Windows 7 on up.

All required visual c++ redistributables and directx9 are included in the installer.

I may remove the AC3Filter as i believe it is causing the false positive malware results but i will test that.

I would also appreciate feedback on if we remove AC3 what other changes should be made to the code or registry etc.

As for LAV the same questions for those that use these...what code or registry change should be made to include these more seamless.

k

[SHS]

Originally Posted by jusjoken

I may remove the AC3Filter as i believe it is causing the false positive malware results but i will test that.

I don't think that causing it as SageTV Placeshifter doesn't come with it I think it some else more like the lack of digital signing certificate

Also being that you the developer maybe this will help
https://www.microsoft.com/en-us/wdsi/filesubmission

[jusjoken]

Originally Posted by SHS

I don't think that causing it as SageTV Placeshifter doesn't come with it I think it some else more like the lack of digital signing certificate

Also being that you the developer maybe this will help
https://www.microsoft.com/en-us/wdsi/filesubmission

I tried that but there is a 50mb limit. is the placeshifter giving you the same thing as it was not for me.

k

[graywolf]

Also, maybe someone could Sticky this?
Or are you waiting until out of Beta to do so?

[jusjoken]

Originally Posted by graywolf

Also, maybe someone could Sticky this?
Or are you waiting until out of Beta to do so?

When we are out of beta and fix what is found then the current sticky one will point to all available versions including the 64 bit ones.

k

[jt4242]

So great to see this up!!

I started the install but get stuck at Select Remote Control - when I choose USB-UIRT Receiver + any remote, I get the message "Failled setting the Infrared Receiver Port! Please ensure that the device is connected"

Has anyone got the usb-uirt working?

[SHS]

Originally Posted by jt4242

So great to see this up!!

I started the install but get stuck at Select Remote Control - when I choose USB-UIRT Receiver + any remote, I get the message "Failled setting the Infrared Receiver Port! Please ensure that the device is connected"

Has anyone got the usb-uirt working?

Mine works but I only edited my Sage.properties
I didn't do a new install

[jt4242]

You installed the x64 version though right? and then copied over your sage.properties from your 32bit version? then what did you edit in sage.properties besides the paths?

[SHS]

The first it Windows Defender is saying the download are unsafe on all of SageTV 64bit files and even the 32 files
There Photo when this all malware results start with SageTV 9.1.10

[jusjoken]

By popular demand I have removed the AC3Filter from the installer. The first post has been updated with new links for all but Placeshifter which has never contained AC3Filter.

k

[VCRUser]

Originally Posted by jusjoken

By popular demand I have removed the AC3Filter from the installer. The first post has been updated with new links for all but Placeshifter which has never contained AC3Filter.

k

Replying to old post because I will probably be doing a new build on a new machine (which I will probably set up as a 64 bit Windows 8.1 OS), because my current server (Wine 7.1 32bit) has become unstable (frequent bsod & spontaneous reboots) and all attempts to troubleshoot have so far failed.

'm looking over the forums to prepare a plan for installing Sage on the new box, and am wondering about two things I saw in the changelogs:

1. Removal of AC3Filter - what is AC3Filter for and what are the consequences of its removal? (I recall converting videos into formats that have "with AC3" in the name. Will those still play correctly without AC3 filter?

2. 9.9.2 changelog notes "• Fix for Hauppauge 885 tuners with Alt TS Capture Devices (Windows)"

One of my tuners is a Hauppauge 1800, which Sage shows as 885 TS. Is the above change relevant, and if so how?

In general, are there ways to track back notes in the change logs to a fuller description?

Thanks!