Open Source Windows Installer

[FriscoJohn]

NYPlayer and others having trouble displaying closed captions, this thread

http://forums.sagetv.com/forums/showthread.php?t=61098

might be of interest, esp. post #12 and following posts.

The ATI decoder is still performing like a champ for me but I'm running stock SageTV 7. Would be interested to know if it works with SageTV9.

[Fuzzy]

Originally Posted by FriscoJohn

NYPlayer and others having trouble displaying closed captions, this thread

http://forums.sagetv.com/forums/showthread.php?t=61098

might be of interest, esp. post #12 and following posts.

The ATI decoder is still performing like a champ for me but I'm running stock SageTV 7. Would be interested to know if it works with SageTV9.

Nothing on the playback engine has really changed, so it should be exactly the same as v7.

[jusjoken]

The V9 Windows Installers for the Server, Client and now the Placeshifter are ready for testing. I will also update the first post with the links.



NOTE: This needs to be considered a BETA installer at this time and should NOT be used for a production system.

For now the files have been named with the SageTV version (9.0.3.214) with the installer version (currently 0.002) appended after "beta"....so "SageTVClientSetup_9.0.3.214_beta0.002.exe" for example. This will help track what has been tested and/or found for issues in each version. As well the installer screens show the SageTV version as well as the installer version to help us track this.

The files are a little smaller thanks to a lot of cleanup in this release.

Updates in this release....

• New Placeshifter installer now available
• Splash screens now show Version 9 (thanks to members of this community)
• Latest Sage code including v9 plugin support when authors start to use it
• if Java 1.8 is already installed the installer will NOT install 1.7
• versioning check on the C++ runtimes was improved
• MAJOR cleanup of the included files based on a lot of feedback. Removed files not used/not needed/not licensed.
• Installer Success screen updated with Launch button to launch Placeshifter or Client or the Service Control application depending on the installer
• Server installer has the ability to enter the EPG license key on the first screen
• AC3Filter part of the Client/Server install
• Lots of code cleanup and added scripting to automate much of the build process

Please post issues/comments in this Thread....if it gets unruly (too many issues ) then I will setup an Issues tracker somewhere or we will just use the SageTV GitHub one perhaps.

If there are not too many issues raised then I should be able to release a non-beta version soon.

k

[nyplayer]

It still kills the SageTV Decoder even if you have a license. Maybe should you let people know this so those that require SageTV Decoder for CC are not surprised.

[jusjoken]

Originally Posted by nyplayer

It still kills the SageTV Decoder even if you have a license. Maybe should you let people know this so those that require SageTV Decoder for CC are not surprised.

Are you saying that installing this latest version on top of a licensed V7 install makes the SageTV Decoder no longer work ?

If that's the case I am at a loss as to why as I "believe" I have removed all the files involved in that decoder from the installer so in theory it should leave that alone.

It could be that something in the V9 Sage.jar file has been written specifically to not use that function and if that's the case I have little control over that but I believe you previously tried a manual install of the V9 files and that worked...correct?

k

[nyplayer]

Originally Posted by jusjoken

Are you saying that installing this latest version on top of a licensed V7 install makes the SageTV Decoder no longer work ?

If that's the case I am at a loss as to why as I "believe" I have removed all the files involved in that decoder from the installer so in theory it should leave that alone.

It could be that something in the V9 Sage.jar file has been written specifically to not use that function and if that's the case I have little control over that but I believe you previously tried a manual install of the V9 files and that worked...correct?

k

Yes I am doing a final test I restored back to my Version 9 with SageTV Decoder CC working. I will use your Install again just to double check. I expect the same result but I will let you know. A manual Install of the jar and STVI works fine.

[nyplayer]

It kills the SageTV decoder using the Install NO CC. The only way to get the decoder back is to uninstall SageTV9 and re-install SageTV 7. Then copy Sage 9 jar and STV.

I am going to try overlaying the files in COMMON with my backed up SageTV 9 see if that restores the Decoder. This did not work so there must be something in the SageTV folder itself that is being overlaid.

[jusjoken]

Originally Posted by nyplayer

It kills the SageTV decoder using the Install NO CC. The only way to get the decoder back is to uninstall SageTV9 and re-install SageTV 7. Then copy Sage 9 jar and STV.

I am going to try overlaying the files in COMMON with my backed up SageTV 9 see if that restores the Decoder. This did not work so there must be something in the SageTV folder itself that is being overlaid.

Do you have a test file you could upload somewhere for me to test with.

k

[nyplayer]

Originally Posted by jusjoken

Do you have a test file you could upload somewhere for me to test with.

k

You mean a short Video? That is not going to help because Installing breaks CC and SageTV Decoder. I mean you can just watch livetv turn on CC. Most Ota have CC.

[jusjoken]

Originally Posted by nyplayer

You mean a short Video? That is not going to help because Installing breaks CC and SageTV Decoder. I mean you can just watch livetv turn on CC. Most Ota have CC.

But I can change the installer as I test and see if i can narrow this down. I do not have a tuner on my virtual test environment so i would need to find a file that works.

k

[nyplayer]

Originally Posted by jusjoken

But I can change the installer as I test and see if i can narrow this down. I do not have a tuner on my virtual test environment so i would need to find a file that works.

k

Ok I will get you a small clip

Check your PM

[TechBill]

Originally Posted by SHS

I think in Bill case it would for his rip media as his TV recording are embed Closed Captioning with in video steam that direcely overlay on top of recording from satellite settop box unless he also doing ATSC/QAM recording then in that case you would be rigth Fuzzy but Note: Bill is deaf like me only more so then me.

Yes, I use DirectTV and CC is overlayed in recording so no problem there but I also use HDHomerun for my local channels so that where I would need the decoder to support CC


if there a paid version that would work with SageTV then great , I would like to know which ones because I would like to switch to SageTV 9 soon since I read somewhere that Gemstone is not supporting older version soon and !y family happens to like Gemstone

Both I and my wife are Deaf. I been Deaf since birth so we always relies on asssitance technology like CC ,

Bilk

[Fuzzy]

Originally Posted by TechBill

I would like to switch to SageTV 9 soon since I read somewhere that Gemstone is not supporting older version soon and !y family happens to like Gemstone

To clarify a bit. Gemstone as you are using it is not going away, and will continue to function as it always has in v7. Future development of Gemstone will be v9 only, but that in no way stops what you've currently got going.

[Narflex]

Originally Posted by jusjoken

Are you saying that installing this latest version on top of a licensed V7 install makes the SageTV Decoder no longer work ?

If that's the case I am at a loss as to why as I "believe" I have removed all the files involved in that decoder from the installer so in theory it should leave that alone.

It could be that something in the V9 Sage.jar file has been written specifically to not use that function and if that's the case I have little control over that but I believe you previously tried a manual install of the V9 files and that worked...correct?

k

Did you use the same product key as SageTV for your installer? (i.e. so that it's actually an upgrade of V7 rather than a whole new product that's being installed) If so (which is what I expected you to do), then the normal Windows upgrade process is to remove V7 and then install V9 as part of that...which would leave the original decoders gone. What I'm hoping is possible...is that there's a way to tell it not to remove those files as part of the upgrade process...or alternatively you could probably add custom scripting into the installer that detects if they're there, then makes backup copies of them so they don't get clobbered on the uninstall and then put them back where they were (and re-register them). This is definitely installer related though.

[jusjoken]

Originally Posted by Narflex

Did you use the same product key as SageTV for your installer? (i.e. so that it's actually an upgrade of V7 rather than a whole new product that's being installed) If so (which is what I expected you to do), then the normal Windows upgrade process is to remove V7 and then install V9 as part of that...which would leave the original decoders gone. What I'm hoping is possible...is that there's a way to tell it not to remove those files as part of the upgrade process...or alternatively you could probably add custom scripting into the installer that detects if they're there, then makes backup copies of them so they don't get clobbered on the uninstall and then put them back where they were (and re-register them). This is definitely installer related though.

No i am not as when i started this i did not have access to the original MSI to extract that nor the know how to know i should

But its a good idea as i have found a way to extract the MSI and in theory i can use Orca to find the upgradecode guid and use that in the v9 installer.

I will test that out and report back....unfortunately i have not found a way to test CC on my test machine so any suggestions to verify the old decoder is working would be helpful.

k

[jusjoken]

Originally Posted by Narflex

Did you use the same product key as SageTV for your installer? (i.e. so that it's actually an upgrade of V7 rather than a whole new product that's being installed) If so (which is what I expected you to do), then the normal Windows upgrade process is to remove V7 and then install V9 as part of that...which would leave the original decoders gone.

This first part is changed to use the same UpgradeCode as v7.1.9 of Sage products and I have tested all 3 and they did a proper inplace upgrade (remove old version and install new). This is a good improvement over what I had going before. The only downside to this is now the UpgradeCode is different from my previous beta installers so those testing will end up with an install OVER top of the previous v9 install (same files so no real issue). But this is better for the long term....thanks for pointing it out.

Now, I need to see if I can do part 2. I am still concerned as if I can accomplish the suggested I am not sure the end result would be different from my 2nd beta which is doing an in place install OVER v7 so in theory beta 0.002 (latest on BinTray) would have also left the V7 decoder files in place so in theory they should have still worked....but they did not.

Suggestions welcome as well as a simple way to test the decoder working and I will start to investigate a method to SAVE the decoder files from a previous V7 install

k

[TechBill]

Originally Posted by Fuzzy

To clarify a bit. Gemstone as you are using it is not going away, and will continue to function as it always has in v7. Future development of Gemstone will be v9 only, but that in no way stops what you've currently got going.

Yes, I understand but we like living on the edge and if supposedly a new features appear in Gemstone v9 that wasn't variable in v7 which we may like to have on our SageTV then it would mean upgrading to SageTV v9 to be able to use the new Gemstone features.

One thing that we wished if the tuner manufacture would actually decode the CC in their tuners instead of passing it over to the DVR to decode it. We like it when the CC is already decoded before it saved to the recording because it allow us to play back the recording in any players without having to find a player that support CC decoding (Keep in mind, CC and subtitles ARE NOT the same thing)

Maybe a bunch of us need to go email to HDHomeRun and ask them to put a CC decoder in their hardware instead of passing it over.

But I have to respect and be thankful to the HDHomeRun folks because many other tuner manufacturer would just strip out the CC and not pass it. It always been a pain to find right tuner each time we wanted to upgrade it.


But still thank you for looking into this and trying to make this possible for us Deaf folks so we can keep our CC if we move to v9

Bill

[jusjoken]

Originally Posted by jusjoken

This first part is changed to use the same UpgradeCode as v7.1.9 of Sage products and I have tested all 3 and they did a proper inplace upgrade (remove old version and install new).

Jeff,

When I change the v9 UpgradeCodes to match V7 I noticed that the Server and the Client installers share the SAME UpgradeCode so I mimicked that.

What that means though is that when I install the V9 Client OVER the V9 Server, the Server is removed leaving only the client.

Is that the expected result?

Since the Server can act as a client there is likely no reason to do this other than I tend to test them together at times so if no one has a concern over these being mutually exclusive....Server OR Client on the same machine, then this will work (I assume v7 would act the same but I did not test that yet).

PS: I still do not have a working CC with V7 so I have not made any progress on that issue. Not sure what is wrong as VLC shows the CC but I have not found a config in Sage V7 that does.

k

[jusjoken]

Originally Posted by jusjoken

Jeff,

When I change the v9 UpgradeCodes to match V7 I noticed that the Server and the Client installers share the SAME UpgradeCode so I mimicked that.

What that means though is that when I install the V9 Client OVER the V9 Server, the Server is removed leaving only the client.

Is that the expected result?

Since the Server can act as a client there is likely no reason to do this other than I tend to test them together at times so if no one has a concern over these being mutually exclusive....Server OR Client on the same machine, then this will work (I assume v7 would act the same but I did not test that yet).

I did some more testing as the V7 installers did allow Client and Server to be installed on the same machine. I found that I had the installer upgrade setting for "AllowSameVersionUpgrades" set to yes (to assist in testing as the version number does not change every time I build the installer and then test). When setting this to the default of no, I can now perform an install of the Client and Server on the same machine as V7 allows.

So ignore this question.

[wayner]

@jusjoken - your PM box is full.