Windows 64 bit Installer news

[Malfunction]

Has anyone gotten this working with the Hauppauge HD-PVR2 IR blaster for channel changing on a cable box? I have it hooked up and I know it works with its' own software.

[JustFred]

Originally Posted by Malfunction

Has anyone gotten this working with the Hauppauge HD-PVR2 IR blaster for channel changing on a cable box? I have it hooked up and I know it works with its' own software.

I've got 9.2.0 installer v1.104 loaded, and tested it with both the HVR-2250 and WinTV-QuadHD (both IR-capable cards). Haven't specifically tried Sage-IR with the HD-PVR due to Hauppauge's lame limitation where they only allow any IR app to control a **single** capture card/device (no matter how many are installed). Can't remember whether this is the very first or very last Hauppauge device that was installed. This made it difficult to test all possible devices.

Does HCW's BlastCfg cause the IR emitter to blink?

Internally, Sage just talks to "THE" Hauppauge IR, without any knowledge of exactly which Hauppauge device is driving the emitter.

If there's a problem, posting the Sage log (sagetv_0.txt) from when the event occurs might prove useful. You might have to zip it up. Posting the Installer logs (in C:\Users\<USERNAME>\AppData\Local\Temp) might also give clues.

[SHS]

If I recall right it the first driver that get install which can be very tricky under Windows OS even with WinTV which why you want to have USB-UIRT unlike with Linux OS which can support mulit Hauppauge IR blaster.

[jptheripper]

can a 64bit client hook to a 32bit server?

[wnjj]

Originally Posted by jptheripper

can a 64bit client hook to a 32bit server?

Yes.

[Malfunction]

Originally Posted by JustFred

I've got 9.2.0 installer v1.104 loaded, and tested it with both the HVR-2250 and WinTV-QuadHD (both IR-capable cards). Haven't specifically tried Sage-IR with the HD-PVR due to Hauppauge's lame limitation where they only allow any IR app to control a **single** capture card/device (no matter how many are installed). Can't remember whether this is the very first or very last Hauppauge device that was installed. This made it difficult to test all possible devices.

Does HCW's BlastCfg cause the IR emitter to blink?

Internally, Sage just talks to "THE" Hauppauge IR, without any knowledge of exactly which Hauppauge device is driving the emitter.

If there's a problem, posting the Sage log (sagetv_0.txt) from when the event occurs might prove useful. You might have to zip it up. Posting the Installer logs (in C:\Users\<USERNAME>\AppData\Local\Temp) might also give clues.

I haven't been able to get far enough into this to be looking at log files. I'm asking about how to install it. How do I get SageTV to recognize the Hauppauge IR blaster? I would just use my USB-UIRT, but I use EventGhost and that won't coxist with any 64-bit USB-UIRT driver.

I've only got one HD-PVR 2 running, so identification wouldn't be a problem. BlastCfg will change the digits on the cable box. I haven't gotten to the point where I can change channels on the cable tuner from 64-bit SageTV. The only other thing that doesn't work for me is the Winamp kludge.

My other Hauppauge device is a dual USB tuner for the antenna. It changes channels over USB and has not had any issues.

[trk2]

I was concerned with this post and its implications for new users since AC3Filter has been removed from the installer and LAV used in its place. I'm creating this post as a reminder until I get the time to look into the issue or if anyone else wants to investigate.

[phelme]

I'm following this thread with great interest.

I'm running PrimeNetEncoder to do my HDHomeRun capturing rather than OpenDCT. Anyone know if it will be compatible or will I need to switch?

I think the author of it is still around...

[JustFred]

Originally Posted by phelme

I'm running PrimeNetEncoder to do my HDHomeRun capturing rather than OpenDCT. Anyone know if it will be compatible or will I need to switch?

I'm running Sage-64 with SageDCT with a HdHomeRun Prime and Ceton InfiniTV-4. Everything works fine. Since SageTV sees SageDCT, PrimeNetEncoder and OpenDCT all as network devices, the likelihood of problems is low.

[SHS]

Originally Posted by phelme

I'm following this thread with great interest.

I'm running PrimeNetEncoder to do my HDHomeRun capturing rather than OpenDCT. Anyone know if it will be compatible or will I need to switch?

I think the author of it is still around...

It should just fine as it Java
Install SageTV 64 you can also go back 32 bit ver as long you keep a copy of it.

[phelme]

Originally Posted by JustFred

I'm running Sage-64 with SageDCT with a HdHomeRun Prime and Ceton InfiniTV-4. Everything works fine. Since SageTV sees SageDCT, PrimeNetEncoder and OpenDCT all as network devices, the likelihood of problems is low.

Originally Posted by SHS

It should just fine as it Java
Install SageTV 64 you can also go back 32 bit ver as long you keep a copy of it.

cool. I'll try a test upgrade today. Maybe now I can actually run Gemstone. Thanks!

[JustFred]

Originally Posted by phelme

cool. I'll try a test upgrade today. Maybe now I can actually run Gemstone. Thanks!

Heap size shouldn't be a limitation any more. One caveat: by default, babgvant's "SageTV Registry Settings.exe" tool will tweak the wrong JVMMaxHeapSizeMB key under Wow6432Node; that's only for Sage-32. You want the same key that occurs earlier in the registry.

[Tiki]

Originally Posted by wnjj

Just to confirm, this is missing on the beta 32-bit (and 64-bit) but works on the released 32-bit V9?

Sorry, I forgot to respond to this post earlier...

Yes (at least I think so).

I was previously running Sage on a different machine (Windows 7 Pro on AMD Athlon II) and it worked there. I was not on the latest release but an earlier version of Sage 9 (9.1.2).

Now I am running the beta version on a Windows 10 Pro machine with AMD Ryzen 5 2400G processor.

The old machine had the AC3 Filter software that was previously supplied with Sage (it did not have LAV installed). The new machine is using the LAV filters installed with the new installer (it does not have AC3 Filter installed).

So, there are a lot of differences - hard to say where the cause lies.

[Tiki]

Originally Posted by Tiki

I think we need a new driver. The 64-bit USBUIRT drivers you provided do not allow me to use the USB-UIRT for both send and receive at the same time when using 64-bit Sage in service mode. It does not seem to matter if I use the default account or a user account for the Sage service.

32-bit Sage Stand-Alone mode: Works as transmitter and receiver
32-bit Sage Service mode: Works as transmitter and receiver
64-bit Sage Stand-Alone mode: Works as transmitter and receiver
64-bit Sage Service mode: Doesn't work (can be transmitter or receiver, but not both).

Has there been any progress on this issue?
Has anyone gotten the USBUIRT to work as both transmitter and receiver in 64-bit Service mode?

[wnjj]

Originally Posted by Tiki

Sorry, I forgot to respond to this post earlier...

Yes (at least I think so).

I was previously running Sage on a different machine (Windows 7 Pro on AMD Athlon II) and it worked there. I was not on the latest release but an earlier version of Sage 9 (9.1.2).

Now I am running the beta version on a Windows 10 Pro machine with AMD Ryzen 5 2400G processor.

The old machine had the AC3 Filter software that was previously supplied with Sage (it did not have LAV installed). The new machine is using the LAV filters installed with the new installer (it does not have AC3 Filter installed).

So, there are a lot of differences - hard to say where the cause lies.

On the OS front, I think there was a legit issue with Windows 10 detection, of which the volume control may be a victim. This code uses the 'VISTA_OS' flag to decide how to handle the volume: https://github.com/google/sagetv/blo...ayer.java#L498 I'm not exactly sure how all of this works but when I see that conditional code in there I suspect that may be related.

My last code push included a fix which should detect Win10. I don't recall if that made it into the latest beta. Sorry, with some time away from this my memory starts to get fuzzy. Maybe Jusjoken can confirm. This bug would happen on older V9 versions on Win10 as well.

[wnjj]

Originally Posted by Tiki

Has there been any progress on this issue?
Has anyone gotten the USBUIRT to work as both transmitter and receiver in 64-bit Service mode?

I wrote Jon and haven't heard back. I'll ping him again in a day or two. If you can run in application mode they'll both work. I know that's been a philosophical discussion on here before but I've been running that way for 10 years with auto-reboots & power outages and no missed recordings or other ill effects.

[jusjoken]

Originally Posted by wnjj

On the OS front, I think there was a legit issue with Windows 10 detection, of which the volume control may be a victim. This code uses the 'VISTA_OS' flag to decide how to handle the volume: https://github.com/google/sagetv/blo...ayer.java#L498 I'm not exactly sure how all of this works but when I see that conditional code in there I suspect that may be related.

My last code push included a fix which should detect Win10. I don't recall if that made it into the latest beta. Sorry, with some time away from this my memory starts to get fuzzy. Maybe Jusjoken can confirm. This bug would happen on older V9 versions on Win10 as well.

No. We have not had a release that included those commits.

I have been waiting for the last few items that are being discussed here to be resolved first.

k

[wnjj]

Originally Posted by wnjj

On the OS front, I think there was a legit issue with Windows 10 detection, of which the volume control may be a victim. This code uses the 'VISTA_OS' flag to decide how to handle the volume: https://github.com/google/sagetv/blo...ayer.java#L498 I'm not exactly sure how all of this works but when I see that conditional code in there I suspect that may be related.

My last code push included a fix which should detect Win10. I don't recall if that made it into the latest beta. Sorry, with some time away from this my memory starts to get fuzzy. Maybe Jusjoken can confirm. This bug would happen on older V9 versions on Win10 as well.

Can someone with Windows 10 confirm whether the volume control is broken on V7 or older V9 installs? Problem is described here: https://forums.sagetv.com/forums/sho...&postcount=293

[trk2]

Originally Posted by wnjj

Can someone with Windows 10 confirm whether the volume control is broken on V7 or older V9 installs? Problem is described here: https://forums.sagetv.com/forums/sho...&postcount=293

I have a V9 client on Windows 10. Volume control works just fine. The audio output is 5.1 analog. If Tiki is using HDMI for the audio output then perhaps this is the expected behavior? I believe PCM digital audio volume can be adjusted because it is a digital representation of an analog soundwave, but other audio formats must be decoded to analog first to have the volume adjusted. This is why the HD300 can control volume on audio it outputs as PCM but not audio it bitstreams.

[Tiki]

Originally Posted by trk2

I have a V9 client on Windows 10. Volume control works just fine. The audio output is 5.1 analog. If Tiki is using HDMI for the audio output then perhaps this is the expected behavior? I believe PCM digital audio volume can be adjusted because it is a digital representation of an analog soundwave, but other audio formats must be decoded to analog first to have the volume adjusted. This is why the HD300 can control volume on audio it outputs as PCM but not audio it bitstreams.

I am using hdmi direct from pc to tv, but that is same as before.