Open Source Windows Installer

[jusjoken]

Originally Posted by HelenWeathers

Everything installed to c:\sagetv with the exception of the StrmDeMux.ax file failing to register as far as I can tell.

Also, sage 7 installs on win 10 to c:\sagetv without issue.

I just verified the issue. You will find that the install placed a number of the files in the Program File folder even though you selected a custom folder in the options.

I know where the issue is and I will fix it in beta 0.003.

Thanks for finding this.

k

[HelenWeathers]

I'm not sure if this has anything to do with installation itself, but my java heap max value in sage setup > system information shows 779 mb no matter what I do in regedit. I've been running at 500hex in win7 sage7 & sage9 win10 for months now (1297mb). I did try 400hex but no matter the value in regedit sage seems to be locked in at approx 300hex on my sage9, win10 pc.

[wubdich]

Changing registry permissions (full access to all users) on "HKLM\Software\Frey Technologies" (32bit OS) or "HKLM\Software\Wow6432Node\Frey Technologies" (64bit OS) will solve the problem.

[HelenWeathers]

Originally Posted by wubdich

Changing registry permissions (full access to all users) on "HKLM\Software\Frey Technologies" (32bit OS) or "HKLM\Software\Wow6432Node\Frey Technologies" (64bit OS) will solve the problem.

I may have been a bit unclear in what I was saying

I'm not having issues with changing the settings with regedit. They stay where I set them. (was the JVMMaxHeapSizeMB moved to a new location??)

But in the sage ui under settings, system information with 500hex or 400hex I still see 779mb for max heap on the pc and also on my extenders since using the new v9 windows installer. I may try lower values today to test 300 & 200 hex.

[nyplayer]

Originally Posted by HelenWeathers

I may have been a bit unclear in what I was saying

I'm not having issues with changing the settings with regedit. They stay where I set them. (was the JVMMaxHeapSizeMB moved to a new location??)

But in the sage ui under settings, system information with 500hex or 400hex I still see 779mb for max heap on the pc and also on my extenders since using the new v9 windows installer. I may try lower values today to test 300 & 200 hex.

That sounds exactly what I had reported here.

http://forums.sagetv.com/forums/show...1&postcount=69

[HelenWeathers]

Originally Posted by nyplayer

That sounds exactly what I had reported here.

http://forums.sagetv.com/forums/show...1&postcount=69

Thank you! I may not be nuts. I had not seen your post. In regedit, I can't seach (edit/find) JVMMaxHeapSizeMB for some reason in Win10 but when I search Frey I find two folders with SageTV subfolders with the JVMMaxHeapSizeMB definition. One is under current user and one is under local machine on my w10 pc.

Changing them may do something - but SageTV UI doesn't show it.

[nyplayer]

It appears that the open source is not reading the correct registry entry or does not have permission in a 64 bit system.

[phantomii]

So I am having the same issue and experience with the java heap settings on version 9. I am also having an issue with my Collosus capture card on version 9 which seems to be related to reading the registry by version 9 according to Jeff in this post: http://forums.sagetv.com/forums/show...3&postcount=18

Not sure this is actually as similar as it seems to me, nor am I confident that my system does not have another issue, it just seems I have seen a few post on version 9 an registry issues. Any thoughts would be great and if I can help let me know.......

[HelenWeathers]

Originally Posted by nyplayer

It appears that the open source is not reading the correct registry entry or does not have permission in a 64 bit system.

My system is Win 10/32 so not just in 64 bit win..

[HelenWeathers]

Originally Posted by phantomii

.....Not sure this is actually as similar as it seems to me, nor am I confident that my system does not have another issue, it just seems I have seen a few post on version 9 an registry issues.......

Did you check to see if you have the entry Jeff mentioned for AdditionalCaptureSetups and that the listings for he Colossus were there? There should be listings for a number of different tuners there. Mine is fully populated but that may be from an older sage install that didn't get completely removed when I uninstalled sage 7.

[phantomii]

My registry includes many AdditionalCaptureSetups including all of these that reference my Colossus Card so I am not sure why V9 does not see them.

xxxx\Common\AdditionalCaptureSetups\Hauppauge Colossus Capture 0
xxxx\Common\AdditionalCaptureSetups\Hauppauge Colossus Capture 1
xxxx\Common\AdditionalCaptureSetups\Hauppauge Colossus Capture 2
xxxx\Common\AdditionalCaptureSetups\Hauppauge Colossus Capture 3
xxxx\Common\AdditionalCaptureSetups\Hauppauge Colossus Capture 4
xxxx\Common\AdditionalCaptureSetups\Hauppauge Colossus Capture 5
xxxx\Common\AdditionalCaptureSetups\Hauppauge Colossus Capture 6
xxxx\Common\AdditionalCaptureSetups\Hauppauge Colossus Capture 7

I can tell you that with a fresh Version 7 install I can watch live TV. Copying the Version 9 exe and JAR Files over the version 7 install brakes live TV Viewing. But recopying the original version 7 files over the version 9 file restores live tv viewing. This leads me to believe the version 9 files are not changing the Registry, they are simply having issues reading the registry.

[HelenWeathers]

I would just sit back and wait for the next installer revision to be released and some of the registry issues to be addressed. Stay with your working setup for now.

[phantomii]

Yes, that is what I plan to do. I am staying on my licensed copy of version 7 for now as that is fully functional and will wait till someone figures out the Registry issues. I assume this may show itself in some strange behaviors that users will stumble on as time moves forward. For now, that and the Java Heap issues are my main challenges which I believe (and think others may as well) are related. Have a great day!

[Narflex]

Just a note...I made a post in the other thread about the Windows Executable which may give a clue to what's up with the executable permissions for reading the registry.

[jusjoken]

Originally Posted by Narflex

    if (!strcmp("SageTV MPEG Video Decoder", cName)|| !strcmp( "SageTV MPEG-2 Video Decoder", cName ) )
    {
        if (GetRegistryDword(HKEY_LOCAL_MACHINE, "SOFTWARE\\Frey Technologies\\Common\\DSFilters\\MpegDec",
                "EnableDXVA", 0))
        {
            slog((env, "Using DXVA Enabled SageTV MPEG-2 Video Decoder\r\n"));
            hr = FindFilterByName(&pFilter, CLSID_LegacyAmFilterCategory, "SageTV MPEG-2 Video Decoder");
        }
        else
        {
            slog((env, "Using legacy SageTV MPEG Video Decoder\r\n"));
            hr = FindFilterByName(&pFilter, CLSID_LegacyAmFilterCategory, "SageTV MPEG Video Decoder");
        }
    }
    else
        hr = FindFilterByName(&pFilter, CLSID_LegacyAmFilterCategory, cName);

Jeff,

I wonder if you can check the code and see if there is a similar type of change to make to get the audio working.

I have narrowed down the video filter and what files I need the installer to retain from a V7 install to get CC working (I was missing some MS runtimes that seem to be used by only these filters) BUT I now seem to have no sound and it looks to my untrained eye that there may be similar code that needs implementing to get the audi working if the filter exists.

Thanks
k

[jusjoken]

Originally Posted by jusjoken

Jeff,

I wonder if you can check the code and see if there is a similar type of change to make to get the audio working.

I believe I have found the audio issue and it seems related to the install of the AC3Filter package. I will dig deeper and let you know what I find but once I manually register the AC3Filter I have audio so no need to dig into the code to see if there was an issue.

Thanks
k

[SHS]

So where the SageJar-9.0.3.214.zip or just still 9.0.3.194

Oh besure add registry to install for HD-PVR 2 and Colossus 2

32bit
[HKEY_LOCAL_MACHINE\SOFTWARE\Frey Technologies\Common\AdditionalCaptureSetups\Hauppauge Siena Video Capture]
"CaptureMask"=dword:00000800
"ChipsetMask"=dword:00100000

64bit
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\Common\AdditionalCaptureSetups\Hauppauge Siena Video Capture]
"CaptureMask"=dword:00000800
"ChipsetMask"=dword:00100000

[jusjoken]

Originally Posted by SHS

So where the SageJar-9.0.3.214.zip or just still 9.0.3.194

I do not believe anyone has posted a 214 build for the jar or the linux install files. My windows java setup is not ready to build those and post them so someone else will need to.

The 214 jar is embedded in the windows installer though.

Originally Posted by SHS

Oh besure add registry to install for HD-PVR 2 and Colossus 2

32bit
[HKEY_LOCAL_MACHINE\SOFTWARE\Frey Technologies\Common\AdditionalCaptureSetups\Hauppauge Siena Video Capture]
"CaptureMask"=dword:00000800
"ChipsetMask"=dword:00100000

64bit
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\Common\AdditionalCaptureSetups\Hauppauge Siena Video Capture]
"CaptureMask"=dword:00000800
"ChipsetMask"=dword:00100000

This is one that is not in the current installer as I only grabbed what V7 already creates. I can add this if you wish.

PS: the Wow6432Node will be created automagically on a 64 bit system so I only need to setup the installer to create the one and depending on the system the "Wow6432Node" may get created.

k

[brianrent]

I used the client install and also had audio issues. Once I manually installed the AC3 filter it worked fine. I would rather install this separately because i noticed on the old installer (version 7) Sage would use the very outdated version even if I installed the latest version in my system. I suppose you could have it install as a separate installer package that way it could be uninstalled through ADD\REMOVE programs in windows but that was not an option in the version 7 installer.

[SHS]

Originally Posted by jusjoken

I do not believe anyone has posted a 214 build for the jar or the linux install files. My windows java setup is not ready to build those and post them so someone else will need to.

The 214 jar is embedded in the windows installer though.

This is one that is not in the current installer as I only grabbed what V7 already creates. I can add this if you wish.

PS: the Wow6432Node will be created automagically on a 64 bit system so I only need to setup the installer to create the one and depending on the system the "Wow6432Node" may get created.

k

I know that not ready jusjoken
Ok I wasn't were Wow6432Node was be created automagically
Hopelly later on I be able give the registry info for newer HD-PVR 60 but for now it dose see the HDMI Input so SageTV think it a Tuner I'm sure it just some that Hauppauge forgot to add inf or need make change to driver as there other software can't even see Video or Audio input to be sel.