9.2.1 (32 bit) changes channels erratically

[JeffHaas]

Since upgrading to 9.2.1 (32 bit), I have a lot of recordings where the channel has not been changed, and the program recorded is on a previously tuned channel. However this isn't true for all recordings, there are some that record correctly. I haven't spotted a pattern yet.

I'm running Win 7 in 32 bit mode. Card is Hauppage Colossus 2, I'm using the IR blaster built into the card.

How do I downgrade? The previous build, 9.1.9, worked fine.

[JustFred]

Originally Posted by JeffHaas

How do I downgrade? The previous build, 9.1.9, worked fine.

Easy: run the installer for v9.1.9

[JeffHaas]

Yes, but won't the installer recognize that a newer version is installed? I've never downgraded, if I uninstall the current build, can I back up config files and copy them back after the install?

[tmiranda]

Originally Posted by JeffHaas

Since upgrading to 9.2.1 (32 bit), I have a lot of recordings where the channel has not been changed, and the program recorded is on a previously tuned channel. However this isn't true for all recordings, there are some that record correctly. I haven't spotted a pattern yet.

I'm running Win 7 in 32 bit mode. Card is Hauppage Colossus 2, I'm using the IR blaster built into the card.

How do I downgrade? The previous build, 9.1.9, worked fine.

Did you check the setting "Always tune channel"? Maybe this setting was changed to No?

[JeffHaas]

That was the first thing I checked...it was still set to "Yes."

[JeffHaas]

Fixed it!

Steps:
Download and install all current Hauppage drivers:
- Colossus 2 driver
- Hauppage capture
- Win TV 8.5 (remember to have your serial number from the CD!)
Reboot as requested.

Once all the drivers are installed, un-install Sage TV.
NOTE: All your settings and configs will be left alone!

Then reboot and re-install Sage TV. This sets up the connection to the new Hauppage drivers.

At that point everything was back to normal.

[JeffHaas]

Update on this...9.2.1 32-bit version did not keep the association with the Hauppage IR blaster software. After going to sleep and waking itself up, it would not change channels correctly. The software would think it changed the channel, but never actually changed to it, so it recorded the wrong thing.

I downgraded to 9.1.9 and everything is working again.

[tvmaster2]

Originally Posted by JeffHaas

Update on this...9.2.1 32-bit version did not keep the association with the Hauppage IR blaster software. After going to sleep and waking itself up, it would not change channels correctly. The software would think it changed the channel, but never actually changed to it, so it recorded the wrong thing.

I downgraded to 9.1.9 and everything is working again.

So you’d recommend NOT upgrading to 9.2.1 then?

[JeffHaas]

In my case, using the Hauppauge Colossus 2 with the IR blaster, version 9.2.1, 32-bit build, is NOT recommended. There seems to be a bug with the connection to the IR blaster software that gets lost when the PC sleeps. (This is just a guess, I haven't tested extensively.)

[JustFred]

Originally Posted by JeffHaas

In my case, using the Hauppauge Colossus 2 with the IR blaster, version 9.2.1, 32-bit build, is NOT recommended. There seems to be a bug with the connection to the IR blaster software that gets lost when the PC sleeps. (This is just a guess, I haven't tested extensively.)

Your issues with the IR blaster aren't the fault of Sage. Blame Hauppauge. Whenever there are multiple Hauppauge capture devices that are IR-capable, the Hauppauge software has it's own idea of which ONE of those devices it will present to other programs (e.g, Sage) for IR control. I can't remember if it's the very FIRST installed driver or the LAST installed driver that gets presented to Sage. Search the Sage forums for more info; this is nothing new. It's also one reason why lots of folks prefer USB-UIRT.

In your case, reinstalling the Hauppauge drivers has resulted in the "other" IR device being the one that's now controlled by Sage. You can easily prove this by plugging your IR blaster into the "other" Hauppauge device. Then, in Sage, go to Setup -> Setup Video Sources -> select one of the IR-capable Hauppauge capture devices. On the Source Details screen, Select "Tuner Control", then "Test Infrared Code". From here, you can manually send IR commands. If you find that Hauppauge device isn't working, reconnect the IR blaster to one of the other Hauppauge capture devices, and Test Infrared Code again.

[JeffHaas]

I guess I don't understand - I only have one Hauppage device installed, the Colossus 2. Does one card get represented as more than one device?

[JustFred]

I misunderstood. Your earlier post said "Hauppauge Capture" and I took that to mean you loaded the drivers for an HD-PVR, too.

You can still test with Test Infrared Code after Sage wakes up. Is anything interesting being logged in sagetv_0.txt log file when you try to use the IR blaster?

After waking, is Hauppauge's BlastCfg utility able to send IR codes?

Sage 9.2.1 had to make a change with the way Sage talks to the Hauppauge IR code. Maybe something subtle happens after wakeup. wnjj worked on that code and might have some insight.

[JeffHaas]

I see. I installed Hauppage Capture because occasionally I use that utility to digitize something off an old VHS.

To test all this stuff I'd have to uninstall the build and reinstall the current one. Not sure I can get to that soon.

[wnjj]

Originally Posted by JustFred

I misunderstood. Your earlier post said "Hauppauge Capture" and I took that to mean you loaded the drivers for an HD-PVR, too.

You can still test with Test Infrared Code after Sage wakes up. Is anything interesting being logged in sagetv_0.txt log file when you try to use the IR blaster?

After waking, is Hauppauge's BlastCfg utility able to send IR codes?

Sage 9.2.1 had to make a change with the way Sage talks to the Hauppauge IR code. Maybe something subtle happens after wakeup. wnjj worked on that code and might have some insight.

The 64-bit version of SageTV has to use a COM driver shim to talk to the 32-bit Hauppauge driver since that’s all we have. The 32-bit one should work the same way it always has. I’m not sure if we used to compile the 32-bit HCWIRBlaster.dll or just included the one from V7. You should be able to use the V7 one in place of the current one.

[JeffHaas]

A bit of clarification...does this mean I can save a file from 32-bit version 9.1.9, install 9.2.1, and then copy the file from the older version to the new install?

Remember, I'm still running Win 7 in 32 bit mode on a now-old HTPC. I'm kinda reluctant to upgrade it to Win 10 due to all the updates, I'd rather it was just an appliance.

[wnjj]

Originally Posted by JeffHaas

A bit of clarification...does this mean I can save a file from 32-bit version 9.1.9, install 9.2.1, and then copy the file from the older version to the new install?

Remember, I'm still running Win 7 in 32 bit mode on a now-old HTPC. I'm kinda reluctant to upgrade it to Win 10 due to all the updates, I'd rather it was just an appliance.

Yes the 32-bit binaries could be copied in. Usually the sage.jar file is where most changes happen in the 32-bit version from rev to rev (with a couple exceptions). Starting with V9.2, some source code was freshly compiled out of necessity to build 64-bit and as a result the 32-bit version now compiled them. The binaries that were built were previously just copied into the 32-bit version from V7. The newly compiled stuff used slightly different source and/or compile methods so could introduce differences. For example the fonts were a little off unless you cleared the cache.

[JeffHaas]

OK, can you give me the list of the binaries?

[wnjj]

Originally Posted by JeffHaas

OK, can you give me the list of the binaries?

I think the following is correct. I'm going by memory and some minor peeking at the code. The installer builder (jusjoken) will have to confirm what's still included in binary form.

SageTV/Common:

as_ir200l.dll (still being copied...not supported on 64-bit)
pthreadGC2.dll (previously needed by pushreader.dll)
pushreader.dll (being compiled as of V9.2.0)
uu_irsage.dll (being compiled as of V9.2.0)


SageTV/SageTV:

avcodec-51.dll (previously needed by pushreader.dll)
avformat-51.dll (previously needed by pushreader.dll)
avutil-49.dll (previously needed by pushreader.dll)
FreetypeFontJNI.dll (being compiled as of V9.2.0)
ImageLoader.dll (being compiled as of V9.1.7)
Mpeg2Transcoder.dll (being compiled as of V9.2.0)
pthreadGC2.dll (previously needed by ImageLoader.dll)
swscale.dll (previously needed by ImageLoader.dll)