Windows 64 bit Installer news

[SteveW]

So just to clarify where things are at for the moment, Sage 64 bit does or does not work with USBUIRT and HDPVR’s at the moment?

[wnjj]

Originally Posted by SteveW

So just to clarify where things are at for the moment, Sage 64 bit does or does not work with USBUIRT and HDPVR’s at the moment?

Does not. We should have HDPVR working really soon if it's the "Hauppauge IR blaster" referred to above. You'll have to forgive my ignorance of which vendor builds which hardware and what is needed in SageTV for support. I only run an ATSC HDHR vanilla setup.

USBUIRT is in the works. No ETA yet.

[SHS]

Originally Posted by SteveW

So just to clarify where things are at for the moment, Sage 64 bit does or does not work with USBUIRT and HDPVR’s at the moment?

That right it dose not work with USB-UIRT nor Hauppauge IR blaster
The HDPVR them self do record video with no problem what so ever

[MattHelm]

Shouldn't the iTach IR2IP would on either 32 or 64 systems?

[wnjj]

Originally Posted by MattHelm

Shouldn't the iTach IR2IP would on either 32 or 64 systems?

I'm not familiar with that one but I'll try to explain generically what should and should not work and why:

Any application that connects to a DLL needs to have a DLL that matches the architecture of the application (i.e. 32-32 or 64-64). The way SageTV supports external tuners is by way of plugin DLL's that reside in SageTV/Common. A few known ones were listed above (Actisys, USB-UIRT and Hauppauge). I've also come to understand there's a more generic one (EXEMultiTunerPlugin) that can call an external EXE with custom parameters. This can support any other device that offers an EXE command line program to operate it. The EXE can still be 32-bit since it runs as a separate process.

As of right now, none of these are in the 64-bit build but I now believe I can build the Hauppauge and EXEMultiTunerPlugin ones with what I have already plus a little effort. Actisys drivers may be available if you contact them and I'm already working on getting one for USB-UIRT.

[Ghildebr]

I did a test install of the x64 bit code on my SageTV server. Prior to doing that I stopped the SageTV 9 Service. I took the default install directories so that I could have both versions installed at the same time. Every time I tried to add a tuner to the x64 bit install I would get an application fault.

Here is the output for when I tried to add the tuner from the SageTV 9 x64 client:

Faulting application name: SageTV.exe, version: 9.2.0.0, time stamp: 0x5c03334c
Faulting module name: ntdll.dll, version: 10.0.14393.2608, time stamp: 0x5bd133d4
Exception code: 0xc0000374
Fault offset: 0x00000000000f7b43
Faulting process id: 0x1440
Faulting application start time: 0x01d48c31d53a12d2
Faulting application path: C:\Program Files\SageTV\SageTV\SageTV.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 5dd02971-ec17-4612-b91a-8ee940c381e4
Faulting package full name:
Faulting package-relative application ID:


Here is the output for when I tried to add the tuner with the x64 SageTV Service running:

Faulting application name: SageTVService.exe, version: 9.2.0.0, time stamp: 0x5c03335b
Faulting module name: ntdll.dll, version: 10.0.14393.2608, time stamp: 0x5bd133d4
Exception code: 0xc0000374
Fault offset: 0x00000000000f7b43
Faulting process id: 0x38d0
Faulting application start time: 0x01d48c3196387c86
Faulting application path: C:\Program Files\SageTV\SageTV\SageTVService.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 55fbf92e-39d5-4e7e-967f-25b7b7c25a72
Faulting package full name:
Faulting package-relative application ID:

It didn't matter whether I was doing it remotely through a Placeshifter client or the SageTV Client. The server itself is headless so I have to configure things remotely in order to get playback with sound and video.

This is running on Windows Server 2016 and has been for quite some time. It works flawless when I use the 32 bit version of Sage. Just a fyi, I moved to Server 2008 R2, then to Server 2012, and finally to Server 2016 for stability reasons. On the Server platform I never have issues. Usually reboot once a month for updates and have as many as 5 clients using the box at the same time. I can't say the same when I was running on XP or Windows 8 for that matter. I never tried 8.1 or 10 because of the stability of the Server product.

Gary

[wnjj]

Originally Posted by wnjj

I'm not familiar with that one but I'll try to explain generically what should and should not work and why:

Any application that connects to a DLL needs to have a DLL that matches the architecture of the application (i.e. 32-32 or 64-64). The way SageTV supports external tuners is by way of plugin DLL's that reside in SageTV/Common. A few known ones were listed above (Actisys, USB-UIRT and Hauppauge). I've also come to understand there's a more generic one (EXEMultiTunerPlugin) that can call an external EXE with custom parameters. This can support any other device that offers an EXE command line program to operate it. The EXE can still be 32-bit since it runs as a separate process.

As of right now, none of these are in the 64-bit build but I now believe I can build the Hauppauge and EXEMultiTunerPlugin ones with what I have already plus a little effort. Actisys drivers may be available if you contact them and I'm already working on getting one for USB-UIRT.

Scratch the Hauppauge off the list...I just figured out that the source code wraps their driver DLL (hcwirblast.dll) which we don't have in 64-bit. Looking at the EXEMultiTunerPlugin one next.

[wnjj]

Originally Posted by Ghildebr

I did a test install of the x64 bit code on my SageTV server. Prior to doing that I stopped the SageTV 9 Service. I took the default install directories so that I could have both versions installed at the same time. Every time I tried to add a tuner to the x64 bit install I would get an application fault.

Here is the output for when I tried to add the tuner from the SageTV 9 x64 client:

Faulting application name: SageTV.exe, version: 9.2.0.0, time stamp: 0x5c03334c
Faulting module name: ntdll.dll, version: 10.0.14393.2608, time stamp: 0x5bd133d4
Exception code: 0xc0000374
Fault offset: 0x00000000000f7b43
Faulting process id: 0x1440
Faulting application start time: 0x01d48c31d53a12d2
Faulting application path: C:\Program Files\SageTV\SageTV\SageTV.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 5dd02971-ec17-4612-b91a-8ee940c381e4
Faulting package full name:
Faulting package-relative application ID:


Here is the output for when I tried to add the tuner with the x64 SageTV Service running:

Faulting application name: SageTVService.exe, version: 9.2.0.0, time stamp: 0x5c03335b
Faulting module name: ntdll.dll, version: 10.0.14393.2608, time stamp: 0x5bd133d4
Exception code: 0xc0000374
Fault offset: 0x00000000000f7b43
Faulting process id: 0x38d0
Faulting application start time: 0x01d48c3196387c86
Faulting application path: C:\Program Files\SageTV\SageTV\SageTVService.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 55fbf92e-39d5-4e7e-967f-25b7b7c25a72
Faulting package full name:
Faulting package-relative application ID:

It didn't matter whether I was doing it remotely through a Placeshifter client or the SageTV Client. The server itself is headless so I have to configure things remotely in order to get playback with sound and video.

This is running on Windows Server 2016 and has been for quite some time. It works flawless when I use the 32 bit version of Sage. Just a fyi, I moved to Server 2008 R2, then to Server 2012, and finally to Server 2016 for stability reasons. On the Server platform I never have issues. Usually reboot once a month for updates and have as many as 5 clients using the box at the same time. I can't say the same when I was running on XP or Windows 8 for that matter. I never tried 8.1 or 10 because of the stability of the Server product.

Gary

That's certainly troubling and those crash reports are pretty generic. What was the last thing in the sagetv_0.txt log file on the server? Did this happen right when you picked the 'add new source' menu option or when you picked a particular source from the list?

[wnjj]

Originally Posted by davidb

Is the issue with the ethernet channel change the exeMultiTunerPlugin.dll or the dvTune.exe?
If it's the exeMultiTunerPlugin.dll is the source still available? I see Narflex offered to freely give it out on a post from 9/5/2003.

David

So I managed to compile a 64-bit EXEMultiTunerPlugin.dll. It's pretty much the TunerStubDll with 'MacroTune' function defined to call into the exe referenced in the registry. If anyone on here uses that and wants to try, put the attached .DLL into SageTV\Common of your 64-bit install.

[Ghildebr]

Originally Posted by wnjj

That's certainly troubling and those crash reports are pretty generic. What was the last thing in the sagetv_0.txt log file on the server? Did this happen right when you picked the 'add new source' menu option or when you picked a particular source from the list?

Well after playing with it for over an hour I was finally able to add 1 of my 6 tuners. I had to add that tuner directly from the server but not scan for channels. That tuner now works remotely. I am still unable to add a second tuner without having a crash occur. Here is the file you requested. I hope it sheds some light on the issue.

Error occurs as soon as I pick the Digital Tuner. I am not sure why it worked to add the tuner locally. I have never done that due to the fact that there is no sound card on the server.

Gary

[JustFred]

I've had a number of issues with the installation of v1.102, but was delaying my report until after I did a Repair of Win7. After seeing Ghildebr's 1st post above, it appears I might not be alone. So here goes some initial observations:

Environment:
OS: Win7pro x64 SP1
Java v1.8u131 32-bit of 20170315 jre-8u131-windows-i586 and
Java v1.8u141 64-bit of 20170718 jre-8u141-windows-x64
Sage v9.1.10 (x86), with its Service disabled.

Installed AC3Filter via command-line (to avoid OpenCandy):
ac3filter_2_6_0b.exe /NOCANDY

Lastly, installed: SageTVSetupx64_9.2.0_beta_1.102.exe
Did this as a fresh install; didn't import any old files from Sage-x86.
Edited registry to increase heap size to 0x800. (Later verified in Sage.)

Started the SageTV64 Service on the above machine.

All further interaction below done is from PlaceShifter (v9.1.10, x86) on another box.

Attempted to add a tuner (Hauppauge HVR-1600)
Source: Hauppauge WinTV 418 TS Capture Digital TV Tuner,
Lineup: Local Over the Air Broadcast - 94086 (sdepg)
Started channel scan:
"Watch request failed. ERROR (-12): There was a null object requested to playback - OK"

2nd attempt to add the same tuner and do a channel scan succeeded.
Channel preview: successful

Attempted to add HDHR tuner :
SageTv64 service (on the server) crashed!

Windows event log (on the server):

Faulting application name: SageTVService.exe, version: 9.2.0.0, time stamp: 0x5c03335b
Faulting module name: ntdll.dll, version: 6.1.7601.24291, time stamp: 0x5be7857f
Exception code: 0xc0000374
Fault offset: 0x00000000000bf302
Faulting process id: 0xd60
Faulting application start time: 0x01d48ab2791cba80
Faulting application path: C:\Program Files\SageTV\SageTV\SageTVService.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 9922dd1e-f6a6-11e8-bfba-001fd0db2e70

Many repeated attempts to add the HDHR tuner result in the same failure.

Back on the server:
Somewhere thru the above process, it appears that something in the Kernel has become corrupt. Attempting to launch other apps that would normally be able to access Hauppauge tuners (Hauppauge WinTv8, Hauppauge Capture) fail. Rebooting the server was needed to allow the Hauppage video apps to access Hauppauge tuners again.

After rebooting the server, I added the following capture devices to Sage:
Hauppauge HVR-2250 (WinTv-7164)
hauppauge HVR-QuadHD (WinTV 885 TS Capture)
Hauppauge HD-PVR

But each time, Sage put up an on-screen error message upon initial install of each device. Without any intervening restart of the OS or Sage, going back into Setup for the device allowed me to finish config. and preview channels without any obvious issues. A superficial check of watching live TV from each configured video source seems to work.

I'm still unable to add the HDHR tuner. The SageTV64 service stops each time.

The sequence of events (performed via PlaceShifter) is:
Please select the input on the Silicondust HDHomeRun Tuner
I select "Digital TV Tuner" and click "Continue".
Progress bar appears: "The Broadcast Standard is being determined".
Several seconds later, the SageTV64 Service dies.

Attempting to access the HDHR tuner via HDHomeRun QuickTV fails: "tuner not available or in use"

See the log file "Crash adding HDHR tuner - sagetv_0.txt"
In the logfile, look around Tue 12/4 19:08:16.869 for the final gasp.
Windows eventlog entry from a previous crash is above.

[wnjj]

Good info and detail there Fred. Do you happen to see any hs_err_pid* files in the SageTV directory? Those will show up when Java crashes and can often help narrow down where.

Have you tried using an edited 32-bit properties file to see if the HDHR tuners work? This may just be an issue in the setup/scan code.

[JustFred]

Originally Posted by wnjj

Good info and detail there Fred. Do you happen to see any hs_err_pid* files in the SageTV directory? Those will show up when Java crashes and can often help narrow down where.

No.. none present.

The failures I'm seeing look similar to the the kind of crashes I dealt with in the Native code when I first ported Sage from VS2005 -> VS2015. At that time I fixed a lot of mis-matched memory models used for compiling the various modules. It made for some pretty spectacular Kernal corruption.

Have you tried using an edited 32-bit properties file to see if the HDHR tuners work? This may just be an issue in the setup/scan code.

No, I intentionally haven't tried that yet. My goal was to start with a clean install without bringing any old baggage. I'll try "migration" after testing a few more things with the current config.

[SHS]

Originally Posted by wnjj

So I managed to compile a 64-bit EXEMultiTunerPlugin.dll. It's pretty much the TunerStubDll with 'MacroTune' function defined to call into the exe referenced in the registry. If anyone on here uses that and wants to try, put the attached .DLL into SageTV\Common of your 64-bit install.

SageTV see the Plug-in now

[SHS]

Originally Posted by wnjj

Good info and detail there Fred. Do you happen to see any hs_err_pid* files in the SageTV directory? Those will show up when Java crashes and can often help narrow down where.

Have you tried using an edited 32-bit properties file to see if the HDHR tuners work? This may just be an issue in the setup/scan code.

I tested a fresh new install and from the look of it I say the root problem get down to LoadTuneTable ATSC as I had no luck with Hauppauge HVR-QuadHD (WinTV 885 TS Capture), it work fine when copy over the old files even scanning for new channel when with out any problem
My HD-PVR 2 and HD-PVR 60 where no problem add them in

[Narflex]

Have you tried putting a NATIVE_LOG.ENABLE file in the SageTV program folder and then seeing if it creates a Native.log file? That may give additional info on where the crash is occurring. It sounds like it might be in the broadcast standard detection code...which is somewhat complicated (and unfortunately I'm not familiar with it).

It's also probably worth it to compare the log files from a 32-bit run vs. a 64-bit run to see how they differ...in fact, that will likely be the most productive path to take in my experience with capture device issues in SageTV like this. I'd just trim off the timestamps from them and use a diff program...I'm more than happy to do that for you guys if you post two logs (one from 32bit and the other from 64bit) and each performed the exact same steps on a fresh config. And I'm referring to just the sagetv_0.txt log file.

[SHS]

Thanks for bring that up I forgot that option

[wnjj]

Originally Posted by Narflex

Have you tried putting a NATIVE_LOG.ENABLE file in the SageTV program folder and then seeing if it creates a Native.log file? That may give additional info on where the crash is occurring. It sounds like it might be in the broadcast standard detection code...which is somewhat complicated (and unfortunately I'm not familiar with it).

It's also probably worth it to compare the log files from a 32-bit run vs. a 64-bit run to see how they differ...in fact, that will likely be the most productive path to take in my experience with capture device issues in SageTV like this. I'd just trim off the timestamps from them and use a diff program...I'm more than happy to do that for you guys if you post two logs (one from 32bit and the other from 64bit) and each performed the exact same steps on a fresh config. And I'm referring to just the sagetv_0.txt log file.

Thanks for the tips. I'm getting closer and it is indeed crashing somewhere in the tuning code. There's a lot going on in there. As of a few minutes ago I can reproduce the crash on my setup here so now can quickly add any debug logging needed. The last thing I'm seeing in Native.log is "Tune Channel (slot:0) ATSC ...".

Since your answer isn't "oh yeah, that because of X", it sounds like I'll have to beat through this one but I now have what I need.

[SHS]

Just in case there my logs from both 32 and 64

[SHS]

OPS wrong log